emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: webdev@toryanderson.com (Tory S. Anderson)
To: "orgmode list" <emacs-orgmode@gnu.org>
Subject: gnus links not followed, also avl-tree error (org-capture issues)
Date: Mon, 18 Apr 2022 09:27:11 -0600	[thread overview]
Message-ID: <8735ias980.fsf@byu.edu> (raw)

Org captures have become an intrinsic part of my daily workflow, but having just upgaded emacs and orgmode, I suddenly find two errors (which clearly have related causes, at least as far as the upgrades go).

First, when I create a new capture link from a Gnus message, it successfully creates the same orgmode link it ever did, eg:
=[[gnus:mail.pro#DM5PR0801MB3799D6BD01F4178BA5F89EBBF6F39@DM5PR0801MB3799.namprd08.prod.outlook.com][Email from Bonnie Bingham: Fw: Moody approved to work]]
However, when attempting to FOLLOW that link it doesn't take me there, instead prompting me with =No match - create this as a new heading? (y or n)
Second, most of my plain (just me typing entries) captures fail to complete at all.

=org-capture: Capture abort: Wrong type argument: avl-tree-, nil
This is sending me back years to before I developed a nicely tuned org workflow, and it isn't pleasant. Is there something I forgot to include, or have there been breaking syntax changes somewhere?

Org mode version 9.5.2 (9.5.2-ga0755e @ /home/torysa/emacs/.emacs.d/straight/build/org/)

GNU Emacs 28.1 (build 1, x86_64-suse-linux-gnu, GTK+ Version 3.24.33, cairo version 1.16.0)

- Tory


             reply	other threads:[~2022-04-18 15:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-18 15:27 Tory S. Anderson [this message]
2022-04-18 15:59 ` gnus links not followed, also avl-tree error (org-capture issues) Ihor Radchenko
2022-04-18 16:54   ` Tory S. Anderson
2022-04-19  3:03     ` Ihor Radchenko
2022-04-21 17:31       ` [RESOLVED] " Tory S. Anderson

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=8735ias980.fsf@byu.edu \
    --to=webdev@toryanderson.com \
    --cc=emacs-orgmode@gnu.org \
    /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).