unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: alexis purslane via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: "71200@debbugs.gnu.org" <71200@debbugs.gnu.org>,
	"michael.albinus@gmx.de" <michael.albinus@gmx.de>
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: Sun, 26 May 2024 21:43:14 +0000	[thread overview]
Message-ID: <smZuuGiJU__EMb_Vn40_6LN4V3JlR_Yoc0WEsinx_WknOHF4kdwK5xdhq8AXJorHJGxDPUUBSWQiWrxdqjVNIlOipG5sI4yQUBDqw70QP9M=@pm.me> (raw)
In-Reply-To: <5iagnGUjF-cYYddc4_1kHHViSr60gM5Lt2t0bTESI41QSUxZ3GPGbAhCpmjTawoMcMaB07DPi5_jHc4-m4ow4AKhS3z5evCwxq75_-emwQw=@pm.me>


[-- Attachment #1.1: Type: text/plain, Size: 2439 bytes --]

Follow up:

I have these containers installed:

1. devcontainers/rust:latest
2. devcontainers/typescript-node:latest
3. devcontainers/cpp:latest
4. texlive/texlive:latest
5. tensorflow/tensorflow:latest-gpu

Only one of them wor--

....

Oh.

Git keeps "detecting dubious ownership" over each project's
.git/
for some reason, which prevents `git ls-files` from running,
hence the
problem. So this isn't really a bug per-se, it's more like a lack
of
clear enough errors.

I could also really use some help with getting the ownership and
gpg & ssh
keychain stuff (commits always fail because Magit over TRAMP can't
access my GPG or SSH private keys) figured out over TRAMP but I can get that help
elsewhere.

Anyway, when git ls-files fails, maybe the stderr output it
produced should be
printed instead of just trying to parse its empty stdin and
crashing.

On Sunday, May 26th, 2024 at 5:46 PM, alexis purslane <alexispurslane@pm.me> wrote:

> > Does the ssh transport work with the "more specialized" containers?
> 

> 

> It took me a bit to get that set up, but no, it doesn't. Did essentially this:
> 

> https://linuxhandbook.com/ssh-into-container/
> 

> Created a directory with some files in it in the homedir of the container,
> and then added the project with the location as `/ssh:root@localhost#7655:Folder`.
> It found the folder just fine (eg showed up in completion), but when I added
> it and did project-find-files, I got the same error as usual.
> 

> On Sunday, May 26th, 2024 at 5:26 PM, Dmitry Gutov dmitry@gutov.dev wrote:
> 

> > On 26/05/2024 20:21, alexis purslane wrote:
> > 

> > > Actually, no, installing git does not help resolve the problem
> > > whatsoever. One works, the other two don't, but I can't tell why. The
> > > one that works is my general purpose development container, and the
> > > other two are more specialized, so that may be the origin of the
> > > problem, but it doesn't explain what in particular is missing. What does
> > > project.el rely on the host having installed?
> > 

> > project-find-file just uses 'git ls-files' if it's in a repository, or
> > 'find' otherwise.
> > 

> > If your file name string juggling made things work correctly, it seems
> > unlikely that the problem is in some missing software on the remote host.
> > 

> > Does the ssh transport work with the "more specialized" containers?

[-- Attachment #1.2: publickey - alexispurslane@pm.me - 0x41E61568.asc --]
[-- Type: application/pgp-keys, Size: 649 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]

  reply	other threads:[~2024-05-26 21:43 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 [this message]
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
     [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='smZuuGiJU__EMb_Vn40_6LN4V3JlR_Yoc0WEsinx_WknOHF4kdwK5xdhq8AXJorHJGxDPUUBSWQiWrxdqjVNIlOipG5sI4yQUBDqw70QP9M=@pm.me' \
    --to=bug-gnu-emacs@gnu.org \
    --cc=71200@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).