From: Christian Moe <mail@christianmoe.com>
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 11:58:30 +0100 [thread overview]
Message-ID: <m2ppm37dm1.fsf@uio.no> (raw)
In-Reply-To: <CA+SyOP9=2_rW8Zyutd-b2Q_3F=3w0s68gFyUq9r3xYjEBZsvCQ@mail.gmail.com>
+1 -- Another user chiming in, broadly in agreement with Gustav,
details below.
Gustav Wikström writes:
> Hi, a "user" signing in. Although not involved in the development of this
> piece of software I'm taking the opportunity to chime in anyway.
>
> I'd like to give Nicolas Goaziou my support in this issue. It makes it much
> simpler to understand, use, develop and maintain the software if it is
> congruent. A well defined syntax, and tools that respect the rules of how
> to parse it, will IMO be of big importance moving forward.
I think we all agree on that. And I think the *presumption* should be
that incongruent features will have to go. Still, Org is about letting
users organize stuff as conveniently and flexibly as possible, and if
some very convenient feature relies on some ad-hoc solution, it should
be possible, on a case-by-case basis, to consider keeping it.
> About the issue of two links on the same line.. From my perspective (for
> what it's worth); Trying to open a link when not being inside a link with
> the mark should give the same behaviour as trying to open a link when on a
> headline. It is not certain which link is intended to be opened, so why not
> give the user the options available instead of guessing? Set the scope to
> parse to the current paragraph, to make a difference from calling C-c C-o
> from the headline. That, to me, is the intuitive behaviour.
+1? Sounds right to me. (This would also alert a user who *accidentally*
hits C-c C-o, instead of unexpectedly moving point to a target he didn't
mean to visit. Not sure if it's ever happened to me, but it could.)
BTW, in years of using Org I never ever realized that you *could* use
C-c C-o for anything outside a link...
> About the issue of links in comments (My opinion, for what it's worth):
> It's a comment.. Expect it to behave as one. Worst case: copy the link and
> paste it in the browser.
+1. I do have links in # comments. It's convenient, but I'd be OK with
the inconvenience of giving them up, if it helps make Org easier to
maintain. I can always put stuff in drawers.
> About the issue of links in properties: Wouldn't it be nice to allow this?
> Maybe a future functionality to consider?
+1? As a user, I've never been quite sure if it's good practice to put
Org links -- or timestamps -- in properties. But since it does actually
work (still does in 8.2.3), I do put them there. And once they are
there, I find it very convenient to be able to visit the link, and
manipulate the timestamps in all the ways Org enables.
Yours,
Christian
next prev parent reply other threads:[~2014-03-03 10:59 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 [this message]
2014-03-03 16:11 ` Sebastien Vauban
2014-03-03 23:16 ` Robert Horn
-- 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=m2ppm37dm1.fsf@uio.no \
--to=mail@christianmoe.com \
--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).