From: Stefan Haller <email@example.com> To: Pratyush Yadav <firstname.lastname@example.org> Cc: email@example.com Subject: Re: [PATCH 0/2] git-gui: Auto-rescan on activate Date: Mon, 2 Nov 2020 20:24:34 +0100 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> On 02.11.20 14:15, Pratyush Yadav wrote: > Hi Stefan, > > On 01/11/20 06:05PM, Stefan Haller wrote: >> Do an automatic rescan whenever the git-gui window receives focus. Most other >> GUI tools do this, and it's very convenient; no more pressing F5 manually. > > I submitted a patch for this a while back but there was a lengthy > discussion.  would be a good read. IIRC the major blocker was that > rescan is a very expensive operation on Windows. Ah, thanks for reminding me of that. I did actually read the discussion back then, but had completely forgotten about it. >> People who don't like this behavior can turn it off using >> "git config gui.autorescan false". > > To make sure the experience on Windows (and for anyone who faces long > rescan times) does not degrade, I think we should keep this off by > default. That said, I would love to be convinced to keep this on by > default because IMO this is a really good feature to have. I tried > coming up with ways to avoid slowdowns while keeping the auto rescan on > but I didn't come up with anything convincing. I still think the default should be on; I consider it more important that the information is accurate than that it is shown without delay. I do use Windows occasionally myself, in a slow VM no less, and it does annoy me that a rescan is so slow there; however, I still prefer that over looking at stale information without realizing it. Also, I had a look at how other git clients deal with this. I didn't do an exhaustive research, just quickly looked at a few: - Fork (https://git-fork.com) Rescans on activate. There's no setting to turn this off. (!) - SourceTree (https://www.sourcetreeapp.com) Rescans on activate. There's an option to turn this off, but it defaults to on. (It is confusingly called "Refresh automatically when files change", which doesn't seem to be accurate, as far as I can tell.) - Visual Studio Code Rescans on activate. There's an option to turn it off, but it defaults to on. - Sublime Merge (https://www.sublimemerge.com) Watches files and rescans in the background. So I would say there's plenty of precedence for having this behavior default to on. >> Stefan Haller (2): >> git-gui: Delay rescan until idle time >> git-gui: Auto-rescan on activate >> >> git-gui.sh | 26 ++++++++++++++++++++++---- >> 1 file changed, 22 insertions(+), 4 deletions(-) >> > >  https://firstname.lastname@example.org/ >
next prev parent reply other threads:[~2020-11-02 19:24 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-01 17:05 Stefan Haller 2020-11-01 17:05 ` [PATCH 1/2] git-gui: Delay rescan until idle time Stefan Haller 2020-11-02 15:45 ` Pratyush Yadav 2020-11-02 19:29 ` Stefan Haller 2020-11-01 17:05 ` [PATCH 2/2] git-gui: Auto-rescan on activate Stefan Haller 2020-11-02 15:48 ` Pratyush Yadav 2020-11-02 19:31 ` Stefan Haller 2020-11-02 13:15 ` [PATCH 0/2] " Pratyush Yadav 2020-11-02 19:24 ` Stefan Haller [this message] 2020-11-03 16:16 ` [PATCH v2 0/1] " Stefan Haller 2020-11-03 16:16 ` [PATCH v2 1/1] " Stefan Haller 2020-11-14 19:14 ` Stefan Haller 2020-11-17 7:36 ` Pratyush Yadav 2020-11-17 11:13 ` Stefan Haller 2020-11-17 12:05 ` Pratyush Yadav 2020-11-18 9:17 ` Stefan Haller 2020-12-17 19:45 ` [PATCH 0/2] " Johannes Sixt 2020-12-17 20:10 ` Pratyush Yadav 2020-12-17 22:21 ` Johannes Sixt 2020-12-18 10:36 ` Stefan Haller 2020-12-18 18:07 ` Johannes Sixt
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 List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH 0/2] git-gui: Auto-rescan on activate' \ /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
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git 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 read-only IMAP folder(s) and NNTP newsgroup(s).