-
Notifications
You must be signed in to change notification settings - Fork 193
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
fix(emacs): only use vfiles in etags action #1764
fix(emacs): only use vfiles in etags action #1764
Conversation
This still has the extra quoting around the regular expression arguments. This is how I see the command
and in a correctly built TAGS file, |
@jdchristensen The command that dune outputs with |
The reason I say that is because I wrote my own
It looks to me as the regex is being passed fine. The quotation you see is an artefact of how dune serialises its internal commands to shell commands. |
f322ea1
to
401f0e5
Compare
No, what etags is getting as "Argument 3" is supposed to be two arguments. The quoting that dune inserts combines them into one argument. But maybe just inserting line breaks in the etags-args file would fix it? |
OK I've managed to fix it. The issue is that we were running the |
Also, Argument 3 has some single quote characters in it that shouldn't be there. |
Signed-off-by: Ali Caglayan <[email protected]>
401f0e5
to
fe44956
Compare
I've also removed the @jdchristensen Can you give this push a go? |
This seems to be working, but I don't see how. There are still extra single quote characters being passed to etags, which should mess it up. It must have some internal code that deletes them. But I think it would be cleaner to not rely on this behaviour. Can dune literally put the contents of a file on the command line? If not, maybe it's cleaner to put the etags command and its args into a script? |
I can try the script method if dune can't create the right command line. |
@jdchristensen The removal of the quote characters is standard shell expansion (i.e. what happens when you shove that expression thorugh sh or bash). This is the same behaviour that the makefile relies on. Feel free to remove any shell behaviours if they are not to your liking. I don't mind keeping them in for something like TAGS however. |
@Alizter I'm going to PR a different method that I think is easier to understand. You can let me know what you think. |
@jdchristensen This should work better.