all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 27108@debbugs.gnu.org
Subject: bug#27108: 26.0.50; tramp and recentf again
Date: Wed, 31 May 2017 16:19:32 +0200	[thread overview]
Message-ID: <87bmq92jnv.fsf@rosalinde> (raw)
In-Reply-To: <87wp8xl5fw.fsf@detlef> (Michael Albinus's message of "Wed, 31 May 2017 11:51:47 +0200")

On Wed, 31 May 2017 11:51:47 +0200 Michael Albinus <michael.albinus@gmx.de> wrote:

[...]
> I'm pretty sure, if you continue to work the usual way, calling Emacs
> w/o "-Q", the problem disappears latest after the second Emacs startup,
> because the cached value is available then from the persistency
> file. That's why I believe it isn't a bug.

You're right.  I accessed a remote file via sftp last night and its name
was saved to the recentf file on exiting Emacs, and when I started Emacs
today, there was no password request.

> OTOH, I understand that the problem is annoying when it appears, and
> when it isn't obvious why this happens. The appended small patch in
> `recentf-load-list' would avoid this, instructing Tramp not to open a
> new connection while reading the previously saved recent list. Would it
> be OK to apply this patch?

IIUC, this would suppress the password request on starting Emacs, but
leave the remote file name in the recentf list?  That sounds like a good
solution to me.  Thanks.

Steve Berman





  reply	other threads:[~2017-05-31 14:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-27 21:26 bug#27108: 26.0.50; tramp and recentf again Stephen Berman
2017-05-31  9:51 ` Michael Albinus
2017-05-31 14:19   ` Stephen Berman [this message]
2017-05-31 18:35     ` Michael Albinus
2017-05-31 20:01       ` Stephen Berman
2017-06-01  7:18         ` Michael Albinus

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=87bmq92jnv.fsf@rosalinde \
    --to=stephen.berman@gmx.net \
    --cc=27108@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 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.