From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Filipp Gunbin <fgunbin@fastmail.fm>
Cc: 32706@debbugs.gnu.org
Subject: bug#32706: 27.0.50; Gnus ignores gnus-visual nil after gnus-article-outlook-deuglify-article
Date: Thu, 13 Sep 2018 09:02:45 +0900 [thread overview]
Message-ID: <b4mk1nqp8m2.fsf@jpl.org> (raw)
In-Reply-To: <m2k1nrdcsr.fsf@fgunbin.playteam.ru>
On Wed, 12 Sep 2018 18:16:34 +0300, Filipp Gunbin wrote:
> This is a bit confusing to me because of the following.
On Wed, 12 Sep 2018 16:21:55 +0900, Katsumi Yamaoka wrote:
>> ...if gnus-visual is non-nil...
>> the header is buttonized if gnus-treat-buttonize is non-nil even
>> if gnus-treat-buttonize-head is nil, for example.
> 1) gnus-article-add-buttons (invoked when gnus-treat-buttonize is in
> gnus-visual) explicitly skips the headers. How is that possible that
> you see them buttonized?
I realized at last why all the treatment functions run on the
whole article buffer.
1999-01-18 09:40:37 Lars Magne Ingebrigtsen <larsi@gnus.org>
* gnus-art.el (article-goto-body-goes-to-point-min-p): New variable.
(article-goto-body): Use it.
(gnus-treat-article): Ditto.
gnus-treat-article binds a-g-b-g-t-point-min-p to t, that forces
article-goto-body to go to point-min and return always t. So,
the article buffer should be narrowed to the body while performing
`(gnus-treat-article nil)' as I did in the trunk.
> 2) It looks like (gnus-treat-article nil) should take care of
> highlighting itself, so probably we can omit (gnus-article-highlight t)
> in gnus-outlook-display-article-buffer.
I see. I've omitted it in the trunk. Thanks.
next prev parent reply other threads:[~2018-09-13 0:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 20:00 bug#32706: 27.0.50; Gnus ignores gnus-visual nil after gnus-article-outlook-deuglify-article Filipp Gunbin
2018-09-12 7:21 ` Katsumi Yamaoka
2018-09-12 15:16 ` Filipp Gunbin
2018-09-13 0:02 ` Katsumi Yamaoka [this message]
2018-09-13 23:52 ` Filipp Gunbin
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b4mk1nqp8m2.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=32706@debbugs.gnu.org \
--cc=fgunbin@fastmail.fm \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).