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

Why does dired-open--start-process use file-truename #218

Open
mbork opened this issue Jun 15, 2024 · 1 comment
Open

Why does dired-open--start-process use file-truename #218

mbork opened this issue Jun 15, 2024 · 1 comment

Comments

@mbork
Copy link

mbork commented Jun 15, 2024

It breaks my workflow (cf. https://xkcd.com/1172/), since it follows symlinks. Does anyone actually need that behavior? If not, can we avoid it? If yes, can we make it configurable?

Note: I'll be happy to actually provide a patch/PR if there is agreement as to what should be done.

@Fuco1
Copy link
Owner

Fuco1 commented Jun 17, 2024

Does it break the working directory? I suppose if it's a symlink and we don't resolve it the application will do so anyway, so that's not really necessary. I think it was used to resolve relative paths, maybe there's a better way for that, if it is even necessary. To be honest I don't know. It was written in 2014 and haven't changed since.

I suppose you can try to change the function in your config and see if it works, then we can change it 🤷

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

No branches or pull requests

2 participants