all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vitalie Spinu <spinuvit@gmail.com>
To: Hielmut Eller <eller.helmut@gmail.com>
Cc: 20487@debbugs.gnu.org, Dmitry Gutov <dgutov@yandex.ru>
Subject: bug#20487: 25.0.50; Format and behavior of *xref* buffer is non-standard
Date: Sun, 03 May 2015 22:30:07 +0200	[thread overview]
Message-ID: <87oam1qu9c.fsf@gmail.com> (raw)
In-Reply-To: <m2zj5lig0h.fsf@gmail.com> (Hielmut Eller's message of "Sun, 03 May 2015 22:05:02 +0200")

 >>> Hielmut Eller on Sun, 03 May 2015 22:05:02 +0200 wrote:

 > 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.

??? Not for me.

Just tried in emacs -q wit byte-compile-file on .el and makeinfo on
.texi and none quits.


  Vitalie

  





  reply	other threads:[~2015-05-03 20:30 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
2015-05-03 20:30         ` Vitalie Spinu [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87oam1qu9c.fsf@gmail.com \
    --to=spinuvit@gmail.com \
    --cc=20487@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=eller.helmut@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 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.