From: Reiner Steib <4uce.02.r.steib@gmx.net>
Subject: Re: Incorporate message-utils.el?
Date: Thu, 12 Sep 2002 15:24:45 +0200 [thread overview]
Message-ID: <v9ptvj1gte.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <vafofb3bexm.fsf@lucy.cs.uni-dortmund.de>
On Thu, Sep 12 2002, Kai Großjohann wrote:
> WIBNI message-utils were autoloaded and mentioned in the menus and in
> the keybindings by default?
ACK.
> Any takers?
For me, it's not clear how to do it. At first, I thought, that it
would be enough to add "(require 'message-utils)" and merge the menu
entries and key-bindings to `message.el' (eventually adjust the
key-bindings to the given conventions).
But Holger Schauer (the original author of message-utils) wrote [1],
that e.g. functions like `message-strip-subject-was' should be
integrated directly into the function building the subject and _not_
be called add a hook afterwards.
Bye, Reiner.
[1] In de.comm.software.gnus:
,----[ news:<whn0x6ulbj.fsf@ipanema.coling.uni-freiburg.de> ]
| Eigentlich sollte eine Funktionalitaet wie message-strip-subject-was
| direkt in der Funktion integriert sein, die das Subject baut und
| nicht als Hook hintendran aufgerufen werden. Es gibt noch mehr
| Kleinigkeiten in dieser Richtung.
`----
--
,,,
(o o)
---ooO-(_)-Ooo--- PGP key available via WWW http://rsteib.home.pages.de/
next prev parent reply other threads:[~2002-09-12 13:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 11:55 Kai Großjohann
2002-09-12 13:24 ` Reiner Steib [this message]
2002-09-12 13:35 ` Kai Großjohann
2002-09-12 20:12 ` Reiner Steib
2002-09-12 23:43 ` Daniel Pittman
2002-09-13 5:25 ` Mark Trettin
2002-09-13 13:15 ` Kai Großjohann
2002-09-13 15:14 ` Reiner Steib
2002-09-13 15:32 ` Kai Großjohann
2002-09-16 18:01 ` Reiner Steib
2002-09-16 19:32 ` Kai Großjohann
2002-12-29 17:21 ` 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=v9ptvj1gte.fsf@marauder.physik.uni-ulm.de \
--to=4uce.02.r.steib@gmx.net \
--cc=reiner.steib@gmx.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).