From: Pratyush Yadav <me@yadavpratyush.com>
To: Stefan Haller <stefan@haller-berlin.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/2] git-gui: Auto-rescan on activate
Date: Mon, 2 Nov 2020 18:45:22 +0530 [thread overview]
Message-ID: <20201102131522.coj5gb2bssvjqngo@yadavpratyush.com> (raw)
In-Reply-To: <20201101170505.71246-1-stefan@haller-berlin.de>
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. [0] would be a good read. IIRC the major blocker was that
rescan is a very expensive operation on Windows.
> 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.
> 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(-)
>
[0] https://lore.kernel.org/git/20190728151726.9188-1-me@yadavpratyush.com/
--
Regards,
Pratyush Yadav
next prev parent reply other threads:[~2020-11-02 13:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-01 17:05 [PATCH 0/2] git-gui: Auto-rescan on activate 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 ` Pratyush Yadav [this message]
2020-11-02 19:24 ` [PATCH 0/2] " Stefan Haller
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 \
--in-reply-to=20201102131522.coj5gb2bssvjqngo@yadavpratyush.com \
--to=me@yadavpratyush.com \
--cc=git@vger.kernel.org \
--cc=stefan@haller-berlin.de \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public 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).