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

destructive influence of possible recent updates of either org-mode or svg-tag-mode #47

Open
wolfangpauli opened this issue Aug 11, 2023 · 1 comment

Comments

@wolfangpauli
Copy link

Salut Nicolás,

As I have pointed out in April 2023 (cf. #41 (comment)) I am using notebook-mode/svg-tag-mode in some of my org documents (under doom emacs), i.e., "notebook-mode"

A recent upgrade/update/change of either org-mode (9.7) or svg-tag-mode had a strange destructive impact on my org notebooks.

The svg-tags are only rendered partially, i.e. the further one goes down the lesser the number of rendered svg-tags.

Let's say, rendering of svg-tags stops somewhere in the middle of an org file and in addition some tags are rendered further down whereas "#+begin_src" tags stop being rendered somewere at the beginning.... (I suspected that the presence of inline-images is responsible for that - but after testing - I think, it isn't)

I either have an org document perfectly colored depending on the text properties (section, programming language, tags) or I have partly rendered org files without some colored elements beginning somewhere ...
Unfortunately i was not able to find out where org-mode breaks. (switching on org-mode again renders a perfect document, but all rendered svg-tags vanish)

What I have noticed is, that switching on svg-tag-mode always shows errors:

Error during redisplay: (jit-lock-function 5959) signaled (wrong-type-argument stringp nil)
Error during redisplay: (jit-lock-function 7795) signaled (wrong-type-argument stringp nil)
Error during redisplay: (jit-lock-function 9338) signaled (wrong-type-argument stringp nil)
Error during redisplay: (jit-lock-function 4763) signaled (wrong-type-argument stringp nil)

I have tried turning jit-lock-debug-mode on and off to no avail.

Do you have a slightest glimpse of what's going on here and what could be a possible solution/workaround.

I'm on (doom)emacs 28.2, org-mode 9.7 (i have reinstalled emacs in different versions 28.1, 28.2, ...) always the same effect.

Best regards and many thanks in advance,
-.w.p.-

@rougier
Copy link
Owner

rougier commented Aug 24, 2023

From your description, I suspect something wrong with the (add-to-list 'font-lock-extra-managed-props 'display) (because I got a lot of jit-lock warning when I debuged earlier version). To debug, I would start with a minimal org file where the problem occurs and then I would manipulate the svg-tag-mode to remove some features (like editing tag) to check when it breaks.

Alos, does it happen only with doom emacs?

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

2 participants