all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Štěpán Němec" <stepnem@gmail.com>
To: Leo <sdl.web@gmail.com>
Cc: 6675@debbugs.gnu.org
Subject: bug#6675: 23.2; field, header and headers
Date: Tue, 20 Jul 2010 11:06:50 +0200	[thread overview]
Message-ID: <87tynuses5.fsf@gmail.com> (raw)
In-Reply-To: <m1vd8a7jf6.fsf@cam.ac.uk> (Leo's message of "Tue, 20 Jul 2010 07:32:13 +0100")

Leo <sdl.web@gmail.com> writes:

> RFC822, 2822, 5322 all seem very clear about the meaning and use of
> 'field' and 'header'.
>
> However in function names and arguments in message.el and Gnus, header
> usually means 'field' and headers means 'header'. Sometimes field is
> used directly to mean 'field' as in message-fetch-field.
>
> I find this inconsistency confusing. I think message.el and Gnus should
> follow the same terminology used in the RFCs mentioned above and other
> files, for example those in mail/, in Emacs to be consistent with their
> use of 'field' and 'header'.

Just in case you didn't know and it might be of some help/reference:

(info "(gnus)Headers")
(info "(gnus)Terminology")

My take on it is: consistency surely is nice, but I never felt this to
be a problem with Gnus (IOW, I see there is a lot of problems with
inconsistent identifier naming, not only in Gnus, but in Emacs in
general (as in any software of its size), but I don't see a problem with
headers/fields in particular); bigger concern for me is that some
not-necessarily-very-careful-and-well-thought-out change to the manual
or even function names as you seem to suggest would make things only
worse.

Štěpán





  reply	other threads:[~2010-07-20  9:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-20  6:32 bug#6675: 23.2; field, header and headers Leo
2010-07-20  9:06 ` Štěpán Němec [this message]
2010-07-20 20:29   ` Leo
2011-06-30  0:15 ` Lars Magne Ingebrigtsen
2011-06-30  2:28   ` Kevin Rodgers
2011-06-30  2:34     ` Lars Magne Ingebrigtsen
2011-06-30  3:14   ` Glenn Morris
2011-06-30 10:56     ` Lars Magne Ingebrigtsen

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=87tynuses5.fsf@gmail.com \
    --to=stepnem@gmail.com \
    --cc=6675@debbugs.gnu.org \
    --cc=sdl.web@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 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.