From: "David A. Gershman" <dagershman@dagertech.net>
To: emacs-orgmode@gnu.org
Subject: Re: [RFC] Change visibility for bracket links
Date: Wed, 05 Oct 2016 14:30:12 -0700 [thread overview]
Message-ID: <2B66CB76-BBC4-4345-A310-CD034130DA1D@dagertech.net> (raw)
In-Reply-To: <520C9DD6-7764-4B07-8E7A-FB42CC0CDF8A@dagertech.net>
Not bad, but could it be customizable via variable giving the user the
choice?
>On October 5, 2016 8:40:08 AM PDT, Nicolas Goaziou
><mail@nicolasgoaziou.fr> wrote:
>>Hello,
>>
>>I'd like to make the following change to bracket links display (i.e.,
>>when `org-highlight-links' contains `bracket', which is the default).
>>
>>Basically, I want to leave a visible pair of brackets around the link,
>>i.e.,
>>
>> [[uri][description]]
>>
>>is displayed as
>>
>> [description]
>>
>>instead of
>>
>> description
>>
>>and
>>
>> [[uri]]
>>
>>is displayed as
>>
>> [uri]
>>
>>instead of
>>
>> uri
>>
>>The rationale behind this suggestion is that editing a mostly
>invisible
>>link is unintuitive when point is at the boundaries of its visible
>>part.
>>
>>More precisely, in the following visible part of a link
>>
>> description
>>
>>if point hits "d" from the right, changes happen in the description of
>>the link, but if point comes from the left, changes happen before the
>>link.
>>
>>I guess I could get used to it, but sometimes, the link happens to be
>>at
>>column 0. In this case, the only way to "come from the left" is to
>move
>>to the previous line and go past the newline character. This is, IMO,
>>very annoying, notwithstanding the fact that it is impossible to
>>realize
>>at the beginning of the buffer.
>>
>>Leaving a pair of brackets, OTOH, disambiguates the situation. Editing
>>before the opening bracket makes changes before the link. Conversely,
>>editing after the former makes changes to the uri or the description,
>>whichever is displayed.
>>
>>The cost a little more visual clutter, but it seems very acceptable to
>>me. I attach a quick patch for testing.
>>
>>Feedback welcome.
>>
>>Regards,
--
David A. Gershman, CISSP
dagershman@dagertech.net
next prev parent reply other threads:[~2016-10-05 21:31 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 [this message]
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
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=2B66CB76-BBC4-4345-A310-CD034130DA1D@dagertech.net \
--to=dagershman@dagertech.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).