| S. Fabian:
|| A function @DIRHISTORY (similar to @DIRSTACK) might be useful.
|| It would be useful to be able to examine the current attributes of
|| the HISTORY and DIRHISTORY tables (order, duplicates, etc.).
| Features that "might be useful" get put at the bottom (the very,
| very bottom) of the suggestion list. If you actually have a use
| (and an example) for it, it'll get bumped up.
| I have no idea what you want for the "current attributes" of the
| history lists. (IMO that is definitely a job either for a custom
| filter or a plugin..)
Dynamic information: current size, free space, entry count; the choices
made in the OPTION dialog: in the "Command History" section of the Command
Line page for (command) HISTORY, and their equivalents for DIRHISTORY.
Since HELP no longer includes the names of the directives set by OPTION,
users without access to the V8 help file cannot programmatically obtain
these settings. Using the OPTION dialog is not possible in batch files
imported from other users.
|| I am too lazy to search HELP. Please verify my understanding that
}} PRE_EXEC and POST_EXEC are never executed for the right side of a pipe.
| The PRE_INPUT, PRE_EXEC, and POST_EXEC behavior is documented in the
| help for ALIAS.
What may be implied but not explicitly stated in alias.htm is that
PRE_EXEC is performed before any pipes required by the new command line are
opened, and POST_EXEC is performed after such pipes, if any, have already
been closed. Obviously, at least now after I reread that section, PRE_INPUT
would need to be an oracle to know about pipes in a command not yet entered.
Nest year? Next century?