i keep encountering an error message when i attempt to use find. the 
following transcript describes the result of my attempts to type "find 
/opt/local/ -name":

[beginning of transcript]

[EMAIL PROTECTED] ~/L/A/LyX-1.4> find /opt/local/ -complete: Too many 
arguments
/opt/local/share/fish/completions/find.fish (line 79): complete -c find 
-o xtype -d (N_ "Check type of file - in case of symlink, check the file 
that is not checked by -type") -x $type_comp
                                                       ^
in . (source) call of file  /opt/local/share/fish/completions/find.fish ,
        called on standard input,

in command substitution
        called on standard input,

/opt/local/share/fish/completions/find.fish (line 79): complete -c find 
-o xtype -d (N_ "Check type of file - in case of symlink, check the file 
that is not checked by -type") -x $type_comp
                                                       ^
in . (source) call of file  /opt/local/share/fish/completions/find.fish ,
        called on standard input,

in command substitution
        called on standard input,


       complete   edit command specific tab completions.


   Synopsis
       complete ( c|  command| p|  path) COMMAND [( s|  short option)
       SHORT_OPTION] [( l|  long option| o|  old option) LONG_OPTION
...
       buffer for the presence of a specified set of options.

[EMAIL PROTECTED] ~/L/A/LyX-1.4> find /opt/local/ -n

[end of transcript]

also, is there a way to disable the documentation dump when an error 
occurs? or perhaps an option to simply provide me with the proper help 
command line to bring up the relevant documentation. the volume of 
output is disorienting.

a separate issue that's indirectly related to find has to do with a 
common error i keep repeating. i type the following command, for example:

find /opt/local/ -name *.sty -print

i seem to remember getting away with this at least some of the time in 
bash, so fish must be more strict about escaping globbing syntax when 
appropriate than other shells. i prefer the way fish wants it but i 
still carry the habits of my old shell. after failing on my first 
attempt. i use the up arrow to recall the last command and editing the 
flawed statement. i only add the backslash and press return, expecting 
the following to execute:

find /opt/local/ -name *.sty -print

but instead, i get the following result without the command having been 
executed:

find /opt/local/ -name \
*.sty -print

i hope this information is useful. thanks!

/mike


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Fish-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fish-users

Reply via email to