all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org, ding@gnus.org
Subject: Re: Mail mode vs message mode
Date: Wed, 18 Nov 2009 20:20:58 +0100	[thread overview]
Message-ID: <87lji3od0l.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87r5rvvknw.fsf@stupidchicken.com> (Chong Yidong's message of "Wed, 18 Nov 2009 11:53:55 -0500")

On Wed, Nov 18 2009, Chong Yidong wrote:

> Reiner Steib <reinersteib+gmane@imap.cc> writes:
[ derive message-from-style's default from mail-from-style ]
>> I don't like this.  The current default value of message-from-style
>> tries to avoid quoting if possible and therefore is preferable to
>> `angles'.  BTW, message-mode doesn't handle the value
>> `system-default'.
>
> We should switch the mail-mode default to `angles'.  

mail-from-style already is `angles' in Emacs 23.1, isn't it?

But deriving message-from-style from mail-from-style would change the
latter from `default' to `angles' (as I already tried to explain).

> Not sure what to do about the `system-default' setting; maybe we
> should deprecate it, as I'm not sure it's useful anymore.

AFAICS, in message-mode, setting message-from-style to
`system-default' leads to a plain "From: foo@bar" header i.e. without
the user name (user-full-name).  So probably this is not a problem.

>> If I understand the correctly, the goal is not to provide full
>> compatibility with mail-mode but to have a default mail composition
>> mode that handles MIME correctly.  So how about simply providing a
>> function, say `message-initalize-from-mail-mode' that initializes
>> message variables and hooks from the corresponding mail-mode ones?
>
> One minor problem: Customize would complain about the value being
> changed from the default.  In general, it's not nice to set the default
> value of a variable outside of its defcustom, as that can lead to
> confusion.

Well, it's not really about setting the default value since it is
change made by the user like any other setq change.

> We can do it your way if you really object to making the message-mode
> options default to the corresponding mail-* options, but I'd like to
> know the reasoning first.  (If any of the default values for the mail-*
> options grate, like mail-from-style, we can change them.)

If the message-mode defaults aren't changed by deriving from mail-*, I
don't object.

I'd certainly object to any change that makes message-mode less
"standard" compliant ("standards" like RFCs, GNKSA [1], good common
practice, ...).  Changing the default `message-yank-prefix' to nil
violates GNKSA, item 10 b and c:

,----[ http://www.newsreaders.com/gnksa/cgi/gnksa-form.cgi ]
| 10. Provides adequate quotation and attribution facilities
| 
|    b. Clearly distinguishes quoted material
|    c. Prefixes quoted material with `>' (or `> ' for the "first" followup)
`----

I didn't check all the other variables you listed.

I doubt that adjusting the mail-* default and the message-* defaults
is worth the effort: user who dislike the message-* values may ...

- stay with mail-mode (by customizing `mail-user-agent' back to
  `sendmail-user-agent')

- use the suggested `message-initalize-from-mail-mode' function.

- customize those few options that (s)he really cares about

Bye, Reiner.

[1] GNKSA (The Good Net-Keeping Seal of Approval)
    http://www.xs4all.nl/~js/gnksa/
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/



  reply	other threads:[~2009-11-18 19:20 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-15 21:22 Mail mode vs message mode Chong Yidong
2009-11-15 22:55 ` Xavier Maillard
2009-11-16  2:53   ` Stefan Monnier
2009-11-16  9:56     ` Xavier Maillard
2009-11-17  1:14       ` Miles Bader
2009-11-17 22:59         ` Xavier Maillard
2009-11-16  4:57   ` Miles Bader
2009-11-17 16:51 ` Chong Yidong
2009-11-17 21:10   ` Reiner Steib
2009-11-18 16:53     ` Chong Yidong
2009-11-18 19:20       ` Reiner Steib [this message]
2009-11-19 14:56         ` Teemu Likonen
2009-11-19 16:53         ` Chong Yidong
2009-11-20  0:07           ` Katsumi Yamaoka
2009-11-22 15:55             ` Reiner Steib
2009-11-24  9:19               ` Katsumi Yamaoka
2009-11-25 21:40                 ` Reiner Steib
2009-11-25 23:02                   ` Stefan Monnier
2009-11-25 23:13                     ` Chong Yidong
2009-11-26  1:27                       ` Stefan Monnier
2009-11-26  1:43                         ` Miles Bader
2009-11-28 13:47                           ` Stefan Monnier
2009-11-27  8:41                   ` Katsumi Yamaoka
2009-11-27 14:51                     ` Chong Yidong
2009-11-29  0:32                       ` Katsumi Yamaoka
2009-11-29 18:49                         ` Chong Yidong
2009-11-30  0:00                           ` Katsumi Yamaoka
2009-11-22 15:55           ` Reiner Steib

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=87lji3od0l.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=cyd@stupidchicken.com \
    --cc=ding@gnus.org \
    --cc=emacs-devel@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.