From: Michael Brand <michael.ch.brand@gmail.com>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Link "bracket-types"
Date: Thu, 17 May 2018 18:17:51 +0200 [thread overview]
Message-ID: <CALn3zogGirUaqDMuxdXoSWr8BpxOiz_3mZX3t8wDsONKuDXvjQ@mail.gmail.com> (raw)
In-Reply-To: <CALn3zohEW80jXUQVdpnK+d4RhoxegYuLJKhco1ohFBk+-qSs=A@mail.gmail.com>
Hi all
On Sat, May 12, 2018 at 10:12 AM, Michael Brand
<michael.ch.brand@gmail.com> wrote:
> Thank you for the patch. I changed it (attached) to something that
> preserves org-toggle-link-display and allows more different configs
> for more different usages, please see the docstring of
> org-link-brackets. I tried it out with org-toggle-link-display and for
> org-link-brackets '(0 0), '(1 1) and '(0 2).
Another use case for playing with org-link-brackets config:
In my opinion the underline in the org-link face makes descriptive
links with many words less readable. Currently I try out underline
turned off. To compensate for the missing indication of beginning and
end of adjacent descriptive links I changed org-link-brackets from my
previous '(0 2) to '(1 2) to get 1 bracket pair around descriptive
links.
For those interested in readability:
Put the following without the #-lines in an empty Org buffer (with the
default face for org-link and underline) and try to read as fast as
possible.
#+begin_example
---- 8< ---- cut here ---- 8< ----
1) TIHS IS RAEADLBE BCUSEAE TEH HUAMN MNID DEOS
NTO RAED ERVEY LTETER BY ISTLEF, BTU TEH WROD AS A WLOHE
2) [[http://example.com][Tihs is raeadlbe bcuseae teh huamn mnid deos
nto raed ervey lteter by istlef, btu teh wrod as a wlohe]]
3) _Tihs is raeadlbe bcuseae teh huamn mnid deos
nto raed ervey lteter by istlef, btu teh wrod as a wlohe_
4) Tihs is raeadlbe bcuseae teh huamn mnid deos
nto raed ervey lteter by istlef, btu teh wrod as a wlohe
---- 8< ---- cut here ---- 8< ----
#+end_example
To my understanding underline and UPPERCASE decrease readability
because they affect the bouma.
http://en.wikipedia.org/wiki/Bouma
michael
ʅǝɐɥɔᴉɯ
prev parent reply other threads:[~2018-05-17 16:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 6:08 Link "bracket-types" Michael Brand
2018-05-10 8:14 ` Nicolas Goaziou
2018-05-10 8:32 ` Eric S Fraga
2018-05-11 12:34 ` Nicolas Goaziou
2018-05-11 13:20 ` Eric S Fraga
2018-05-10 9:41 ` Michael Brand
2018-05-10 12:44 ` Nicolas Goaziou
2018-05-10 13:23 ` Michael Brand
2018-05-10 13:33 ` Nicolas Goaziou
2018-05-10 14:29 ` Michael Brand
2018-05-10 16:27 ` Nicolas Goaziou
2018-05-10 19:58 ` Samuel Wales
2018-05-12 23:35 ` Samuel Wales
2018-05-13 11:10 ` Eric S Fraga
2018-05-10 19:59 ` Michael Brand
2018-05-11 0:22 ` Nicolas Goaziou
2018-05-11 13:10 ` Nicolas Goaziou
2018-05-11 13:55 ` Michael Brand
2018-05-11 14:15 ` Nicolas Goaziou
2018-05-12 8:12 ` Michael Brand
2018-05-17 16:17 ` Michael Brand [this message]
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=CALn3zogGirUaqDMuxdXoSWr8BpxOiz_3mZX3t8wDsONKuDXvjQ@mail.gmail.com \
--to=michael.ch.brand@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.