From: Aaron Ecay <aaronecay@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: [RFC] Change visibility for bracket links
Date: Thu, 13 Oct 2016 23:05:51 +0100 [thread overview]
Message-ID: <871szjj45c.fsf@gmail.com> (raw)
In-Reply-To: <878tts5svn.fsf@nicolasgoaziou.fr>
Hi Nicolas,
2016ko urriak 13an, Nicolas Goaziou-ek idatzi zuen:
>
> Hello,
>
> Aaron Ecay <aaronecay@gmail.com> writes:
>
>> FWIW, I agree. On the other hand, many people object to the brackets.
>
> I don't mind adding a variable.
I think that org in general has too many customization variables. Of
course, for each of them there is some user(s) who regard it as very
important to their workflow. So, we should think hard before
introducing new ones about whether there is a way to accomplish what we
want which does not need a variable. (Of course, sometimes this goal is
not possible and a new defcustom is needed.)
[...]
>> WDYT?
>
> That would only partly solve the problem. Cursor's color would tell you
> where you are, but the dance (e.g., C-a or backward-forward) is still
> needed to effectively move to the other side.
Yes: the point will always be in only one of the two positions indicated
in my previous mail. And some command(s) will always be needed to move
between the two. AFAICT this remains true under any scenario: the status
quo, the proposal for visible brackets, or the one for distinctive cursor
color. The question as I understood it is finding a display mechanism
that communicates the information about which of the two positions point
is in when it is relevant, without being obtrusive during other
editing. You also pointed out the importance of making the commands
needed as obvious as possible.
I think the bracket proposal satisfies the goal of perspicuous commands,
but not of presenting the information only when relevant. Changing point
color satisfies the presentation criteria, but the movement commands
would not be very obvious.
The suggestion of hiding and showing markers based on point motion,
raised in another subthread, is interesting. It might be the best of
both worlds. I would like to try out a POC implementation. (I believe
I can predict the effect of either the brackets or the cursor colors on
my editing experience, but not necessarily the other.)
--
Aaron Ecay
next prev parent reply other threads:[~2016-10-13 22:06 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
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 ` Aaron Ecay [this message]
2016-10-13 17:31 ` [RFC] " 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=871szjj45c.fsf@gmail.com \
--to=aaronecay@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).