From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Fwd: Editing the history in the shell
Date: Tue, 26 May 2020 20:32:29 -0700 [thread overview]
Message-ID: <CAH+w=7bXeQo8Uvz3fNpC3ruzFxKeDzO928VTGhJGH_24g+CxOg@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7bTCCC2XBr+_HCAPqXWuOV_YOrDv+36C6jJScKrxZjhLQ@mail.gmail.com>
On Sun, May 24, 2020 at 7:35 PM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
>
> Bart Schaefer wrote on Sat, 23 May 2020 14:30 -0700:
> > @@ -133,6 +140,28 @@ if ((fun)) then
> > + for (( hist=1; hist <= savehist; hist++ )) print -rs -- "$var[hist]"
>
> This generates a syntax error when SHORT_LOOPS is unset.
I think zed has a long-standing problem with SH_WORD_SPLIT and
probably some other SH_ options?
% setopt shwordsplit
% zed "/tmp/one two"
Where does this go?
% cat "/tmp/one two"
cat: '/tmp/one two': No such file or directory
% cat /tmp/one
Where does this go?
%
So ... how far do we go to make "zed" compatible with nonstandard
options, and how do we approach doing it? Try to use entirely
portable syntax, or invoke "emulate -L", or something in between?
Look at the handling of function names, too -- it creates the empty
function definition with ${(q-)1} but makes no attempt to quote $1
when calling "functions" or "autoload".
next prev parent reply other threads:[~2020-05-27 3:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 22:24 Bart Schaefer
2020-05-23 2:28 ` Daniel Shahaf
2020-05-23 21:30 ` Bart Schaefer
2020-05-24 22:02 ` _arguments optspecs (was Re: Editing the history in the shell) Bart Schaefer
2020-05-25 17:29 ` Oliver Kiddle
2020-05-25 22:32 ` Bart Schaefer
2020-05-26 7:56 ` Oliver Kiddle
2020-05-25 22:42 ` Bart Schaefer
[not found] ` <20200525023515.7855610a@tarpaulin.shahaf.local2>
[not found] ` <CAH+w=7bTCCC2XBr+_HCAPqXWuOV_YOrDv+36C6jJScKrxZjhLQ@mail.gmail.com>
2020-05-27 3:32 ` Bart Schaefer [this message]
2021-04-25 21:56 ` [PATCH] Re: Editing the history in the shell Bart Schaefer
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='CAH+w=7bXeQo8Uvz3fNpC3ruzFxKeDzO928VTGhJGH_24g+CxOg@mail.gmail.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).