-
Notifications
You must be signed in to change notification settings - Fork 20
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
Use call instead of execute before system to run external commands #6
Conversation
Hmm, what else are you changing to make it open with the firefox executable? Did you just override something in this? |
Actually, it is odd that execute was working. |
Hmm yea it just returns the string output of the command I think. Which in this case I don't care about. |
I'm still worried about that being the root of the issue. I saw the same error message a few times during development because of unquoted URLs. |
I think this is still a pretty safe fix, I don't think it will mess any one up. Do you agree @justinmk |
Yes! |
Use call instead of execute before system to run external commands
@a-sk I'd still like to hear what you did to make it default to using firefox as the executable. I've thought about allowing customization of the commands via variables which may make whatever you did a little easier. |
@Keithbsmiley And of course, customization of the commands via variables would be nice. |
Ok cool. So as long as your patch fixed it for you we're good here. And I'll add command customization shortly. |
Ok, thanks :) |
Before this commit, calling of investigate produced
E492: Not an editor command
error.For example I got this error in
:message
for bash files:Not an editor command: firefox https://encrypted.google.com/search?q=exec&sitesearch=ss64.com^@