Make hasktags command customizable #963
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Good idea, but we need to improve the execution. There was a recent discussion in #891 resulting in the following observation: 'find tags' should never go through haskell-process, it should be invoked directly, outside of cabal repl. Can you please first help with untangling this functionality and then we get proper defcustoms in place? Thanks. |
|
Closing in favor of #964. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Because of some some pretty odd reasons in my setup, I found myself needing to customize the find/hasktags command that haskell-mode runs to generate a TAGS file. Some valid reasons for this being customizable could include having different versions of either hasktags or GNU find. Went ahead and loaded this into my own editor and it appears to work fine.