From: Eric Fraga <e.fraga@ucl.ac.uk>
To: <ding@gnus.org>
Subject: Re: gnus-buffer-configuration and wide screens
Date: Mon, 7 May 2012 21:13:38 +0930 [thread overview]
Message-ID: <87y5p4dxn9.fsf@ucl.ac.uk> (raw)
In-Reply-To: <b4mhavs7aml.fsf@jpl.org> (Katsumi Yamaoka's message of "Mon, 7 May 2012 15:45:06 +0900")
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> Eric S Fraga wrote:
> [...]
>> (article (horizontal 1.0 (article 0.6 point) (summary 1.0)))
>
>> I get an error:
>
>> ,----
>>| Debugger entered--Lisp error: (args-out-of-range 0)
>>| get-char-property(0 invisible)
>>| gnus-summary-show-thread()
>>| gnus-summary-scroll-up(1)
>>| call-interactively(gnus-summary-scroll-up nil nil)
>> `----
>
> Many summary commands assume the point to be in a summary buffer.
Sure but point is allowed to be in the article window and gnus works
just fine with point there although obviously some commands are not
available and/or work differently.
> So, some of the ones, that run (gnus-configure-windows 'article),
> need to be modified like the following, I think.
>
> (defun gnus-summary-* ()
> ...
> (gnus-configure-windows 'article)
> + (gnus-eval-in-buffer-window gnus-summary-buffer
> ...)
> + )
I didn't understand this at all. Sorry.
My question is why cannot point be placed in the article window
automatically using the gnus configuration settings? I can obviously
display the article and then immediately hit "h" to put point in the
article window and gnus works fine when I do so.
>> 2. I have tried adding the "server" buffer to the group display, again
[...]
> How about this one?
>
> (group
> (horizontal 1.0
> (group 0.6 point)
> (progn (gnus-group-enter-server-mode)
> '(server 1.0))))
Thanks. I'll try this out.
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1 + Ma Gnus v0.6
next prev parent reply other threads:[~2012-05-07 11:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 5:06 Eric S Fraga
2012-05-07 6:45 ` Katsumi Yamaoka
2012-05-07 11:43 ` Eric Fraga [this message]
2012-05-08 0:22 ` Katsumi Yamaoka
2012-05-08 1:47 ` Eric S Fraga
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=87y5p4dxn9.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=ding@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).