From: "Christopher M. Miles" <numbchild@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: numbchild@gmail.com, Org mode <emacs-orgmode@gnu.org>
Subject: [CLOSED] Re: [BUG] Org mode treat tags as links
Date: Sat, 29 Oct 2022 17:22:40 +0800 [thread overview]
Message-ID: <m25yg3x9ta.fsf@numbchild@gmail.com> (raw)
In-Reply-To: <87y1szi42i.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 1332 bytes --]
Ihor Radchenko <yantar92@posteo.net> writes:
> "Christopher M. Miles" <numbchild@gmail.com> writes:
>
>> I defined a custom link type "video:".
>>
>> And when I added tag "video" in tags like bellowing:
>>
>> #+begin_src org
>> * headline 1 :tag1:video:hello
>> #+end_src
>
> Note that this particular example actually contains a link. Because you
> forgot the closing ":" in the tags.
>
> I guess you meant
>
> * headline 1 :tag1:video:hello:
>
Yes, I miss typed the last colon. Thanks for understanding correctly.
>> It caused the tag ":video:" parsed and recognized as link. Here is the screenshot:
>> I suppose the link parsing need to be improved.
>
> This is fontification error.
> You can examine the parser state by issuing M-: (org-element-context) with
> point at the "link". It is correctly recognized as a headline with no link.
>
> The error is due to limitations in our current implementation of
> fontification. Will be fixed in
> https://orgmode.org/list/87ee7c9quk.fsf@localhost
I see, Thanks for notifying.
--
[ stardiviner ]
I try to make every word tell the meaning that I want to express without misunderstanding.
Blog: https://stardiviner.github.io/
IRC(libera.chat, freenode): stardiviner, Matrix: stardiviner
GPG: F09F650D7D674819892591401B5DF1C95AE89AC3
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2022-10-29 9:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-29 4:13 [BUG] Org mode treat tags as links Christopher M. Miles
2022-10-29 5:36 ` Ihor Radchenko
2022-10-29 9:22 ` Christopher M. Miles [this message]
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=m25yg3x9ta.fsf@numbchild@gmail.com \
--to=numbchild@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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).