From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: Dario Gjorgjevski <dario.gjorgjevski@gmail.com>, 38294@debbugs.gnu.org
Subject: bug#38294: [PATCH] Handle killing of virtual buffers in Ido
Date: Thu, 13 Aug 2020 10:16:37 +0200 [thread overview]
Message-ID: <87imdnhsey.fsf@gnus.org> (raw)
In-Reply-To: <CADwFkmky-pq9qBcLB8Q9=0Xkc83ycOd6qcSHKgO_Q_aQCTXOBA@mail.gmail.com> (Stefan Kangas's message of "Wed, 12 Aug 2020 15:01:17 -0700")
Stefan Kangas <stefan@marxist.se> writes:
> The idea specifically with ido-use-virtual-buffers (from reading its doc
> string, not from being a user) is that one shouldn't have to worry about
> whether or not the buffer is open or not. To my mind, that implies that
> it means that even when manually killing buffers, I should still be able
> to switch to it.
>
> (It also seems a bit too surprising to now change the long-standing
> default behaviour.)
Yeah, that sounds reasonable. The only question is whether manual
killing should be handled differently than automatic killing (i.e., by
midnight.el).
But... that would be a kinda finicky interface, with C-x k working one
way, and indirect calls to it another.
So I agree with you that this is probably not something we want....
> However, if some users specifically want this behaviour only for
> auto-cleaned buffers (e.g. by midnight), I don't see why we couldn't
> provide it optionally.
An option for something as obscure as this seems like overkill.
> Anyways, I don't know if there is anything useful in the above or if I'm
> just rambling. I agree that it would be good to hear the opinion of
> someone else who actually uses this.
It would. :-)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-08-13 8:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 8:56 bug#38294: [PATCH] Handle killing of virtual buffers in Ido Dario Gjorgjevski
2020-01-20 18:40 ` Stefan Kangas
2020-01-22 8:21 ` Dario Gjorgjevski
2020-01-22 9:00 ` Stefan Kangas
2020-08-09 13:20 ` Lars Ingebrigtsen
2020-08-12 22:01 ` Stefan Kangas
2020-08-13 8:16 ` Lars Ingebrigtsen [this message]
2020-08-13 8:37 ` Stefan Kangas
2020-08-13 8:39 ` Lars Ingebrigtsen
2020-08-13 9:50 ` Dario Gjorgjevski
2020-08-13 11:04 ` Stefan Kangas
2020-08-14 9:23 ` Dario Gjorgjevski
2020-08-14 11:00 ` Lars Ingebrigtsen
2020-08-14 16:14 ` Stefan Kangas
2020-08-14 21:58 ` Dario Gjorgjevski
2020-08-14 22:56 ` Stefan Kangas
2020-08-15 8:03 ` Dario Gjorgjevski
2020-08-15 10:29 ` Lars Ingebrigtsen
2020-08-15 14:03 ` Stefan Kangas
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=87imdnhsey.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=38294@debbugs.gnu.org \
--cc=dario.gjorgjevski@gmail.com \
--cc=stefan@marxist.se \
/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).