From: Ihor Radchenko <yantar92@gmail.com>
To: Jan Ulrich Hasecke <juh+org-mode@mailbox.org>
Cc: Org-mode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: frustrations
Date: Thu, 02 Dec 2021 09:41:36 +0800 [thread overview]
Message-ID: <87r1av7pgv.fsf@localhost> (raw)
In-Reply-To: <Yado1Oq8saqGDPn2@sokrates>
Jan Ulrich Hasecke <juh+org-mode@mailbox.org> writes:
> Today I discovered that pamparam does not work anymore with an error
> message mentioned here:
> https://github.com/nobiot/org-transclusion/issues/105
This most likely indicates that some third-party packages you use are
implementing risky Elisp practices known to break Org. The were also a
source of (pretty bad) issues in the past, but Org now shows the warning
explicitly.
If you can hunt down to the problematic package, I advice to report this
as a bug in there. If you think that third-party packages are fine and
Org is the cause, please open a separate thread.
> There are some more issues. Startup time of my emacs is more than 30
> seconds even after optimizing something with esup. I have 10.000+ files
> in my org-roam and fear that I hit some limitation either of org-roam or
> my hardware.
Such problem has been observed a few weeks ago. An update might help.
If not, you can try to set org-element-cache-persistent to nil. It can
theoretically improve loading Org if your hard drive is very slow.
> How do you configure your emacs using current versions like org 9.5 but
> at the same time avoiding problems with incompatible packages or newly
> introduced bugs?
From straight.el readme:
>> We support :branch, but not :commit or :version-regexp. To lock a package to a specific commit, use a lockfile. See also #246 for discussion of extensions to the recipe to support package pinning, which is a planned feature.
Best,
Ihor
next prev parent reply other threads:[~2021-12-02 1:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 12:21 frustrations Jan Ulrich Hasecke
2021-12-01 12:36 ` frustrations Timothy
2021-12-01 15:43 ` frustrations Arthur Miller
2021-12-01 12:56 ` frustrations Eric S Fraga
2021-12-01 15:52 ` frustrations Tim Visher
2021-12-01 22:12 ` frustrations Tim Cross
2021-12-03 9:36 ` frustrations juh
2021-12-02 1:41 ` Ihor Radchenko [this message]
2021-12-03 11:51 ` frustrations Dr. Arne Babenhauserheide
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=87r1av7pgv.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=juh+org-mode@mailbox.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).