unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Oleksandr Gavenko <gavenkoa@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: can't access info dir in emacs under msys2
Date: Mon, 10 Oct 2016 17:01:00 +0300	[thread overview]
Message-ID: <87k2dg5mn7.fsf@gavenkoa.example.com> (raw)
In-Reply-To: c259728c-5134-41c7-b25b-8227ee8cae07@googlegroups.com

On 2016-10-03, Bostjan Vilfan wrote:

> 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.

``Info-directory-list`` is the easiest way to extend INFOPATH.

With native Emacs and ``cygwin-mount.el`` you may have:

--8<---------------cut here---------------start------------->8---
  INFOPATH=:/cygdrive/d/home/usr/share/info:/usr/share/info:/usr/local/share/info
  MANPATH=:/cygdrive/d/home/usr/share/man:/usr/share/man:/usr/local/share/man
--8<---------------cut here---------------end--------------->8---

Trailing ``:`` ensure that default search path included in search.

In that way these variables can be used both by Cygwin/MSYS ``info``/``emacs``
and native Emacs. See example in:

  http://hg.defun.work/skel/file/e40a0cc2ec05/.env

Because I have personal info pages store and always use ``cygwin-mount.el`` on
Windows I have:

--8<---------------cut here---------------start------------->8---
  (unless (getenv "INFOPATH")
    (if (eq system-type 'windows-nt)
        (setenv "INFOPATH" (concat (expand-file-name "~/usr/share/info") ":/usr/share/info:"))
      (setenv "INFOPATH" (expand-file-name "~/usr/share/info:"))))

  ;; Assume that cygwin-mount already activated.
  (when (featurep 'cygwin-mount)
    (setenv "INFOPATH" "/usr/share/info/:~/usr/share/info/:")
    ;; Redefine path-separator to UNIX to update Info-directory-list.
    (let ( (path-separator ":") )
      (require 'info)
      (info-initialize) ))
--8<---------------cut here---------------end--------------->8---

-- 
http://defun.work/




  parent reply	other threads:[~2016-10-10 14:01 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
2016-10-07 19:07   ` Eli Zaretskii
2016-10-08  4:18     ` Óscar Fuentes
2016-10-10 14:01 ` Oleksandr Gavenko [this message]
     [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=87k2dg5mn7.fsf@gavenkoa.example.com \
    --to=gavenkoa@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).