From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ista Zahn Subject: Re: link interfering with brackets when abbreviated Date: Sun, 2 Mar 2014 20:30:31 -0500 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40329) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WKHiZ-00046O-7n for emacs-orgmode@gnu.org; Sun, 02 Mar 2014 20:30:56 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WKHiY-0001hp-6f for emacs-orgmode@gnu.org; Sun, 02 Mar 2014 20:30:55 -0500 Received: from mail-pb0-x232.google.com ([2607:f8b0:400e:c01::232]:61543) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WKHiX-0001hE-Tv for emacs-orgmode@gnu.org; Sun, 02 Mar 2014 20:30:54 -0500 Received: by mail-pb0-f50.google.com with SMTP id md12so3077475pbc.23 for ; Sun, 02 Mar 2014 17:30:51 -0800 (PST) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Org Mode List Another user here, chiming in to support Nicolas's position. From my perspective orgmode is so vast and complicated that the number one thing we need (even from a user perspective) is predictability. I'd rather see minor conveniences removed in favor of a constancy and a logical interface. Best, Ista On Sun, Mar 2, 2014 at 4:16 PM, Gustav Wikstr=C3=B6m wrote: > 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 mu= ch > 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. > > 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 n= ot > 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. > > About the issue of links in comments (My opinion, for what it's worth): I= t's > a comment.. Expect it to behave as one. Worst case: copy the link and pas= te > it in the browser. > > About the issue of links in properties: Wouldn't it be nice to allow this= ? > Maybe a future functionality to consider? > > > Best regards > > Gustav Wikstr=C3=B6m