From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh workers <zsh-workers@zsh.org>
Subject: Re: _make doesn't work in dirs with spaces
Date: Sun, 22 May 2011 18:10:51 -0700 [thread overview]
Message-ID: <110522181051.ZM7938@torch.brasslantern.com> (raw)
In-Reply-To: <BANLkTikp5k0EnP870F8s7ucoxNcyHsKcaA@mail.gmail.com>
On May 21, 8:03pm, Mikael Magnusson wrote:
}
} There's some (q) in there that maybe shouldn't be. Removing the one on
} line 176 fixes completing in a directory with spaces, but I'm unsure
} of the intention of it, and the others in the file.
The one on line 176 just looks wrong and should probably be removed.
For those on lines 163 an 166, I wonder if they should be (D) ?
next prev parent reply other threads:[~2011-05-23 1:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-21 18:03 Mikael Magnusson
2011-05-23 1:10 ` Bart Schaefer [this message]
2011-05-24 1:36 ` Mikael Magnusson
2011-05-24 1:38 ` PATCH: _make: put body in _make() and don't redefine helpers every time Mikael Magnusson
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=110522181051.ZM7938@torch.brasslantern.com \
--to=schaefer@brasslantern.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).