From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: Disabling null elision (was: Re: Most Recent File)
Date: Mon, 25 Oct 2021 14:00:44 -0700 [thread overview]
Message-ID: <0b5401d6-3aae-8caa-ed95-75c0df625cb5@eastlink.ca> (raw)
In-Reply-To: <048e0b3d-6da9-4905-b1ad-253647cea0d3@www.fastmail.com>
On 2021-10-25 1:41 p.m., Daniel Shahaf wrote:
> Yeah. I assume that if we make this change, then once the
> incompatibility wave is past us (i.e., once everyone has made their code
> Y2k compliant, so to speak), the resulting language would be more
> intuitive — just like it's more intuitive with NO_SH_WORD_SPLIT than
> with sh's word splitting behaviour.
>
> Well, why not push an implementation to a branch? If you've got the
> tuits, of course.
But wouldn't such a thing be enabled via some option, so that nothing
changes unless you explicitly activate it? I have the same assumption
regarding my various bitches and complaints -- some option enables the
change so that nothing is different out of the box.
next prev parent reply other threads:[~2021-10-25 21:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-23 16:15 Most Recent File Vin Shelton
2021-10-23 16:43 ` Dominik Vogt
2021-10-23 16:58 ` Peter Stephenson
2021-10-23 17:24 ` Dominik Vogt
2021-10-23 17:32 ` Peter Stephenson
2021-10-23 18:39 ` Bart Schaefer
2021-10-23 19:07 ` Vin Shelton
2021-10-23 19:26 ` Bart Schaefer
2021-10-23 20:43 ` Vin Shelton
2021-10-23 20:56 ` Pier Paolo Grassi
2021-10-23 22:42 ` Bart Schaefer
2021-10-24 0:24 ` Pier Paolo Grassi
2021-10-24 0:32 ` Paul
2021-10-24 1:45 ` Dominik Vogt
2021-10-24 7:22 ` Roman Perepelitsa
2021-10-25 19:45 ` Disabling null elision (was: Re: Most Recent File) Daniel Shahaf
2021-10-25 20:02 ` Roman Perepelitsa
2021-10-25 20:41 ` Daniel Shahaf
2021-10-25 21:00 ` Ray Andrews [this message]
2021-10-25 21:09 ` Bart Schaefer
2021-10-25 21:05 ` Bart Schaefer
2021-10-25 21:20 ` Roman Perepelitsa
2021-10-25 20:05 ` Bart Schaefer
2021-10-24 1:37 ` Most Recent File Dominik Vogt
2021-10-23 16:47 ` david rayner
2021-10-23 16:54 ` Vin Shelton
2021-10-23 16:51 ` david rayner
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=0b5401d6-3aae-8caa-ed95-75c0df625cb5@eastlink.ca \
--to=rayandrews@eastlink.ca \
--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).