From: Michael Albinus via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: alexis purslane <alexispurslane@pm.me>
Cc: Dmitry Gutov <dmitry@gutov.dev>,
"71200@debbugs.gnu.org" <71200-done@debbugs.gnu.org>
Subject: bug#71200: TRAMP: Trying to do a project-find-file or (find-directory) using the podman method causes a (wrong-type-argument stringp nil) error
Date: Wed, 29 May 2024 19:01:22 +0200 [thread overview]
Message-ID: <87mso8een1.fsf@gmx.de> (raw)
In-Reply-To: <-wt3_nsE6oodYaxd5JN1ab1NDts1TOBWr_rFbUljxua0xcKmNyivkT0fPfuGOjfHo3WpDoXgmHNH4E7XTizRifFSDmrwblh7AaEbHBppPRc=@pm.me> (alexis purslane's message of "Wed, 29 May 2024 16:38:50 +0000")
Version: 30.1
alexis purslane <alexispurslane@pm.me> writes:
Hi Alexis,
[you've removed the Cc again :-( ]
> I really apologize for not checking this earlier, but it didn't occur
> to me to test this, it came up naturally: if you try to enter a
> distrobox that doesn't exist, Emacs will hang and peg one CPU until
> you hit C-g. But yes I think this bug can be closed for sure
Well, I don't believe it is up to Tramp to check it. For all
container-based methods it is requested that the respective container
is running. In case of toolbox and distrobox, it is sufficient that the
container is created. If not running, it is started then.
Like the other Tramp methods, distrobox offers host name
completion. Typing "C-x C-f /distrobox: TAB" will show you existing
containers.
And yes, closing the bug. Feel free to report further problems. But
likely they won't fit to the scope of this bug report; a new bug report
would be better I believe.
Best regards, Michael.
next prev parent reply other threads:[~2024-05-29 17:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-26 0:12 bug#71200: TRAMP: Trying to do a project-find-file or (find-directory) using the podman method causes a (wrong-type-argument stringp nil) error alexis purslane via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-26 8:11 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-26 11:27 ` alexis purslane via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-26 15:29 ` Dmitry Gutov
2024-05-26 15:33 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-26 15:35 ` alexis purslane via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-26 17:07 ` alexis purslane via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-26 17:14 ` alexis purslane via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-26 17:19 ` alexis purslane via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-26 17:21 ` alexis purslane via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-26 17:26 ` Dmitry Gutov
2024-05-26 17:46 ` alexis purslane via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-26 21:43 ` alexis purslane via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-26 22:44 ` Dmitry Gutov
2024-05-26 22:48 ` alexis purslane via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-27 2:06 ` alexis purslane via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-27 12:44 ` Dmitry Gutov
2024-05-27 7:52 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <C7v2QL8o01X80EawTfTPEJmEJE7I5chjpYb1T1rAaI5YyEkvaC6zxPutPdOgQ9D84zse2AFTGDGvKAVO_ZyDa1WzyLtv8pDNmLPz1-z0IEw=@pm.me>
[not found] ` <87jzjcg92r.fsf@gmx.de>
[not found] ` <gUO8_i1pVrprtCyX4E4Paiklddt5V48SzZehFrtu3wJP5cz8o2SDuUJAOAREvxt6pY45ok96drmglpxaWbCRLKI_Zb5Yul82Yl-qaWoeFeI=@pm.me>
2024-05-29 13:57 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-29 13:59 ` Alexis Purslane via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-29 14:06 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-29 14:41 ` alexis purslane via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-29 16:35 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <-wt3_nsE6oodYaxd5JN1ab1NDts1TOBWr_rFbUljxua0xcKmNyivkT0fPfuGOjfHo3WpDoXgmHNH4E7XTizRifFSDmrwblh7AaEbHBppPRc=@pm.me>
2024-05-29 17:01 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
[not found] ` <efcf8a73-a46d-4c10-9df3-2ddee97583ad@gutov.dev>
2024-05-30 8:47 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87mso8een1.fsf@gmx.de \
--to=bug-gnu-emacs@gnu.org \
--cc=71200-done@debbugs.gnu.org \
--cc=alexispurslane@pm.me \
--cc=dmitry@gutov.dev \
--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).