From: Hielmut Eller <eller.helmut@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Vitalie Spinu <spinuvit@gmail.com>, 20487@debbugs.gnu.org
Subject: bug#20487: 25.0.50; Format and behavior of *xref* buffer is non-standard
Date: Sun, 03 May 2015 22:05:02 +0200 [thread overview]
Message-ID: <m2zj5lig0h.fsf@gmail.com> (raw)
In-Reply-To: <55465BDD.8080101@yandex.ru> (Dmitry Gutov's message of "Sun, 3 May 2015 20:33:17 +0300")
On Sun, May 03 2015, Dmitry Gutov wrote:
>> I never have problems with that. Emacs pops buffers in a variety of ways
>> but rarely hides them. I think people are used to manage their own
>> buffers as they see fit. I don't think xref should "help" them with
>> that.
>
> Helmut, thoughts?
*Completion* buffers are automatically closed after the selection is
made. The *xref* buffer is similar in purpose: select a candidate from
a list. I think it's rarely an advantage but often a annoyance to have
to close the *xref* buffer manually. We could always have an
alternative key say SPC that jumps to the location without closing the
*xref* buffer.
Helmut
next prev parent reply other threads:[~2015-05-03 20:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-02 22:20 bug#20487: 25.0.50; Format and behavior of *xref* buffer is non-standard Vitalie Spinu
2015-05-03 14:30 ` Dmitry Gutov
2015-05-03 16:39 ` Vitalie Spinu
2015-05-03 17:33 ` Dmitry Gutov
2015-05-03 17:36 ` Dmitry Gutov
2015-05-03 18:46 ` Vitalie Spinu
2015-05-03 21:52 ` Dmitry Gutov
2015-05-03 22:20 ` Vitalie Spinu
2015-05-04 2:24 ` Dmitry Gutov
2015-05-03 20:05 ` Hielmut Eller [this message]
2015-05-03 20:30 ` Vitalie Spinu
2015-05-03 20:48 ` Dmitry Gutov
2015-05-03 21:49 ` Vitalie Spinu
2016-02-21 23:07 ` Dmitry Gutov
2015-05-04 2:18 ` Stefan Monnier
2015-05-04 2:29 ` Dmitry Gutov
2015-05-04 11:15 ` Vitalie Spinu
2015-05-04 11: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=m2zj5lig0h.fsf@gmail.com \
--to=eller.helmut@gmail.com \
--cc=20487@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=spinuvit@gmail.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).