all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Texas Cyberthal <texas.cyberthal@gmail.com>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Make code elements in prose unobtrusive [legibility 6/6]
Date: Tue, 4 Feb 2020 12:11:00 +0800	[thread overview]
Message-ID: <CAMUm493zrTk2kP-wnWhfimXwwb41sYDRXrPKez6wN0B1MYsnNQ@mail.gmail.com> (raw)

Org intersperses bits of code in prose, such as datestamps, drawers,
keywords, etc. The code distracts when reading the prose. The solution
is to make the code less prominent.

That way it's easy to read the paragraphs of prose without
interruption. If one wants to focus on a code bit, it's still easily
readable. Prose needs to be larger to be human-scannable, but the code
bits aren't in paragraphs, so they can be smaller. Code only needs to
be readable when the eye is centered on it, whereas a prose paragraph
must be read with multiple saccades.

Org should provide a way to make all the code bits smaller with one settings:

#+begin_src elisp
(custom-set-faces
 ;; custom-set-faces was added by Custom.
 ;; If you edit it by hand, you could mess it up, so be careful.
 ;; Your init file should contain only one such instance.
 ;; If there is more than one, they won't work right.
 '(org-date ((t (:foreground "#7590db" :underline t :height 0.8 :width
normal))))
 '(org-drawer ((t (:foreground "LightSkyBlue" :height 0.7 :width condensed))))
 '(org-special-keyword ((t (:foreground "#bc6ec5" :height 0.7 :width
condensed)))))
#+end_src

             reply	other threads:[~2020-02-04  4:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04  4:11 Texas Cyberthal [this message]
2020-02-04  5:01 ` Make code elements in prose unobtrusive [legibility 6/6] Tim Cross
2020-02-10  7:08   ` Bastien
2020-02-04  6:35 ` Adam Porter
2020-02-05  3:38   ` Matthew Lundin
2020-02-05  3:59     ` Samuel Wales
2020-02-05 13:56     ` Russell Adams

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

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

  git send-email \
    --in-reply-to=CAMUm493zrTk2kP-wnWhfimXwwb41sYDRXrPKez6wN0B1MYsnNQ@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.