From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 21969@debbugs.gnu.org, david.reitter@gmail.com
Subject: bug#21969: VC opens new window to display minimal messages
Date: Sun, 22 Nov 2015 18:58:28 +0200 [thread overview]
Message-ID: <83lh9q2cp7.fsf@gnu.org> (raw)
In-Reply-To: <5651F11D.4090404@yandex.ru>
> Cc: 21969@debbugs.gnu.org, david.reitter@gmail.com
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Sun, 22 Nov 2015 18:45:17 +0200
>
> On 11/22/2015 06:08 PM, Eli Zaretskii wrote:
>
> > Why not always show the output in a window, and remove the code that
> > shows it in the echo area?
>
> Because showing it in a buffer disturbs the window configuration, and
> you have to press `q' to quit it. Seems reasonable to want to avoid that
> when there's nothing to show.
How is that different from when Grep doesn't find any hits, or a
compile command produces no output?
IOW, we already have this kind of popping windows elsewhere in Emacs,
so why cannot this use case behave similarly?
next prev parent reply other threads:[~2015-11-22 16:58 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83lh9q2cp7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=21969@debbugs.gnu.org \
--cc=david.reitter@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.