From: "Nikolai Weibull" <now@bitwi.se>
To: "Ag. D. Hatzimanikas" <a.hatzim@gmail.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: PATCH: _vim
Date: Thu, 17 May 2007 09:28:52 +0200 [thread overview]
Message-ID: <dbfc82860705170028j386c37bdt834c80e54cd0186a@mail.gmail.com> (raw)
In-Reply-To: <20070516191733.GA23466@TMS>
On 5/16/07, Ag. D. Hatzimanikas <a.hatzim@gmail.com> wrote:
> Just a couple of _vim additions, most notably the (-p) and
> (--remote-tab), which both have to do with tabs; introduced
> in vim 7.0 version (currently in 7.1).
> + {--nofork,-f}'[do not detach the GUI version from the shell]'
This line should be
+ '(--nofork -f)'{--nofork,-f}'[do not detach the GUI version from the shell]'
Other than that it looks good. Thanks!
nikolai
prev parent reply other threads:[~2007-05-17 7:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 19:17 Ag. D. Hatzimanikas
2007-05-17 7:28 ` Nikolai Weibull [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=dbfc82860705170028j386c37bdt834c80e54cd0186a@mail.gmail.com \
--to=now@bitwi.se \
--cc=a.hatzim@gmail.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).