From: Adam Porter <adam@alphapapa.net>
To: emacs-orgmode@gnu.org
Subject: Re: Prose with markup needs more line spacing [legibility 5/6]
Date: Tue, 04 Feb 2020 01:32:50 -0600 [thread overview]
Message-ID: <87k152yfh9.fsf@alphapapa.net> (raw)
In-Reply-To: CAMUm493kMZsKF8w0q=x6JdXMdynB1bogWg_Cn5f9Q6NwY9fYag@mail.gmail.com
Texas Cyberthal <texas.cyberthal@gmail.com> writes:
> Code requires less line spacing. It has more whitespace, fewer capital
> letters, and no markup such as underlining. Code is read differently
> than prose; it requires less sequential scanning.
Code certainly can have markup like underlining. For example,
flymake/flycheck highlighting, highlight-function-calls-mode, Semantic,
etc.
> Prose has big blocks of text with taller capital letters that must be
> scanned sequentially. The tall bits bump into lines above and below.
> Org prose adds markup. Underlining and all-caps tags are common. This
> requires a bit more line spacing for optimal legibility:
>
> #+begin_src elisp
> ;; prose with markup needs more line spacing
> (defun leo-space-lines ()
> (setq line-spacing 0.175))
> (add-hook 'org-mode-hook 'leo-space-lines)
> #+end_src
We should definitely not be messing with line spacing in default
settings. Line spacing is a very personal preference, and it varies
widely by other configuration, such as font.
Please, feel free to make your own prose-specific Org theme or minor
mode, or use or improve one of the several that already exist. Org
defaults need not be changed to meet your preferences.
next prev parent reply other threads:[~2020-02-04 7:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 4:10 Prose with markup needs more line spacing [legibility 5/6] Texas Cyberthal
2020-02-04 7:32 ` Adam Porter [this message]
2020-02-10 7:07 ` Bastien
-- strict thread matches above, loose matches on Subject: below --
2020-02-04 22:07 Texas Cyberthal
2020-02-04 23:17 ` Samuel Wales
2020-02-05 2:27 ` Texas Cyberthal
2020-02-10 7:11 ` Bastien
2020-02-10 19:58 ` Samuel Wales
2020-02-10 21:52 ` 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=87k152yfh9.fsf@alphapapa.net \
--to=adam@alphapapa.net \
--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).