Sublime expands file name to absolute path

[KES777]

$ pwd
/home/kes/a
$ pwd -P
/home/kes/work/projects/art
$ /opt/sublime_text/sublime_text Makefile
# Opens file as: /home/kes/work/projects/art/Makefile  # NOT EXPECTED
$ /opt/sublime_text/sublime_text ~/a/Makefile
# Opens file as: /home/kes/a/Makefile

Sublime should use current folder instead of absolute path.

Implement option to expand absolute path if someone need one

Environment

• Operating system and version:
  • Linux Mint 18.0
• Sublime Text:
  • Build 3126

[FichteFoll]

Sublime Text does not treat the working directory in any special way, because a ST session is both directory- and file-independant. I.e. you can open multiple files in a single ST process and they can be any files in your file system. As such, it would make little sense to show only relative paths to the working directory because that makes ST behave inconsistent.

The only part where the working directory matters is when opening files or folders from the commandline, which you displayed as working correctly.

[KES777]

do not understand. Why if file is opened from directory xxx is showed as it is opened from directory yyy

[KES777]

In any case sublime get absolute path. That is right and it should be done. As you said:

they can by any files in your file system

But it is not expected that it resolves sym links too

[FichteFoll]

Your issue is most likely #1548 (#151) then.

I heard that symlink behavior (in the sidebar) might receive some improvements for the next release.

[KES777]

I did not found follows_symlinks option in my configuration files. Neither at preferences nor project settings.

I do not think this issues belongs to the referred one. But I agree that this is some problem with symlinks

[KES777]

Hi. again. I have found this doc

Doc says:

The path may be relative to the project directory, or a fully qualified path

but did not answer:

1. How to setup project directory?
2. How to setup option follow_symlinks without configuring each directory in project root?

Please explain or update doc. thank you.

[KES777]

it would make little sense to show only relative paths to the working directory because that makes ST behave inconsistent.

It would make sense to show relative path the project root. It really makes sense here.

The only part where the working directory matters is when opening files or folders from the commandline, which you displayed as working correctly.

No, it works incorrect

The expected path is: /home/kes/s/lib/App/Schema/Result/Payment.pm
and not /home/kes/work/projects/safevpn/repo2/lib/App/Schema/Result/Payment.pm

So. When sublime text is given relative path and invoked from command line
it should use current path AS IS and should not drop symlinks from it/convert it to physical path

[KES777]

Also path is significant because most of time (exept browser and sublime text) I work in console.
I think, it will be also significant for people who work in console too

[KES777]

I dig a bit and the problem maybe with pwd. Just compare:

~/s/lib $ echo $PWD
/home/kes/s/lib
 ~/s/lib $ /bin/pwd
/home/kes/work/projects/safevpn/repo2/lib

So when sublime text is given relative file name and you turn it into absolute. You should use value from PWD environment variable instead of run pwd command.

Hope this will help.