Discovered while double-checking Terminal Links for #342
A terminal link for e.g. ./file.ext will actually link to ssh://<config>/file.ext, i.e. it is handled as an absolute path. Mostly because the RegExp ignores the leading (double) dot.
To add support for relative links, we need a way to keep track of which directory the path is relative to:
Add seamless integrations for most popular shells to (silently) report their work directory (changes) to the extension
Possibly enhance PS1 or similar to write the working directory to stdout and then clear it from the terminal
Same enhancement, but instead of using stdout, use the remote terminal channel (experimental) with a unique terminal identifier
Keep track of whenever the user sends cd ... and assume that'll properly keep track of work directory changes
Could go wrong with denied permissions (detectable?), bash variable/command substitution, other aliases for cd, ...
Discovered while double-checking Terminal Links for #342
A terminal link for e.g.
./file.extwill actually link tossh://<config>/file.ext, i.e. it is handled as an absolute path. Mostly because the RegExp ignores the leading (double) dot.To add support for relative links, we need a way to keep track of which directory the path is relative to:
PS1or similar to write the working directory tostdoutand then clear it from the terminalstdout, use the remote terminal channel (experimental) with a unique terminal identifiercd ...and assume that'll properly keep track of work directory changescd, ...