Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: Modify hook in group parameters?
Date: Thu, 15 Oct 2009 07:44:19 +0900	[thread overview]
Message-ID: <b4m3a5ly4sc.fsf@jpl.org> (raw)
In-Reply-To: <yb0ws2ycjfu.fsf@osl2u223.oslo2.fast.no>

>>>>> Steinar Bang wrote:
>>>>>> Katsumi Yamaoka <yamaoka@jpl.org>:

>> I don't know why it takes too much time though.

> The check in is from May 2003, and one of the machines I was running on,
> at that point in time, was the PII 233MHz machine with 128MB of RAM,
> that is the same machine that hosts the imap server (a 1996 vintage DEC
> PC 5000... still running... still hosting the imap server).

> Another Gnus machine was a 1997 vintage DEC HiNote Ultra II, with 48MB
> RAM.

> Anyway, the machines used may have had something to do with the speed
> issues. :-)

I see.  I recalled the machine I'd been using till the year before
last. :)

>> This will work:

>> (setq gnus-summary-prepare-exit-hook nil)
>> (add-to-list 'gnus-parameters
>> 	     '("\\`nnimap[+:]" (gnus-summary-prepare-exit-hook
>> 				'(gnus-summary-expire-articles t))))

> Hm... what does the backslash-quoted backquote at the start of the
> rexexp mean?  My existing gnus-parameters entries all start with a "^"
> (start of line).

Both "\\`" and "^" match the beginning of a string object (and
the beginning of contents in an Emacs buffer), while "^" also
matches the beginning of a line (i.e., the next position of the
newline character) in a string or a buffer.  Anyway you can use
either in that case.  I usually use "\\`" when the matching target
is a string (a newsgroup name in that case).
Cf. (info "(emacs)Regexp")

[...]

> So if I leave my current
>  (remove-hook 'gnus-summary-prepare-exit-hook 'gnus-summary-expire-articles)
> in place in your example, instead of setting it to nil, that should also
> work?

It should be ok.



      reply	other threads:[~2009-10-14 22:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-13 15:30 Steinar Bang
2009-10-13 17:57 ` Reiner Steib
2009-10-13 19:23 ` Ted Zlatanov
2009-10-13 22:47 ` Katsumi Yamaoka
2009-10-14 11:18   ` Steinar Bang
2009-10-14 22:44     ` Katsumi Yamaoka [this message]

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=b4m3a5ly4sc.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).