From: "Luiz Romário Santana Rios" <luizromario@tecgraf.puc-rio.br>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Multi-hop access keeps asking for password on second machine
Date: Tue, 19 Nov 2024 12:32:59 -0300 [thread overview]
Message-ID: <073036ae-481b-4fdd-95c4-2f542dc84b90@tecgraf.puc-rio.br> (raw)
In-Reply-To: <eae7ce68-1514-41ee-aa08-e10d7b84a4b8@tecgraf.puc-rio.br>
Em 19/11/2024 10:59, Luiz Romário Santana Rios escreveu:
>
> I'll be back soon to report results. Thanks for the help.
>
It looks like your refactoring really did fix my bug. I've been running
Emacs for a couple of hours now and Tramp still hasn't asked my password
unnecessarily. Thanks!
When will this correction hit stable Emacs?
next prev parent reply other threads:[~2024-11-19 15:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 21:06 Multi-hop access keeps asking for password on second machine Luiz Romário Santana Rios
2024-11-19 8:48 ` Michael Albinus
2024-11-19 13:59 ` Luiz Romário Santana Rios
2024-11-19 15:32 ` Luiz Romário Santana Rios [this message]
2024-11-19 16:55 ` 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
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=073036ae-481b-4fdd-95c4-2f542dc84b90@tecgraf.puc-rio.br \
--to=luizromario@tecgraf.puc-rio.br \
--cc=help-gnu-emacs@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.
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).