From: Tim Cross <theophilusx@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Make code elements in prose unobtrusive [legibility 6/6]
Date: Tue, 04 Feb 2020 16:01:17 +1100 [thread overview]
Message-ID: <87y2tj54ki.fsf@gmail.com> (raw)
In-Reply-To: <CAMUm493zrTk2kP-wnWhfimXwwb41sYDRXrPKez6wN0B1MYsnNQ@mail.gmail.com>
It strikes me that much of what seems to be required for 'legible' org
would possibly be handled by an org 'theme'. As it is possible to
combine themes, it should be possible to create a 'org pros theme',
which users could add to their existing theme. This theme could adjust
face sizes, colours, fonts etc. For things which cannot be modified
using a theme, we could define profiles e.g. a pros profile and a coding
profile. Provided these are adequately documented, new users will be
able to try them out.
Changing defaults is far more problematic as it has the potential to
impact a large number of existing users who have their environment
configured the way they like already. In this day and age of cut and
paste, pre-configured setups and stack overflow solutions, we cannot
assume that these users are advanced enough to 'fix' or restore their
setup when defaults change.
I also think it important to not consider this to be a simple pros v
code use case. Personally, while I do use org to write pros quite often,
my main use of org is for organisation of information, tracking tasks,
planning and notes. In the majority of my workflows, a lot of that
'code' information is important and not something I would want hidden or
de-emphasised all the time. Rather than changing defaults, what I think
is really needed is something along the 'profile' lines - a way to
reliably switch to a pros profile when I'm writing pros and switch out
to a 'standard' profile when not.
Texas Cyberthal <texas.cyberthal@gmail.com> writes:
> 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
--
Tim Cross
next prev parent reply other threads:[~2020-02-04 5:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 4:11 Make code elements in prose unobtrusive [legibility 6/6] Texas Cyberthal
2020-02-04 5:01 ` Tim Cross [this message]
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
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=87y2tj54ki.fsf@gmail.com \
--to=theophilusx@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).