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:38:46 +0300 [thread overview]
Message-ID: <83615819bd.fsf@gnu.org> (raw)
In-Reply-To: <55B3B91A.2000509@yandex.ru>
> Cc: emacs-devel@gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Sat, 25 Jul 2015 19:28:10 +0300
>
> On 07/25/2015 07:15 PM, Eli Zaretskii wrote:
>
> > 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.
>
> The tick doesn't change if the user hasn't modified the contents. And if
> the buffer is not visible just now, that doesn't mean that it's
> unwanted. Both useful heuristics, but still less than ideal, IMO.
I meant 3 devices, not 2.
And I think all of them together go a long way towards eliminating
accidental deletion of a buffer the user would like to keep. Plus,
they can always refrain from invoking the command, if they are afraid
of losing buffers. And if worse comes to worst, the file can be
visited again.
next prev parent reply other threads:[~2015-07-25 16:38 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
2015-07-25 16:28 ` Dmitry Gutov
2015-07-25 16:38 ` Eli Zaretskii [this message]
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
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=83615819bd.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 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).