Open n171n-sharma opened 3 years ago
Not sure if that was already discussed, but the emerging V language is unfortunately also using the .v file extension.
A configuration option can be given to the user to map the file extension to the required language.
@n171n-sharma are you referring to ripgrep configuration or dumb-jump?
If you want .v
to mean verilog
and not coq
then in your config you should be able to do something like this
(setq dumb-jump-language-file-exts
(append
(list '(:language "systemverilog" :ext "v" :agtype "verilog" :rgtype "verilog"))
dumb-jump-language-file-exts))
this will just put it first in the list so it will be found/used first. Other things people might want to do. Remove a language by extension
(setq dumb-jump-language-file-exts
(seq-filter (lambda (i) (not (equal (plist-get i :ext) "v"))) dumb-jump-language-file-exts))
combine both (in practice you don't really need this but there could be a use-case):
(setq dumb-jump-language-file-exts
(append
(list '(:language "systemverilog" :ext "v" :agtype "verilog" :rgtype "verilog"))
(seq-filter (lambda (i) (not (equal (plist-get i :ext) "v"))) dumb-jump-language-file-exts)))
Thanks for the explanation!
Thanks, this does help.
As discussed in the issue, jump to define works if it is invoked from a "sv" file. But it fails when invoked from a verilog file (ext "v"), as it is treated as coq file. Systemverilog is an extension of the verilog language.
240