Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'What's the touch for?' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
What's the touch for?
Authored by: porkchop_d_clown on Jun 12, '02 11:43:21AM

I haven't tried this; I don't use pine - but why do you need the touch? Is it creating the file $1? Wouldn't bbedit do that for you if you gave it the name of a file that doesn't exist?
Also, you referenced an old hint for modifying your .cshrc. OS X users really shouldn't do that - it's a clunky 30 year old technique that can be hard to maintain.
Instead, use Apple's own supplied methods for extending the shell through scripts in your ~/Library/init/tcsh folder. I documented a tool for dynamically building aliases for all your .apps here. It's based on the older hint on ResExcellence, but supports multiple application directories.



[ Reply to This | # ]
Re: What's the touch for?
Authored by: Anonymous on Jun 12, '02 12:30:59PM

It is indeed necessary for the touch command to create the file first. Otherwise, the open command throws an error message out when it tries to have BBEdit Lite open the file and won't go any farther.



[ Reply to This | # ]
What's the touch for?
Authored by: nkuitse on Jun 16, '02 02:45:19PM
If you have the full BBEdit 6.5, set the environment variable EDITOR to bbedit -c -w. The -c switch creates the file if necessary, and the -w switch "allows the bbedit tool to be used as an external editor for Unix tools that use the EDITOR global environment variable" (from the manpage).

[ Reply to This | # ]