emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Mark Kerr <mark@kerrsolutions.ca>
Cc: emacs-orgmode@gnu.org
Subject: Re: [O] Bug: Bulk adding tags in agenda does not respect radio groups
Date: Mon, 24 Oct 2022 13:03:19 +0000	[thread overview]
Message-ID: <878rl5v0fc.fsf@localhost> (raw)
In-Reply-To: <CAM9qJ5K4Tx7hpQiRo1zuRJ7OhfJKALTgrCK-t8DYqJDnYX-UhQ@mail.gmail.com>

Mark Kerr <mark@kerrsolutions.ca> writes:

> I have a radio group of 3 tags defined in org-tag-alist: now. next, later.
> This tag group works correctly when editing the tags directly in the
> original org files or when the tags are edited individually in the agenda
> using ':'.
>
> When editing tags via the agenda's bulk editing command, however, adding a
> tag from that radio group does not remove any pre-existing tags from that
> group.
>
> For example, say an item is already tagged "now", and the tag "next" is
> added to it via bulk editing. The expected result is that the tag "next" is
> added and the tag "now" is removed. Instead, the result is ":now:next:", as
> the pre-existing tag is not removed.
>
> I have version 9.2.3

Sorry for the late reply.
This is yet another case where limited tag group support shows up.
Note that Org mode support for group tags is mostly tailored for agenda
matching. Commands are not well-adapted.
The fix will require careful review of Org code and is not trivial.
Patches always welcome though.

-- 
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:[~2022-10-24 13:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-10  1:37 Bug: Bulk adding tags in agenda does not respect radio groups Mark Kerr
2022-10-24 13:03 ` Ihor Radchenko [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=878rl5v0fc.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=mark@kerrsolutions.ca \
    /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).