From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-workers@zsh.org
Subject: Re: Aliasing separators (Re: grammar triviality with '&&')
Date: Sat, 07 Mar 2015 09:18:55 -0800 [thread overview]
Message-ID: <54FB32FF.90908@eastlink.ca> (raw)
In-Reply-To: <20150307155252.75848f74@ntlworld.com>
On 03/07/2015 07:52 AM, Peter Stephenson wrote:
> If you did make that change, making "&&" a string rather than a token
> at the start of the line, then you could alias it willy-nilly. So I
> still don't really see it as relevant to the behaviour of tokens. I
> suspect I'm not explaining this point properly. pws
As for me, I didn't realize I'd be guilty of being a party to the
creation of an ouroboros.
Can it even be contemplated to make fundamental syntax aliasable? Can I
alias
a backtick? Can I alias the word alias? Not on this side of sanity. I
dunno, maybe
what you guys are contemplating makes sense, but it sure looks like the
time-traveler's
paradox to me. Allowing syntax to change it's own meaning? Is there
anywhere in this
universe where aliasing '&&' is useful, even if it didn't create
paradox? I myself am
happy with Bart's last explanation, it's robust, understandable,
necessary, fundamental.
[ -e file1 ]\
&& do-this
isn't hard to type. Pandora, meet Kurt Godel, meet Doctor Who.
Lawrence, forgive me ;-)
next prev parent reply other threads:[~2015-03-07 17:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54F33934.2070607@eastlink.ca>
[not found] ` <13666281425228233@web7o.yandex.ru>
[not found] ` <54F345D3.9010204@eastlink.ca>
[not found] ` <D0509295-7DA9-4F18-9E3D-D50C0A756998@larryv.me>
[not found] ` <20150302022754.GA7449@xvii.vinc17.org>
[not found] ` <CABx2=D8efL3X2tfB+_+VweY2yye6EhaMNbJa3b3jJeVMp=7gaQ@mail.gmail.com>
[not found] ` <20150302104619.GC6869@xvii.vinc17.org>
[not found] ` <20150302110610.2e2c7e86@pwslap01u.europe.root.pri>
[not found] ` <CAH+w=7YoHjN85hqOZVywOfYGZqvU74vZrbE84Ln+V2HQi-6nSA@mail.gmail.com>
[not found] ` <20150304144756.GA27231@ypig.lip.ens-lyon.fr>
2015-03-04 15:18 ` grammar triviality with '&&' Peter Stephenson
2015-03-04 21:13 ` Daniel Shahaf
2015-03-04 22:05 ` Mikael Magnusson
2015-03-05 9:46 ` Peter Stephenson
[not found] ` <150304175112.ZM19818@torch.brasslantern.com>
[not found] ` <20150305100638.55631238@pwslap01u.europe.root.pri>
2015-03-05 17:07 ` Aliasing separators (Re: grammar triviality with '&&') Bart Schaefer
2015-03-05 17:40 ` Peter Stephenson
2015-03-06 1:42 ` Bart Schaefer
2015-03-06 4:13 ` Mikael Magnusson
2015-03-06 16:43 ` Vincent Lefevre
2015-03-06 9:40 ` Peter Stephenson
2015-03-06 19:26 ` Bart Schaefer
2015-03-07 15:52 ` Peter Stephenson
2015-03-07 17:18 ` Ray Andrews [this message]
2015-03-07 21:10 ` Bart Schaefer
2015-03-09 11:46 ` Vincent Lefevre
2015-03-09 16:33 ` Peter Stephenson
2015-03-09 17:03 ` Bart Schaefer
2015-03-09 17:39 ` Peter Stephenson
2015-03-09 17:47 ` Ray Andrews
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=54FB32FF.90908@eastlink.ca \
--to=rayandrews@eastlink.ca \
--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).