[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Catching invisible edits: problem understanding doc
From: |
Alain . Cochard |
Subject: |
Catching invisible edits: problem understanding doc |
Date: |
Thu, 9 Feb 2023 16:22:04 +0100 |
Hello. The documentation (version 9.6) says:
2.2.3 Catching invisible edits
------------------------------
Sometimes you may inadvertently edit an invisible part of the
buffer and be confused on what has been edited and how to undo the
mistake. Setting ‘org-fold-catch-invisible-edits’ to non-‘nil’
helps preventing this.
I visit a new file. I type
* foo
then
<RET>
then
bar
Then I move the cursor one line up and press
<TAB>
So now the headline is folded and I see
* foo...
In my understanding, 'bar' is now in an invisible part of the buffer.
But whether org-fold-catch-invisible-edits is set to 'nil, 'error',
'show', 'show-and-error' or nothing (i.e., 'smart' by default in 9.6),
if then I do
M-x undo
I visually see no change, but I can observe by unfolding the headline
that 'bar' has disappeared. In my understanding of the documentation
above and of the docstring for org-fold-catch-invisible-edits, this
should only happen with 'nil'.
What am I understanding incorrectly? Thank you.
Tests performed with 'emacs -Q -l .emacs.git' with '.emacs.git' being
(add-to-list 'load-path "~/Org/Coch-git/org-mode/lisp")
(custom-set-variables
'(org-fold-catch-invisible-edits 'nil)
;; or 'error or 'show or 'show-and-error (or nothing)
)
giving:
Org mode version 9.6.1 (release_9.6.1-239-g739ccf @
/home/cochard/Org/Coch-git/org-mode/lisp/)
PS: a very minor incidental point: after 'bar' has disappeared, the
headline is then void, so I tend to say that the ellipsis should
immediately disappear as well.
--
EOST (École et Observatoire des Sciences de la Terre)
ITE (Institut Terre & Environnement) | alain.cochard@unistra.fr
5 rue René Descartes [bureau 110] | Phone: +33 (0)3 68 85 50 44
F-67084 Strasbourg Cedex, France | [ slot available for rent ]
- Catching invisible edits: problem understanding doc,
Alain . Cochard <=
- Should we extend org-catch-invisible-edits to more interactive commands? (was: Catching invisible edits: problem understanding doc), Ihor Radchenko, 2023/02/10
- Re: Should we extend org-catch-invisible-edits to more interactive commands? (was: Catching invisible edits: problem understanding doc), Alain . Cochard, 2023/02/11
- Re: Should we extend org-catch-invisible-edits to more interactive commands? (was: Catching invisible edits: problem understanding doc), Ihor Radchenko, 2023/02/11
- Re: Should we extend org-catch-invisible-edits to more interactive commands? (was: Catching invisible edits: problem understanding doc), Alain . Cochard, 2023/02/12
- [PATCH] Allow customizing commands affected by `org-fold-catch-invisible-edits' (was: Should we extend org-catch-invisible-edits to more interactive commands? (was: Catching invisible edits: problem understanding doc)), Ihor Radchenko, 2023/02/12
- Re: [PATCH] Allow customizing commands affected by `org-fold-catch-invisible-edits' (was: Should we extend org-catch-invisible-edits to more interactive commands? (was: Catching invisible edits: problem understanding doc)), Alain . Cochard, 2023/02/14
- Re: [PATCH] Allow customizing commands affected by `org-fold-catch-invisible-edits' (was: Should we extend org-catch-invisible-edits to more interactive commands? (was: Catching invisible edits: problem understanding doc)), Ihor Radchenko, 2023/02/16
- Re: [PATCH] Allow customizing commands affected by `org-fold-catch-invisible-edits' (was: Should we extend org-catch-invisible-edits to more interactive commands? (was: Catching invisible edits: problem understanding doc)), Alain . Cochard, 2023/02/17