From: Katsumi Yamaoka <yamaoka@jpl.org>
To: David Engster <dengste@eml.cc>
Cc: Steinar Bang <sb@dod.no>, ding@gnus.org
Subject: Re: nndrafts folder doesn't display the Drafts menu
Date: Tue, 06 Jan 2009 15:28:54 +0900 [thread overview]
Message-ID: <b4mhc4d7xsp.fsf@jpl.org> (raw)
In-Reply-To: <84hc4d2wjv.fsf@incoming.verizon.net>
>>>>> Dave Goldberg <david.goldberg6@verizon.net>:
>>> This happened to me once a long time ago (very likely in Oort). As I
>>> recall it, I just deleted the drafts folder completely and ran
>>> (gnus-start-draft-setup) by hand and somehow things got fixed.
>>>>> On Mon, 05 Jan 2009 21:51:04 +0100, Steinar Bang <sb@dod.no> said:
>> I did a `C-k' on the folder, saved the .newsrc.eld file, and then
>> evaluated (gnus-start-draft-setup) in the *scratch* buffer, and that
>> didn't fix things.
Ouch! The culprits are me and David, sorry. A workaround that
enables the minor mode `gnus-draft-mode' again is to put this form
in the ~/.gnus.el file:
(defvar gnus-dummy nil)
The symbol `gnus-dummy' is set in the draft group as a group
parameter as follows:
(gnus-dummy . ((gnus-draft-mode)))
It means setting the result of evaluating the `(gnus-draft-mode)'
form to the variable `gnus-dummy'. In that case, what we want is
to evaluate the form, not the result. However, now parameter's
operands got to not be evaluated if the parameters are not bound
variables because of the following change:
2008-12-24 David Engster <dengste@eml.cc>
* gnus-sum.el (gnus-summary-set-local-parameters): Don't bind
parameters that haven't existed as variables as buffer-local variables.
See also the thread:
http://news.gmane.org/group/gmane.emacs.gnus.general/thread=67886
This also breaks similar usages of group parameters like the one
mentioned in the Gnus Info:
,---- (info "(gnus)Group Parameters")
| This can also be used as a group-specific hook function. If you
| want to hear a beep when you enter a group, you could put
| something like `(dummy-variable (ding))' in the parameters of that
| group. `dummy-variable' will be set to the (meaningless) result
| of the `(ding)' form.
`----
David, do you have an idea to fix this?
next prev parent reply other threads:[~2009-01-06 6:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 11:58 Steinar Bang
2009-01-05 12:36 ` Steinar Bang
2009-01-05 19:23 ` Steinar Bang
2009-01-05 20:28 ` Dave Goldberg
2009-01-05 20:51 ` Steinar Bang
2009-01-05 22:54 ` Dave Goldberg
2009-01-06 6:28 ` Katsumi Yamaoka [this message]
2009-01-06 6:46 ` Katsumi Yamaoka
2009-01-06 12:56 ` David Engster
2009-01-06 22:11 ` Katsumi Yamaoka
2009-01-06 6:49 ` Steinar Bang
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=b4mhc4d7xsp.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=dengste@eml.cc \
--cc=ding@gnus.org \
--cc=sb@dod.no \
/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).