From: Javier <j@invalid.invalid>
To: help-gnu-emacs@gnu.org
Subject: Re: can't access info dir in emacs under msys2
Date: Fri, 7 Oct 2016 18:28:01 +0000 (UTC) [thread overview]
Message-ID: <nt8pfh$15na$1@gioia.aioe.org> (raw)
In-Reply-To: c259728c-5134-41c7-b25b-8227ee8cae07@googlegroups.com
> however, I am experiencing difficulties in accessing manuals, other
> than the emacs manual and the emacs lisp manual (for example, I
> would like to access the org mode manual). Could someone, please,
> let me know how to set up emacs so that I can access all manuals in
> /msys64/mingw64/share/info.
adding this to .emacs should solve it
(add-to-list 'Info-default-directory-list "/msys64/mingw64/share/info")
Another pesky detail is that there needs to exist a file named 'dir' in
each of the info directories /msys64/mingw64/share/info/dir and
the org-mode manual needs to be listed in the file.
Then hit C-h i and you should see a list of all installed manuals.
Since some manuals are not included in distros (or the distros put
them in the wrong place) you can keep a private info dir with the
manuals that interest you.
(add-to-list 'Info-default-directory-list "~/MY_OWN_INFO_DIR")
and add an entry for each manual in ~/MY_OWN_INFO_DIR/dir
The format of the file is very picky on capitalization.
Mine is
----------------------------------------------------------------
This is the file .../info/dir, which contains the
topmost node of the Info hierarchy, called (dir)Top.
The first time you invoke Info you start off looking at this node.
^_
File: dir, Node: Top This is the top of the INFO tree
This (the Directory node) gives a menu of major topics.
Typing "q" exits, "?" lists all Info commands, "d" returns here,
"h" gives a primer for first-timers,
"mEmacs<Return>" visits the Emacs manual, etc.
In Emacs, you can click mouse button 2 on a menu item or cross reference
to select it.
* Menu:
Python
* Python-3.3: (python-3.3). The Python Documentation
* Python-2.7: (python-2.7). The Python Documentation
* numpy-1.8.0: (numpy-1.8.0). Numpy for python2
* scipy-0.13.3: (scipy-0.13.3). Scipy for python2
* sphinx: (sphinx). Sphinx 1.1.3 Doc
LANGS
* perldoc-all: (perldoc-all). perldoc
MISC
* sicp: (sicp) SICP
next prev parent reply other threads:[~2016-10-07 18:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-03 7:25 can't access info dir in emacs under msys2 Bostjan Vilfan
2016-10-03 13:36 ` Byung-Hee HWANG (황병희, 黃炳熙)
2016-10-03 15:39 ` Bostjan Vilfan
2016-10-03 16:01 ` Eli Zaretskii
2016-10-03 19:33 ` Óscar Fuentes
2016-10-04 6:19 ` Eli Zaretskii
2016-10-04 13:15 ` Óscar Fuentes
2016-10-04 14:46 ` Eli Zaretskii
2016-10-04 15:51 ` Óscar Fuentes
2016-10-04 17:34 ` Eli Zaretskii
2016-10-04 20:47 ` Óscar Fuentes
2016-10-03 13:51 ` Óscar Fuentes
2016-10-03 14:20 ` Thien-Thi Nguyen
2016-10-03 18:53 ` Robert Thorpe
2016-10-07 18:28 ` Javier [this message]
2016-10-07 19:07 ` Eli Zaretskii
2016-10-08 4:18 ` Óscar Fuentes
2016-10-10 14:01 ` Oleksandr Gavenko
[not found] <CAAm34zrx18a0YgDqg=ht1NSg+Q+fbx6nu_oMkwNqfSZpCpg3Dw@mail.gmail.com>
2016-10-05 0:23 ` Robert Thorpe
2016-10-05 2:07 ` Óscar Fuentes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='nt8pfh$15na$1@gioia.aioe.org' \
--to=j@invalid.invalid \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).