Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

org-appear broken with org 9.7.2 and newer #428

Open
3 tasks
dev-zero opened this issue Jan 24, 2025 · 1 comment
Open
3 tasks

org-appear broken with org 9.7.2 and newer #428

dev-zero opened this issue Jan 24, 2025 · 1 comment

Comments

@dev-zero
Copy link

Operating System

Mac

Additional Operating System information

No response

Emacs Version

29

Emacs Configuration Details

  • Native Compilation
  • pGTK
  • alternative package manager (use-package, straight.el, ...)

Anything else that may be related to the issue you're having?

Actually, I am using the latest pretest.

What happened?

I got this error when using the Crafted org-packages: Error in post-command-hook (org-appear--post-cmd): (wrong-type-argument number-or-marker-p nil).
Googling lead me to this issue: awth13/org-appear#58

What should have happened?

Crafted should either pin the compatible Org version or use the org-appear branch with the fix.

@dev-zero dev-zero added the bug Something isn't working label Jan 24, 2025
@jeffbowman
Copy link
Contributor

We don't track individual package versions in Crafted Emacs, nor do we track issues related to how multiple packages interact with each other.

We do make an attempt to provide an opinion on configuring some packages to provide a better user experience. The Crafted Emacs team will also do our level best to assist with configuration issues directly related to the code we provide, help debug or troubleshoot Crafted Emacs elements in your configuration, and sometimes give some general advice or other assistance as we have time and experience.

So, it is very unlikely we are going to track each individual package from external sources, figure out which ones need to be pinned to a specific version and why. Remember, our goal is to provide you a framework to bootstrap your own configuration so you can have a quicker way to setup your Emacs, but essentially, the configuration is yours, not ours. See the philosophy portion of the readme which spells out where we stand.

I did test this on a fresh install of Emacs running a bare minimum Crafted Emacs configuration and pulling in the crafted-org module. The version of org out of the box is 9.6.15. The version available from GNU ELPA is 9.7.20. The version of org-appear is 0.3.1. With org 9.6.15, I do not encounter the problem mentioned on this ticket. We deliberately prefer the released versions from melpa-stable which is why org-appear is at the version it is (as of this writing). Here are a couple of options that might help:

(add-to-list 'package-pinned-packages (cons 'org-appear "melpa")) which would get the current development version

(customize-set-variable 'package-load-list '((org "9.6.15") all)) which would lock the version of org to the built-in version. You would need to uninstall non-built-in versions first, add this line in your early-init.el file and restart Emacs.

I hope this helps, but the problem needs to be fixed outside of Crafted Emacs. Once the appropriate fixes are applied to the packages concerned and they are published to the normal archives, you would still need to update your packages and test again.

@sthesing sthesing removed the bug Something isn't working label Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants