emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Martin Marshall <law@martinmarshall.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] org-ctags: Fix regexp to not break radio targets
Date: Mon, 12 Feb 2024 14:05:57 +0000	[thread overview]
Message-ID: <87eddhn5fe.fsf@localhost> (raw)
In-Reply-To: <87frxylw33.fsf@martinmarshall.com>

Martin Marshall <law@martinmarshall.com> writes:

> Subject: [PATCH] org-ctags: Fix regexp to not break radio-target links
>
> * org-ctags.el (org-ctags-tag-regexp): Add left angle-bracket to
> excluded characters for tag text.
> ...
> This updates `org-ctags-tag-regexp' to avoid adding broken entries for
> radio targets in the TAGS file.
>
> With the old regexp, org-ctags would add radio targets to the TAGS file
> with an extra angle bracket at the beginning.  So a target of
> "<<<radio target>>>" would be entered in the TAGS file as
> "<radio target", instead of just "radio target".

Thanks!
Applied, onto main, with amendments to the commit message.
I added a TINYCHANGE cookie and linked to this thread.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=38dd88268

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


  reply	other threads:[~2024-02-12 14:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-11 18:00 [PATCH] org-ctags: Fix regexp to not break radio targets Martin Marshall
2024-02-12 14:05 ` Ihor Radchenko [this message]
2024-02-12 17:19   ` Martin Marshall
2024-02-12 18:32     ` Ihor Radchenko
2024-02-12 19:19       ` Martin Marshall
2024-02-12 19:53         ` Ihor Radchenko
2024-02-12 21:35           ` Martin Marshall
2024-02-24 10:49           ` Bastien Guerry
2024-02-24 13:04             ` Ihor Radchenko

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=87eddhn5fe.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=law@martinmarshall.com \
    /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).