From: Jeff King <peff@peff.net>
To: George Brown <321.george@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] contrib/git-jump: cat output when not a terminal
Date: Mon, 11 May 2020 10:31:57 -0400 [thread overview]
Message-ID: <20200511143157.GA1415@coredump.intra.peff.net> (raw)
In-Reply-To: <CAFKec1VGzpxVJV4zak46r_p2gGcw4UanFr7U4U4MSsG7t2A23w@mail.gmail.com>
On Sun, May 10, 2020 at 07:34:09PM +0100, George Brown wrote:
> Arguably the most interoperable way for "git jump" to work would be to
> output the formatted lines and do nothing else, leaving it to users to
> choose how to operate upon the output/invoke editors. Of course such
> a change would break the workflow of anyone who uses "git jump" today
> and isn't a valid option.
Looks like I missed an exciting thread, but let me add a few thoughts as
the author of git-jump:
- I had no inkling that people would run it from within vim; I assumed
they'd use more integrated tools like fugitive.vim. ;) I don't think
it's wrong to do so, though.
- The paragraph quoted above is the heart of the matter. The tool does
two things: generate the list and open the editor. My thinking in
combining them was that "generate the list" was pretty simple and
just used existing tools anyway, but we have grown a _bit_ of a
complexity over the years that might make it worth using.
IMHO the right solution here is a command-line option to say "don't
start an editor, just send output". Setting GIT_EDITOR=cat
accomplishes the same thing, but it's much less obvious/discoverable.
- I'm pretty sure git-jump does _not_ work with emacs or emacsclient.
Somebody corresponded with me off-list about patches many years ago,
but I can't remember what the hold-up was. If anybody is interested
in pushing that forward, I'd be happy to dig it out my archive.
However, it should work with gvim, and any isatty() check would
potentially cause issues there. So I'd much prefer the caller say
explicitly that they're not expecting the editor to start.
So I'm OK to leave the status quo and let people use the GIT_EDITOR
solution in this instance. But I'd also be happy to take a patch for
"--no-editor" or similar if somebody wants to work it up.
-Peff
next prev parent reply other threads:[~2020-05-11 14:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 19:15 [PATCH] contrib/git-jump: cat output when not a terminal George Brown
2020-05-09 21:41 ` Junio C Hamano
2020-05-09 22:04 ` George Brown
2020-05-09 23:42 ` Junio C Hamano
2020-05-10 9:03 ` George Brown
2020-05-10 16:47 ` Junio C Hamano
2020-05-10 17:33 ` George Brown
2020-05-10 18:12 ` Junio C Hamano
2020-05-10 18:34 ` George Brown
2020-05-10 19:10 ` Junio C Hamano
2020-05-10 19:25 ` George Brown
2020-05-10 19:38 ` Junio C Hamano
2020-05-10 20:20 ` George Brown
2020-05-11 14:31 ` Junio C Hamano
2020-05-11 14:31 ` Jeff King [this message]
2020-05-11 15:36 ` Junio C Hamano
2020-05-11 15:42 ` Jeff King
2020-05-11 16:46 ` Re* " Junio C Hamano
2020-05-12 19:23 ` Jeff King
2020-05-12 21:30 ` Junio C Hamano
2020-05-13 4:52 ` Jeff King
-- strict thread matches above, loose matches on Subject: below --
2020-05-10 20:26 Benjamin
2020-05-11 14:33 ` Junio C Hamano
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=20200511143157.GA1415@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=321.george@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).