You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some calendar related functions (e.g. org-deadilne) are failing with org-9.7 as org-journal is creating an entry in a calendar hook that calls the method org-journal--with-journal. This method creates a buffer in fundamental mode with org contents that are parsed with the org-element api, generating a warning that makes the invocation to fail.
Long story short, Spacemacs is using a 3y old fork of org-journal that has not seen any updates since. Meanwhile upstream seems to be back to life after a period of low activity and they have fixed this particular bug and some others.
Although it does not seem that the changes that started the fork have been merged upstream, it seems that moving back to, better supported, upstream would be a wise move for Spacemance. If these changes are needed, upstream might be more willing to accept it that it was 3y ago.
Alternatively, I guess that @dalanicolai could update his fork with the latest changes from upstream so that he can preserve his changes.
The text was updated successfully, but these errors were encountered:
Emacs 29.4
Head of Spacemacs develop branch
Some calendar related functions (e.g. org-deadilne) are failing with org-9.7 as org-journal is creating an entry in a calendar hook that calls the method
org-journal--with-journal
. This method creates a buffer in fundamental mode with org contents that are parsed with theorg-element
api, generating a warning that makes the invocation to fail.Long story short, Spacemacs is using a 3y old fork of org-journal that has not seen any updates since. Meanwhile upstream seems to be back to life after a period of low activity and they have fixed this particular bug and some others.
Although it does not seem that the changes that started the fork have been merged upstream, it seems that moving back to, better supported, upstream would be a wise move for Spacemance. If these changes are needed, upstream might be more willing to accept it that it was 3y ago.
Alternatively, I guess that @dalanicolai could update his fork with the latest changes from upstream so that he can preserve his changes.
The text was updated successfully, but these errors were encountered: