From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: emacs-devel@gnu.org
Subject: Re: xref and leaving "temporary" buffers open
Date: Sat, 25 Jul 2015 19:15:20 +0300 [thread overview]
Message-ID: <83a8uk1aef.fsf@gnu.org> (raw)
In-Reply-To: <55B3B428.5080301@yandex.ru>
> Cc: emacs-devel@gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Sat, 25 Jul 2015 19:07:04 +0300
>
> On 07/25/2015 06:27 PM, Eli Zaretskii wrote:
>
> > Then perhaps there should be a command to kill all those buffers
> > created by xref for these purposes.
>
> Suppose we tag them with a buffer-local variable.
>
> What if the use switches to one of these buffers on their own accord,
> with find-file or switch-to-buffer? They might not be aware that that
> buffer was opened by xref, and would be surprised to see M-x
> xref-kill-temporary-buffers kill that buffer as well.
You could detect this using buffer-modified-tick, no? You could also
refrain from killing any of these buffers displayed in some window, or
present in the relevant history lists.
> > OTOH, look at the example of info.el's info-apropos: it doesn't keep
> > around the Info manuals it visits. So this is also a reasonable
> > behavior we have elsewhere.
>
> It keeps a cache of search results (and initiates full search for any
> input not in cached list). That's nice, but probably solves a different
> problem.
That's not what I meant. What I meant was that the manuals are not
available once the command finishes, although its quite clear the
command had to visit each and every one of them.
next prev parent reply other threads:[~2015-07-25 16:15 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-25 0:47 xref and leaving "temporary" buffers open Dmitry Gutov
2015-07-25 7:27 ` Eli Zaretskii
2015-07-25 13:26 ` Dmitry Gutov
2015-07-25 14:07 ` Eli Zaretskii
2015-07-25 14:24 ` Dmitry Gutov
2015-07-25 14:36 ` Eli Zaretskii
2015-07-25 15:09 ` Dmitry Gutov
2015-07-25 15:27 ` Eli Zaretskii
2015-07-25 16:07 ` Dmitry Gutov
2015-07-25 16:15 ` Eli Zaretskii [this message]
2015-07-25 16:28 ` Dmitry Gutov
2015-07-25 16:38 ` Eli Zaretskii
2015-07-25 17:03 ` Dmitry Gutov
2015-07-25 18:17 ` martin rudalics
2015-07-25 18:30 ` Dmitry Gutov
2015-07-27 17:34 ` Nix
2015-07-28 13:30 ` Dmitry Gutov
2015-07-29 15:02 ` Nix
2015-07-25 8:28 ` martin rudalics
2015-07-25 13:36 ` Dmitry Gutov
2015-07-25 14:12 ` martin rudalics
2015-07-25 14:44 ` Dmitry Gutov
2015-07-25 15:53 ` martin rudalics
2015-07-25 20:12 ` Dmitry Gutov
2015-07-26 11:27 ` martin rudalics
2015-07-26 13:50 ` Dmitry Gutov
2015-07-27 16:02 ` martin rudalics
2015-07-28 12:57 ` Dmitry Gutov
2015-07-28 13:16 ` martin rudalics
2015-07-28 13:35 ` Dmitry Gutov
2015-07-28 15:10 ` martin rudalics
2015-07-28 15:18 ` Dmitry Gutov
2015-07-28 15:40 ` martin rudalics
2015-07-28 19:13 ` Dmitry Gutov
2015-07-28 23:48 ` Stefan Monnier
2015-07-29 1:42 ` Dmitry Gutov
2015-07-30 21:41 ` Stefan Monnier
2015-08-03 2:12 ` Dmitry Gutov
2015-08-03 6:47 ` martin rudalics
2015-08-03 10:10 ` Dmitry Gutov
2015-08-03 10:45 ` martin rudalics
2015-08-03 10:50 ` Stefan Monnier
2015-07-26 19:00 ` Stephen Leake
2015-07-26 19:11 ` Dmitry Gutov
2015-07-27 16:02 ` martin rudalics
2015-07-28 1:32 ` Stephen Leake
2015-07-25 13:47 ` Stephen Leake
2015-07-25 14:19 ` martin rudalics
2015-07-25 15:51 ` 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=83a8uk1aef.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
/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.