emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Daimrod <daimrod@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-element-context doesn't parse consistently link with spaces
Date: Wed, 05 Mar 2014 22:37:01 +0900	[thread overview]
Message-ID: <87r46gahs2.fsf@tanger.home> (raw)
In-Reply-To: <87ha7clqz3.fsf@gmail.com> (Nicolas Goaziou's message of "Wed, 05 Mar 2014 14:22:56 +0100")

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> Hello,
>
> Daimrod <daimrod@gmail.com> writes:
>
>> I think that there is a bug in `org-element-context' because it doesn't
>> seem to parse link with spaces consistently.
>>
>> For example:
>>
>> #+BEGIN_EXAMPLE
>>             v
>> [[file:test 1 2 3]]
>>             ^
>> #+END_EXAMPLE
>>
>> If the cursor is before the '1', then `org-element-context' will return:
>>
>> #+BEGIN_EXAMPLE
>> (link (:type "file" :path "test" :raw-link "file:test" :application nil :search-option nil :begin 26 ...))
>> #+END_EXAMPLE
>>
>> if the cursor is one or after the '1', then `org-element-context' will return:
>>
>> #+BEGIN_EXAMPLE
>> (link (:type "file" :path "test%201%202%203" :raw-link "file:test%201%202%203" :application nil :search-option nil :begin 1 ...))
>> #+END_EXAMPLE
>
> I cannot reproduce it. What Org version do you use? Did you try to
> disable `org-element-use-cache'?

Sorry, it happens with:
#+BEGIN_EXAMPLE
[[file:test%201%202%203][file:test 1 2 3]]
#+END_EXAMPLE

I use org-mode version release_8.0.2-101-gce5988 (I follow the git
upstream) and I tried it with `org-element-use-cache' set to nil.


It doesn't happen with:
#+BEGIN_EXAMPLE
[[file:test 1 2 3]]
#+END_EXAMPLE
but as soon as the cursor leaves the link, org-mode rewrite the link to:
#+BEGIN_EXAMPLE
[[file:test%201%202%203][file:test 1 2 3]]
#+END_EXAMPLE


Best,

-- 
Daimrod/Greg

  reply	other threads:[~2014-03-05 13:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04  8:53 org-element-context doesn't parse consistently link with spaces Daimrod
2014-03-05 13:22 ` Nicolas Goaziou
2014-03-05 13:37   ` Daimrod [this message]
2014-03-05 13:45     ` Nicolas Goaziou
2014-03-05 14:12       ` Daimrod
2014-03-05 14:25         ` Nicolas Goaziou
2014-03-05 14:29           ` Bastien
2014-03-05 14:36             ` Daimrod
2014-03-05 15:02               ` Bastien
2014-03-05 15:35                 ` Thorsten Jolitz
2014-03-05 15:42                 ` Nicolas Richard
2014-03-05 16:04                   ` Bastien
2014-03-05 16:27                     ` Nicolas Richard
2014-03-13 15:01                       ` Bastien
2014-03-05 14:51             ` Nicolas Goaziou
2014-03-05 15:00               ` Bastien
2014-03-05 15:16                 ` Nicolas Goaziou
2014-03-05 15:40                   ` Bastien
2014-03-10 14:25                     ` Nicolas Goaziou
2014-03-08 12:45                   ` Achim Gratz
2014-03-05 14:30           ` Jonathan Leech-Pepin
2014-03-05 14:32           ` Daimrod
2014-03-05 14:52             ` Daimrod

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=87r46gahs2.fsf@tanger.home \
    --to=daimrod@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).