Omar Antolín Camarena <o...@matem.unam.mx> writes: > Setting org-catch-invisible-edits to 'error does catch > org-delete-backward-char (bound to <backspace> by default), but it doesn't > catch backward-kill-word (<C-backspace>), or kill-word with argument -1 (M-- > M-d), or backward-kill-sexp (ESC <C-backspace>). > ... > I'd suggest that naming the variable org-catch-invisible-edits strongly > suggests it should catch all deletions in the invisible text and that the > current behavior is misleading.
Catching all commands is impossible because we cannot know in advance which command (including user-defined) is going to perform editing and which does not. And throwing an error /while/ a command is performing edits can easily break command logic and cause unpredictable bugs. Not to mention that some commands are OK to edit inside folded text. Org mode now has `org-fold-catch-invisible-edits-commands' where you can manually specify the commands you want Org to abort before they are executed. Handled. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
