From: Robert Thorpe <rt@robertthorpeconsulting.com>
To: Bostjan Vilfan <bjvilfan@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: can't access info dir in emacs under msys2
Date: Mon, 03 Oct 2016 19:53:08 +0100 [thread overview]
Message-ID: <87k2dptgbv.fsf@robertthorpeconsulting.com> (raw)
In-Reply-To: <c259728c-5134-41c7-b25b-8227ee8cae07@googlegroups.com> (message from Bostjan Vilfan on Mon, 3 Oct 2016 00:25:10 -0700 (PDT))
Bostjan Vilfan <bjvilfan@gmail.com> writes:
> set up emacs so that I can access all manuals in
> /msys64/mingw64/share/info.
As Thien-Thi Nguyen says you can set infopath, and as Eli Zaretski says
that should work. The path needs to be set so that it's seen by Emacs.
You have to make sure the value isn't just local to some instance of
cmd.exe.
I don't do that, instead I do something like this:
(setq Info-additional-directory-list '("C:/MinGW/msys/1.0/share/info"))
Note that the "dir" file in directory you specify has to be correct.
There can sometimes be problems with this on Mingw and derivatives. You
can check that it's correct by running command line info.
BR,
Robert Thorpe
next prev parent reply other threads:[~2016-10-03 18:53 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 [this message]
2016-10-07 18:28 ` Javier
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=87k2dptgbv.fsf@robertthorpeconsulting.com \
--to=rt@robertthorpeconsulting.com \
--cc=bjvilfan@gmail.com \
--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).