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

Re: Very simple popen() code request, ground-shaking functionality openned by it

From
SGSebastian Gniazdowski <psprint@zdharma.org>
Date
Sep 22, 2018, 18:16 UTC
Message-ID
<etPan.5ba686e3.762c4412.1ba0@zdharma.org>
In-Reply-To
<87musajun7.fsf@evledraar.gmail.com>
On 22 września 2018 at 01:30:36, Ævar Arnfjörð Bjarmason (avarab@gmail.com) wrote: 
> Duy's  
> https://public-inbox.org/git/20180920161928.GA13379@duynguyen.home/ is  
> another recent thing that reminded me of this, i.e. that suggested  
> "\\|/-" spinner could be made much neater with non-ASCII.  
Here is a IMO very large collection of spinner-like unicode animations: 
https://asciinema.org/a/ex8z3z6d5m7uv4buww0o2qeq2 
This comes from Zsh world, it's a plugin with spinners to use in Zsh scripts. I've never managed to see even 1/3 of them. 
Show 5 quoted lines
> I'll just add that a 3rd thing that would also make sense would be to  
> add a feature to configure the value of these GIT_TRACE_*=* variables  
> via the .gitconfig, that's been suggested before (too lazy to dig up a  
> ML archive reference), and would make this as easy to configure as  
> Sebastian's suggestion.  
Yes git config setting of this is most convenient IMO, most expected to occur in ~/.gitconfig, in which it would be set once to a favourite gauge-box script, and rather long long before looking at this part of config again. Or maybe in the beginning, dawn of such gauge-scripts (if there actually would be any new group of such scripts; but as it's a quite broad problem (see last `PS.' paragraph), then who knows), when some unstable gauge-box would be breaking login/passwords prompt (but that's stdout not stderr, shouldn't go through gauge-box-script) or "fatal: ..." messages, etc., user might be disabling it temporarily or choosing an alternate gauge-box solution, editing the config option ;) So not rarely edited in the beginning. (I don't know how much important would a fancy gauge box be for a regular user; I can tell it would be quite important to me). I think this is more convenient and clean than `export GIT_*' in .bashrc/.zshrc, rarely edited, just sitting there. 
Guys you seem to like the idea, I hope someone will approach the coding! 
PS. There's much room for improvement in the git-process-output.zsh in the Asciinema video, gauge scripts won't be simple. In general, the number of 0..100% sequences (like: compressing, resolving, etc. – they all go 0 to 100% on their own) should be somehow predicted (does Git know this in advance?) and the gauge should be divided into that many segments, each filling up per one corresponding 0..100% sequence, together forming single global 0..100% gauge.
--  
Sebastian Gniazdowski 
News: https://twitter.com/ZdharmaI 
IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin 
Blog: http://zdharma.org
Previous: Jeff KingNext: Duy Nguyen
Message 5 of 6 in “Very simple popen() code request, ground-shaking functionality openned by it”
  1. Sebastian GniazdowskiSep 21, 2018
  2. Jeff KingSep 21, 2018
  3. Ævar Arnfjörð BjarmasonSep 21, 2018
  4. Jeff KingSep 21, 2018
  5. Sebastian GniazdowskiSep 22, 2018
  6. Duy NguyenSep 23, 2018

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.