From: Eli Zaretskii <eliz@gnu.org>
To: scame <laszlomail@protonmail.com>
Cc: 47529@debbugs.gnu.org
Subject: bug#47529: Make quoted entities stand out more in info
Date: Thu, 01 Apr 2021 11:54:58 +0300 [thread overview]
Message-ID: <83czvegza5.fsf@gnu.org> (raw)
In-Reply-To: <xEofpRMwVesBNIV3JR3jkZP-_O7q0tULCf-Qa9R7ztBw2UdAxMR26pN1M0oY2T0CzBeZSEbLIHy_1qd0YKy6MuTIg1h6xn312pNfcq9pYIk=@protonmail.com> (message from scame on Thu, 01 Apr 2021 08:30:33 +0000)
> Date: Thu, 01 Apr 2021 08:30:33 +0000
> From: scame <laszlomail@protonmail.com>
> Cc: "47529@debbugs.gnu.org" <47529@debbugs.gnu.org>
>
> True, but first impression matters. Emacs' default appearance is like
> it's stuck in the 80s. Emacs is from the 70s, but it doesn't mean it
> can't have an appealing, polished default look.
>
> People coming from other tools like VSCode or IntelliJ often put off
> by the face Emacs shows them the first time.
Emacs is unlike those other tools, in that it's infinitely more
customizable than any of them. It is also unique in that its
development is not hierarchical, and therefore personal UI preferences
get in the way of changing the defaults according to unilateral
decisions of a single manager. Enough said.
> if can show a prettier face (subjective) then maybe less people are
> turned away before giving emacs a serious try.
I'm skeptical because the likes of Spacemacs and Doom Emacs already
exist to fill that niche. Given the time it typically takes us to
change the defaults, by the time we do it, those new defaults are
already "stuck in" whatever previous decade you fancy for the kind of
unflattering language people tend to use in these cases.
next prev parent reply other threads:[~2021-04-01 8:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 19:52 bug#47529: Make quoted entities stand out more in info scame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-01 6:40 ` Eli Zaretskii
2021-04-01 7:32 ` scame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-01 7:50 ` Eli Zaretskii
2021-04-01 7:54 ` scame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-01 8:08 ` Eli Zaretskii
2021-04-01 8:30 ` scame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-01 8:54 ` Eli Zaretskii [this message]
2021-04-01 16:53 ` Glenn Morris
2021-04-01 17:07 ` bug#47529: [External] : " Drew Adams
2021-04-03 23:58 ` Stefan Kangas
2021-04-04 7:36 ` Eli Zaretskii
2021-04-04 8:50 ` Stefan Kangas
2021-04-04 11:00 ` Eli Zaretskii
2022-06-28 13:49 ` Lars Ingebrigtsen
2021-04-01 18:41 ` scame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-01 18:57 ` Eli Zaretskii
2021-04-01 18:59 ` Eli Zaretskii
2021-04-01 19:07 ` scame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-01 19:11 ` Eli Zaretskii
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=83czvegza5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=47529@debbugs.gnu.org \
--cc=laszlomail@protonmail.com \
/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).