From: Philipp Stephani <p.stephani2@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 41333@debbugs.gnu.org
Subject: bug#41333: 27.0.91; Spurious errors using TRAMP and auto-save-visited-mode
Date: Thu, 16 Jun 2022 19:57:06 +0200 [thread overview]
Message-ID: <CAArVCkQVFNnhNfRbcBD77Dpnujizsbhm1vA5NYxCvU6j4sMpMQ@mail.gmail.com> (raw)
In-Reply-To: <87leu9vrqs.fsf@gnus.org>
Am Mo., 6. Juni 2022 um 15:36 Uhr schrieb Lars Ingebrigtsen <larsi@gnus.org>:
>
> Philipp Stephani <p.stephani2@gmail.com> writes:
>
> > Some observations:
> >
> > - Several file-attributes invocations incorrectly return nil. (Or does
> > TRAMP temporarily remove files to be written?)
> >
> > - Requesting attributes for the bogus file /ssh:HOSTNAME:(("‘/tmp/’") 45
> > 0 0 1589649700 1589649799 1589649799 258048 "drwxrwxrwt" t 19136513
> > -1); i.e., TRAMP doesn't correctly parse the results to extract the
> > filename.
>
> (I'm going through old bug reports that unfortunately weren't resolved
> at the time.)
>
> Do you still see these problems with the current trunk?
I've stopped auto-save-visited-mode for remote files due to this bug,
and recently I've stopped using TRAMP altogether, so personally I
can't reproduce the problem any more. That doesn't mean the root cause
is fixed, though; maybe Michael can make some sense of the logs I
posted?
next prev parent reply other threads:[~2022-06-16 17:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 17:48 bug#41333: 27.0.91; Spurious errors using TRAMP and auto-save-visited-mode Philipp Stephani
2022-06-06 13:36 ` Lars Ingebrigtsen
2022-06-16 17:57 ` Philipp Stephani [this message]
2022-06-17 12:01 ` Lars Ingebrigtsen
2022-06-22 15:27 ` Michael Albinus
2022-07-05 13:11 ` Stefan Kangas
2022-07-05 16:54 ` Michael Albinus
2022-07-05 17:49 ` Stefan Kangas
2022-07-05 19:25 ` 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=CAArVCkQVFNnhNfRbcBD77Dpnujizsbhm1vA5NYxCvU6j4sMpMQ@mail.gmail.com \
--to=p.stephani2@gmail.com \
--cc=41333@debbugs.gnu.org \
--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).