From: Marcel Kilgus <cygwin@mail.kilgus.net>
To: cygwin@cygwin.com
Subject: Breaking change in Cygwin 2.10.0-1
Date: Tue, 13 Feb 2018 19:55:00 -0000 [thread overview]
Message-ID: <9010244566.20180213205520@kilgus.net> (raw)
Yesterday I got to investigate why the unit tests for one of my
projects didn't work anymore. The tests are collected by a short Perl
program that scans all *.c files and generates the test structure.
But... it didn't find some c files anymore :-o I can see them using
"DIR", I can see them in Explorer and everywhere else, but Perl is
completely oblivious to their existence.
It took a while to understand that I recently updated Cygwin and that
this now hides "temporary" files by default. The thing is, this
"temporary" flag on Windows is so obscure that there is no UI to
set/unset it and even if it is set you usually don't notice it. Turns
out my IDE sets the flag by accident, and did so for a decade, I just
never noticed until now! It writes a temporary file and then renames
that to the final name, without removing the flag... but whatever the
reason, even Microsoft occasionally screws this up, apparently:
https://social.technet.microsoft.com/Forums/windows/en-US/5d63a03a-f711-4035-a601-d66994c411eb/microsoft-print-to-pdf-troublesome-t-attribute?forum=win10itproapps
TL;DR: Please roll back the change in fhandler_disk_file.cc, do not
hide files that are otherwise completely visible in all other tools
due to a flag that nobody knows about and that cannot be unset
trivially, not even by Window's own ATTRIB command or Explorer.
Thanks, Marcel
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2018-02-13 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 19:55 Marcel Kilgus [this message]
2018-02-14 14:06 ` Corinna Vinschen
2018-02-14 15:10 ` Marcel Kilgus
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=9010244566.20180213205520@kilgus.net \
--to=cygwin@mail.kilgus.net \
--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).