public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: cygpath 2.4.0 (32-bits) in error?
Date: Thu, 21 Jan 2016 19:53:00 -0000	[thread overview]
Message-ID: <20160121190902.GD20175@calimero.vinschen.de> (raw)
In-Reply-To: <892d9876668c7f8a417ed63db8befa8a@xs4all.nl>

[-- Attachment #1: Type: text/plain, Size: 1573 bytes --]

On Jan 21 19:34, Houder wrote:
> On 2016-01-21 16:42, Corinna Vinschen wrote:
> >On Jan 21 15:11, Achim Gratz wrote:
> >>Houder <houder <at> xs4all.nl> writes:
> >>> %% uname -a
> >>> CYGWIN_NT-6.1-WOW Seven 2.4.0(0.293/5/3) 2016-01-15 16:14 i686 Cygwin
> >>>
> >>> %% /usr/bin/cygpath -S -u
> >>> /drv/c/Windows/SysWOW64 <==== Nice, the truth is out! ... but do we want
> >>> it here?
> >>> %% /usr/bin/cygpath -S -w
> >>> C:\Windows\system32
> >>> %%
> >>> %% /usr/bin/cygpath -S -U
> >>> /proc/cygdrive/c/Windows/SysWOW64 <==== ditto
> >>
> >>Well
> >>
> >>/usr/bin/cygpath -u $( /usr/bin/cygpath -Sw )
> >>
> >>delivers the right result.  I guess an option to chose which result to
> >>get
> >>might be nice, but I can cope either way.
> >
> >I hate this path redirection stuff.  Patches welcome.  Maybe we should
> >simply replace SysWOW64 with System32, a simple string operation.
> 
> Hi Corinna,
> 
> Did not mean to get you angry ...

It's not you getting me angry here ;)

> do_sysfolders() in cygpath.cc has changed between 2.3.1 and 2.4.0 where
> it attempts to ascertain the 'system directory'.
> 
> The postprocessing after GetSystemDirectoryW() is different ...

Yes, that was necessary to return case-correct paths.  I commited a
patch and hour and a half ago and uploaded a new snapshot to
https://cygwin.com/snapshots/  Please give it a try.


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-01-21 19:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-21 15:45 Houder
2016-01-21 15:53 ` Achim Gratz
2016-01-21 16:01   ` Houder
2016-01-21 17:40   ` Corinna Vinschen
2016-01-21 19:52     ` Houder
2016-01-21 19:53       ` Corinna Vinschen [this message]
2016-01-21 19:56         ` Houder
2016-01-22  5:03           ` Houder
2016-01-22 21:19           ` Corinna Vinschen
2016-01-21 20:10         ` Achim Gratz

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=20160121190902.GD20175@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --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).