unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: "Sébastien Vauban" <zthjwsqqafhv@spammotel.com>
Cc: re.2YV9XX9BLMAAX@spammotel.com, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Color-theme problems in Emacs 22+ (Ubuntu, Windows)
Date: Tue, 30 Jan 2007 12:21:53 -0500	[thread overview]
Message-ID: <87odogfn0u.fsf@stupidchicken.com> (raw)
In-Reply-To: <87ps8wvh6g.fsf_-_@missioncriticalit.com> (Sébastien Vauban's message of "30 Jan 2007 13\:21\:27 +0100")

Sébastien Vauban <zthjwsqqafhv@spammotel.com> writes:

> I've done the following:
>
>     o   ultra-simplified my .emacs file - see attachment;
>
>     o   ultra-simplified my .gnus file - see attachment;
>
>     o   triple-checked that I'm loading the last version of
>         color-theme - see the Messages buffers attached.

The .emacs file you attached is 5000 lines long---hardly
"ultra-simplified".

Furthermore, it relies on a lot of files that seem to be specific to
your setup---I get errors when I try to use it.  So probably the only
one who can debug this is you.  The strategy is to keep removing items
from .emacs until the bug no longer appears (assuming the bug does not
happen with an empty .emacs---this is at least the case for me.)  Then
the last change made was the one that caused the bug.

  reply	other threads:[~2007-01-30 17:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-21  6:49 Color-theme problems in Emacs 22+ (Ubuntu, Windows) Richard Stallman
2007-01-22 18:06 ` Chong Yidong
2007-01-25  8:49   ` Sébastien Vauban
2007-01-30 12:21   ` Sébastien Vauban
2007-01-30 17:21     ` Chong Yidong [this message]
2007-01-31  8:27       ` Sébastien Vauban
     [not found]       ` <1170232136.ZTHJWSQQAFHV@spammotel.com>
2007-01-31 15:23         ` Chong Yidong
2007-02-01  8:42           ` Sébastien Vauban

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87odogfn0u.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=re.2YV9XX9BLMAAX@spammotel.com \
    --cc=rms@gnu.org \
    --cc=zthjwsqqafhv@spammotel.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).