unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "Reiner Steib" <Reiner.Steib@gmx.de>, <bug-gnu-emacs@gnu.org>
Cc: Lennart Borgman <lennart.borgman.073@student.lu.se>
Subject: RE: bad tool-bar icons in Emacs 22.1 release
Date: Sat, 9 Jun 2007 10:11:26 -0700	[thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICKEEIDNAA.drew.adams@oracle.com> (raw)
In-Reply-To: <v9abv9w0u2.fsf@marauder.physik.uni-ulm.de>

> >> I'm not sure if this is what your asking for, but for nicer icons, you
> >> need to install some image DLLs (see the README below).
> >
> > No, I wasn't looking for nicer icons (but thanks anyway).
> > I was reporting a bug in the Emacs 22.1 release (with the
> > default icons).
>
> The nicer color icons (GNOME/GTK/style; see e.g. etc/images/save.xpm)
> are "the default icons" [1].  They only require external image
> libraries whereas the monochrome PBM/PGM/PPM icons are supported by
> natively by the Emacs binary w/o further libs (DLLs on Windows), see
> the README file cited previously.
>
> [1] I'd consider the monochrome icons as a fallback e.g. for
>     monochrome displays.

You might consider color to be the default, but for Windows, you don't get
color by default - you must install external image libraries. You might
consider B&W to be only a fallback for monochrome displays, but it is also
the default installation for color displays on Windows: out of the box, that
is, with just the downloaded zip or tar, you get B&W. If you follow
additional instructions, performing additional steps (optional), then you
can get color.

To my understanding of "default", the default for Windows is B&W, not color.

Nothing wrong with that, if it's unavoidable, but let's not pretend that the
default is color if a user needs to jump through extra hoops (on Windows) to
get color. BTW, when was the last time anyone saw Windows used with a
monochrome display?

This is one reason that I support the idea of an Emacs installer for
Windows, such as the one Lennart Borgman supplies. Windows users are used to
simply pushing a button to get something installed, perhaps answering yes or
no a few times to simple customization questions, and perhaps changing a
location or two - that's it. They are less used to digging out and reading
READMEs with instructions about possibly downloading supplemental packages
and installing them to obtain optional features. That happens sometimes, but
it is not very common. It certainly doesn't happen for something as basic as
color support.

Wrt color: I've installed lots of programs on Windows, and I've never had to
do anything special to get them to be color-able or color-aware. For many
Windows users, this will reflect poorly on Emacs, I'm afraid, not on
Windows. They see color everywhere in Windows, so they will not think this
is something lacking in Windows - they will think that it is something
lacking in Emacs. Which, in a sense, it is ;-).

I don't use Lennart's installer myself, BTW, because AFAIK it bundles other
things that I don't want, it sets up a version of server/client that I don't
want, and it makes assumptions of where I want to put Emacs etc. Still, I
think the idea of an installer is a good one, even if I personally use just
a zip file of vanilla Emacs. (Please note the "AFAIK" - I haven't tried
Lennart's installer in a while, and I might be mistaken about it.)

> >> Looks like a bug.  But I couldn't reproduce this when using
> >> emacs-22.1-bin-i386.zip without further DLLs.
> >
> > Did you do just what I did? I downloaded and installed first the full
> > Windows binary distrib (i.e. bin, not barebin), and then downloaded and
> > installed the full source distrib, on top of the Windows binary
> > distrib. See my description for details.
>
> No, I downloaded and unzipped emacs-22.1-bin-i386.zip.  But I doubt
> that it makes a difference WRT the misaligned icons.

You might doubt it, and you might be right. But from your and my
descriptions, that is the only difference between what we each did. Either
our descriptions are incomplete or that difference is significant. To
reproduce a bug, it's usually not a bad idea to follow the recipe provided
;-).

  reply	other threads:[~2007-06-09 17:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BDEIJAFNGDOAGCJIPKPBCEPNCEAA.drew.adams@oracle.com>
2007-06-09 14:27 ` bad tool-bar icons in Emacs 22.1 release Drew Adams
2007-06-09 14:31   ` Drew Adams
2007-06-09 15:05     ` Reiner Steib
2007-06-09 15:34       ` Drew Adams
2007-06-09 16:26         ` Reiner Steib
2007-06-09 17:11           ` Drew Adams [this message]
2007-06-09 20:46             ` Eli Zaretskii
2007-06-09 20:54               ` Drew Adams
2007-06-10  9:51               ` Reiner Steib
2007-06-10 19:27                 ` Eli Zaretskii
2007-06-10 22:52                   ` Jason Rumney
2007-06-11  9:44                     ` Richard Stallman
2007-06-11 11:40                       ` Jason Rumney
2007-06-11 17:58                         ` Glenn Morris
2007-06-12 16:00                         ` Richard Stallman
2007-06-10 21:00                 ` Richard Stallman
2007-06-10 10:01             ` Reiner Steib
2007-06-10 14:11               ` Drew Adams
2007-06-09 21:12     ` Jason Rumney
2007-06-09 21:30       ` Drew Adams
2007-06-09 21:48         ` 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=DNEMKBNJBGPAOPIJOOICKEEIDNAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.com \
    --cc=Reiner.Steib@gmx.de \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=lennart.borgman.073@student.lu.se \
    /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).