emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Texas Cyberthal <texas.cyberthal@gmail.com>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Defaults for noobs, dotfiles for vets [legibility 1/6]
Date: Wed, 5 Feb 2020 05:09:01 +0800	[thread overview]
Message-ID: <CAMUm492H9Bi5xLvKFngqQ95uqPGSj+KPPyyVduA2rwjnPzyyeA@mail.gmail.com> (raw)
In-Reply-To: <mailman.933.1580832377.2408.emacs-orgmode@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 782 bytes --]

Making a vet change a default if he decides he doesn't like a change upon
upgrading won't drive him away, but Emacs' unfriendly defaults are always
driving away noobs. Therefore Org's defaults should be noob-friendly, not
vet-friendly.

Probably vets should use legible settings as well. I became accustomed to
less-legible Org settings, and thought they were superior. But when I
cleaned up my Spacemacs config, I incidentally restored some default
legibility tweaks I'd disabled. After a brief exposure, I realized the
tweaks were superior, and that my preferences had been wrong. Changing the
defaults can overcome vet inertia and improve their UI.

> Terminals can display colors, underlines, italics, and bold text

Proposed legibility changes don't affect those font aspects.

[-- Attachment #2: Type: text/html, Size: 935 bytes --]

       reply	other threads:[~2020-02-04 21:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.933.1580832377.2408.emacs-orgmode@gnu.org>
2020-02-04 21:09 ` Texas Cyberthal [this message]
2020-02-05 13:36   ` Defaults for noobs, dotfiles for vets [legibility 1/6] Texas Cyberthal
2020-02-05 15:25   ` Adam Porter
2020-02-04  4:07 Texas Cyberthal
2020-02-04  6:56 ` Adam Porter
2020-02-10  6:56   ` Bastien

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.orgmode.org/

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

  git send-email \
    --in-reply-to=CAMUm492H9Bi5xLvKFngqQ95uqPGSj+KPPyyVduA2rwjnPzyyeA@mail.gmail.com \
    --to=texas.cyberthal@gmail.com \
    --cc=emacs-orgmode@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/org-mode.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).