From: Stefan Kangas <stefan@marxist.se>
To: Dario Gjorgjevski <dario.gjorgjevski@gmail.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 38294@debbugs.gnu.org
Subject: bug#38294: [PATCH] Handle killing of virtual buffers in Ido
Date: Fri, 14 Aug 2020 15:56:08 -0700 [thread overview]
Message-ID: <CADwFkmmrk0Ksxn=0VCVFGci26gmktHgdGP6AOiqvx+91r3hk1w@mail.gmail.com> (raw)
In-Reply-To: <fv2zoj364oanzw.fsf@gmail.com>
Dario Gjorgjevski <dario.gjorgjevski@gmail.com> writes:
>> But the virtual buffers are only visible on `C-x C-f', not on `C-x b',
>> right?
>
> They’re visible everywhere: also on ‘C-x b’ and ‘C-x k’. The latter is
> what this patch is related to.
>
>> 2. (setq ido-virtual-buffers t)
>
> The correct variable is ‘ido-use-virtual-buffers’, not
> ‘ido-virtual-buffers’.
Uhm, okay, yes that explains why I didn't see it...
But my question is then why this buffer even shows up on `C-x k' if it's
a virtual buffer. Instead of making it do something on kill, isn't it
better to just never show it if it's not actually open?
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2020-08-14 22:56 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
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 [this message]
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='CADwFkmmrk0Ksxn=0VCVFGci26gmktHgdGP6AOiqvx+91r3hk1w@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 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).