From: "Richard M. Stallman" <rms@gnu.org>
Cc: michael.cadilhac-@t-lrde.epita.fr, emacs-devel@gnu.org,
monnier@iro.umontreal.ca, eliz@gnu.org, snogglethorpe@gmail.com,
miles@gnu.org
Subject: Re: File modes facilities.
Date: Fri, 21 Oct 2005 13:51:29 -0400 [thread overview]
Message-ID: <E1ET13B-0006X9-Av@fencepost.gnu.org> (raw)
In-Reply-To: <87d5lz3bna.fsf@mahaena.lrde> (message from Michael Cadilhac on Fri, 21 Oct 2005 03:24:25 +0200)
That's what I feared, thanks ;-) So Richard meant to modify the
C function, okey.
Here's what I sent you before, but it bounced because the address
in your message is not the real one.
Part of this package would be good to install. I don't see a need for
the special feature for changing the current file's modes on the next
save. Why wait for that?
I would like a function to set the modes of a file--what you've called
chmod, but I think it should be called set-file-modes.
There IS a function called set-file-modes. It is not interactive. My
idea is to rename that to set-file-modes-internal, and use your chmod
command under the name set-file-modes. It should accept a numeric
mode argument too; that way, existing callers will still work. It
would use file-modes-to-number.
Would you like to work on such a patch?
Have we got legal papers from you for Emacs?
(defvar file-modes 0
"File modes of the file visited in the current buffer. Do not
rely on this variable to know current file modes, use `buffer-file-modes'
instead.")
Please note the rule that the first line of a doc string must always
stand on its own.
next prev parent reply other threads:[~2005-10-21 17:51 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-19 20:09 File modes facilities Michael Cadilhac
2005-10-19 20:35 ` Stefan Monnier
2005-10-19 21:28 ` Michael Cadilhac
2005-10-19 22:19 ` Nick Roberts
2005-10-19 22:44 ` Michael Cadilhac
2005-10-19 22:48 ` Kim F. Storm
2005-10-19 22:57 ` Edward O'Connor
2005-10-19 23:00 ` Michael Cadilhac
2005-10-20 9:04 ` Eli Zaretskii
2005-10-20 10:41 ` Michael Cadilhac
2005-10-20 11:51 ` Romain Francoise
2005-10-20 12:41 ` Eli Zaretskii
2005-10-20 14:18 ` Michael Cadilhac
2005-10-20 16:15 ` Stefan Monnier
2005-10-20 22:16 ` Kim F. Storm
2005-10-21 3:21 ` Stefan Monnier
2005-10-21 8:44 ` Andreas Schwab
2005-10-21 12:59 ` Michael Cadilhac
2005-10-21 14:14 ` Miles Bader
2005-10-21 14:43 ` Kim F. Storm
2005-10-21 16:42 ` Michael Cadilhac
2005-10-21 22:19 ` Richard M. Stallman
2005-10-24 14:02 ` Kim F. Storm
2005-10-24 14:16 ` David Kastrup
2005-10-24 16:02 ` Andreas Schwab
2005-10-24 21:00 ` Kim F. Storm
2005-10-24 14:46 ` Stefan Monnier
2005-10-24 22:14 ` Kim F. Storm
2005-10-24 23:02 ` Stefan Monnier
2005-10-25 8:51 ` Kim F. Storm
2005-10-25 20:29 ` Richard M. Stallman
2005-10-25 15:58 ` Richard M. Stallman
2005-10-25 21:34 ` Kim F. Storm
2005-10-26 8:52 ` Kim F. Storm
2005-10-27 1:31 ` Richard M. Stallman
2005-10-27 1:29 ` Richard M. Stallman
2005-10-21 10:58 ` Kim F. Storm
2005-10-21 11:05 ` Kim F. Storm
2005-10-21 15:07 ` Stefan Monnier
2005-10-21 17:51 ` Richard M. Stallman
2005-10-21 18:43 ` Stefan Monnier
2005-10-22 4:18 ` Richard M. Stallman
2005-10-22 5:39 ` Drew Adams
2005-10-22 6:17 ` Miles Bader
2005-10-22 6:32 ` Drew Adams
2005-10-22 7:33 ` Miles Bader
2005-10-22 7:45 ` Drew Adams
2005-10-23 18:05 ` Stefan Monnier
2005-10-23 18:27 ` Drew Adams
2005-10-24 13:37 ` Richard M. Stallman
2005-10-24 13:40 ` Stefan Monnier
2005-10-24 16:41 ` Drew Adams
2005-10-24 16:59 ` Stefan Monnier
2005-10-24 17:13 ` Drew Adams
2005-10-20 23:38 ` Richard M. Stallman
2005-10-21 0:58 ` Michael Cadilhac
2005-10-21 1:06 ` Miles Bader
2005-10-21 1:24 ` Michael Cadilhac
2005-10-21 17:51 ` Richard M. Stallman [this message]
2005-10-23 23:42 ` Michael Cadilhac
2005-10-24 14:09 ` Kim F. Storm
2005-10-25 15:58 ` Richard M. Stallman
2005-10-20 1:42 ` Kevin Ryde
2005-10-20 2:01 ` Miles Bader
2005-10-20 7:12 ` Michael Cadilhac
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1ET13B-0006X9-Av@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael.cadilhac-@t-lrde.epita.fr \
--cc=miles@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=snogglethorpe@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).