From: James Ferguson <james@faff.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Michael Albinus <michael.albinus@gmx.de>, 57676@debbugs.gnu.org
Subject: bug#57676: 29.0.50; Tramp: Unable to close vterm buffer with remote default-directory
Date: Thu, 8 Sep 2022 11:20:10 -0400 [thread overview]
Message-ID: <CAMtGdS=B9b1ooEGFbZ8WtJkyfebgeGkLO+sTZB8mp+GRdnPgiQ@mail.gmail.com> (raw)
In-Reply-To: <87tu5i101v.fsf@gnus.org>
[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]
That's definitely what raises the error, though the comment implies to me
that it's unexpected/undesirable that it is triggered.
On Thu, Sep 8, 2022 at 9:13 AM Lars Ingebrigtsen <larsi@gnus.org> wrote:
> James Ferguson <james@faff.org> writes:
>
> > When trying to close the terminal one way or another (with
> debug-on-error) I now
> > get:
> >
> > Debugger entered--Lisp error: (file-error "File ‘.’ must be absolute")
> > signal(file-error ("File ‘.’ must be absolute"))
> > tramp-error((tramp-file-name "sshx" nil nil "4x02" nil "." nil)
> file-error "File `%s'
> > must be absolute" ".")
> > tramp-file-name-unify((tramp-file-name "sshx" nil nil "4x02" nil "."
> nil) ".")
>
> I think this is the same as bug#57572 -- it's bugging out here:
>
> ;; FIXME: This is a sanity check. When this error
> ;; doesn't happen for a while, it can be removed.
> (or (file-name-absolute-p localname)
> (tramp-error
> vec 'file-error "File `%s' must be absolute"
> localname))
>
> So I guess this sanity check should perhaps be removed? Michael?
>
[-- Attachment #2: Type: text/html, Size: 1765 bytes --]
next prev parent reply other threads:[~2022-09-08 15:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 12:48 bug#57676: 29.0.50; Tramp: Unable to close vterm buffer with remote default-directory James Ferguson
2022-09-08 12:50 ` bug#57676: further info James Ferguson
2022-09-08 13:13 ` bug#57676: 29.0.50; Tramp: Unable to close vterm buffer with remote default-directory Lars Ingebrigtsen
2022-09-08 15:20 ` James Ferguson [this message]
2022-09-10 11:48 ` Michael Albinus
2022-09-10 20:50 ` James Ferguson
2022-09-11 13:14 ` 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='CAMtGdS=B9b1ooEGFbZ8WtJkyfebgeGkLO+sTZB8mp+GRdnPgiQ@mail.gmail.com' \
--to=james@faff.org \
--cc=57676@debbugs.gnu.org \
--cc=larsi@gnus.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).