public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.com
Subject: Re: [cygwin] Issue on output when using javac or scalac under emacs
Date: Wed, 26 Aug 2020 08:16:17 -0400	[thread overview]
Message-ID: <7dfd6884-fc20-5e62-c014-cb6151f7f819@cs.umass.edu> (raw)
In-Reply-To: <f39b995e-c6e5-6676-68e9-6b15520027a6@orange.fr>

On 8/26/2020 2:31 AM, Luc Henninger wrote:
> 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?

Here's a thought.  Emacs NT would be a native Windows build of Emacs, so is definitely organized to 
interact properly with Windows subprocesses.  The Cygwin versions are designed to interact most 
easily with Cygwin subprocesses.  They can probably be made to work with Windows subprocesses, but 
as you found, there is at least one rough edge here.  My first guess would be something to do with 
line endings as they are conveyed back to the parent Emacs - the Windows "extra" CRs may confuse a 
Cygwin Emacs if it is not expecting them.  We sometimes see this with bash scripts brought over from 
Linux to Cygwin.  Anyway, this, or other character set related things, is where I would start to 
diagnose the issue and try different settings.  I would ask questions around what the terminal 
settings are that the subprocesses see, what exact characters are they outputting, etc.

Other are more expert than I in these details and may have specific settings to suggest that you 
look at :-) ...

Regards - Eliot Moss

  parent reply	other threads:[~2020-08-26 12:16 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
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     ` Eliot Moss [this message]
2020-08-26  0:36 ` Issue on output when using javac or scalac under emacs 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=7dfd6884-fc20-5e62-c014-cb6151f7f819@cs.umass.edu \
    --to=moss@cs.umass.edu \
    --cc=cygwin@cygwin.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.
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).