Skip to content

Treat original and symlinked folder the same way #458

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

Open
aik099 opened this issue Feb 14, 2025 · 2 comments
Open

Treat original and symlinked folder the same way #458

aik099 opened this issue Feb 14, 2025 · 2 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@aik099
Copy link

aik099 commented Feb 14, 2025

Use case:

  1. the /home folder is a symlink to a /mnt/UserData/home folder (mounted from another disk)
  2. sometimes I access the folder doing cd /home/username and sometimes doing cd /mnt/UserData/home/username
  3. mcfly is seeing them as 2 different folders and keeping separate command histories for both

Suggestion:

This is good in general, but in case of symlinks I suggest tracking history based on a path where symlink resolves into.

@cantino cantino added enhancement New feature or request help wanted Extra attention is needed labels Feb 17, 2025
@cantino
Copy link
Owner

cantino commented Feb 17, 2025

Seems reasonable, but might be hard in practice. Happy to accept PRs around this.

@aik099
Copy link
Author

aik099 commented Feb 17, 2025

Ah, maybe I've overcomplicated things. What I was actually doing:

  1. accessing the VM via OS's SSH Client > going to the /home/username/folder folder > executing my commands;
  2. accessing the VM via PhpStorm's SSH Client, which was automatically going to the /mnt/UserData/home/username/folder folder automatically > executing my commands.

Now I've found the way how to teach PhpStorm to automatically go to the /home/username/folder folder and McFly is picking up the correct history automatically. So for me this isn't a problem anymore.

If you'd like, you can close this ticket now. If somebody has the same problem, then they could use that solution as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants