From: "Ugly Me" <ugly@frightenstein.com>
To: "Emacs Devel" <emacs-devel@gnu.org>
Subject: Re: [h-e-w] Re: Emacs 23.0.92 pretest
Date: Thu, 2 Apr 2009 16:18:21 -0400 [thread overview]
Message-ID: <004901c9b3d0$2b5f86e0$8807ef63@MYLITTLEPHONY> (raw)
In-Reply-To: 49D2032F.6030600@gnu.org
> Chong Yidong wrote:
> > Emacs pretest 23.0.92 is now available; this is the third pretest for
> > what will be the Emacs 23.1 release. You can download it via FTP, at
> > the following location:
> >
> > http://alpha.gnu.org/gnu/emacs/pretest/emacs-23.0.92.tar.gz
> >
> > The xdelta against the previous pretest, 23.0.91, is here:
> >
> > http://alpha.gnu.org/gnu/emacs/pretest/emacs-23.0.91-23.0.92.xdelta
> >
> > Pretesters: please send an email to me reporting success or failure on
> > your build platform. In addition, please report bugs via M-x
> > report-emacs-bugs, or send an email to emacs-pretest-bug@gnu.org. For
> > questions, please email emacs-devel@gnu.org.
> >
> > Thank you.
Because I don't know if this is a bug or not, I'm sending the message here.
This build opens up TWO processes. One being the main emacs application, and
the other opens in what resembles a DOS screen with nothing but a cursor
that I can't seem to do anything with except move it around the screen.
If I try to close that, both processes terminate. I don't recall this ever
happening in previous builds.
However, in a previous version I had a colour scheme problem which still
holds true.
For example, the opening line on the title screen: "Welcome to GNU Emacs,
one component of the GNU operating system."
This is in red, which is fine, except for "GNU Emacs" and "GNU" which is in
a bright turquoise shade. So are the links and the build information.
This makes it VERY difficult to read and I'm wondering how to change the
default colours. I know it's probably there somewhere but I'm having
trouble finding it.
True, I'm not fluent in Emacs but I still don't mind using beta versions,
and, the colour problem is not limited to this version anyhow, but also of
22.3.1 as well.
Prior to this I never had a problem.
-Sean
msudol0928@rogers.com
next prev parent reply other threads:[~2009-04-02 20:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 2:49 Emacs 23.0.92 pretest Chong Yidong
2009-03-31 11:49 ` Jason Rumney
2009-04-02 20:18 ` Ugly Me [this message]
2009-04-02 22:51 ` [h-e-w] " Chong Yidong
[not found] ` <002901c9b401$1ae98b90$8807ef63@MYLITTLEPHONY>
2009-04-03 3:58 ` Chong Yidong
2009-04-03 4:52 ` Jan Djärv
2009-04-04 0:50 ` Ugly Me
2009-04-04 14:33 ` Andy Moreton
2009-03-31 12:24 ` Neal Becker
2009-03-31 13:42 ` Chong Yidong
2009-04-02 16:20 ` David Robinow
2009-04-02 19:28 ` Eli Zaretskii
2009-04-02 21:53 ` David Robinow
2009-04-06 14:54 ` Jason Rumney
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='004901c9b3d0$2b5f86e0$8807ef63@MYLITTLEPHONY' \
--to=ugly@frightenstein.com \
--cc=emacs-devel@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).