From: Alain.Cochard@unistra.fr
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Catching invisible edits: problem understanding doc
Date: Thu, 9 Feb 2023 16:22:04 +0100 [thread overview]
Message-ID: <25573.3996.714544.156631@gargle.gargle.HOWL> (raw)
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 ]
next reply other threads:[~2023-02-09 15:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 15:22 Alain.Cochard [this message]
2023-02-10 9:56 ` Should we extend org-catch-invisible-edits to more interactive commands? (was: Catching invisible edits: problem understanding doc) Ihor Radchenko
2023-02-11 17:12 ` Alain.Cochard
2023-02-11 18:22 ` Ihor Radchenko
2023-02-12 6:32 ` Alain.Cochard
2023-02-12 15:23 ` [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-14 14:59 ` Alain.Cochard
2023-02-16 15:06 ` Ihor Radchenko
2023-02-17 7:41 ` Alain.Cochard
2023-04-17 13:39 ` Ihor Radchenko
2023-04-17 13:40 ` Ihor Radchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=25573.3996.714544.156631@gargle.gargle.HOWL \
--to=alain.cochard@unistra.fr \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).