This adds the faust
filetype for Faust .dsp
and .lib
files.
The .lib
file extension was marked as being for COBOL files, but I couldn't find any evidence to support .lib
being an extension that's used by COBOL (see sources below), so I reassigned it to Faust, which does use the .lib
extension (example). If anyone can find a .lib
file in COBOL, I'll gladly write a file type detector for it, but I would need to see it in order to know what I'm detecting.
Sources proving that COBOL doesn't use .lib
:
.lib
as an extension.lib
as an extension they detect as a COBOL file..lib
files on github are all in repos that do not contain any COBOL codehttps://github.com/vim/vim/pull/14894
(1 file)
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
It might be a good idea to email the Cobol runtime files maintainer (Ankit Jain aja...@yahoo.co.in) and see if they can offer an explanation for this extension. It appears to have been assigned to Cobol for at least twenty five years.
Linguist doesn't recognise it as a Cobol extension either.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Thanks. Another issue: *.dsp
is already used for Makefiles
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Yes, I just noticed that - I'll write a detector for it. It seems like checking for #
characters at the beginnings of lines, no semicolons ;
at the ends of lines, and looking for keywords like ifeq
and endif
could be a good way of doing this.
Example .dsp
in Makefile: https://github.com/alberto-fc/csr-spi-ftdi/blob/21cda76812b916bb8e31097c389fe6b82fcb8512/obj-win32/Makefile.dsp
Example .dsp
in Faust: https://github.com/magnetophon/lamb/blob/a2151cfd20c9827c92fb6fc092dc367b2b40d450/lamb.dsp
Also, I've never submitted a PR here before. Should this PR touch the same files as #12363?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
@PowerUser64 I think it is safe to remove .lib from COBOL filetype detector as it is not a standard COBOL extension. Standard types are .cbl and .cob and .cpy for copybooks.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
I think #12363 is a good example, which you can use as a template for you changes. Thanks for working on that.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
@PowerUser64 pushed 1 commit.
—
View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.
Good news, it turns out that Make doesn't actually use the .dsp
extension. Rather it's used by a discontinued program called Microsoft Developer Studio, hence the Developer Studio Project .dsp format. What's nice is these files are auto-generated, and all seem to have the same text at the top, "# Microsoft Developer Studio Project File". The format of the file is the same as that of Makefile, hence the association. I added in a few extra tests for things like keywords and comments for good measure.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
@PowerUser64 pushed 1 commit.
You are receiving this because you are subscribed to this thread.
@PowerUser64 pushed 1 commit.
You are receiving this because you are subscribed to this thread.
Cool, tests pass. By the way, any idea why https://github.com/vim/vim/actions/runs/9557808149/job/26345595245?pr=14894#step:11:15186 failed?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Thanks, those 2 failing ones are known flaky ones.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
thanks, looks good now.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Thanks for the review!
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.