From: zzapper <zsh@rayninfo.co.uk>
To: zsh-users@zsh.org
Subject: Re: Alias help
Date: Tue, 27 Apr 2021 08:10:54 +0100 [thread overview]
Message-ID: <dbb8e11e-030b-3a07-be5e-cde5fc8ac844@rayninfo.co.uk> (raw)
In-Reply-To: <a08205a9-64fc-56a2-c06c-5a1914f1c8ff@gmx.com>
On 27/04/2021 00:15, Eric Cook wrote:
> On 4/26/21 6:55 PM, Hoji, Aki wrote:
>> alias pu ="pip3 list -o | sed "1,2 d" |cut -d ' ' -f1 | xargs -n1
>> pip3 install -U”
>
> As a shell function:
> pu() { ~
> pip3 list -o |
> sed "1,2 d" |
> cut -d ' ' -f1 |
> xargs -n1 pip3 install -U
> }
>
> While not to the degree of say python, whitespace matters often in shell;
> You have an extra space after the name of the alias pu, so the =word
> triggered a different
> feature of zsh that expands the path to a command. in this case "pip3
> list -o | sed 1,2"
> once you remove the space you still have the problem of not quoting
> correctly.
>
> alias pu='pip3 list -o | sed "1,2 d" |cut -d '\'' '\'' -f1 | xargs -n1
> pip3 install -U'
>
> Is how to quote that command properly, which is less readable than a
> function is in my opinion.
>
thanks for this explanation Eric (I've been having my own battles with
shell white space recently)
When you are desperate to get something working not noticing a little
thing like the extra space in >>>>alias pu ="pip3<<<
Pity we don't have an online script tester for zsh (many for bash)
I prefer an Alias to a Function where possible because it's easy to tab
expand an alias and then if required tweak it
next prev parent reply other threads:[~2021-04-27 7:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 22:55 Hoji, Aki
2021-04-26 23:15 ` Eric Cook
2021-04-27 7:10 ` zzapper [this message]
2021-04-27 20:41 ` Bart Schaefer
2021-04-29 13:30 ` Daniel Shahaf
2021-04-29 13:55 ` zzapper
2021-04-29 14:13 ` Daniel Shahaf
2021-04-27 13:06 ` Akihiko Hohji
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=dbb8e11e-030b-3a07-be5e-cde5fc8ac844@rayninfo.co.uk \
--to=zsh@rayninfo.co.uk \
--cc=zsh-users@zsh.org \
/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).