zsh-workers
 help / color / mirror / code / Atom feed
From: Mikael Magnusson <mikachu@gmail.com>
To: Derek Gleim <mail@dcgleim.com>
Cc: zsh workers <zsh-workers@zsh.org>
Subject: Re: prexec never gets empty string?
Date: Sat, 14 Feb 2015 00:04:54 +0100	[thread overview]
Message-ID: <CAHYJk3RLr7PO6ARW5Xn-GBXvvs_UYXpBJ9C4Y5vFFyXxWrtDyg@mail.gmail.com> (raw)
In-Reply-To: <CANOe-=7ti2p7uUAAtD309i1BkfmUwPtK+3K0eunJJkmkEJnpGQ@mail.gmail.com>

On Fri, Feb 13, 2015 at 11:41 PM, Derek Gleim <mail@dcgleim.com> wrote:
>> I certainly would never want preexec to be disabled just because a
> line isn't stored in history.
>
> I don't follow.  Me neither.  My understanding is if the line isn't going to
> be stored, preexec is still called, but it is supposed to be given an empty
> string as the first argument when the command will be ignored by history
> (while the second and third arguments give you the command regardless). No?

Judging by http://www.zsh.org/mla/workers/2001/msg00605.html , the
empty string was never intended as a feature, just a workaround for
not having access to the string. I guess a subsequent change made the
string always be available. Possibly the feature that always keeps the
last command in history until you run another command is newer than
this change and is why it always works now.

-- 
Mikael Magnusson


  reply	other threads:[~2015-02-13 23:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-13 17:19 Derek Gleim
2015-02-13 17:35 ` Peter Stephenson
2015-02-13 19:27   ` Derek Gleim
2015-02-13 20:19   ` Peter Stephenson
2015-02-13 22:16 ` Mikael Magnusson
2015-02-13 22:41   ` Derek Gleim
2015-02-13 23:04     ` Mikael Magnusson [this message]
2015-02-13 23:14       ` Mikael Magnusson
2015-02-14 21:37     ` Peter Stephenson
2015-02-16 15:11       ` Derek Gleim
2015-02-16 15:16         ` Derek Gleim
2015-02-16 15:59         ` Peter Stephenson
2015-02-17 17:09         ` 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=CAHYJk3RLr7PO6ARW5Xn-GBXvvs_UYXpBJ9C4Y5vFFyXxWrtDyg@mail.gmail.com \
    --to=mikachu@gmail.com \
    --cc=mail@dcgleim.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).