From: Alan Shutko <ats@acm.org>
Subject: Re: Starting Gnus litters my files with ill-tasting cookies ...
Date: Tue, 04 Nov 2003 15:00:16 -0600 [thread overview]
Message-ID: <87y8uvx3gp.fsf@wesley.springies.com> (raw)
In-Reply-To: <537D2148-0F04-11D8-BF74-00306558A4D4@iparadigms.com> (James Felix Black's message of "Tue, 4 Nov 2003 12:20:26 -0800")
James Felix Black <jfb@iparadigms.com> writes:
> Starting Gnus for me leads to nasty coding cookies being added against
> my will to files. This breaks my builds. This is not acceptable.
> Why is this happening?
Because you're using a slightly old CVS Emacs, which has broken
add-hook when it deals with local variables, and BBDB, which tries to
set local-write-file-functions.
An Emacs CVS checkin was recently made to fix this.
--
Alan Shutko <ats@acm.org> - I am the rocks.
Bad day: Spouse is reading "Celibacy, The Secret Weapon."
prev parent reply other threads:[~2003-11-04 21:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-04 20:20 Starting Gnus litters my files with ill-tasting cookies ... why? James Felix Black
2003-11-04 20:24 ` Starting Gnus litters my files with ill-tasting cookies Adam Sjøgren
2003-11-04 20:33 ` James Felix Black
2003-11-04 20:48 ` Reiner Steib
2003-11-04 21:00 ` Alan Shutko [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=87y8uvx3gp.fsf@wesley.springies.com \
--to=ats@acm.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).