-
Notifications
You must be signed in to change notification settings - Fork 125
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
Shortcuts that are symlinks are dereferenced #59
Comments
Intended behavior (canonical paths), please check the answer at #57 (comment). |
I have read the discussion for this issue and the ChangeLog for v0.13, and neither address the exact issue I am pointing. Are you sure this is not an unintentional change that is a side effect of an intentional one? At the very least, the fact that the shortcut appears with its source name in the list but is created with the target name is inconsistent and misleading and needs to be fixed. |
Sorry, that's my fault. I forgot to add the symlink target patch even though it came in my mind. That is likely the issue. Will try fixing it soon. The name needs to be generated from absolute path too instead of canonical |
…ctions to `ShortcutFile` and change shortcut path behaviour The `ShortcutFile` will now store the path instead of the file object This commit will also now pass absolute path of shortcuts when creating intents for shortcuts and widgets instead of canonical path. This will allow path expansion to be done during execution instead of at creation and if underlying symlink destination changes, new destination will be executed. There will still be a security check during execution to check if shortcut is under allowed directories. The shortcut label will now also be generated from absolute path instead of canonical path as mentioned in termux#59 Co-authored-by: Fabian Thomas <[email protected]> Co-authored-by: agnostic-apollo <[email protected]>
…ctions to `ShortcutFile` and change shortcut path behaviour The `ShortcutFile` will now store the path instead of the file object This commit will also now pass absolute path of shortcuts when creating intents for shortcuts and widgets instead of canonical path. This will allow path expansion to be done during execution instead of at creation and if underlying symlink destination changes, new destination will be executed. There will still be a security check during execution to check if shortcut is under allowed directories. The shortcut label will now also be generated from absolute path instead of canonical path as mentioned in termux#59 Co-authored-by: Fabian Thomas <[email protected]> Co-authored-by: agnostic-apollo <[email protected]>
Problem description
When a shortcut is a symlink, it is shown it is own name in the list to create the widget, but then the actual shortcut uses the target of the symlink.
Steps to reproduce
.shortcuts/host1
with basicallyssh $0
.ln -s host1 host2
host2
in the list.Expected behavior
I would expect a widget named
host2
that ssh me tohost2
. Instead, I get a widget namedhost1
that ssh me tohost1
.Additional information
It used to work with Termux:Widget 0.12. I had to re-create all widgets after recently upgrading to 0.13.
The text was updated successfully, but these errors were encountered: