Plugin conflict

[christos-chatzifountas-biotz-io]

I am not sure if i should post it here or on project.nmin issues, there is a conflict with the Clojure Conjure plugin.
Namely conjure creates conjure-log*.cljc buffers and the combination with project.nvim causes the root directory
to create theese files and keep them.

[Olical]

Hmm I don't think I can do much more from my side, I think this might be a project.nvim thing? I set nofile, hidden and no swap file here when creating the log:

conjure/fnl/conjure/buffer.fnl

Lines 15 to 37 in b4b9b90

	(fn upsert-hidden [buf-name new-buf-fn]
	(let [(ok? buf) (pcall nvim.fn.bufnr buf-name)
	loaded? (and ok? (nvim.buf_is_loaded buf))]
	;; This state happens when the user unloads the buffer somehow.
	;; It still exists but is in a bad state, we delete and start over.
	(when (and (not= -1 buf) (not loaded?))
	(nvim.buf_delete buf {}))
	(if (or (= -1 buf) (not loaded?))
	(let [buf (if loaded?
	buf
	(let [buf (nvim.fn.bufadd buf-name)]
	(nvim.fn.bufload buf)
	buf))]
	(nvim.buf_set_option buf :buftype :nofile)
	(nvim.buf_set_option buf :bufhidden :hide)
	(nvim.buf_set_option buf :swapfile false)
	(unlist buf)
	(when new-buf-fn
	(new-buf-fn buf))
	buf)
	buf)))

If there's another hint I can set in order to get it to play nicely I'm more than happy to.

[christos-chatzifountas-biotz-io]

I am not sure, i already opened an issue on project-nvim, with similar wording
ahmedkhalf/project.nvim#176
A work around would be to spawn any files inside /tmp or another specific folder

[Olical]

Hm, but I (iirc) open the buffer under your working directory so that things like LSP can pick up the symbols and understand that buffer as if it was part of your project. Ay least I think so, I don't think it's a temp file? I will need to check the code but doing some family things at the moment.

…

On Mon, 23 Dec 2024, 21:58 Christos Chatzifountas, ***@***.***> wrote: I am not sure, i already opened an issue on project-nvim, with similar wording ahmedkhalf/project.nvim#176 <ahmedkhalf/project.nvim#176> A work around would be to spawn any files inside /tmp or another specific folder — Reply to this email directly, view it on GitHub <#633 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACM6XOYPI3VCJH4LTIZHD32HCBRRAVCNFSM6AAAAABUAMQY22VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRQGM2TONBZGM> . You are receiving this because you commented.Message ID: ***@***.***>