Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: Starting Gnus litters my files with ill-tasting cookies ...
Date: Tue, 04 Nov 2003 21:48:40 +0100	[thread overview]
Message-ID: <v9sml3oo5z.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <537D2148-0F04-11D8-BF74-00306558A4D4@iparadigms.com>

On Tue, Nov 04 2003, James Felix Black wrote:

> Starting Gnus for me leads to nasty coding cookies being added
> against my will to files.

This has nothing to with Gnus.

> This breaks my builds.  This is not acceptable.  Why is this
> happening?

As I understood, it's a bug in BBDB and the effect has been triggered
by a change in Emacs CVS HEAD (fixed some days ago):

<URL:http://article.gmane.org/gmane.emacs.devel/17668>
<URL:http://news.gmane.org/onethread.php?group=gmane.emacs.devel&root=%3Cw4dy8uxpqks.fsf%40felix.riic.uni-linz.ac.at%3E>

> GNU Emacs 21.3.50.1 (powerpc-apple-darwin7.0.0)
            ^^^^^^^

People using CVS version of are supposed to read the developers list
(emacs-devel in this case) and consult the list archives in case of
problems.  Searching for "coding cookie" on Gmane in gmane.emacs.devel
gives above mentioned thread as first hit.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/




  parent reply	other threads:[~2003-11-04 20:48 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 [this message]
2003-11-04 21:00 ` Alan Shutko

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=v9sml3oo5z.fsf@marauder.physik.uni-ulm.de \
    --to=4.uce.03.r.s@nurfuerspam.de \
    --cc=reiner.steib@gmx.de \
    /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).