From: Martin Geisler <mg@daimi.au.dk>
To: info-gnus-english@gnu.org
Subject: Re: re-specifying ~/News and ~/Mail
Date: Tue, 12 Feb 2008 08:17:17 +0100 [thread overview]
Message-ID: <w1bwspaskxu.fsf@thyra03.daimi.au.dk> (raw)
In-Reply-To: <vcodanlf2l.fsf@dev.null.blueoakdb.com>
Pablo Sanchez <dev.null@blueoakdb.com> writes:
> Martin Geisler <mg@daimi.au.dk> writes:
>
>> I think you want to change either this variable:
>>
>> `gnus-home-directory'
>> `gnus-directory'
>> `message-directory'
>>
>> [ snipped ]
>
> Thank you.
>
>> When searching for a variable controlling something, then it is
>> often useful to search with M-x apropos-value for the value in
>> question.
>
> Thank you for the hint as I rather learn to `fish than to be fed a
> fish.' :)
Yeah, me too :-) That apropos command is really powerful!
I found the gnus-home-directory and gnus-directory variables in the
Gnus Info manual, but I had to search with apropos-value for the
message-directory variable (although I ought to have guessed the name
since it is so similar to the other names).
> I thought I'd try it out. After entering 'M-x apropos-value' I
> entered 'gnus.*directory' At this point I received a `stack overflow
> in regexp matcher'
>
> Am I doing sometihng incredibly lame?
I get the same error. I guess it is understandable since your regexp
is matched against all variable *values*, and some of these values are
apparently too big to be searched with that a regexp. If you search
with a regexp that does not require as much backtracking, then it
works fine:
M-x apropos-value RET gnus.\{1,10\}directory
returns matches in my Emacs.
--
Martin Geisler
VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
SMPC (Secure Multi-Party Computation) to Python. See: http://viff.dk/.
next prev parent reply other threads:[~2008-02-12 7:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 13:28 Pablo Sanchez
2008-02-11 9:57 ` Martin Geisler
[not found] ` <mailman.7275.1202723861.18990.info-gnus-english@gnu.org>
2008-02-11 14:53 ` Pablo Sanchez
2008-02-12 7:17 ` Martin Geisler [this message]
2008-02-11 15:33 ` Pablo Sanchez
2008-02-12 7:20 ` Martin Geisler
[not found] ` <mailman.7324.1202801114.18990.info-gnus-english@gnu.org>
2008-02-12 13:46 ` Pablo Sanchez
2008-02-13 8:30 ` Martin Geisler
[not found] ` <mailman.7364.1202891426.18990.info-gnus-english@gnu.org>
2008-02-13 13:41 ` Pablo Sanchez
2008-02-14 11:08 ` anhnmncb
2008-02-14 20:01 ` Reiner Steib
2008-02-15 1:54 ` anhnmncb
2008-02-13 18:57 ` Reiner Steib
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=w1bwspaskxu.fsf@thyra03.daimi.au.dk \
--to=mg@daimi.au.dk \
--cc=info-gnus-english@gnu.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).