From: "Richard Hartmann" <richih.mailinglist@gmail.com>
To: "Bart Schaefer" <schaefer@brasslantern.com>
Cc: "Zsh hackers list" <zsh-workers@sunsite.dk>
Subject: Re: Strange parsing bug(?)
Date: Wed, 1 Oct 2008 09:36:20 +0200 [thread overview]
Message-ID: <2d460de70810010036g1e8b257bjb0265f4e0aada37f@mail.gmail.com> (raw)
In-Reply-To: <080930230614.ZM32707@torch.brasslantern.com>
On Wed, Oct 1, 2008 at 08:06, Bart Schaefer <schaefer@brasslantern.com> wrote:
> It's not a hidden feature, but it is a feature. Doc says:
Yah, I realized that pretty much the second I sent of the initial
email..
Stupid me.
Richard
prev parent reply other threads:[~2008-10-01 7:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 0:56 Richard Hartmann
2008-10-01 1:05 ` Richard Hartmann
2008-10-01 6:06 ` Bart Schaefer
2008-10-01 7:36 ` Richard Hartmann [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=2d460de70810010036g1e8b257bjb0265f4e0aada37f@mail.gmail.com \
--to=richih.mailinglist@gmail.com \
--cc=schaefer@brasslantern.com \
--cc=zsh-workers@sunsite.dk \
/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).