Custom Query (76 matches)

Many operations to get user input are done via status line in VIO eFTE2 but little PM dialogs are brought up for these things in the PM version:

File Open (or Load Desktop, etc.) or File Save (as, write to, etc.), Set Dir, Rename file, Confirm deleting file, Line transform, Find/FindReplace?, Create Folds at RegExp?, Confirm compile command line, grep, Left/Right? Margin, TabSize?, Print to, About dialog (and maybe some I overlooked).

If I press F1 on any of the dialogs above, eFTE2 PM traps here, whereas VIO eFTE2 just ignores it (I don't know if it's supposed to bring up help).

Also, Help -> Contents does nothing, while VIO eFTE2 correctly opens eFTE2.HLP with newview.

eFTE path included in path, help and dpath via SET in an OS/2 prompt prior to running. Plain vanilla MCP2 system +XWP, no eStyler, FoC enhancers or the like.

I don't know if what gets in popuplog.os2 is useful or just garbage, I am attaching it just in case: (First line sure keeps changing, but only SS:ESP and EBP lines do change after that)

`------------------------------------------------------ 10-08-2017 12:47:28 SYS3175 PID 0151 TID 0001 Slot 00b1 D:\UTIL\EFTE\EFTEPM.EXE c0000005 1df21bb0 P1=00000001 P2=1df21bb0 P3=XXXXXXXX P4=XXXXXXXX EAX=1c77fffe EBX=1c772a84 ECX=00000000 EDX=1df21bb0 ESI=00000000 EDI=1c77cb3c DS=0053 DSACC=f0f3 DSLIM=ffffffff ES=0053 ESACC=f0f3 ESLIM=ffffffff FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC= GSLIM= SS:ESP=0053:0053ea94 SSACC=f0f3 SSLIM=ffffffff EBP=0053eb18 FLG=00012246

Background: in most languages, accented/combined/composite characters are typed in by pressing a sequence of two keys: a "dead" key for the diacritic, followed by a "normal" key for the base character, f.e. I should press ´ + a to get á.

This works as expected in VIO eFTE2, but in PM eFTE2 two characters are produced: "´á", "¨ö", etc. (I kind of understand this, because getting keyboard input is totally different in PM and VIO.)

FTEPM/2006 has the same problem.

I suspect PM actually produces two characters for these combinations, somehow marking the first one for replacement, and it is up to the application to handle it: both system E and Aaron Lawrence's AE show the diacritic character *after* the cursor when a dead key is pressed, and when a normal key is pressed, the accent character is replaced and the cursor position is moved after the combined character as normal.

Example: I press "dead" "^" and I see "^", then I press "A", and "^" is replaced with "Â" and cursor is moved.

EPM does not ever show the accent character nor moves the cursor, it only shows the final combined character after the normal key is pressed.

Regular expression anchoring for beginning of line fails, apparently since 2008.

Finding "^$" as a regular expression should match empty lines (it does in FTE/2006) but in eFTE2 (also FTE/2008) it fails and instead matches lines that are 1-character long.

Also, "^." should match the first character of every non-empty line, but matches the second one instead.