From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Issue on output when using javac or scalac under emacs
Date: Tue, 25 Aug 2020 20:50:36 -0600 [thread overview]
Message-ID: <71b2831a-710a-688e-a0bd-775b6ed6fd6c@SystematicSw.ab.ca> (raw)
In-Reply-To: <9d7d9903-5a88-6320-5f0a-f966d3f0e5ce@cs.umass.edu>
On 2020-08-25 18:36, Eliot Moss wrote:
> Dear Luc
> You should be aware that while Cygwin can invoke Java, the Windows Java still
> expects _Windows-style_ arguments, including Windows paths, etc.
> > For example, not a/b/c:d/e but 'a\b\c;d\e" for a path.
>
> Just because you're using Cygwin, the installed Java is not "magically"
> transported to the Linux world!
>
> You may also run into issues around line endings (CR/LF vs LF only, and so forth).
Many Windows APIs and programs accept either path separator and in such cases
there are seldom issues as long as the paths are not too long e.g. try:
$ /proc/cygdrive/c/Windows/System32/icacls path/with/slash/delimiters
and many programs, including editors and terminals, do a good job of adapting to
line endings, including mintty and less.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in IEC units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2020-08-26 2:50 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 ` [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 [this message]
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=71b2831a-710a-688e-a0bd-775b6ed6fd6c@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).