-
Notifications
You must be signed in to change notification settings - Fork 19
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
Using backtick #70
Comments
No. Parameters are expanded by default if they are known variables: vim os@name
# opens a file called "manjaro" It should also work for programs: vim (which COMMAND) But that is currently broken. I'll open an issue. |
Okay, thanks. |
Now it stores variable as expected but still cannot work on them I pulled from your repo Aloso/dune branch pipe-stdout |
I think the issue is that |
Is there a workaround?
…On Mon, Nov 1, 2021 at 4:19 PM Ludwig Stecher ***@***.***> wrote:
I think the issue is that which adds a line break after the path.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#70 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALIA54APAC6M4WKHQU7ENZLUJ2HUZANCNFSM5GTYX2SQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
I even tried which removes the newline but it doesn't work |
Is it possible to use shell backtick to expand variables eg.
vim `which COMMAND
The text was updated successfully, but these errors were encountered: