From: Leo Butler <l.butler@cmich.edu>
To: ding@gnus.org
Subject: Re: gnus-setup-message-winconf-name
Date: Mon, 29 Aug 2011 16:35:33 -0400 [thread overview]
Message-ID: <878vqchs6i.fsf@cmich.edu> (raw)
In-Reply-To: <871uw5jrmb.fsf@cmich.edu>
Leo Butler <l.butler@cmich.edu> writes:
> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>
>> Katsumi Yamaoka wrote:
>>> Leo Butler wrote:
>>>> gnus-configure-windows: No such setting in
>>>> gnus-buffer-configuration': gnus-setup-message-winconf-name
>>
>>> I've never seen such an error though, I suspect it might be due
>>> to a mote having been accidentally added to `gnus-setup-message'.
>>> Here's an extract:
>>
>>> (defmacro gnus-setup-message (config &rest forms)
>>> (let ((winconf-name (make-symbol "gnus-setup-message-winconf-name")))
>>> `(let ((,winconf-name gnus-current-window-configuration))
>>> (gnus-inews-add-send-actions ,winconf ,buffer ,article ,config
>>> ,yanked ',winconf-name)
>>> ^
>>> `winconf-name' is quoted by this extra apostrophe, so it will be
>>> expanded into the symbol `gnus-setup-message-winconf-name', not
>>> the `gnus-current-window-configuration' variable. I'm not quite
>>> sure to remove it is the solution, though.
>>
>> Fixed in git and bzr. Now I'm sure that is the right solution.
>> The reason I've never faced such an error is that I don't use
>> the functions that try to configure the window layout for the
>> setting `gnus-setup-message-winconf-name'. Those functions are
>> `gnus-group-make-nnir-group', `gnus-pick-setup-message', and
>> `gnus-summary-rescan-group'.
>
> It appears that that did fix the problem. Thanks!
Well, I spoke too soon. That change did reduce the number of
times I see this error, but it has occurred since I picked up the fixes
from the git repo. Any additional ideas?
next prev parent reply other threads:[~2011-08-29 20:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 12:15 gnus-setup-message-winconf-name Leo Butler
2011-08-25 16:44 ` gnus-setup-message-winconf-name Dave Abrahams
2011-08-25 20:07 ` gnus-setup-message-winconf-name John Wiegley
2011-08-26 0:09 ` gnus-setup-message-winconf-name Katsumi Yamaoka
2011-08-26 4:25 ` gnus-setup-message-winconf-name Katsumi Yamaoka
2011-08-26 4:47 ` gnus-setup-message-winconf-name John Wiegley
2011-08-28 18:52 ` gnus-setup-message-winconf-name Leo Butler
2011-08-29 20:35 ` Leo Butler [this message]
2011-08-29 23:27 ` gnus-setup-message-winconf-name Katsumi Yamaoka
2011-08-30 20:20 ` gnus-setup-message-winconf-name Leo Butler
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=878vqchs6i.fsf@cmich.edu \
--to=l.butler@cmich.edu \
--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).