From: Stefan Kangas <stefan@marxist.se>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Dario Gjorgjevski <dario.gjorgjevski@gmail.com>, 38294@debbugs.gnu.org
Subject: bug#38294: [PATCH] Handle killing of virtual buffers in Ido
Date: Wed, 12 Aug 2020 15:01:17 -0700 [thread overview]
Message-ID: <CADwFkmky-pq9qBcLB8Q9=0Xkc83ycOd6qcSHKgO_Q_aQCTXOBA@mail.gmail.com> (raw)
In-Reply-To: <874kpcrm5q.fsf@gnus.org>
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Stefan Kangas <stefan@marxist.se> writes:
>
>>> What this patch changes is exactly this behavior: once a virtual buffer
>>> has been “killed” from C-x k, it no longer appears in the list of
>>> buffers.
>>>
>>> Let me know if this makes sense.
>>
>> I think the current behaviour makes sense, but I can very much see
>> that some users would want what you suggest. Both choices here are
>> valid.
>
> I think so, too, but I don't use this combination of features, so I'm
> not sure.
>
> It does seem natural that killing a buffer would remove it from the list
> of buffers ido-mode offers up, though, so I'm not totally sure whether
> any ido users really expect this behaviour, or if they've just lived
> with it as a bug.
>
> Any opinions here?
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.)
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.
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.
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2020-08-12 22:01 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 [this message]
2020-08-13 8:16 ` Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADwFkmky-pq9qBcLB8Q9=0Xkc83ycOd6qcSHKgO_Q_aQCTXOBA@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=38294@debbugs.gnu.org \
--cc=dario.gjorgjevski@gmail.com \
--cc=larsi@gnus.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.