-
Notifications
You must be signed in to change notification settings - Fork 13
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
Losing org text properties #13
Comments
Text properties need not be moved. They are shared. The problem is most likely due to the fact that properties are no longer applied as they should. Probably in |
Thank you. I'm pretty new to emacs and it is not fully clear to me when and where text properties are applied. I will dig into to the org codebase to find out. My first guess is that the In general, the canonical way to check context in org-files today seems to be using |
@vspinu https://github.com/bzg/org-mode/blob/7a9a8a56af4cf02abc1fb86eda96f0c7dc6b0348/lisp/org.el#L5288 also edit1: |
I made the observation that org text properties are somewhat falling apart inside chunks after edititing in innermodes. E.g. i cannot check for
org-in-src-block-p
anymore (that function internally relies on(get-char-property)
. Is there anything I can do to make sure that text properties are reliably moved to the respective innermodes (ess and elisp in my case). My current workaround is a custom version of that predicate that falls back toorg-element-context
andorg-element-type
.The text was updated successfully, but these errors were encountered: