From: Stefan Kangas <stefan@marxist.se>
To: Lars Ingebrigtsen <larsi@gnus.org>,
Dario Gjorgjevski <dario.gjorgjevski@gmail.com>
Cc: 38294@debbugs.gnu.org
Subject: bug#38294: [PATCH] Handle killing of virtual buffers in Ido
Date: Fri, 14 Aug 2020 09:14:49 -0700 [thread overview]
Message-ID: <CADwFkmmkG+Z0SecND=saMY4f1GaC6oy9r+f81y1vFnUTnS8Y8w@mail.gmail.com> (raw)
In-Reply-To: <87r1s9a3vb.fsf@gnus.org>
Lars Ingebrigtsen <larsi@gnus.org> writes:
>>> Killing it isn't a no-op though. When you kill it, you get prompted to
>>> save changes, it runs hooks in the background, presumably removes it
>>> from active memory, other functions will no longer be able to just
>>> switch to it, etc., etc.
>
> Yeah, but these "virtual buffers" don't really exist, so none of that
> will happen, I'd have thought?
But the virtual buffers are only visible on `C-x C-f', not on `C-x b',
right?
At least, that's what it looks like when I do:
0. emacs -Q
1. M-x ido-mode
2. (setq ido-virtual-buffers t)
3. C-x C-f existing-file-foo RET
4. C-x k RET
5. C-x k => existing-file-foo is not shown
But I may very well be overlooking something...
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2020-08-14 16:14 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 [this message]
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='CADwFkmmkG+Z0SecND=saMY4f1GaC6oy9r+f81y1vFnUTnS8Y8w@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).