From: "Óscar Fuentes" <ofv@wanadoo.es>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Installing the current emacs-28 branch under Windows 10
Date: Mon, 18 Oct 2021 01:01:22 +0200 [thread overview]
Message-ID: <87lf2rp871.fsf@telefonica.net> (raw)
In-Reply-To: <83a6jcm7ej.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 14 Oct 2021 09:45:24 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> That's a long-standing problem on MSYS2/Mingw-w64 Emacs. The info files
>> are installed, but they are not directly accesible through M-x info. You
>> still can visit an info file and M-x Info-mode.
>
> I don't have this problem here with a MinGW built Emacs.
>
> How come this is "a long-standing problem" about which we have no bug
> report and no solution? Can you tell the details so we could try
> fixing this?
I'm pretty sure it is a problem on our side.
https://github.com/msys2/MINGW-packages/issues/631
next prev parent reply other threads:[~2021-10-17 23:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 9:23 Installing the current emacs-28 branch under Windows 10 H. Dieter Wilhelm
2021-10-12 14:06 ` Eli Zaretskii
2021-10-12 18:02 ` H. Dieter Wilhelm
2021-10-12 18:59 ` Eli Zaretskii
2021-10-13 20:30 ` H. Dieter Wilhelm
2021-10-13 21:28 ` Óscar Fuentes
2021-10-14 6:45 ` Eli Zaretskii
2021-10-17 23:01 ` Óscar Fuentes [this message]
2021-10-17 23:43 ` Óscar Fuentes
2021-10-14 6:33 ` Eli Zaretskii
2021-10-14 15:59 ` H. Dieter Wilhelm
2021-10-14 16:41 ` Eli Zaretskii
2021-10-15 9:26 ` H. Dieter Wilhelm
2021-10-15 10:58 ` Eli Zaretskii
2021-10-16 9:57 ` H. Dieter Wilhelm
2021-10-18 20:13 ` H. Dieter Wilhelm
2021-10-18 20:34 ` Óscar Fuentes
2021-10-19 7:00 ` H. Dieter Wilhelm
2021-10-19 19:43 ` H. Dieter Wilhelm
2021-10-20 11:49 ` Eli Zaretskii
2021-10-20 19:15 ` H. Dieter Wilhelm
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=87lf2rp871.fsf@telefonica.net \
--to=ofv@wanadoo.es \
--cc=eliz@gnu.org \
--cc=emacs-devel@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).