From: Greg Thompson <gregt@visix.com>
Subject: message.el bugout in message-buffer-name in 5.2.6
Date: 04 Jun 1996 10:14:17 -0400 [thread overview]
Message-ID: <1ln32jk66e.fsf@zagato.visix.com> (raw)
message-buffer name was invoking mail-extract-address-components with
nil. the following patch is probably non-optimal (i make no claims at
being an elisp guy), but it works for me.
*** message.el~ Tue Jun 4 07:45:49 1996
--- message.el Tue Jun 4 09:43:59 1996
***************
*** 2170,2181 ****
(if message-generate-new-buffers
(generate-new-buffer-name
(concat "*" type
! (if (or to group)
(concat " to "
(or (car (mail-extract-address-components to))
! to)
! (if group (concat " on " group) ""))
"")
"*"))
(format "*%s message*" type)))
--- 2170,2181 ----
(if message-generate-new-buffers
(generate-new-buffer-name
(concat "*" type
! (if to
(concat " to "
(or (car (mail-extract-address-components to))
! to) "")
"")
+ (if group (concat " on " group) "")
"*"))
(format "*%s message*" type)))
--
-greg ego is beast and ego is evil
but ego knows best,
at least she says so
-the god machine
reply other threads:[~1996-06-04 14:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1ln32jk66e.fsf@zagato.visix.com \
--to=gregt@visix.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.
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).