emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: John Mathena <jmmathena@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Setting org-map-continue from to avoid skipping headings while archiving no longer works [9.5.2 (9.5.2-gd01235 @ /home/john/.emacs.d/straight/build/org/)]
Date: Sat, 01 Jan 2022 14:36:34 +0800	[thread overview]
Message-ID: <87h7aonerx.fsf@localhost> (raw)
In-Reply-To: <874k6soyvg.fsf@localhost>

Ihor Radchenko <yantar92@gmail.com> writes:

> I tried to make sure that org-map-continue-from is not broken, but your
> scenario is apparently not covered by our tests.
> Let me investigate and fix this.

It turned out to be more tricky than I thought.

Fixed by 06f58e475

Let me know if you are still seeing the problem.


  reply	other threads:[~2022-01-01  6:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-28 16:39 John Mathena
2021-12-29  3:48 ` Ihor Radchenko
2022-01-01  6:36   ` Ihor Radchenko [this message]
2022-01-06 22:42     ` John Mathena
2022-01-07 14:20       ` 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:

  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=87h7aonerx.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jmmathena@gmail.com \
    --subject='Re: [BUG] Setting org-map-continue from to avoid skipping headings while archiving no longer works [9.5.2 (9.5.2-gd01235 @ /home/john/.emacs.d/straight/build/org/)]' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:


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).