To: "email@example.com" <firstname.lastname@example.org>
Cc: Kyle Meyer <email@example.com>
Subject: Re: Bug: org-clone-subtree-with-time-shift throws error [9.3 (release_9.3 @ /usr/share/emacs/27.1/lisp/org/)]
Date: Mon, 23 Nov 2020 12:54:50 +0000 [thread overview]
Message-ID: <2wYZbUrw599nuDG1iOkNr-TKx97Kz_P8lQtWItDxGy6lmet6WjkchDFBqmobRVspuQC15m0pPY0zzjesCqLhAOQcM42_lF99QWChY1_FdQYfirstname.lastname@example.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 661 bytes --]
Kyle Meyer wrote:
> Thanks for detailed report and nice reproduction steps.
> I believe this has already been addressed by c716b7c08 (org-id: Allow
> file name to be overridden on ID creation, 2020-04-16), which was
> included in the 9.3.7 release.
> related thread: https://orgmode.org/list/87a73caayj.fsf@phaktory/T/#u
Thanks for the reply. I used the version shipped with emacs in the report, and now I installed org 9.4 from the gnu default repository via package-list-packages within emacs and the error indeed goes away. Is that the recommended stable version to use? Should I report bugs against the latest git version only?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 509 bytes --]
next prev parent reply other threads:[~2020-11-23 12:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 8:59 Bug: org-clone-subtree-with-time-shift throws error [9.3 (release_9.3 @ /usr/share/emacs/27.1/lisp/org/)] skaphle
2020-11-20 6:06 ` Kyle Meyer
2020-11-23 12:54 ` skaphle [this message]
2020-11-23 22:58 ` Kyle Meyer
-- strict thread matches above, loose matches on Subject: below --
2020-11-15 16:00 skaphle
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 \
* 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
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).