On Tue, 20 Dec 2005, Netocrat wrote:
> I can't find a way to suppress the error message generated by an attempt
> to run an unknown command. Redirection of stderr or stdout has no
> effect, nor does it make a difference whether the situation is
> interactive or scripted. This is a pretty useful thing to be able to
> do, especially in scripts. Does fish have an existing mechanism that
> I'm missing?
There is no mechanism, other than redirecting the stderr of _fish
itself_ to /dev/null, which can only be done at startup.
Suggestions of a simple and discoverable general purpuse way of doinf
this is welcome.
Some possible methods:
* Allow the user to change the debug level at runtime
* Allow the user to redirect stderr at runtime
* Do some magic to attempt to skip redirect parse errors on commands
where stderr is redirected. This may be arbitrarily hard for
moderatly broken syntax.
>
> --
> http://members.dodo.com.au/~netocrat
>
--
Axel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Fish-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fish-users
