emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] link interfering with brackets when abbreviated


From: Christian Moe
Subject: Re: [O] link interfering with brackets when abbreviated
Date: Mon, 03 Mar 2014 11:58:30 +0100
User-agent: mu4e 0.9.9.5-dev6; emacs 24.3.1

+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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]