all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Daniele Nicolodi <daniele@grinta.net>,
	Emacs developers <emacs-devel@gnu.org>
Subject: RE: [External] : Easy way to make Emacs look more "modern"
Date: Sat, 9 Apr 2022 21:43:19 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488AE8A48DA1004B8E0F1E6F3E89@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <a1554aef-462b-2100-1925-8bd2c92c9300@grinta.net>

That's a pretty minor change in appearance.

It's fine with me either way.  (I don't see
a real need to adopt it as the default.)

There's less contrast in the backgrounds of
active and inactive than what we've had -
so it's harder to see which is active.  And
you lose ~1 line of real estate for content.
Those are drawbacks, I think, however minor.

But it's OK by me.
___

However, if there's one thing that really
comes across as old-fashioned, IMO, it's
talking about something being "modern" or
more "modern".

That's been the watchword of has-been
advertising since the middle of the 19th
century (if not soon after Gutenberg).

There's _nothing_ new about declaring
something "modern".  Old as the hills.
So it means nothing.  Nothing more than
suggesting that someone wants to sell it
to folks inclined to jump on the latest
passing band wagon.  Smells of snake oil.

Just speak to _what_ the differences are,
objectively.  And tout the advantages of
those differences.  Never mind trying to
convince folks it's an advancement because
it's sold as a "modern" remedy.
___

[IMO, more important than changing the
"prettiness" of the mode-line is giving
it content that's more useful.  But I see
themes and custom mode-lines that get
adopted only for their "looks", so my
opinion is likely a minority one.]

  parent reply	other threads:[~2022-04-09 21:43 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-09 21:13 Easy way to make Emacs look more "modern" Daniele Nicolodi
2022-04-09 21:25 ` Dmitry Gutov
2022-04-09 21:34   ` Daniele Nicolodi
2022-04-09 21:51     ` Dmitry Gutov
2022-04-09 21:43 ` Drew Adams [this message]
2022-04-09 21:49   ` [External] : " Daniele Nicolodi
2022-04-09 21:54   ` Daniele Nicolodi
2022-04-09 22:03     ` Dmitry Gutov
2022-04-10  1:57     ` Drew Adams
2022-04-10  2:41       ` Visuwesh
2022-04-10  6:38         ` Daniele Nicolodi
2022-04-10  6:47           ` Po Lu
2022-04-10  8:04           ` Visuwesh
2022-04-10  6:13   ` tomas
2022-04-09 23:20 ` Philip Kaludercic
2022-04-10  1:12   ` Po Lu
2022-04-10 13:46     ` Philip Kaludercic
2022-04-10  1:10 ` Po Lu
2022-04-10  6:44   ` Daniele Nicolodi
2022-04-10  6:50     ` Po Lu
2022-04-10  6:58       ` Daniele Nicolodi
2022-04-10 12:24 ` Lars Ingebrigtsen
2022-04-10 12:28   ` Po Lu

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

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

  git send-email \
    --in-reply-to=SJ0PR10MB5488AE8A48DA1004B8E0F1E6F3E89@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=daniele@grinta.net \
    --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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.