From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: message-utils.el: some remarks
Date: Fri, 07 Jun 2002 14:39:53 +0200 [thread overview]
Message-ID: <vafadq7gt46.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
I think that message-utils are quite nice, but I do have some minor
remarks.
* The filename could be shorter, to comply with whatever rule we have
for filenames. Maybe mess-util.el or messutil.el?
* 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.
* Should message-strip-subject-was be added to message-setup-hook by
default, as suggested by the commentary?
Or should the contents of message-utils.el be moved to message.el, as
suggested there? I'm not sure about this.
kai
--
~/.signature is: umop 3p!sdn (Frank Nobis)
next reply other threads:[~2002-06-07 12:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-07 12:39 Kai Großjohann [this message]
2002-06-07 14:49 ` Josh Huber
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=vafadq7gt46.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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).