This feature is not used by FILELIST co, but by HELP. You can see the
difference in XEDIT's status area: in HELP you can observe MACRO READ, not
the case for FILELIST.
FILELIST's command execution is based on this
SET ENTER IGNORE MACRO EXECUTE
Meaning that when you press enter and the XEDIT
Thanks Kris. That refreshes my memory! Since THE can't do any of those things,
I've taken a different approach.
Les
Kris Buelens wrote:
This feature is not used by FILELIST co, but by HELP. You can see the
difference in XEDIT's status area: in HELP you can observe MACRO READ, not
the case
It's all documented. Issue HELP XEDIT READ.
Thanks Alan, but I'm retired and don't have a VM system to play with. My sandbox
is now the THE editor on a W7 laptop.
Les
Alan Winson wrote:
It's all documented. Issue HELP XEDIT READ.
Alan Winson wrote:
It's all documented. Issue HELP XEDIT READ.
Indeed. The brain cells are fading fast now!
I think what's not documented is that CTLCHARs in the file being XEDITed are
interpreted on READ NOCHANGE TAG. So you can create template files sort of like
DMS and use those for
That sure sounds familiar! The pdf manual that I downloaded has this note about
READ:
Using CTLCHARs in non-RESERVED lines with READ NOCHANGE, may
cause unpredictable results.
However, as has been pointed out earlier, what we both remember is, in fact, a
dependent behavior of some system
Do I recall correctly that in order to use an unprotected field in a reserved
line, the macro has to issue a READ ALL so that Xedit will honor the control
characters?
I've been playing with trying to do something like that with THE on my pc and
just wanted to refresh my memory about that
On Fri, Aug 6, 2010 at 5:50 PM, Les Koehler vmr...@tampabay.rr.com wrote:
Do I recall correctly that in order to use an unprotected field in a reserved
line, the macro has to issue a READ ALL so that Xedit will honor the control
characters?
I've been playing with trying to do something like
