From: Luc Henninger <luc.henninger@orange.fr>
To: Jason Pyeron <jpyeron@pdinc.us>, cygwin@cygwin.com
Subject: Re: [cygwin] Issue on output when using javac or scalac under emacs
Date: Wed, 26 Aug 2020 08:31:35 +0200 [thread overview]
Message-ID: <f39b995e-c6e5-6676-68e9-6b15520027a6@orange.fr> (raw)
In-Reply-To: <069901d67b36$35b4f370$a11eda50$@pdinc.us>
Le 26/08/2020 à 01:19, Jason Pyeron a écrit :
>> -----Original Message-----
>> From: Luc Henninger
>> Sent: Tuesday, August 25, 2020 6:40 PM
>>
> I'm thick - what the issue? There was no body to the email.
>
>
Hello,
( My previous message dos not contain the text, only the attachments!!! )
For years, I use emacs-nt (the one provided by gnu.org) under cygwin. I
just discover that emacs is also directly provided by cygwin (late is
better than never :-)). So I try to use it successfully up to a
compilation error in one of my program in java.
To compile java (or scala), I use my own makefile that I start from emacs.
In case of error, I encountered a strange output undex emacs_w32 and
emacs_nox compared to emacs_nt (see trace_nox, trace_w32 and trace_nt in
attachment).
I currently use emacs release 27.1 for all emacses, but I verify that I
have the same strange behaviour with emacs 26.3.
Can anybody explain this? and more gane give a workaround?
Regards
--
Luc.Henninger@orange.fr +33 6 32 96 32 27
--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus
next prev parent reply other threads:[~2020-08-26 6:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 22:40 Luc Henninger
2020-08-25 23:19 ` [cygwin] " Jason Pyeron
2020-08-26 2:38 ` Brian Inglis
2020-08-26 6:31 ` Luc Henninger [this message]
2020-08-26 9:17 ` Takashi Yano
2020-08-26 10:09 ` [cygwin] Issue on output when using javac or scalac under emacs solved Luc Henninger
2020-08-26 12:22 ` Eliot Moss
2020-08-26 12:16 ` [cygwin] Issue on output when using javac or scalac under emacs Eliot Moss
2020-08-26 0:36 ` Eliot Moss
2020-08-26 2:50 ` Brian Inglis
2020-08-26 3:51 ` Eliot Moss
2020-08-26 14:35 ` Eliot Moss
2020-08-26 6:49 ` Luc Henninger
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=f39b995e-c6e5-6676-68e9-6b15520027a6@orange.fr \
--to=luc.henninger@orange.fr \
--cc=cygwin@cygwin.com \
--cc=jpyeron@pdinc.us \
/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).