Thread View: comp.sys.next.software
2 messages
2 total messages
Started by Scott Denning
Thu, 07 Jan 1993 18:29
named pipes in Edit
Author: Scott Denning
Date: Thu, 07 Jan 1993 18:29
Date: Thu, 07 Jan 1993 18:29
18 lines
1157 bytes
1157 bytes
Does anybody know how to save and name pipes and commands in the Utilities sub-menu in Edit? This is a great feature, but I have searched in vain for documentation in the User's Guide and online docs. A related question ... how do you set Edit to default to the C-shell instead of the Bourne shell when executing piped instructions? I need to provide a path for the pipe to search, and again, the documentation is no help. Thanks for replying via email or posting. I'll summarize if I get enough info. -- A. Scott Denning (303)491-8346 <scott@abyss.atmos.colostate.edu> Dept. of Atmospheric Science Colorado State University Fort Collins, CO 80523
Re: named pipes in Edit
Author: Alex Blakemore
Date: Fri, 08 Jan 1993 02:22
Date: Fri, 08 Jan 1993 02:22
21 lines
1091 bytes
1091 bytes
In article <Jan07.182928.22404@yuma.ACNS.ColoState.EDU> scott@abyss.ATMOS.ColoState.Edu (Scott Denning) writes: > Does anybody know how to save and name pipes and commands in the Utilities > sub-menu in Edit? edit ~/.commanddict ~/.pipedict and ~/.editdict for commands, pipes and the expansion dictionary. > how do you set Edit to default to the C-shell > instead of the Bourne shell when executing piped instructions? how about menu_entry csh script_name in .pipedict or putting #! /bin/csh at the top of your script -- --------------------------------------------------- Alex Blakemore alex@cs.umd.edu NeXT mail accepted
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads