Gnus development mailing list
 help / color / mirror / Atom feed
From: Jesper Harder <harder@ifa.au.dk>
Subject: Re: Patch for filesystems that do not support chmod.
Date: Thu, 20 May 2004 03:08:01 +0200	[thread overview]
Message-ID: <m3y8nnnbwu.fsf@defun.localdomain> (raw)
In-Reply-To: <m3y8nox9yx.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Thu, 20 May 2004 01:39:50 +0200")

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Jesper Harder <harder@ifa.au.dk> writes:
>
>> It's not clear to me whether you're saying that `set-file-modes'
>> actually throws an error or you think it _might_ throw an error.
>>
>> But if it does, I'd tend to think it's a bug in XEmacs, which it would
>> be bette to fix there instead of in Gnus.
>
> Hm...  I'm not sure.  Would it be better for the chmod to fail
> silently on some OS-es than letting the user control this explicitly
> and be made aware of the issue?

As far as I can tell, none of the other places in the Emacs sources
where `set-file-modes' is used take any OS specific precautions.

Also, does this only happen for XEmacs+cygwin -- what about
XEmacs+windows, Emacs+windows, Emacs+cygwin, Emacs+dos etc.

If XEmacs+cygwin is the odd man out, I think it would be better to
make it consistant with the other ports.

-- 
Jesper Harder                                <http://purl.org/harder/>



  reply	other threads:[~2004-05-20  1:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-19 12:53 Paul Stodghill
2004-05-19 13:26 ` Jesper Harder
2004-05-19 23:39   ` Lars Magne Ingebrigtsen
2004-05-20  1:08     ` Jesper Harder [this message]
2004-05-20 16:43       ` Lars Magne Ingebrigtsen
2004-05-20 17:08       ` Paul Stodghill
2004-05-20 17:28         ` Paul Stodghill
2004-05-20 23:40           ` Jon Ericson
2004-05-22 23:29           ` Lars Magne Ingebrigtsen
2004-05-20 19:58         ` Jesper Harder
2004-05-20 17:04   ` Paul Stodghill

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=m3y8nnnbwu.fsf@defun.localdomain \
    --to=harder@ifa.au.dk \
    /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 NNTP newsgroup(s).