From: Bart Schaefer <schaefer@brasslantern.com>
To: Raghavendra Prabhu <raghu.prabhu13@gmail.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: Issue with histreduceblanks
Date: Thu, 26 Sep 2013 10:12:54 -0700 [thread overview]
Message-ID: <130926101254.ZM23201@torch.brasslantern.com> (raw)
In-Reply-To: <CAEtq3tNjNumBv2BZMS0FXUL9-pRWDtGZJ1pZ1NKPw3rxtOFunA@mail.gmail.com>
On Sep 26, 12:52am, Raghavendra Prabhu wrote:
}
} On Thu, Sep 19, 2013 at 1:42 AM, Peter Stephenson
} <p.w.stephenson@ntlworld.com> wrote:
} >
} > Are there any non-ASCII characters on the line that might be confusing
} > the algorithm (the option pre-dates handling of multibyte characters)?
}
} Sorry for the delay in replying (it had ended in my Junk due to
} Precedence headers).
You didn't really answer Peter's question. Also I think something is
being lost in the cut-and-paste-and-email process, because this ...
} Archie% Only two kinds of witnesses exist. The first live in a
} neighborhood where
} zsh: command not found: Only
... obviously has a newline where there must not have been one in your
original string. To have much hope of debugging this, we need a copy
of EXACTLY what you typed, including what might be characters that
"look like" spaces but really are not.
} b) Also tested with print as requested
Did you see/try this?
> If that were the case, I would expect history ops that reference words by
> position would also be confused. E.g., something like
>
> zsh% print Only two kinds of witnesses exist. The first live in a neighborhood where !#:7 !#:8 !#:9
>
> would likely substitute the wrong substrings for !#:7 etc., because the
> same array of word positions is used to condense blanks.
next prev parent reply other threads:[~2013-09-26 17:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 18:50 Raghavendra D Prabhu
2013-09-18 20:12 ` Peter Stephenson
2013-09-18 21:32 ` Bart Schaefer
2013-09-25 19:22 ` Raghavendra Prabhu
2013-09-26 17:12 ` Bart Schaefer [this message]
2013-09-26 17:47 ` Raghavendra Prabhu
2013-09-26 21:03 ` 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=130926101254.ZM23201@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=raghu.prabhu13@gmail.com \
--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).