Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: gnus-buffer-configuration and wide screens
Date: Mon, 07 May 2012 15:45:06 +0900	[thread overview]
Message-ID: <b4mhavs7aml.fsf@jpl.org> (raw)
In-Reply-To: <871umwvauy.fsf@ucl.ac.uk>

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.
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
    ...)
+ )

> 2. I have tried adding the "server" buffer to the group display, again
>    for symmetry, but this doesn't seem to work.  The server buffer
>    becomes inactive.  I haven't explored this one fully so I may have
>    done something wrong.  However, if anybody has the server buffer
>    shown simultaneously with the group buffer, can you please send me
>    your buffer configuration settings?  Anyway, this one is much less
>    important than point 1 above!

How about this one?

(group
 (horizontal 1.0
	     (group 0.6 point)
	     (progn (gnus-group-enter-server-mode)
		    '(server 1.0))))



  reply	other threads:[~2012-05-07  6:45 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 [this message]
2012-05-07 11:43   ` Eric Fraga
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=b4mhavs7aml.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --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).