From: "Martin Carlé" <mc@aiguphonie.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: [bug] fuzzy link not matching commented headlines
Date: Fri, 27 Mar 2015 11:29:21 +0200 [thread overview]
Message-ID: <m1zj6yhjpq.fsf@on27.dyndns.org> (raw)
In-Reply-To: <87twx7ldvi.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 3475 bytes --]
Great, thanks for the quick fix!
Well, besides exports there is also tangling. Still, thanks for the
warning. I am aware of the exports 'issue' but turned it into a feature
while automatically removing unresolvable internal links. As a result,
we get a nice private comment system for notes only relevant to author
during writing phase. (Notes in drawers are fine, but cannot be linked
up, as far as I know.)
All best,
mc
On 2015-03-26 Thu 22:09, Nicolas Goaziou wrote:
> Hello,
>
> Martin Carlé <mc@aiguphonie.com> writes:
>
>> Guess it's a bug that fuzzy links won't match a commented headline
>> whereas the other internal link types (custom_id and org ID) do.
>>
>> Or is there a special purpose for this specific type of link regarding comments?
>>
>> Just check the following example:
>>
>> ,------------------------------------------------------------------------------------------
>> | * First headline
>> | 1. fuzzy link to [[Second headline]] -- ok
>> | 2. fuzzy link to commented [[Third headline]] -- fails
>> |
>> | 3. custom_id link to commented [[#Fourth][Fourth headline]] -- ok
>> | 4. id link to commented [[id:D91E1EF3-2918-4F37-98EB-E2C92ACBE372][Fifth headline]] -- ok
>> |
>> | * Second headline
>> |
>> | * COMMENT Third headline
>> |
>> | * COMMENT Fourth headline
>> | :PROPERTIES:
>> | :CUSTOM_ID: Fourth
>> | :END:
>> |
>> | * Fifth headline
>> | :PROPERTIES:
>> | :ID: D91E1EF3-2918-4F37-98EB-E2C92ACBE372
>> | :END:
>> |
>> `------------------------------------------------------------------------------------------
>
> Thank you. This should be fixed in
> 22f732c2553cc8ab42e8465018042bf0f49b6f4f.
>
> However, this kind of link is sort of pointless, since it is bound to
> fail during export, as the targeted headline will be removed. As
> a consequence, this document cannot be exported, even though COMMENT
> keyword is only meaningful during export.
>
>
> Regards,
--
Fetch my gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 7E3CA33F
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 805 bytes --]
next prev parent reply other threads:[~2015-03-27 9:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 14:38 [bug] fuzzy link not matching commented headlines Martin Carlé
2015-03-26 20:09 ` Nicolas Goaziou
2015-03-27 9:29 ` Martin Carlé [this message]
2015-03-27 10:48 ` Nicolas Goaziou
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=m1zj6yhjpq.fsf@on27.dyndns.org \
--to=mc@aiguphonie.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).