From: Randy Yates <yates@ieee.org>
Subject: Re: disabling autosave
Date: Wed, 20 Sep 2006 13:01:53 GMT [thread overview]
Message-ID: <m3y7sewv27.fsf@ieee.org> (raw)
In-Reply-To: <v9slim7pv5.fsf@marauder.physik.uni-ulm.de>
Reiner Steib <reinersteib+gmane@imap.cc> writes:
> On Wed, Sep 20 2006, Tassilo Horn wrote:
>
>> Randy Yates <yates@ieee.org> writes:
>>> My #.newsrc-dribble# file is about 2MB and when gnus/xemacs
>>> autoaves, it takes several hundred milliseconds away from me. How
>>> do I turn off auto-saving this file? I've already (setq
>>> auto-save-default nil) in my init.el
>>
>> ,----[ (info "(gnus)Auto Save") ]
>> | If `gnus-use-dribble-file' is `nil', Gnus won't create and maintain
>> | a dribble buffer. The default is `t'.
>> `----
>
> BTW, this is the first hit when doing `i auto-save' or `i dribble'
> within the Gnus manual. Is there anything we could improve in the
> documentation to make it even more easy to find?
Hi Reiner,
The problem is that there is too much information. I see now that if I
had HAPPENED to use the info page for gnus, I would have found my answer
almost immediately. Instead, what I did was
a. Perform an on-line search via C-h a "auto-save", which came up
with a whole bunch of stuff that I tried to search through.
b. Searched the xemacs manual for auto-saving.
After spending about 10 fruitless minutes on this, I gave up and
posted my question.
Another part of the problem is that it is not always clear (as in this
case) what functions are xemacs and what are gnus. This multiplies the
required searches by a factor of two.
To my discredit, I have never become comfortable with the info
tool. Thus I tend not to use it. However, I did notice just now that
it is in the gnus manual as well.
Whatever the reasons or judgements, this is what happened, and why
I posted here.
--
% Randy Yates % "Bird, on the wing,
%% Fuquay-Varina, NC % goes floating by
%%% 919-577-9882 % but there's a teardrop in his eye..."
%%%% <yates@ieee.org> % 'One Summer Dream', *Face The Music*, ELO
http://home.earthlink.net/~yatescr
prev parent reply other threads:[~2006-09-20 13:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-20 2:14 Randy Yates
2006-09-20 10:43 ` Tassilo Horn
2006-09-20 11:13 ` Reiner Steib
2006-09-20 13:01 ` Randy Yates [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=m3y7sewv27.fsf@ieee.org \
--to=yates@ieee.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).