From: Kyle Meyer <email@example.com> To: firstname.lastname@example.org Cc: "email@example.com" <firstname.lastname@example.org> 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 17:58:18 -0500 Message-ID: <email@example.com> (raw) In-Reply-To: <2wYZbUrw599nuDG1iOkNr-TKx97Kz_P8lQtWItDxGy6lmet6WjkchDFBqmobRVspuQC15m0pPY0zzjesCqLhAOQcM42_lF99QWChY1_FdQYfirstname.lastname@example.org> email@example.com writes: > 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? I suppose it depends largely on the user. For many, the version of Org bundled with Emacs will do, and it's not worth the hassle of installing it from another source. But, if you've hit into a bug that's fixed in the latest release or just always want to keep up with the latest release, then the default ELPA source is a good choice. There's also Org's ELPA archives, if you instead wanted code based off of the maint branch. https://orgmode.org/elpa.html > Should I report bugs against the latest git version only? Reporting a bug against the Org bundled with Emacs is fine. Many times this issue is still around, and a fix is applied to the maint branch and will be included in the next release. But if it turns out that it's already fixed, then there's no other action we take on our end. However, if a reporter is willing to take the time to check the latest release (or even the maint or master branch) or search the mailing list archives, that's of course appreciated and helpful.
next prev parent reply other threads:[~2020-11-23 22:59 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-16 8:59 skaphle 2020-11-20 6:06 ` Kyle Meyer 2020-11-23 12:54 ` skaphle 2020-11-23 22:58 ` Kyle Meyer [this message] -- strict thread matches above, loose matches on Subject: below -- 2020-11-15 16:00 skaphle
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://orgmode.org * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.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
Org-mode mailing list This inbox may be cloned and mirrored by anyone: git clone --mirror https://orgmode.org/list/0 list/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 list list/ https://orgmode.org/list \ firstname.lastname@example.org public-inbox-index list Example config snippet for mirrors. Newsgroups are available over NNTP: nntp://news.yhetil.org/yhetil.emacs.orgmode nntp://news.gmane.io/gmane.emacs.orgmode AGPL code for this site: git clone https://public-inbox.org/public-inbox.git