Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: prexec never gets empty string?
- X-seq: zsh-workers 34539
- From: Mikael Magnusson <mikachu@xxxxxxxxx>
- To: Derek Gleim <mail@xxxxxxxxxxx>
- Subject: Re: prexec never gets empty string?
- Date: Sat, 14 Feb 2015 00:04:54 +0100
- Cc: zsh workers <zsh-workers@xxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=WB0RqTnvSPnyBAyLJHrapEVb0GTH0REuH00QzTwwYHg=; b=BxoYGxAxkB8r7vytWbfmMTYwZz1cjZYhTeS8QqHdSSd9ECFBLcJgLkYmAjyCUXMC3m NETrGRDww6Pkw7K552Lc10TpbNdbSmq5S4LpLkteZPAMdJH95MSuA8Io15FSta82UZZM ATV1euFrtCem6P7Bi9zAkH6ClFlyBtqF6C/zmD8/VOypEV8G9jDGVeoTMboKbAGE2OuD huuHqUgeLT+Q3JtHDZidfU3eAmLgi1KdSJ4sF2gWfcH5O8i8dmGfCHwOmCZtttTigUdH hNS0jXe/uVUxDd8veco69dALg2QGtejMgI542nQ/5n7SuKku/TTIFOHNngALlwYPEdSU jTkw==
- In-reply-to: <CANOe-=7ti2p7uUAAtD309i1BkfmUwPtK+3K0eunJJkmkEJnpGQ@mail.gmail.com>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <CADS3xe8na+zBiEMT1qp+pjLXtDxzvRmC7QVjCt5VXSUu_1jbmA@mail.gmail.com> <CAHYJk3RKv8bZUy-DS3-QWZ6ykRRZejrF0Wwpwa=wdA1-1HCNZw@mail.gmail.com> <CANOe-=7ti2p7uUAAtD309i1BkfmUwPtK+3K0eunJJkmkEJnpGQ@mail.gmail.com>
On Fri, Feb 13, 2015 at 11:41 PM, Derek Gleim <mail@xxxxxxxxxxx> 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
Messages sorted by:
Reverse Date,
Date,
Thread,
Author