
With `--fully-qualified` fast-tags also generates qualified tags: ``` GHC.Hs GHC/Hs.hs 21;" m GHC.Hs.Binds GHC/Hs/Binds.hs 20;" m GHC.Hs.Binds.ABE GHC/Hs/Binds.hs 349;" C ... ``` If your code editor can search for qualified tags, I guess it should work. There is a script for Vim (https://github.com/elaforge/fast-tags/blob/master/tools/qualified_tag.py) for example. Sylvain On 23/10/2019 15:26, Matthew Pickering wrote:
I use `fast-tags` which doesn't look at the hierarchy at all and I'm not sure what the improvement would be as the names of the modules would still clash.
If there is some other recommended way to jump to a module then that would also work for me.
Matt
On Wed, Oct 23, 2019 at 12:08 PM Sylvain Henry
wrote: Hi,
How do you generate your tags file? It seems to be a shortcoming of the generator to not take into account the location of the definition file.
Perhaps `HsUtils` and `StgUtils` would be appropriate to disambiguate`Hs/Utils` and `StgToCmm/Utils`.
We are promoting the module prefixes (`Hs`, `Stg`, `Tc`, etc.) into proper module layers (e.g. `HsUtils` becomes `GHC.Hs.Utils`) so it would be redundant to add the prefixes back. :/
Cheers, Sylvain
On 23/10/2019 12:52, Matthew Pickering wrote:
Hi,
The module rework has broken my workflow.
Now my tags file is useless for jumping for modules as there are multiple "Utils" and "Types" modules. Invariable I am jumping to the wrong one. What do other people do to avoid this?
Can we either revert these changes or give these modules unique names to facilitate that only reliable way of navigating the code base. Perhaps `HsUtils` and `StgUtils` would be appropriate to disambiguate `Hs/Utils` and `StgToCmm/Utils`.
Cheers,
Matt _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs