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

[BUG] Stop quoting entries in history when running them #1961

Closed
1 of 2 tasks
quyykk opened this issue Mar 11, 2024 · 5 comments
Closed
1 of 2 tasks

[BUG] Stop quoting entries in history when running them #1961

quyykk opened this issue Mar 11, 2024 · 5 comments
Labels
bug Incomplete Report - Please follow the guidelines Your report is incomplete and does not follow the guidelines, you may not expect an answer

Comments

@quyykk
Copy link

quyykk commented Mar 11, 2024

Rofi version (rofi -v)

afc65ac

Configuration

n/a

Theme

n/a

Timing report

No response

Launch command

rofi -show run

Step to reproduce

  1. Run say code /path/to/project (it's in history so gets autocompleted)
  2. The full entry is quoted, so it tries to run "code /path/to/project" which is a non-existent command

Expected behavior

I expect the entry to be run unquoted, respecting the arguments passed.

Actual behavior

Quotes the full history entry before running it, result in it trying to run a command that includes the arguments.

Additional information

I saw that this was intentional, so maybe the solution here would be to make the command handling smarter by only quoting the entry if the quoted entry is an actual command in PATH, and if not retain the old behavior (idk if this is feasible, was just an idea).

Note: Another related bug is that, if the command with spaces is not in the history (so no code /path/to/project in history), then the command doesn't get quoted and runs. This seems like an inconsistency that should probably be fixed too.

Using wayland display server protocol

  • No, I don't use the wayland display server protocol

I've checked if the issue exists in the latest stable release

  • Yes, I have checked the problem exists in the latest stable version
@quyykk quyykk added the bug label Mar 11, 2024
@DaveDavenport
Copy link
Collaborator

#1951

@DaveDavenport DaveDavenport closed this as not planned Won't fix, can't repro, duplicate, stale Mar 11, 2024
@DaveDavenport DaveDavenport added the Incomplete Report - Please follow the guidelines Your report is incomplete and does not follow the guidelines, you may not expect an answer label Mar 11, 2024
@quyykk
Copy link
Author

quyykk commented Mar 11, 2024

I don't understand how this is a duplicate. That issue is about having duplicate entries in your history, and this issue is about how commands with arguments are quoted when run (making them fail, because the arguments are not part of the command name).

@DaveDavenport
Copy link
Collaborator

Where did it say it is duplicate, It should be fixed by the fix in that issue.

@quyykk
Copy link
Author

quyykk commented Mar 11, 2024

Oh sorry. But I'm on afc65ac which should include the commit that fixes the linked issue, so it seems like this is still a problem?

Copy link

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 12, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Incomplete Report - Please follow the guidelines Your report is incomplete and does not follow the guidelines, you may not expect an answer
Projects
None yet
Development

No branches or pull requests

2 participants