unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: David Reitter <david.reitter@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 21969@debbugs.gnu.org
Subject: bug#21969: VC opens new window to display minimal messages
Date: Sat, 21 Nov 2015 20:07:05 -0500	[thread overview]
Message-ID: <2DD7D456-BD0F-47A7-9138-E771094E169E@gmail.com> (raw)
In-Reply-To: <56510676.2010305@yandex.ru>

On Nov 21, 2015, at 7:04 PM, Dmitry Gutov <dgutov@yandex.ru> wrote:

> So, I'm not sure what's the best course of action here:
> 
> - Call 'git diff' synchronously, and leave all other backends with this problem.
> 
> - Call all 'diff' commands synchronously, and disregard the backends that might respond slowly to this command; the user will wait.
> 
> - Invent some other solutions, like introduce a timeout which we might wait for the backend to respond before popping the window, and abort (?) if the user interacts with Emacs during that time.


Try this:

Call asynchronously.  Install timeout or sentinel that checks if or when the process has finished.  If it’s just one line, remove the window that was created.

My thinking is that this is likely to be handled so quickly that redisplay will not have time to pop up the window.

However, I can see that this might use low-level functions (pop-to-buffer is very configurable).  

Alternatively, and perhaps that is the correct solution, I would start asynchronously and install a very brief timeout that opens up the new window unless the process has finished with just one line of output (or an error).

For the 25.1 branch, one could consider just calling it synchronously.




  reply	other threads:[~2015-11-22  1:07 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-21 13:55 bug#21969: VC opens new window to display minimal messages David Reitter
2015-11-21 18:21 ` Dmitry Gutov
2015-11-22  0:04 ` Dmitry Gutov
2015-11-22  1:07   ` David Reitter [this message]
2015-11-22  1:27     ` Dmitry Gutov
2015-11-22  2:28       ` David Reitter
2015-11-22  5:01         ` Dmitry Gutov
2015-11-22 16:20         ` Eli Zaretskii
2015-11-22 16:46           ` Dmitry Gutov
2015-11-22 17:00             ` Eli Zaretskii
2015-11-22 17:02               ` Dmitry Gutov
2015-11-22 16:58           ` David Reitter
2015-11-22 16:08   ` Eli Zaretskii
2015-11-22 16:45     ` Dmitry Gutov
2015-11-22 16:58       ` Eli Zaretskii
2015-11-22 17:01         ` Dmitry Gutov
2015-11-22 17:40           ` Eli Zaretskii
2015-11-22 17:41             ` Dmitry Gutov
2015-11-22 17:45               ` David Reitter
2015-11-27 22:26                 ` Daniel Colascione
2015-11-28  0:50                   ` Dmitry Gutov
2015-11-28  8:21                     ` Eli Zaretskii
2015-11-28 12:01                       ` Dmitry Gutov
2015-11-28 12:15                         ` Eli Zaretskii
2015-11-28 12:19                           ` Dmitry Gutov

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=2DD7D456-BD0F-47A7-9138-E771094E169E@gmail.com \
    --to=david.reitter@gmail.com \
    --cc=21969@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    /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).