Add content-based filetype detection for application resource files matching extension *.app or *.app.src.
Related: #18835
@jparise @hcs42, does this make sense? Those extensions are generic and the content appears easy to match.
I don't know a lick of Erlang so I may be missing something...or everything.
https://github.com/vim/vim/pull/18842
(4 files)
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
@dkearns pushed 1 commit.
—
View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
@jparise @hcs42, does this make sense? Those extensions are generic and the content appears easy to match.
Yes, this makes sense to me. Like I noted in #18835 (comment), we could also consider constraining these file patterns to their conventional directories, too:
In a development environment, it is acceptable that the .app file for the release resides in the ebin directory, but it is recommended that it is an artifact of the build step. By convention a .app.src located in the src directory is used. This file is nearly identical to the .app file, but certain fields, such as the application version, are replaced during the build step.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Thanks! It looks good to me too.
Maybe a comment above the function would be nice to make it obvious that this is for Erlang application files.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()