Closed vdikan closed 5 years ago
Thanks for contributing! I didn't know about quelpa before. Minor thing: Could you update the commit message so that it conforms to the standard practices? Something like "Add support for the quelpa build tool".
I applied the changes and completed the merge.
Hi! Thank you. Sorry, didn't have time to answer.
By the way, emacs community gurus gave me a hint that there is M-x checkdoc
command that will also interactively guide you for turning module.el file into an emacs package (apart from overall style checking).
You can try it out by invoking M-x checkdoc
for fortran-tags.el
Thanks, I'll check it out!
Hi @raullaasner !
Thank you for what seems to be the best tagging fortran/emacs system on the market! Helps to carry on that burden of a Physics Ph.D student.
With this pull request I'm asking you to enter some package metadata for your plugin, according to this spec. Even if you do not want to bother with packaging and shipping to (m)elpa, it will help installing your package with quelpa-use-package directly from github.
I entered a minimal header; without it quelpa (read: use-package) throws
Package lacks a file header
exception. You might fill the rest of meta and let it be. Below I describe an alternative installation method, without a need to manually pull anything.While emacs's use-package allows to install elisp modules as packages in a sane descriptive way (hooray!),
quelpa
can build them directly from github repos (hooray! x3). Assuming it is switched in your.init.el
:the forran-tags package could be installed with this: