Gnus development mailing list
 help / color / mirror / Atom feed
From: Josh Huber <huber@alum.wpi.edu>
Subject: Re: message-utils.el: some remarks
Date: Fri, 07 Jun 2002 10:49:21 -0400	[thread overview]
Message-ID: <87n0u7b0um.fsf@alum.wpi.edu> (raw)
In-Reply-To: <vafadq7gt46.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de>

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> * The filename could be shorter, to comply with whatever rule we
>   have for filenames.  Maybe mess-util.el or messutil.el?

Is there a rule for filenames?  Personally, I'd rather keep the longer
name than rename it to something which isn't as clear.

> * There should be default keybindings for all them functions, as
>   well as menu entries.  The commentary at the beginning of the file
>   has a menu structure; the keys cannot be used because C-c <letter>
>   is reserved for the user.

Yeah, that would be very nice.  Actually I hadn't even looked in that
file until now -- it has some handy functions!  Perhaps my
message-to-list-only would belong in there instead of in the
message.el propper.  (plug: C-c C-l in message mode is cool! ;)

> * Should message-strip-subject-was be added to message-setup-hook by
>   default, as suggested by the commentary?

I think it should be.  If anything, we should also have a default
keybinding for the subject change function.  that's pretty handy,
IMHO.

> Or should the contents of message-utils.el be moved to message.el,
> as suggested there?  I'm not sure about this.

I'd rather keep them separate, but that's just me.

-- 
Josh Huber



  reply	other threads:[~2002-06-07 14:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-07 12:39 Kai Großjohann
2002-06-07 14:49 ` Josh Huber [this message]
2002-06-07 15:25   ` Simon Josefsson
2002-06-07 16:55   ` Kai Großjohann
2002-06-24 16:14   ` David Kågedal
2002-06-07 15:27 ` 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=87n0u7b0um.fsf@alum.wpi.edu \
    --to=huber@alum.wpi.edu \
    /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).