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

Re: [PATCH] request-pull: do not paginate output of git commands

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 30, 2009, 16:20 UTC
Message-ID
<7vws6t8zhv.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1246361606-20457-1-git-send-email-mmarek@suse.cz>
Michal Marek <mmarek@suse.cz> writes:
> git request-pull called inside a terminal prints part of the output to
> the terminal and other parts are piped through the pager. Fix this.
Hmph, I have always thought this was meant to be a feature.

That is, you run it to yourself, instead of piping it to a file or "| mail torvalds", in order to sanity check before you actually do the latter. When the request is larger than a screenful, you would want a pager while reviewing.

Admittedly, I do not regularly use request-pull, so I wouldn't know if use of the pager is inconvenient to people who have to use this feature regularly. Your patch could be addressing a real usability issue.

But I have this nagging suspicion that you may be lacking F (or FX) from your LESS environment variable?

Previous: Michal MarekNext: Junio C Hamano
Message 2 of 7 in “request-pull: do not paginate output of git commands”
  1. request-pull: do not paginate output of git commandsMichal Marek, Jun 30, 2009
  2. Junio C HamanoJun 30, 2009
  3. Junio C HamanoJun 30, 2009
  4. Michal MarekJun 30, 2009
  5. Junio C HamanoJun 30, 2009
  6. Michal MarekJul 1, 2009
  7. Junio C HamanoJul 1, 2009

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.