From: dag via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "Michael Albinus" <michael.albinus@gmx.de>
Cc: 46568@debbugs.gnu.org
Subject: bug#46568: 27.1; TRAMP: wrong-argument-type processp: nil on find-file
Date: Fri, 19 Feb 2021 10:00:51 -0600 [thread overview]
Message-ID: <436802c6-6e63-4dad-a539-535d6145cef2@victor> (raw)
In-Reply-To: <87k0r585hg.fsf@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 810 bytes --]
Yes, I think we can close this. I did try tramp-cleanup-all-connections but it didn't help. David On 2021-02-18 14:51, Michael Albinus <michael.albinus@gmx.de> wrote: > > dag <dag@obbligato.org> writes: > > > Hello Michael, > > Hi David, > > > It's a mystery, but it's at least working now, for unknown reasons. > > As I noted in th bug report, things just stopped working without any > > config changes on my end, so I'm not sure what the cause was. Just as > > mysteriously, they're now working again. > > Does this mean, we could close the bug as unreproducible? > > And btw, there could be some cached Tramp values which have made the > problem happen. Next time you see this, you could also check, whether > "M-x tramp-cleanup-all-connections" fixes this for you. > > > David > > Best regards, M
ichael.
[-- Attachment #2: Type: text/html, Size: 1212 bytes --]
next prev parent reply other threads:[~2021-02-19 16:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 19:28 bug#46568: 27.1; TRAMP: wrong-argument-type processp: nil on find-file David Greene via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-16 20:18 ` Michael Albinus
2021-02-18 18:20 ` dag via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-18 20:51 ` Michael Albinus
2021-02-19 16:00 ` dag via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-02-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=436802c6-6e63-4dad-a539-535d6145cef2@victor \
--to=bug-gnu-emacs@gnu.org \
--cc=46568@debbugs.gnu.org \
--cc=dag@obbligato.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).