From: Robert Horn <rjhorn@alum.mit.edu>
To: "Gustav Wikström" <gustav.erik@gmail.com>
Cc: Bastien <bzg@gnu.org>, Nicolas Goaziou <n.goaziou@gmail.com>,
Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: link interfering with brackets when abbreviated
Date: Mon, 03 Mar 2014 18:16:03 -0500 [thread overview]
Message-ID: <m3zjl63mbw.fsf@quad.robs.office> (raw)
In-Reply-To: <CA+SyOP9=2_rW8Zyutd-b2Q_3F=3w0s68gFyUq9r3xYjEBZsvCQ@mail.gmail.com>
I'm a user who doesn't much care about link following command behavior,
but Bastien's point about context is important. The behavior of a
command needs to depend upon much more than just syntax.
Two really dramatic examples are region narrowing and outline folding.
When operating on a narrowed region there are a great many differences
in how commands behave. Similarly, when a headline is folded, commands
behave very differently.
So be very careful to include consideration of the context when defining
commands. Some context is much more subtle.
My one link related comment is that I'm very puzzled by those who think
that links in comments should not be followed. In programs I make heavy
use of links in comments so that the comment can include a "see this
[document]" as part of the comment. It's a link that other programmers
want to follow. I don't often put comments into my org files, but I
would expect to follow links in them also. In programming a comment
means "don't try to compile or execute this". It doesn't mean
destruction of all other semantic value. It means a highly selective
removal of semantics.
I would expect links in comments to still be followable.
R Horn
next prev parent reply other threads:[~2014-03-03 23:52 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-02 21:16 link interfering with brackets when abbreviated Gustav Wikström
2014-03-03 1:30 ` Ista Zahn
2014-03-03 19:33 ` Samuel Wales
2014-03-03 19:46 ` Samuel Wales
2014-03-03 22:18 ` Sebastien Vauban
2014-03-03 22:33 ` Samuel Wales
[not found] ` <CAJcAo8vh0F0tqgX4=gUhJoWFcAsTiwfyi7Fp=spQeoaBog1OMQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-04 12:16 ` Sebastien Vauban
2014-03-04 20:06 ` Samuel Wales
2014-03-19 11:19 ` Bastien
2014-03-03 10:58 ` Christian Moe
2014-03-03 16:11 ` Sebastien Vauban
2014-03-03 23:16 ` Robert Horn [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-10-03 12:11 Michael Brand
2014-02-26 15:10 ` Michael Brand
2014-02-26 15:25 ` Nicolas Goaziou
2014-02-26 15:44 ` Michael Brand
2014-02-26 15:54 ` Nicolas Goaziou
2014-02-26 16:22 ` Michael Brand
2014-02-26 16:41 ` Nicolas Goaziou
2014-02-26 17:03 ` Michael Brand
2014-02-26 17:20 ` Bastien
2014-02-26 19:02 ` Nicolas Goaziou
2014-02-26 22:54 ` Bastien
2014-02-27 10:28 ` Nicolas Goaziou
2014-02-27 11:04 ` Bastien
2014-02-27 20:01 ` Michael Brand
2014-02-27 22:08 ` Bastien
2014-02-27 23:43 ` Nicolas Goaziou
2014-03-01 18:44 ` Yasushi SHOJI
2014-03-01 20:20 ` Nicolas Goaziou
2014-03-01 20:54 ` Bastien
2014-03-01 20:57 ` Bastien
2014-03-01 21:35 ` Nicolas Goaziou
2014-03-01 21:50 ` Bastien
2014-03-01 22:14 ` Nicolas Goaziou
2014-03-02 13:35 ` Bastien
2014-03-03 14:12 ` Matt Lundin
2014-03-02 0:22 ` Yasushi SHOJI
2014-03-02 9:05 ` Nicolas Goaziou
2014-03-02 13:22 ` Bastien
2014-03-02 14:27 ` Nicolas Goaziou
2014-03-02 15:49 ` Bastien
2014-03-02 16:32 ` Thorsten Jolitz
2014-03-03 3:41 ` Josiah Schwab
2014-03-03 5:54 ` Michael Brand
2014-03-01 18:44 ` Yasushi SHOJI
2014-02-26 17:42 ` Bastien
2014-02-26 21:15 ` Nicolas Goaziou
2014-02-26 22:21 ` Bastien
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=m3zjl63mbw.fsf@quad.robs.office \
--to=rjhorn@alum.mit.edu \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=gustav.erik@gmail.com \
--cc=n.goaziou@gmail.com \
/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).