From: Eli Zaretskii <eliz@gnu.org>
To: Ergus <spacibba@aol.com>
Cc: 60966@debbugs.gnu.org
Subject: bug#60966: 30.0.50; Emacs -nw on msys2 is not clearing the terminal
Date: Tue, 24 Jan 2023 18:57:54 +0200 [thread overview]
Message-ID: <83mt67hnu5.fsf@gnu.org> (raw)
In-Reply-To: <20230124152429.7ihf3y5naana7khr@Ergus> (message from Ergus on Tue, 24 Jan 2023 16:24:29 +0100)
> Date: Tue, 24 Jan 2023 16:24:29 +0100
> From: Ergus <spacibba@aol.com>
> Cc: 60966@debbugs.gnu.org
>
> It is just a bit weird that emacs shouldn't be called from within the
> msys terminal, maybe a warning message or something may help here. It is
> not terrible, just a bit confusing.
Maybe you should ask mintty developers to look into this? No one
never asked Emacs to support mintty on Windows. But then almost no
one uses the -nw sessions on Windows (why would you want to?).
> gcc -c -mtune=generic -DUSE_CRT_DLL=1 -I /c/Documents and
> Settings/T008593/Downloads/emacs/build/../source/nt/inc -mtune=generic
> -MMD -MF deps/fingerprint.d -MP -g3 -O2 -gdwarf-2 -I. -I../src
> -I../../source/lib -I../../source/lib/../src -DGL_COMPILE_CRYPTO_STREAM
> -o fingerprint.o ../../source/lib/fingerprint.c
>
> So, probably is this the problem??
Yes. Feel free to suggest a patch for configure.ac that would quote
the names. Better yet, don't build Emacs inside directories with
whitespace in their names ;-)
next prev parent reply other threads:[~2023-01-24 16:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87v8l1p3bi.fsf.ref@aol.com>
2023-01-20 16:40 ` bug#60966: 30.0.50; Emacs -nw on msys2 is not clearing the terminal Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-20 19:17 ` Eli Zaretskii
2023-01-23 22:45 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-24 13:16 ` Eli Zaretskii
2023-01-24 15:24 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-24 16:57 ` Eli Zaretskii [this message]
2023-01-31 16:55 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-31 18:04 ` 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
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=83mt67hnu5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=60966@debbugs.gnu.org \
--cc=spacibba@aol.com \
/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).