3 ms·

Probably would have been more helpful to link to the blog post explaining the project - http://nathangrigg.net/2013/09/reproducing-vim-help-as-a-fully-cross-ref

Probably would have been more helpful to link to the blog post explaining the project - http://nathangrigg.net/2013/09/reproducing-vim-help-as-a-fully-cross-referenced-pdf/ http://nathangrigg.net/2013/09/reproducing-vim-help-as-a-ful.... It would be great if the top comments at least had a look at the PDF, and maybe read that blog post - the file is full of hyperlinks (that was the whole point), has a beautiful index viewable in the sidebar of Skim, and he made it because he wanted to read on his iPad, and be able to annotate... Very cool. Would love something similar for Emacs... Maybe it exists, haven't really looked

pelario 13y ago
Of course there's an emacs command to do that
- bo1024 13y ago
  Oh, yeah. Good old C-m M-x M-generate-hyperlinked-documentation.
kroger 13y ago
The Emacs manual is available in many formats, including PDF: http://www.gnu.org/software/emacs/manual/emacs.html http://www.gnu.org/software/emacs/manual/emacs.html
- mheathr 13y ago
  The Emacs documentation is excellent and among the handful of products that have documentation that approaches that of Vim's in any meaningful way, but the PDF does not have interpage links like the one in the OP does. That is not as important as it is with Vim's documentation because of how the documentation is written and because the topics are more self-contained, but it is a significant difference. The documentation within Emacs has such links though and the topics are slightly more discoverable because the documentation can be searched without knowing its prefixes for different sections ahead of time. I have to know that some commands are organized with i_<topic> to find some insert mode documentation for instance with Vim. They are consistent in their semantics though, but that is one gotcha for newcomers and something I did not realize initially. Without that merely doing :h <topic> won't return what the user is actually wanting the documentation for as topics shadow each other in their naming and are made distinct with the naming prefixes.

pelario 13y ago

Of course there's an emacs command to do that

bo1024 13y ago
Oh, yeah. Good old C-m M-x M-generate-hyperlinked-documentation.

kroger 13y ago

The Emacs manual is available in many formats, including PDF: http://www.gnu.org/software/emacs/manual/emacs.html http://www.gnu.org/software/emacs/manual/emacs.html

mheathr 13y ago
The Emacs documentation is excellent and among the handful of products that have documentation that approaches that of Vim's in any meaningful way, but the PDF does not have interpage links like the one in the OP does. That is not as important as it is with Vim's documentation because of how the documentation is written and because the topics are more self-contained, but it is a significant difference. The documentation within Emacs has such links though and the topics are slightly more discoverable because the documentation can be searched without knowing its prefixes for different sections ahead of time. I have to know that some commands are organized with i_<topic> to find some insert mode documentation for instance with Vim. They are consistent in their semantics though, but that is one gotcha for newcomers and something I did not realize initially. Without that merely doing :h <topic> won't return what the user is actually wanting the documentation for as topics shadow each other in their naming and are made distinct with the naming prefixes.