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

Re: run-command: output owner picking strategy

From
Junio C Hamano <gitster@pobox.com>
Date
May 20, 2016, 18:54 UTC
Message-ID
<xmqqwpmod0hh.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<CAGZ79kbTa-E3QTgGhzEPKnEHiOMq_On6h6RC8jrrQaot1YE94g@mail.gmail.com>
Stefan Beller <sbeller@google.com> writes:
Show 5 quoted lines
> I choose "as much live output" as an approximation of "least amount buffered
> over time, i.e. if you were to integrate the buffer size over time
> that should be
> minimized. (c.f. users waiting for output: http://imgur.com/gallery/lhjhbB9)
> I am not sure if that is ultimate thing to optimize for though.

It might be interesting to optimize to minimize the time the user needs to stare an inactive screen, i.e. make sure there always is something flowing. That may involve throttling the output from a buffer if that is the only buffer with any output, the foreground thing hasn't made any output yet, and expected to stay silent for a while, etc.

Previous: Stefan Beller
Message 5 of 5 in “run-command: output owner picking strategy”
  1. William DuclotMay 20, 2016
  2. Stefan BellerMay 20, 2016
  3. William DuclotMay 20, 2016
  4. Stefan BellerMay 20, 2016
  5. Junio C HamanoMay 20, 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.