From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 25526@debbugs.gnu.org
Subject: bug#25526: 26.0.50; Gnus sometimes doesn't show article header fully
Date: Thu, 12 Apr 2018 14:52:43 +0900 [thread overview]
Message-ID: <b4mmuy96kes.fsf@jpl.org> (raw)
In-Reply-To: <b4ma8afo90w.fsf@jpl.org>
On Thu, 12 Apr 2018 00:34:06 +0200, Lars Ingebrigtsen wrote:
> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>> I was sometimes annoyed with this problem, but I have found
>> neither a cause of it nor a solution so far. But this is a
>> workaround I found today:
>> (add-hook
>> 'gnus-article-prepare-hook
>> (lambda ()
>> (save-selected-window
>> (select-window (get-buffer-window gnus-article-buffer))
>> (goto-char (point-min)))))
Oh, I totally forgot the problem bacause of having set this hook,
but by removing the hook I confirmed it still exists. Thank you
for following this up.
> Did you try to do the same thing, only just putting it into the Gnus
> source code? :-) It kinda looks like the right thing to do, but I
> don't know anymore what with the hooks and stuff for dedicated windows
> and stuff...
I tried this,
--- gnus-art.el~ 2018-03-25 21:34:24.056766300 +0000
+++ gnus-art.el 2018-04-12 05:50:51.190490800 +0000
@@ -4699,2 +4699,6 @@
(gnus-configure-windows 'article)
+ ;; Make sure the article begins with the top of the header.
+ (save-selected-window
+ (select-window (get-buffer-window gnus-article-buffer))
+ (goto-char (point-min)))
(gnus-run-hooks 'gnus-article-prepare-hook)
and verified it does the trick, too. The point is that to select
the article window while performing (goto-char (point-min)).
Regards,
next prev parent reply other threads:[~2018-04-12 5:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 8:09 bug#25526: 26.0.50; Gnus sometimes doesn't show article header fully Katsumi Yamaoka
2018-04-11 22:34 ` Lars Ingebrigtsen
2018-04-12 5:52 ` Katsumi Yamaoka [this message]
2018-04-12 11:19 ` Lars Ingebrigtsen
2018-04-12 23:19 ` Katsumi Yamaoka
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=b4mmuy96kes.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=25526@debbugs.gnu.org \
--cc=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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.