emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [RFC] Change visibility for bracket links
Date: Mon, 10 Oct 2016 10:17:08 -0400	[thread overview]
Message-ID: <87k2dgffvf.fsf@gmail.com> (raw)
In-Reply-To: 11075f37-d56a-da83-dca7-f33b98001062@gmail.com

Clément Pit--Claudel <clement.pit@gmail.com> writes:

> On 2016-10-07 22:38, Adam Porter wrote:
>> I understand the motivation for making this change, but I respectfully
>> request that this be made configurable.  I much prefer the "clean" links
>> without visible brackets, and adding them would seem like a regression
>> to me.  I'm guessing that many current Org users would also prefer to
>> keep the brackets invisible.
>
> Adam, what do you think of my earlier suggestion (displaying the
> brackets when the pointer is on them, hiding them otherwise? (In the
> style of prettify-symbols-mode with unprettify-symbol-at-point)
>

I don't particularly care whether the brackets are shown or not, but I
dislike things that change the visual appearance as you roll over
them. The web is full of such things and they drive me bananas: you
are trying to read something and you roll over something in the text
that changes its appearance, possibly shifting the text that you are
reading and leaving you to chase it around the page - good bye,
concentration.  Even if you do it by just switching visibility on the
brackets, it's distracting when you are reading; it might be helpful
when composing but I'm not convinced even for that.

If this proposal is considered at all, *please* make it optional.

My 2 cents.

Thanks!
-- 
Nick

  parent reply	other threads:[~2016-10-10 14:17 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-05 15:40 [RFC] Change visibility for bracket links Nicolas Goaziou
2016-10-05 15:46 ` Rainer M Krug
2016-10-05 16:46 ` Marco Wahl
2016-10-05 21:13   ` Nicolas Goaziou
2016-10-05 19:21 ` Detlef Steuer
     [not found] ` <520C9DD6-7764-4B07-8E7A-FB42CC0CDF8A@dagertech.net>
2016-10-05 21:30   ` David A. Gershman
2016-10-05 22:26     ` Nicolas Goaziou
2016-10-06  0:16       ` David A. Gershman
2016-10-06  0:27         ` Clément Pit--Claudel
2016-10-07  6:13           ` Nicolas Goaziou
2016-10-12  9:27             ` Rasmus
     [not found]         ` <e78992df838c44419e7893671dbe2adb@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-10-06  7:38           ` Eric S Fraga
2016-10-06 14:53             ` William Denton
2016-10-08  2:38 ` Adam Porter
2016-10-08  3:50   ` Clément Pit--Claudel
2016-10-08  4:00     ` Adam Porter
2016-10-10 14:17     ` Nick Dokos [this message]
2016-10-10 14:56       ` Clément Pit--Claudel
2016-10-10 16:28         ` Nick Dokos
2016-10-14 20:00         ` Joost Kremers
2016-10-14 21:24           ` Thomas S. Dye
2016-10-12  7:10 ` Daniele Nicolodi
2016-10-12 10:37   ` Nicolas Goaziou
2016-10-12 10:40     ` Nicolas Goaziou
2016-10-12 17:36     ` Daniele Nicolodi
2016-10-13 12:07       ` Nicolas Goaziou
2016-10-13 12:28         ` Aaron Ecay
2016-10-13 12:35           ` Nicolas Goaziou
2016-10-13 13:20             ` Michael Brand
2016-10-13 18:23               ` Nicolas Goaziou
2016-10-13 17:46             ` Gregor Zattler
2016-10-13 22:05             ` [RFC] " Aaron Ecay
2016-10-13 17:31         ` Daniele Nicolodi
2016-10-13 18:33           ` Nicolas Goaziou
2016-10-13 19:11           ` William Denton
2016-10-12  9:23 ` Rasmus
2016-10-12 10:32   ` Nicolas Goaziou
2016-10-12 11:08     ` Rasmus
2016-10-12 12:21       ` Nicolas Goaziou
2016-10-12 12:47         ` Rasmus
2016-10-13 12:30           ` Nicolas Goaziou
2016-10-20 23:44             ` Clément Pit--Claudel
2016-10-22  1:02               ` Stig Brautaset
2016-10-13 12:19 ` Rasmus
2016-10-13 16:13   ` Nick Dokos
2016-10-13 16:24     ` Rasmus
2016-10-13 16:43     ` Clément Pit--Claudel
2016-10-13 17:18       ` Nick Dokos
2016-10-13 12:19 ` Rasmus

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=87k2dgffvf.fsf@gmail.com \
    --to=ndokos@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).