unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: michael@cadilhac.name (Michaël Cadilhac)
To: rms@gnu.org
Cc: juri@jurta.org, dann@ics.uci.edu, emacs-devel@gnu.org
Subject: Re: suggestion for set-file-modes
Date: Sun, 17 Feb 2008 22:01:42 -0500	[thread overview]
Message-ID: <87ir0nhsrt.fsf@cadilhac.name> (raw)
In-Reply-To: <E1JQq94-0002Qv-Ia@fencepost.gnu.org> (Richard Stallman's message of "Sun, 17 Feb 2008 15:29:54 -0500")

[-- Attachment #1: Type: text/plain, Size: 1107 bytes --]

Richard Stallman <rms@gnu.org> writes:

>     > The standard convention when reading a value in the minibuffer is to put
>     > the default value in the prompt and make it available for editing by
>     > M-n.
>
>     First, if we have three different notations, why this one should be
>     preferred as the default one?
>
> Because I made the decision that way.  This is a general policy
> I have adopted for Emacs.
>
> What format the input should have is a separate question.

My question was about the three different notations for file modes, and
why this one (-rwxrwx-wx) should be preferred as the one to express the
default value.  I wasn't questioning the way values are entered in the
minibuffer at all.  I was referring to what you call the format.

-- 
 |   Michaël `Micha' Cadilhac       |  La culture c'est comme la confiture,  |
 |   http://michael.cadilhac.name   |      c'est meilleur avec du pain.      |
 |   JID/MSN:                       |           -- MOI59                     |
 `----  michael.cadilhac@gmail.com  |                                   -  --'

[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2008-02-18  3:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200801201812.m0KICxYl009632@sallyv1.ics.uci.edu>
     [not found] ` <871w7jqiic.fsf@cadilhac.name>
     [not found]   ` <200802112200.m1BM0pke028675@sallyv1.ics.uci.edu>
2008-02-11 23:41     ` suggestion for set-file-modes Michaël Cadilhac
2008-02-16 19:19       ` Juri Linkov
2008-02-16 23:07         ` Michaël Cadilhac
2008-02-16 23:27           ` Juri Linkov
2008-02-17  0:14             ` Michaël Cadilhac
2008-02-17  0:48               ` Juri Linkov
2008-02-17  1:08                 ` Miles Bader
2008-02-17  1:31                   ` Juri Linkov
2008-02-17  2:04                     ` Michaël Cadilhac
2008-02-17  2:21                       ` Miles Bader
2008-02-17 21:54                       ` Juri Linkov
2008-07-29 17:43                   ` Juri Linkov
2008-02-17  1:39                 ` Michaël Cadilhac
2008-02-17 20:29                   ` Richard Stallman
2008-02-18  3:01                     ` Michaël Cadilhac [this message]
2008-02-17 21:57                       ` Juri Linkov
2008-02-17 21:55                   ` Juri Linkov
2008-02-17 22:18                     ` Miles Bader
2008-02-17 22:59                       ` Juri Linkov

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=87ir0nhsrt.fsf@cadilhac.name \
    --to=michael@cadilhac.name \
    --cc=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.org \
    --cc=juri@jurta.org \
    --cc=rms@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 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).