From: Noam Postavsky <npostavs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: INFOPATH on MSYS(2) (WAS: Emacs 26.1 on Windows is HUGE)
Date: Wed, 1 May 2019 10:22:08 -0400 [thread overview]
Message-ID: <CAM-tV-99iEHyVG5ibT9hbLfQwg_6pjH9vTwes89ZME_6UfXgUQ@mail.gmail.com> (raw)
In-Reply-To: <C824F647-93FC-4AA8-A76B-6D1A4694264D@gnu.org>
On Wed, 1 May 2019 at 00:04, Eli Zaretskii <eliz@gnu.org> wrote:
> > ??? You mean MSYS2 Bash doesn't convert the colons to semi-colons (and
> > the /d/foo/bar file names to Windows d:\foo\bar) when they pass
> > INFOPATH to native MS-Windows programs? That's a terrible bug. Doing
> > these conversions are the main reason for MSYS existence, and the main
> > difference between it and Cygwin.
> I just checked, and MSYS does perform this conversion, both on INFOPATH and on any other FOOPATH variable that looks like a list of directories.
>
> So INFOPATH should look in MinGW Emacs as expected, separated by semi-colons. If it doesn't happen for you, there's some other factor at work here.
>
It seems that it does perform the conversion, but in doing so drops
the the trailing colon.
$ export INFOPATH=/c/foo:/c/bar:
$ emacs -Q --batch --eval '(print (getenv "INFOPATH"))'
"C:\\foo;C:\\bar"
next prev parent reply other threads:[~2019-05-01 14:22 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-14 22:01 Emacs 26.1 on Windows is HUGE Björn Lindqvist
2019-04-15 1:40 ` Óscar Fuentes
2019-04-15 11:42 ` Phillip Lord
2019-04-15 14:55 ` Óscar Fuentes
2019-04-15 17:00 ` Phillip Lord
2019-04-16 20:57 ` Björn Lindqvist
2019-04-16 21:19 ` Phillip Lord
2019-04-16 22:18 ` Björn Lindqvist
2019-04-17 2:48 ` Eli Zaretskii
2019-04-17 3:34 ` Óscar Fuentes
2019-04-17 4:13 ` Eli Zaretskii
2019-04-17 15:28 ` Phillip Lord
2019-04-17 16:41 ` Eli Zaretskii
2019-04-19 8:13 ` Tomas Nordin
2019-04-23 15:11 ` Phillip Lord
2019-04-25 19:54 ` Tomas Nordin
2019-04-26 16:22 ` Phillip Lord
2019-04-26 17:56 ` Eli Zaretskii
2019-04-26 20:59 ` Phillip Lord
2019-04-26 21:29 ` Óscar Fuentes
2019-04-27 11:17 ` Phillip Lord
2019-04-27 11:26 ` Eli Zaretskii
2019-04-29 13:55 ` Phillip Lord
2019-04-29 15:12 ` Eli Zaretskii
2019-04-30 9:48 ` Phillip Lord
2019-04-30 15:09 ` Eli Zaretskii
2019-04-30 15:35 ` Óscar Fuentes
2019-04-30 16:05 ` Eli Zaretskii
2019-04-30 21:13 ` Phillip Lord
2019-05-01 2:43 ` Eli Zaretskii
2019-05-01 4:04 ` Eli Zaretskii
2019-05-01 14:22 ` Noam Postavsky [this message]
2019-05-01 17:17 ` INFOPATH on MSYS(2) (WAS: Emacs 26.1 on Windows is HUGE) Eli Zaretskii
2019-05-01 22:07 ` INFOPATH on MSYS(2) Phillip Lord
2019-05-02 2:36 ` Eli Zaretskii
[not found] ` <87pnopx929.fsf@russet.org.uk>
2019-05-11 16:14 ` Emacs 26.1 on Windows is HUGE Phillip Lord
2019-05-13 13:27 ` Óscar Fuentes
2019-04-27 7:14 ` Eli Zaretskii
2019-04-16 20:35 ` Björn Lindqvist
2019-04-16 20:54 ` Óscar Fuentes
2019-04-17 4:09 ` Björn Lindqvist
2019-04-17 15:25 ` Óscar Fuentes
2019-04-17 16:36 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAM-tV-99iEHyVG5ibT9hbLfQwg_6pjH9vTwes89ZME_6UfXgUQ@mail.gmail.com \
--to=npostavs@gmail.com \
--cc=eliz@gnu.org \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.