The one on PickWiki (http://www.pickwiki.com/cgi-bin/wiki.pl?TclStack) is mine, and attempts to be somewhat "bash compatible" with ^A, ^E, ^D doing the usual things. It is (unfortunately) vt100 centric, with a small nod at wy50. I've had plans forever to add tab-expansion of file names but y'all know how that goes. We have restricted access to TCL where I work and only allow access through the stack program. We produce weekly audit reports showing what commands were run, in which accounts, by whom.
One of the selling points is a lot of short cuts for the programmer - the dot commands are for anyone using the stack, but slash commands are for the programmer to compile, catalog, run, checkin, diff, edit etc. Think I got that idea from some ancient "programmer's workbench" on Ultimate back in the 80's. Gosh, I'm old. The workflow is something like: ACCOUNT>/N4 Program Name: BP.DEV STACK (svn stuff happens, tells me if the local copy differs, offers to do svn update etc.) ACCOUNT>/E4 (edits the program in AE, command line editor still useful for lots of things ;-) ACCOUNT>/W4 (BP.DEV STACK opens in $VISUAL, in my case /usr/local/bin/joe) ACCOUNT>/BR4 (compiles, catalogs and runs BP.DEV STACK, making sensible choices about LOCAL, GLOBAL or DIRECT catalog) ACCOUNT>/CI4 (checks the program back in to svn, asks for comments etc.) I usually have 10-20 programs in my stack at any one time, and get used to "this week #4 is TRIN.MAIL.SUB". It saves a tremendous amount of typing. Rolling your own stack is an interesting rite of passage, and worth doing. Ian -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Bill Haskett Sent: Monday, June 13, 2011 7:14 PM To: U2 Users List Subject: Re: [U2] Unidata command stack (history) 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]<mailto:[email protected]> *To:* [email protected]<mailto:[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]<mailto:[email protected]> http://listserver.u2ug.org/mailman/listinfo/u2-users ----------------------------------------- IMPORTANT NOTICE: This message is intended only for the addressee and may contain confidential, privileged information. If you are not the intended recipient, you may not use, copy or disclose any information contained in the message. If you have received this message in error, please notify the sender by reply e-mail and delete the message. _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
