Le 15/01/2015 17:11, Phillip Lord a écrit : >>> I spent some time figuring out how to use it. >>> >>> This is what I did eventually: >>> M-xlentic-mode >>> M-xlentic-mode ;; twice >>> M-x lentic-mode-split-window-below >>> Then change the new buffer to the desired mode (Java mode, C++ mode, >>> whatever). >>> (I was created in fundamental mode). >>> >>> Is this the standard way to use it? >> I also scratched my head before figuring anything out. >> >> I installed from Melpa, and the Melpa Lentic comes with 0 docs, which is sad. > What sort of docs are you looking for? Info? > > > Of course, even when installed from Melpa it is self-documenting in the > sense that the source files are full of documentation. The lentic-org.el > file contains a description of how to convert an existing file from > being an normal el file to an "orgel" file (which is the name I have > given to an el file that converts cleanly to an org file with lentic). > > I could translate these to info (via org-mode and texinfo). But melpa > presents a challenge here, since it works on the source only, and I need > to generate the texinfo from the source, at least as far as I know. So, > unless, I can get MELPA to run arbitrary lisp during build, I do not > know how this would work. Or I could denormalise my git repo and > put the generated files in there; not ideal. > >
One possibility, not as good as info, but quite easy, is given by GitHub. Replace your current README.md with a README.org, in org-mode syntax. Then tell Melpa that the Lentic home page is https://github.com/phillord/lentic. And begin this documentation with a "quick start" chapter. Thierry
