zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: Alias named '='
Date: Mon, 9 Oct 2017 08:30:13 -0700	[thread overview]
Message-ID: <171009083013.ZM15279@torch.brasslantern.com> (raw)
In-Reply-To: <20171009162002.395c3c2b@pwslap01u.europe.root.pri>

On Oct 9,  4:20pm, Peter Stephenson wrote:
} Subject: Re: Alias named '='
}
} On Mon, 09 Oct 2017 15:04:47 +0000
} Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
} > Peter Stephenson wrote on Mon, 09 Oct 2017 15:49 +0100:
} > > Should we say something like this, or is it simply adding more words for
} > > people to say they can't be bothered to read it?
} > 
} > I think this section should describe the common, and
} > less-common-but-still-sane, use-cases before it discusses corner cases
} > such as aliasing "((", "&&", and "x=y".
} 
} So we could do something like this?

This doesn't describe what the question/discussion was about, does it?

torch% aliases[=]='echo equal'
torch% =
equal

The text you've written isn't wrong about assignment interpretation, but
it implies that the above would not work.  The problem with the above is
that the alias *builtin* can't deal with it, not that it's a problem in
command position.

Also I'm abivalent about moving the text about about the "((" token as
that is closely related to the dicussion about global aliasing of other
operator-like tokens.


  reply	other threads:[~2017-10-09 15:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6e3f43ea-45b0-d6a8-43b9-18845ea4edc9@necoro.eu>
     [not found] ` <m360bqt54h.fsf@luffy.cx>
     [not found]   ` <7d8ab2fa-3130-1e43-8807-f94025fd62ed@necoro.eu>
     [not found]     ` <CGME20171008183934epcas3p470fe7672a1689fa0e84d328d2ffaf2b1@epcas3p4.samsung.com>
     [not found]       ` <20171008183756.h45qeeqqbn2wthh3@tarpaulin.shahaf.local2>
2017-10-09 14:49         ` Peter Stephenson
2017-10-09 15:04           ` Daniel Shahaf
2017-10-09 15:20             ` Peter Stephenson
2017-10-09 15:30               ` Bart Schaefer [this message]
2017-10-09 15:35                 ` Daniel Shahaf
2017-10-10  9:02                   ` Peter Stephenson

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=171009083013.ZM15279@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@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).