From: Jonathan Nieder <jrnieder@gmail.com>
To: Bert Wesarg <bert.wesarg@googlemail.com>
Cc: Pat Thoyts <patthoyts@users.sourceforge.net>,
"Shawn O . Pearce" <spearce@spearce.org>,
git@vger.kernel.org
Subject: Re: [PATCH/RFC/WIP/POC] git-gui: grep prototype
Date: Sun, 14 Nov 2010 17:48:48 -0600 [thread overview]
Message-ID: <20101114234848.GB26104@burratino> (raw)
In-Reply-To: <AANLkTi=JR3vVnZ4Yz8o9MpZKiQ2_ASYxahbPNv8QACir@mail.gmail.com>
Bert Wesarg wrote:
> Now I got your point. Maybe I should call GIT_EDITOR with $FILENAME as
> argument but with a new variable to indicate open'n'forget. So
> existing setups would always open the file (even without honoring the
> line number) and new/smart wrappers can honor the open'n'forget and
> line number flag.
Yes, I like the communication-via-environment idea.
In fact, there are multiple questions an editor might want answered:
1. GUI or no GUI? (The combination of $DISPLAY and $(tty) often
yields a reasonable answer.)
2. open'n'forget or wait for answer? (gvim's --nofork option)
3. What line number?
4. regex to use to highlight matches?
Ideally $LINENUMBER would only be used represent (3), while a
separate variable would indicate (2).
next prev parent reply other threads:[~2010-11-14 23:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-14 21:41 [PATCH/RFC/WIP/POC] git-gui: grep prototype Bert Wesarg
2010-11-14 21:54 ` Jonathan Nieder
2010-11-14 22:04 ` Bert Wesarg
2010-11-14 22:09 ` Jonathan Nieder
2010-11-14 22:15 ` Bert Wesarg
2010-11-14 23:48 ` Jonathan Nieder [this message]
2010-11-19 12:15 ` Bert Wesarg
2010-11-19 19:49 ` Jonathan Nieder
2010-11-19 20:16 ` Bert Wesarg
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=20101114234848.GB26104@burratino \
--to=jrnieder@gmail.com \
--cc=bert.wesarg@googlemail.com \
--cc=git@vger.kernel.org \
--cc=patthoyts@users.sourceforge.net \
--cc=spearce@spearce.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.
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).