From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-users@zsh.org
Subject: Re: alias with a parameter
Date: Wed, 7 Apr 2021 13:58:08 +0100 (BST) [thread overview]
Message-ID: <1077600344.1098154.1617800288527@mail2.virginmedia.com> (raw)
In-Reply-To: <EBD2CC2F-AD38-4E65-AFFA-FDC03265DF09@covisp.net>
> On 07 April 2021 at 13:48 lb@covisp.net wrote:
>
> On 07 Apr 2021, at 01:05, Stephane Chazelas <stephane@chazelas.org> wrote:
> > 2021-04-05 20:47:47 -0600, Grant Taylor:
> > [...]
> >> pd() {
> >> [ -n "${1}" ] && pushd "${1}" || popd;
> >> }
>
> > That function would run popd when pushd fails. It's generally a
> > bad idea to use this kind of a && b || c in place of proper
> > if/then/else constructs.
>
> Bad idea, or just a style "this is proper practice" sort of thing?
>
> I can't imagine any 'bad idea' from this, as it is doing the same basic thing.
Stephane is pointing out that what you want is:
if [[ -n $1 ]]; then
pushd "$1"
else
popd
fi
but what you've got is (writing out in full for clarity):
if [[ -n $1 ]]; then
if ! pushd "$1"; then
popd
fi
else
popd
fi
because of the slightly obscure but nonetheless well-defined way && and || work.
pws
next prev parent reply other threads:[~2021-04-07 12:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 22:55 dukeofpurl
2021-04-06 0:16 ` lb
2021-04-06 3:40 ` Duke Normandin
2021-04-06 14:42 ` Greg Klanderman
2021-04-06 2:47 ` Grant Taylor
2021-04-07 7:05 ` Stephane Chazelas
2021-04-07 12:48 ` lb
2021-04-07 12:58 ` Peter Stephenson [this message]
2021-04-08 1:06 ` Grant Taylor
2021-04-08 1:25 ` Daniel Shahaf
2021-04-09 2:55 ` Grant Taylor
2021-04-09 22:49 ` Daniel Shahaf
2021-04-10 7:32 ` david rayner
2021-04-10 10:38 ` Marc Chantreux
2021-04-14 11:10 ` zzapper
2021-04-15 18:19 ` Bart Schaefer
2021-04-15 19:56 ` (prefix case terminators?) " Marc Chantreux
2021-04-15 23:52 ` Bart Schaefer
2021-04-16 6:46 ` Marc Chantreux
2021-04-15 20:30 ` Daniel Shahaf
2021-04-16 7:34 ` zapper
2021-04-16 10:12 ` Stephane Chazelas
2021-04-10 16:30 ` Grant Taylor
2021-04-10 16:34 ` Grant Taylor
2021-04-13 11:22 ` Daniel Shahaf
2021-04-07 14:43 ` Daniel Shahaf
2021-04-07 14:54 Duke Normandin
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=1077600344.1098154.1617800288527@mail2.virginmedia.com \
--to=p.w.stephenson@ntlworld.com \
--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).