projectile-compile-projectin a go project, projectile runs
go build ./.... The command finishes without error, but I can find no binary. When I change that to
go build, a binary is created.
go build? I don't want to use
C-u C-c p callways...
make run-projectileI got the following
I've come to rely a lot on
projectile-toggle-between-implementation-and-test to jump between implementation and test when developing Clojure. However when I tried to use it in my Haskell projects it didn't work at all. I found that two things needed adjusting.
The project type was wrongly set to
make. I fixed that by explicitly setting it to
haskell-cabal in my
((nil . ((projectile-project-type . haskell-cabal))))
Second, the test suffix,
Spec, didn't match what I use so I put this in my config:
(with-eval-after-load 'haskell-mode (plist-put (alist-get 'haskell-cabal projectile-project-types) 'test-suffix "Test"))
I'm not very experienced with configuring Emacs, so I'm wondering if this is a good way of doing it, or if there's a better way?
Hey, I have a parent folder
X that is versioned with git. Inside this folder I have a bunch of nested directories and in some of them I have projects that I would like projectile, LSPs and the like to acknowledge. This seems to be very hard as
X is constantly recognized as the project and I haven't found a reliable way to not let that happen.
I never want
X to be considered a project, is there some blocklist I can use.
I have already tried adding
.projectile files to the subfolders that are actual projects. I usually need to reload the file for it to be recognized and even that does'nt seem reliadble as just now the LSP decided that the project is
X even after I manually switched to the subproject.
does anyone know anything that alleviates this issue?