Custom URL handler executes from wrong working directory
Bug #1841968 reported by
BLuFeNiX
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Terminator |
New
|
Undecided
|
Unassigned |
Bug Description
The default URL handler is able to open files relative to the PWD. For example, Ctrl-clicking on a URL like "foo/bar.txt" will open the path `$(pwd)
Proposed fixes:
1. Execute the custom URL handler from the terminal session's PWD
2. pass the terminal session's PWD as an argument or env variable to the custom URL handler
To post a comment you must log in.
I have created a work-around for this. By modifying my URL handler plugin to prepend the terminal's CWD, we can pass the fully-qualified path to the custom URL handler. However, this requires that the end user maintains forks of all effected plugins, in the case that they want to use a custom URL handler.
``` "/"): .terminals: .last_focused_ term: expanduser( url)
def callback(self, url):
if not url.startswith("~") and not url.startswith(
for terminal in self.terminator
if terminal is self.terminator
return terminal.get_cwd() + "/" + url
else:
return os.path.
```