Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Treemacs not updating with docker Tramp mode in Emacs 29 #1081

Open
cphoward opened this issue Dec 28, 2023 · 4 comments
Open

Treemacs not updating with docker Tramp mode in Emacs 29 #1081

cphoward opened this issue Dec 28, 2023 · 4 comments

Comments

@cphoward
Copy link

I'm not getting any errors, I cannot find a definitive answer if treemacs supports /docker:container-id:/path. Does treemacs support the new build-in /docker:... TRAMP mode?

@Alexander-Miller
Copy link
Owner

I don't know. Internally treemacs just calls primitives like directory-files. If those can deal with docker then in theory treemacs should be able to do that as well.

I remember an issue in the past where treemacs would incorrectly transform a tramp path, maybe something similar is happening here as well. Call treemacs-edit-workspaces and check whether the path you see in the listing has been changed from what you've originally given.

Copy link

stale bot commented Mar 2, 2024

This issue has been automatically marked as stale because it has not had recent activity (this bot only works as a reminder, it will not close issues).

@stale stale bot added the stale label Mar 2, 2024
@nettoyoussef
Copy link

I would like to just point out for anyone that is researching this problem that creating tunnels using different methods, such as ssh and docker, will create this issue.

So, if, e.g., you have a path that is like /ssh:user@machine|docker:root@container, that gets transformed in /docker:root@container afterwards (and of course, treemacs cannot find the path, since it is not in the local machine).

One solution, as @Alexander-Miller point out, is to edit manually the paths using treemacs-edit-workspaces. I don't know if there is a better way, though.

@stale stale bot removed the stale label Nov 6, 2024
Copy link

stale bot commented Jan 5, 2025

This issue has been automatically marked as stale because it has not had recent activity (this bot only works as a reminder, it will not close issues).

@stale stale bot added the stale label Jan 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants