If you think U2's stack is bad, take a look at D3's. The pits! I've used
my own stacker for so many years, I can't stand to use others. One of
the nice things is that if I want a new capability, I just add it. I
have it set for 1000 lines right now, and usually keep 8 Jbase sessions
open. Each has its own stack, but can borrow from the others as needed.
Charlie Noah
Charles W. Noah Associates
[email protected]
View Charlie Noah's profile on LinkedIn
<http://www.linkedin.com/in/charlienoah>
The views and opinions expressed herein are my own (Charlie Noah) and do
not necessarily reflect the views, positions or policies of any of my
former, current or future employers, employees, clients, friends,
enemies or anyone else who might take exception to them.
On 06-13-2011 9:13 PM, Bill Haskett wrote:
Jeff:
The U2 command stack is completely neanderthal. I've been using UD
for awhile and have ignored the U2 stack completely. I run a
home-written shell. There's one on Pickwiki and I have one I'd be
glad to give you.
Here's some documentation on the U2 stack
The UniData command stack stores statements entered from the ECL
command line and allows you to recall, edit, reexecute, or save them.
If you make a typographical error in a command, the command stack
feature allows you to correct the error without having to retype the
entire statement.
By default, UniData stores up to 49 commands in the command stack. To
change the default, you can set the CSTACKSZ environment variable to
save a specified number of command lines. Each command line can
contain up to 2720 characters. See Administering UniData for
information about setting UniData environment variables.Note: If you
change the value of the CSTACKSZ environment variable on Windows
platforms, you must restart UniData for the change to take effect.
When you enter a statement on the ECL command line, UniData stores it
in position 1 of the stack. As you enter more commands, UniData pushes
prior commands in the stack up one position and inserts the current
command in position 1 of the stack. When a command moves beyond the
stack's limit, it is discarded.
The command stack for each user is saved in a file called
.ustk_logname in the directory of the current UniData account. Each
time you enter UniData, the stack is recalled.
HTH,
Bill
------------------------------------------------------------------------
----- Original Message -----
*From:* [email protected]
*To:* [email protected]
*Date:* 6/13/2011 5:50 PM
*Subject:* [U2] Unidata command stack (history)
Unidata 7.2.9 on linux
Is there a UDT.OPTION or other setting that can control the size of
the command stack (history)? We max out at 99 and I'd really like to
have it recall more - but cannot find an option to do this.
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users