From: ndame via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 49774@debbugs.gnu.org
Subject: bug#49774: 27.1; if diff commands finds no differences then do not pop up a window
Date: Fri, 30 Jul 2021 11:58:08 +0000 [thread overview]
Message-ID: <c0O91eHm7YcB-0kPmVr2dCIh6WiSPs1EbqBUJAQmblD2UOxHT5HD1UF8Yg8llx8e_ez47yO-X_ZgvjBK9fgf0C_95BtvCTbMydU9zCzhdvQ=@protonmail.com> (raw)
In-Reply-To: <875ywsowdh.fsf@gnus.org>
>
> > Diff output arrives pretty much instantly
>
> Depends on many things -- the files may be on remote systems, for
> instance.
Okay, then how about adding a configurable delay before popping up the diff window?
E.g. if no results arrive within, say, 1 second then a timer pops up the
window, so the user knows the diff is in progress, but slow.
This takes care of the slow remote system problem and the timer would practically
never fire on a local machine where the filesystem response is quick.
next prev parent reply other threads:[~2021-07-30 11:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 16:59 bug#49774: 27.1; if diff commands finds no differences then do not pop up a window ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-30 1:18 ` Dmitry Gutov
2021-07-30 4:18 ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-30 10:03 ` Lars Ingebrigtsen
2021-07-30 11:19 ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-30 11:24 ` Lars Ingebrigtsen
2021-07-30 11:47 ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-30 11:48 ` Lars Ingebrigtsen
2021-07-30 11:58 ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-07-30 12:44 ` Dmitry Gutov
2021-07-30 13:19 ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-30 18:47 ` Lars Ingebrigtsen
2021-07-31 21:06 ` Juri Linkov
2021-07-31 22:11 ` Lars Ingebrigtsen
2021-08-02 1:07 ` Richard Stallman
2022-08-22 10:30 ` Lars Ingebrigtsen
2021-07-30 18:28 ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-16 18:29 ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
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: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='c0O91eHm7YcB-0kPmVr2dCIh6WiSPs1EbqBUJAQmblD2UOxHT5HD1UF8Yg8llx8e_ez47yO-X_ZgvjBK9fgf0C_95BtvCTbMydU9zCzhdvQ=@protonmail.com' \
--to=bug-gnu-emacs@gnu.org \
--cc=49774@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=laszlomail@protonmail.com \
/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://git.savannah.gnu.org/cgit/emacs.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).