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
The help text for org-edit-src-content-indentation states, "[org-edit-src-content-indentation] has no effect if org-src-preserve-indentation is non-nil." However, the value of :indent-offset in define-auto-innermode does not take into account the value of org-src-preserve-indentation.
Any easy workaround for users is to set org-edit-src-content-indentation to 0. Alternatively, if the argument to :indent-offset can be a quoted function, one could easily be defined to respect both values.
The text was updated successfully, but these errors were encountered:
org-edit-src-content-indentation is used only as a default value of body-indent-offset which is not intended to respect that variable semantics. I had to pick the default from somewhere and that variable seemed the most appropriated place to sniff it from.
The question is whether it's feasible to use a function as the value of body-indent-offset. On reconsideration, though, I don't know if that would provide any tangible benefits over just more clearly documenting that org-src-preserve-indentation is ignored.
The help text for
org-edit-src-content-indentation
states, "[org-edit-src-content-indentation
] has no effect iforg-src-preserve-indentation
is non-nil." However, the value of:indent-offset
indefine-auto-innermode
does not take into account the value oforg-src-preserve-indentation
.Any easy workaround for users is to set
org-edit-src-content-indentation
to 0. Alternatively, if the argument to:indent-offset
can be a quoted function, one could easily be defined to respect both values.The text was updated successfully, but these errors were encountered: