all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: mismatch between what Emacs considers read-only and file	permissions
Date: Wed, 04 Feb 2015 22:00:09 +0200	[thread overview]
Message-ID: <83h9v1fnw6.fsf@gnu.org> (raw)
In-Reply-To: <slrnmd4u5s.32r.varro@anukis.local>

> From: Will Parsons <varro@nodomain.invalid>
> Date: 4 Feb 2015 19:53:33 GMT
> 
> > My advice is not to mix Cygwin programs with native Emacs on Windows.
> > Good native ports of Unix and GNU software to Windows are available,
> > and you are advised to use them instead, if you don't want to deal
> > with these incompatibilities.
> 
> I've been using Cywin for over a decade and find it far too useful to
> live without.

Unless you are using applications for which native Windows ports are
not available at all, you can have the same usefulness without Cygwin.

> My real question is the second circumstance, where a file with the
> Unix write bit set is marked read-only by Emacs.  Since it only occurs
> when I log in directly as root in console mode (which I don't do that
> often), I can live with that too, using the same method.  By *why*
> does it happen?

Because using sudo doesn't make you root, it only gives you root's
security privileges.



  reply	other threads:[~2015-02-04 20:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-04 17:12 mismatch between what Emacs considers read-only and file permissions Will Parsons
2015-02-04 19:04 ` Eli Zaretskii
     [not found] ` <mailman.19279.1423076671.1147.help-gnu-emacs@gnu.org>
2015-02-04 19:53   ` Will Parsons
2015-02-04 20:00     ` Eli Zaretskii [this message]
     [not found]     ` <mailman.19282.1423080028.1147.help-gnu-emacs@gnu.org>
2015-02-04 20:19       ` Will Parsons
2015-02-05 13:24     ` Stefan Monnier

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=83h9v1fnw6.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.