From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Editors set x-bit (sometimes)
Date: Tue, 13 Dec 2016 13:54:00 -0000 [thread overview]
Message-ID: <7bbc7866-32f9-1c22-c39e-e7cc92e28222@cornell.edu> (raw)
In-Reply-To: <1481625566.176738.817340945.718D9CF0@webmail.messagingengine.com>
On 12/13/2016 5:39 AM, Ronald Fischer wrote:
> Does anybody have an explanation for the following strange phenomenon?
>
> When I create Ruby files (*.rb) with an, the files end up with the x-bit
> set with some editors, while this does not happen with some other
> editors. This is annoying, because when I use git to put the file in a
> repository, and the repository is later read on Linux, the incorrect
> x-bit is applied there too. The text editors where this happens, do so
> consistently, as long as the file is below my Ruby HOME directory. It
> does not happen, if I store the file outside my $HOME, say in c:\tmp.
>
> Since a few editors do not show this behaviour, one might blame the way
> the editor creates the file. However, these text editors were not
> written with a Cygwin environment in mind, and Windows doesn't have the
> concept of an "executable bit", and it happens only if I create files
> below my Cygwin Home, so I think this happens when Cygwin tries to
> "infer" the x-bit from some other file properties.
Does this help?
https://cygwin.com/faq/faq.html#faq.using.same-with-permissions
Ken
--
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 prev parent reply other threads:[~2016-12-13 13:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 10:39 Ronald Fischer
2016-12-13 13:54 ` Ken Brown [this message]
2016-12-13 15:20 ` Ronald Otto Valentin Fischer
2016-12-13 19:03 ` Brian Inglis
2016-12-13 19:47 ` Achim Gratz
2016-12-13 20:15 ` Henry S. Thompson
2016-12-14 13:37 ` Nellis, Kenneth
2016-12-14 17:35 ` Andrey Repin
2016-12-14 18:23 ` Achim Gratz
2016-12-14 20:28 ` Nellis, Kenneth
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=7bbc7866-32f9-1c22-c39e-e7cc92e28222@cornell.edu \
--to=kbrown@cornell.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).