emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jack Kamm <jackkamm@gmail.com>
To: Texas Cyberthal <texas.cyberthal@gmail.com>,
	Diego Zamboni <diego@zzamboni.org>, Eric <e.fraga@ucl.ac.uk>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: customizing Org for legibility
Date: Sat, 01 Feb 2020 08:17:40 -0800	[thread overview]
Message-ID: <87sgjuuvrv.fsf@gmail.com> (raw)
In-Reply-To: <CAMUm493mq=Z1jc2MYunq9wSY8oYiu_udoA29go-6ci=OJvSXUQ@mail.gmail.com>

> One thing I don't understand: It seems that GUI and terminal modes are
> completely different. Rather than constrain GUI defaults to terminal
> limitations, it makes sense to gracefully degrade them when a terminal
> is detected. I assume that terminal users don't care about variable
> pitch. They're likely doing sysadmin, with little or no prose
> interaction.

Personally, I run emacs in daemon mode, and often have both GUI and
terminal emacsclients connected to the same session. So I like to have
settings that work well in both.

I agree terminal users typically won't want variable pitch, but disagree
that they are generally doing sysadmin -- I know users who use org-mode
for their notes, but prefer to use emacs in the terminal.

Speaking to my own preferences -- I prefer fixed-width for editing text,
whether it's prose or code. For example, if I execute a command to move
the cursor down 10 lines, I like to know where my cursor is going to end
up. Fixed-width also works better for certain editing commands, such as
rectangle commands.

I am not sure what the majority preference is here, but it would be
interesting to know, and also how it distributes across old-timers and
newcomers. Ideally, it should be easy to accommodate all preferences,
with a small amount of configuration and easily discoverable
documentation.

  reply	other threads:[~2020-02-01 16:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-31  9:34 customizing Org for legibility Texas Cyberthal
2020-01-31 11:34 ` Fraga, Eric
2020-01-31 13:19 ` Diego Zamboni
2020-01-31 17:47   ` Texas Cyberthal
2020-02-01 16:17     ` Jack Kamm [this message]
2020-02-01 20:11       ` Bob Newell
2020-02-01 20:38         ` Diego Zamboni
2020-02-02  2:02       ` Tim Cross
2020-01-31 20:13 ` Samuel Wales
2020-02-01  1:23   ` Texas Cyberthal
2020-02-01  1:34     ` Samuel Wales
2020-02-01  2:47       ` Texas Cyberthal
2020-02-01 20:46         ` Diego Zamboni
2020-02-01 20:36   ` Diego Zamboni
2020-02-01  9:36 ` 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=87sgjuuvrv.fsf@gmail.com \
    --to=jackkamm@gmail.com \
    --cc=diego@zzamboni.org \
    --cc=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=texas.cyberthal@gmail.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/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).