From: "Tory S. Anderson" <webdev@toryanderson.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: orgmode list <emacs-orgmode@gnu.org>
Subject: [RESOLVED] Re: gnus links not followed, also avl-tree error (org-capture issues)
Date: Thu, 21 Apr 2022 11:31:44 -0600 [thread overview]
Message-ID: <874k2ml4vz.fsf_-_@toryanderson.com> (raw)
In-Reply-To: <877d7lpyfp.fsf@localhost> (Ihor Radchenko's message of "Tue, 19 Apr 2022 11:03:06 +0800")
The avl-tree error was an issue with vertico, which I updated and it went away.
The Gnus Links error seems to have gone away with that updgrade, too.
Thanks!
- Tory
Ihor Radchenko <yantar92@gmail.com> writes:
> "Tory S. Anderson" <webdev@toryanderson.com> writes:
>
>>> Thanks for reporting! Are you able to reproduce with emacs -Q?
>>
>> Thanks! I am not sure what an emacs -Q would mean in cases like this, since they are custom written capture templates in the first place, so -Q would lose them.
>
> Please refer to https://orgmode.org/manual/Feedback.html
> Basically, you can create the minimal possible config containing your
> problematic custom capture template and whatever it takes to trigger the
> problem and share it + steps to reproduce.
>
> Otherwise, it is very difficult to debug the problem on our side.
>
>> Important update: By including all of org-contrib the two problems go away, although other problems are introduced. But trying to search the contrib for which things in particular are solving these errors has not been successful.
>
> You may try to bisect your config. I have recorded a video explaining
> how to do it:
> https://open.tube/videos/watch/4d819114-43bf-42df-af94-f94fc53dd0d9
>
> Best,
> Ihor
prev parent reply other threads:[~2022-04-21 18:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 15:27 gnus links not followed, also avl-tree error (org-capture issues) Tory S. Anderson
2022-04-18 15:59 ` Ihor Radchenko
2022-04-18 16:54 ` Tory S. Anderson
2022-04-19 3:03 ` Ihor Radchenko
2022-04-21 17:31 ` Tory S. Anderson [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=874k2ml4vz.fsf_-_@toryanderson.com \
--to=webdev@toryanderson.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@gmail.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
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).