unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: scame via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "47529@debbugs.gnu.org" <47529@debbugs.gnu.org>
Subject: bug#47529: Make quoted entities stand out more in info
Date: Thu, 01 Apr 2021 18:41:10 +0000	[thread overview]
Message-ID: <OhyoHYdKWrjqpwnFVXy1CnbwfaSx--T8ESZlJfeyH3P-Z14_IRF_Iav7rTcsclXivVfEh7HVHj2JUCm4L3PsMyT2L5YPn8PxLJtxKzIn-UA=@protonmail.com> (raw)
In-Reply-To: <83czvegza5.fsf@gnu.org>

>
> I'm skeptical because the likes of Spacemacs and Doom Emacs already
> exist to fill that niche.

Are those variants recommended on the Gnu Emacs homepage? If not
then barebones Emacs should also offer an appealing experience
in case a new user goes there from google.

> 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.

The project should just ask a graphical designer from an other
free software project to create a pleasant default theme for
Emacs (including the default colors, customize, info, etc.)

It is not a task for engineers, so it should be done by somebody
who's qualified to do this job.





  parent reply	other threads:[~2021-04-01 18:41 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
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 [this message]
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='OhyoHYdKWrjqpwnFVXy1CnbwfaSx--T8ESZlJfeyH3P-Z14_IRF_Iav7rTcsclXivVfEh7HVHj2JUCm4L3PsMyT2L5YPn8PxLJtxKzIn-UA=@protonmail.com' \
    --to=bug-gnu-emacs@gnu.org \
    --cc=47529@debbugs.gnu.org \
    --cc=eliz@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).