From: Mikael Magnusson <mikachu@gmail.com>
To: Hans Meine <hans_meine@gmx.net>
Cc: zsh workers <zsh-workers@zsh.org>
Subject: Re: Bug in 'histreduceblanks' w.r.t. multi-line commands
Date: Fri, 9 Jan 2015 03:47:39 +0100 [thread overview]
Message-ID: <CAHYJk3SC3ZEtxRSMPLjZkc0Gd_Wg-Ju9S6+WJDkv5u5eg0yXXw@mail.gmail.com> (raw)
In-Reply-To: <0267E518-E25F-4D97-9D2D-66A0603A6C28@gmx.net>
On Thu, Jan 8, 2015 at 11:31 AM, Hans Meine <hans_meine@gmx.net> wrote:
> Hi,
>
> with the histreduceblanks option enabled, I suffered from the problem that multi-line commands like the following were mangled in the history:
>
> cd ~/Developer && \
> svn up --accept postpone -r190973 MeVisLab MeVis/Foundation && \
> svn up --accept postpone -r197619 FMEwork FMEstable
>
> The command appears in history totally broken, with missing and duplicate/substituted parts as follows:
>
> cd ~/Developer && n n up -cceptpt ptponene -9097373 MisLabab Mis/Foundationon && svn up -eptcept ponepone -6197619 ork ork FMbltable
>
> Interestingly, when trying to simplify this example, I noticed that the following works:
>
> cd foo && \
> ls && \
> echo bar
>
> I did create a new user for testing and could verify that this is not caused by a conflict with any of the other options that I enabled; even with the default config (or no_zle etc.), the problem starts to appear as soon as I enable histreduceblanks.
What version of zsh are you using? A bug like this was fixed quite recently.
--
Mikael Magnusson
prev parent reply other threads:[~2015-01-09 2:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 10:31 Hans Meine
2015-01-09 2:47 ` Mikael Magnusson [this message]
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=CAHYJk3SC3ZEtxRSMPLjZkc0Gd_Wg-Ju9S6+WJDkv5u5eg0yXXw@mail.gmail.com \
--to=mikachu@gmail.com \
--cc=hans_meine@gmx.net \
--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).