From: Wayne Davison <wayne@clari.net>
To: Sweth Chandramouli <sweth@astaroth.nit.gwu.edu>
Cc: ZSH Users <zsh-users@sunsite.auc.dk>
Subject: Re: making sudo work with functions/builtins
Date: Tue, 16 Feb 1999 14:41:41 -0800 [thread overview]
Message-ID: <199902162241.OAA11943@bebop.clari.net> (raw)
In-Reply-To: sweth's message of Mon, 15 Feb 1999 19:15:09 -0500. <19990215191509.A28737@astaroth.nit.gwu.edu>
Sweth Chandramouli writes:
> i just had a little brainstorm about how to get around this:
>
> % alias mv='nocorrect mv'
> % ls
> cmd foo
> % alias sudo='sudo cmd '
> % cat cmd
> #!/bin/sh
> eval $SHELL -c \"$@\"
> % sudo mv foo bar
> % ls
> bar cmd
> %
While this cures the error of sudo trying to run "nocorrect", it
does not propagate the "nocorrect" forward soon enough to turn off
spelling corrections on the command. This delayed application is
more of a problem with a command that has the "noglob" modifier:
% alias e='noglob echo'
% e f*
f*
% sudo e f*
foo
I know of no way around this problem.
Note that your solution also some quoting problems:
% sudo echo 'f*'
foo
% sudo echo 'one two' 'three four'
one two three four
% touch 'one two'
% sudo cat 'one two'
cat: cannot open one
cat: cannot open two
One way to fix these is by changing your "cmd" shell script to be:
#!/local/bin/zsh
noglob $@
The way I worked around the sudo problem was to use the following
alias and function. In addition to avoiding the errors, it also
allows me to type just "sudo" to get the effect of "sudo zsh":
alias sudo='my_sudo '
function my_sudo {
while [[ $# > 0 ]]; do
case "$1" in
command) shift ; break ;;
nocorrect|noglob) shift ;;
*) break ;;
esac
done
if [[ $# = 0 ]]; then
command sudo zsh
else
noglob command sudo $@
fi
}
It doesn't allow me to run any shell builtins or functions, though.
..wayne..
next prev parent reply other threads:[~1999-02-16 22:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-16 0:15 Sweth Chandramouli
1999-02-16 22:41 ` Wayne Davison [this message]
1999-02-17 5:30 ` Bart Schaefer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199902162241.OAA11943@bebop.clari.net \
--to=wayne@clari.net \
--cc=sweth@astaroth.nit.gwu.edu \
--cc=zsh-users@sunsite.auc.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).