From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: many-to boring header (was Re: long-to boring header)
Date: 25 Oct 1997 00:20:15 +0200 [thread overview]
Message-ID: <m3ra9akdls.fsf@sparky.gnus.org> (raw)
In-Reply-To: dsg@linus.mitre.org's message of "13 Oct 1997 12:46:35 -0400"
dsg@linus.mitre.org (David S. Goldberg) writes:
> Sounds reasonable. Here's one such implementation. I've also patched
> gnus.texi to document it.
Thanks for the patch; I've applied it to Quassia Gnus v0.13.
> One thing that I found kind of weird while
> working on this: My first thought was to simply re-search-forward to
> the first `to' header and call (gnus-article-hide-header "to"). Go
> back to the beginning and try again. Repeat until none left.
[...]
> But... if I selected the *Article* buffer (after reading it),
> turned off read-only and explicitly called (gnus-article-hide-header
> "to") via eval-expression, it did the "right" thing and got rid of
> each instance of the header in succession. I'm curious as to why this
> happens.
Because the Gnus function binds `inhibit-point-motion-hooks', which
means that it treats intangible text as tangible.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1997-10-24 22:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-07 17:39 long-to boring header David S. Goldberg
1997-10-12 21:53 ` Lars Magne Ingebrigtsen
1997-10-13 16:46 ` many-to boring header (was Re: long-to boring header) David S. Goldberg
1997-10-24 22:20 ` Lars Magne Ingebrigtsen [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=m3ra9akdls.fsf@sparky.gnus.org \
--to=larsi@gnus.org \
/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).