git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Bug: pager.<cmd> doesn't work well with editors

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 19, 2016, 16:03 UTC
Message-ID
<xmqqh99bho7a.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<nrmd6u$imf$1@blaine.gmane.org>
Anatoly Borodin <anatoly.borodin@gmail.com> writes:
>> I think, the pagination should be turned off when the editor is being
>> called.

This is a fun one. IIRC, we decide to spawn a pager and run our output via pipe thru it fairly early, even before we figure out which subcommand is being run (especially if you do "git -p subcommand"), which by definition is way before we know if that subcommand wants to let the user edit things with the editor.

Previous: Anatoly BorodinNext: Jeff King
Message 3 of 8 in “Bug: pager.<cmd> doesn't work well with editors”
  1. Anatoly BorodinSep 18, 2016
  2. Anatoly BorodinSep 18, 2016
  3. Junio C HamanoSep 19, 2016
  4. Jeff KingSep 20, 2016
  5. Junio C HamanoSep 21, 2016
  6. Jeff KingSep 22, 2016
  7. Junio C HamanoSep 22, 2016
  8. Jeff KingSep 23, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.