Immediately after new installation, I launched MacVim, ":cd"'d to a multi-package Stack project directory, and issued the ",tg" command. I got this:
:!codex update --force
codex: *warning* your configuration has been migrated automatically!
The tags file will now include the tags of the *current* project as well,
if that is not the behavior you want, please edit `~/.codex`.
Cloning into '/Users/dbanas/Documents/Projects/concat/.stack-work/downloaded/GPQk22x75thG'...
remote: Counting objects: 1216, done.
remote: Total 1216 (delta 0), reused 0 (delta 0), pack-reused 1216
Receiving objects: 100% (1216/1216), 228.62 KiB | 0 bytes/s, done.
Resolving deltas: 100% (505/505), done.
codex: No cabal file found.
CallStack (from HasCallStack):
error, called at src/Codex/Project.hs:65:16 in codex-0.5.1.2-2sevYNN39I9LUjjRC8Vu6v:Codex.Project
shell returned 1
:call LoadHscope()
Is codex confused by the layout of a multi-package Stack project (i.e. - no *.cabal file (just stack.yaml) at the top level)?
Immediately after new installation, I launched MacVim, ":cd"'d to a multi-package Stack project directory, and issued the ",tg" command. I got this:
Is codex confused by the layout of a multi-package Stack project (i.e. - no *.cabal file (just stack.yaml) at the top level)?