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

Save full path to edited file #16

Closed
alx73n opened this issue Jun 15, 2017 · 2 comments
Closed

Save full path to edited file #16

alx73n opened this issue Jun 15, 2017 · 2 comments

Comments

@alx73n
Copy link

alx73n commented Jun 15, 2017

Hello.
Currently "local-history.path" parameter changes where extention saves edited file with relative path to opened workspace. That's fine but not always.

i.e.

  • set "local-history.path": "c:\history"
  • if we open c:\projects directory.
  • edit file .\hello-world\file.txt
    then history file will be saved to c:\history.history\projects\hello-world.

What if I open the same project from different paths (like current and archive/backup).
History will be messed up.

It would be more consistent if extention saves full path (from root directory inside .history) to file, so that one can find for sure where edited file exists.
like this: c:\history.history\c\projects\hello-world\file-yyyymmddhhmiss3.
like this: c:\history.history\d\projects\hello-world.

The same way works SublimeText and Atom.

Thank you, Alexander.

@zabel-xyz
Copy link
Owner

I had already thought of this alternative. Especially to save a file history when no workspace is loaded (issue 8).
I started something for this purpose, I'll publish it soon ...

zabel-xyz added a commit that referenced this issue Aug 7, 2017
@zabel-xyz
Copy link
Owner

Fix in version 1.3.0
Set new settings 'absolute' to true.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants