From: "Felicián Németh" <felician.nemeth@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 34529@debbugs.gnu.org
Subject: bug#34529: C-x b became unusable (ido, recentf, tramp)
Date: Wed, 20 Feb 2019 08:34:30 +0100 [thread overview]
Message-ID: <CAGLaV2byUmyP5w5_721gRZFcO7qqsA6_Scr0jLzidTVx1UTZzw@mail.gmail.com> (raw)
In-Reply-To: <87va1gql6d.fsf@gmx.de>
Hi Michael,
>> However, that doesn't explain how that entry ended up in my
>> recentf-save-file. I'm guessing I opened many tramp files in a
>> virtual machine, and after I had halted the virtual machine,
>> emacs wanted to convert the file names to absolute paths.
>
> Do you use ad-hoc multi-hop file names?
With this virtual machine, definitely not. However, the problem occurred
in a long lasting emacs session and I do remember trying to ssh|su
into a remote system. It wasn't successful because (I think) tramp
failed to find the password prompt because of an unfortunate locale
setting.
However, I found a probable cause of evenets that inserts a wrong entry
into recentf-list:
bug.el:
(require 'recentf)
(setq recentf-save-file "/tmp/bug2-recentf")
(setq ido-use-virtual-buffers t)
(setq ido-save-directory-list-file "/tmp/bug-ido.last")
(ido-mode t)
(ffap-bindings)
0. emacs -Q -l bug.el
1. Open a relative file in a VM (/ssh:localhost#2222:~/a.txt)
2. Close the file, halt the VM.
3. (Accidentally) open the same file from the file-name-history.
(C-x C-f M-p)
4. Close emacs.
=> /tmp/bug2-recentf has the relative path.
Thanks again,
Felicián
next prev parent reply other threads:[~2019-02-20 7:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 16:58 bug#34529: C-x b became unusable (ido, recentf, tramp) Felicián Németh
2019-02-19 7:42 ` Michael Albinus
2019-02-20 7:34 ` Felicián Németh [this message]
2019-02-20 9:40 ` Michael Albinus
2019-02-21 8:12 ` Felicián Németh
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=CAGLaV2byUmyP5w5_721gRZFcO7qqsA6_Scr0jLzidTVx1UTZzw@mail.gmail.com \
--to=felician.nemeth@gmail.com \
--cc=34529@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
/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).