From: David Moore <dmoore@UCSD.EDU>
Subject: Re: message-expand-group doesn't grok "nnml:foo" groups
Date: 27 Jan 1997 09:14:00 -0800 [thread overview]
Message-ID: <rvu3o36nxj.fsf@sdnp5.ucsd.edu> (raw)
In-Reply-To: Kai Grossjohann's message of 27 Jan 1997 12:12:58 +0100
Kai Grossjohann <grossjohann@charly.informatik.uni-dortmund.de> writes:
> I have done a quick hack which sort of seems to work:
>
> ;; from message.el
> (defun message-expand-group ()
> (let* ((b (save-excursion (skip-chars-backward "^, :\t\n") (point)))
> ^
> removed colon here ---'
>
> What's the right way to do this?
You could set the beginning to the larger of the points found by
your search with removed colon and the spot just after the ':' of the
header name. Otherwise, things won't work well if someone has no space
after the first colon.
--
David Moore <dmoore@ucsd.edu> | Computer Systems Lab __o
UCSD Dept. Computer Science - 0114 | Work: (619) 534-8604 _ \<,_
La Jolla, CA 92093-0114 | Fax: (619) 534-1445 (_)/ (_)
<URL:http://oj.egbt.org/dmoore/> | In a cloud bones of steel.
prev parent reply other threads:[~1997-01-27 17:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-01-27 11:12 Kai Grossjohann
1997-01-27 17:14 ` David Moore [this message]
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=rvu3o36nxj.fsf@sdnp5.ucsd.edu \
--to=dmoore@ucsd.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).