-
Notifications
You must be signed in to change notification settings - Fork 3
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
ghc-tags seems to choke on CPP ! negation #6
Comments
You need to add these defines to ghc-tags.yaml, like
since The garbled output is an unfortunate consequence of multithreading + GHC calling gcc for preprocessing, I can't do much about this since I can't control gcc's output. If you want readable output in case of errors to figure out which defines you need to add to the configuration, temporarily pass |
Not really sure how to teach it to look for |
Yeah, me neither to be fair 😞 |
Provide a ghc-tags.yaml file to make use of ghc-tags with Hledger easy. ghc-tags is a standalone tool to replace the formerly-builtto -in ":ctags" feature (and I presume ":etags") in GHCi. These walked over the source and produced a TAGS file (in vim-compatible ctags or Emacs-compatible etags format) that allows the relevant editors to quickly navigate around function definitions. ghc-tags trips over some of the CPP used in Hledger. The solution is to provide ghc-tags with explicit CPP defines via a YAML file. However, if a YAML file is provided, one also must specify the source paths, as the tool XORs config file | paths-on-command-line. See <arybczak/ghc-tags#6> for more information. Signed-off-by: Jonathan Dowland <[email protected]>
Provide a ghc-tags.yaml file to make use of ghc-tags with Hledger easy. ghc-tags is a standalone tool to replace the formerly-built-in ":ctags" feature (and I presume ":etags") in GHCi. These walked over the source and produced a TAGS file (in vim-compatible ctags or Emacs-compatible etags format) that allows the relevant editors to quickly navigate around function definitions. ghc-tags trips over some of the CPP used in Hledger. The solution is to provide ghc-tags with explicit CPP defines via a YAML file. However, if a YAML file is provided, one also must specify the source paths, as the tool XORs config file | paths-on-command-line. See <arybczak/ghc-tags#6> for more information. Signed-off-by: Jonathan Dowland <[email protected]>
Provide a ghc-tags.yaml file to make use of ghc-tags with Hledger easy. ghc-tags is a standalone tool to replace the formerly-built-in ":ctags" feature (and I presume ":etags") in GHCi. These walked over the source and produced a TAGS file (in vim-compatible ctags or Emacs-compatible etags format) that allows the relevant editors to quickly navigate around function definitions. ghc-tags trips over some of the CPP used in Hledger. The solution is to provide ghc-tags with explicit CPP defines via a YAML file. However, if a YAML file is provided, one also must specify the source paths, as the tool XORs config file | paths-on-command-line. See <arybczak/ghc-tags#6> for more information. Signed-off-by: Jonathan Dowland <[email protected]>
Provide a ghc-tags.yaml file to make use of ghc-tags with Hledger easy. ghc-tags is a standalone tool to replace the formerly-built-in ":ctags" feature (and I presume ":etags") in GHCi. These walked over the source and produced a TAGS file (in vim-compatible ctags or Emacs-compatible etags format) that allows the relevant editors to quickly navigate around function definitions. ghc-tags trips over some of the CPP used in Hledger. The solution is to provide ghc-tags with explicit CPP defines via a YAML file. However, if a YAML file is provided, one also must specify the source paths, as the tool XORs config file | paths-on-command-line. See <arybczak/ghc-tags#6> for more information. Signed-off-by: Jonathan Dowland <[email protected]>
I often use CPP like:
in my code which seems to trip up ghc-tags (I am using 1.5).
I get an error like:
which is quite "interesting". :)
If you want to reproduce this is with https://github.com/juhp/fedora-repoquery but I don't think that particularly matters.
The text was updated successfully, but these errors were encountered: