From: Guilherme Mesquita Gondim <semente@taurinus.org>
To: rms@gnu.org
Cc: emacs-pretest-bug@gnu.org, rfrancoise@debian.org
Subject: Re: 23.0.60; Frame colors differ from customized
Date: Thu, 21 Feb 2008 21:27:59 -0300 [thread overview]
Message-ID: <873arlq1gw.fsf@taurinus.org> (raw)
In-Reply-To: <E1JSJux-0001Rt-8z@fencepost.gnu.org> (Richard Stallman's message of "Thu, 21 Feb 2008 17:29:27 -0500")
Richard Stallman <rms@gnu.org> writes:
> To help us reproduce the problem, could you please post a *precise*
> test case for this bug?
>
> The test case should start with `emacs -q', so that your .emacs file
> does not affect it, and it should show exactly what text to put in the
> buffer, what commands to execute, and how and where to click. Also
> please say exactly what incorrect results you get.
Hi Stallman,
I've started the emacs with `-q' and `--no-site-file'.
For reproduce the bug, I only change the colors for foreground (for
white) and background (for black) with customize-face' (default face)
and create a new frame. The colors that I've changed not affects the new
frames (starts with background white and foreground text black). Other
faces, like hl-line, works properly in new frames.
My Emacs version:
GNU Emacs 23.0.60.1 (i486-pc-linux-gnu, GTK+ Version 2.12.8) of
2008-02-15 on elegiac, modified by Debian
I uses GNOME in Debian Sid (updated), but with X in failsafe mode I have
the same problem.
My Emacs package is from: http://emacs.orebokech.com/
> Please read the Bugs section in the Emacs manual, which provides
> guidelines on how to write a bug report to give us the necessary
> information so we can fix the bug.
Ok. Thanks! :-)
semente
--
Guilherme Mesquita Gondim (semente)
prev parent reply other threads:[~2008-02-22 0:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-20 21:15 23.0.60; Frame colors differ from customized Guilherme Mesquita Gondim
2008-02-21 22:29 ` Richard Stallman
2008-02-22 0:27 ` Guilherme Mesquita Gondim [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
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=873arlq1gw.fsf@taurinus.org \
--to=semente@taurinus.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=rfrancoise@debian.org \
--cc=rms@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.
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).