From: Lennart Borgman <lennart.borgman.073@student.lu.se>
Cc: Rodney Dawes <dobey@novell.com>, emacs-devel@gnu.org
Subject: Re: New Emacs Icon and Tango
Date: Sat, 22 Oct 2005 11:30:47 +0200 [thread overview]
Message-ID: <435A06C7.80006@student.lu.se> (raw)
In-Reply-To: <435A0153.1000106@soem.dk>
Lars Hansen wrote:
>Rodney Dawes wrote:
>
>
>>On the subject of branding through, I am not quite sure what the best
>>way to do that is. I like the Gnu-horns E on the notepad. I'm not sure
>>that a notepad is the best metaphor for Emacs though, as it does so much
>>more than just edit text. The branding should be strong though, and
>>preferrably be done without having the text "Emacs" in the icon itself.
>>If the icon should say anything, it should be "this is Emacs, a very
>>powerful IDE and text processing solution", I think.
>>
>>
>
>I agree. I like the looks of the notepad, but IMHO it resembles the icon
>of notepad.exe on MS Windows to much. notepad.exe is no more than a
>notepad, but Emacs is much more. But which metaphor is better?
>Maybe this: Emacs is sometimes referred to as
>
> "The Swiss Army Knife of Editors"
>
>since it has a tool for every need. But I don't know if it would do as
>an icon.
>
A very important feature of Emacs for me (currently using MS Windows) is
the portability. Maybe a bag of some kind with the Gnu-horns? (I would
like a backpack, but that's me and it is too difficult in small sizes of
course.)
In a bag you can carry many tools and you can move -- to GNU/Linux. The
Gnu-horns tells where you are going.
next prev parent reply other threads:[~2005-10-22 9:30 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-21 15:32 New Emacs Icon and Tango Rodney Dawes
2005-10-21 17:06 ` Lennart Borgman
2005-10-21 17:16 ` Rodney Dawes
2005-10-21 22:19 ` Richard M. Stallman
2005-10-24 14:45 ` Rodney Dawes
2005-10-24 23:34 ` Juri Linkov
2005-10-22 9:07 ` Lars Hansen
2005-10-22 9:30 ` Lennart Borgman [this message]
2005-10-22 9:45 ` Lars Hansen
2005-10-22 9:52 ` Lennart Borgman
2005-10-22 18:16 ` Richard M. Stallman
2005-10-22 10:15 ` David Kastrup
2005-10-22 10:29 ` Lars Hansen
2005-10-22 10:38 ` Lennart Borgman
2005-10-22 23:20 ` Kim F. Storm
2005-10-23 0:23 ` Miles Bader
2005-10-23 8:34 ` David Kastrup
2005-10-23 16:14 ` Richard M. Stallman
2005-10-23 16:18 ` David Kastrup
2005-10-23 21:48 ` Kim F. Storm
2005-10-24 1:13 ` Miles Bader
2005-10-24 6:32 ` Frank Schmitt
2005-10-23 16:14 ` Richard M. Stallman
2005-10-22 18:15 ` Richard M. Stallman
2005-10-22 10:09 ` Drew Adams
2005-10-23 9:18 ` Florian Weimer
2005-10-23 11:25 ` Miles Bader
2005-10-23 20:42 ` Frank Schmitt
2005-10-24 6:59 ` David Kastrup
2005-10-24 7:24 ` Frank Schmitt
2005-10-22 16:26 ` Ken Manheimer
2005-10-22 16:44 ` Lennart Borgman
2005-10-22 18:48 ` Ken Manheimer
2005-10-22 19:14 ` Ken Manheimer
2005-10-22 23:01 ` Drew Adams
2005-10-23 8:25 ` David Kastrup
2005-10-23 16:14 ` Richard M. Stallman
2005-10-23 18:31 ` Stefan Monnier
2005-10-25 18:33 ` Kevin Rodgers
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=435A06C7.80006@student.lu.se \
--to=lennart.borgman.073@student.lu.se \
--cc=dobey@novell.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).