From: Alain.Cochard@unistra.fr
To: Ihor Radchenko <yantar92@posteo.net>
Cc: alain.cochard@unistra.fr, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Should we extend org-catch-invisible-edits to more interactive commands? (was: Catching invisible edits: problem understanding doc)
Date: Sat, 11 Feb 2023 18:12:02 +0100 [thread overview]
Message-ID: <25575.52322.757469.405610@gargle.gargle.HOWL> (raw)
In-Reply-To: <87bkm1etd9.fsf@localhost>
Ihor Radchenko writes on Fri 10 Feb 2023 09:56:
> Only a handful of interactive commands support invisible edit
> checks. In particular: self-insert-command (typing), deleting char
> forward/backward, and `org-meta-return'.
>
> I guess we may instead provide a defcustom and hook the check into
> `pre-command-hook'. Would it be of interest?
Thank you for the feedback. Let me add that the issue I raised was
not at all a theoretical/abstract one for me. I constantly use 'undo'
to see where in the buffer I was working (then, I insert a space, do
'undo undo', and can resume what I was doing). So obviously it would
be of a huge interest for me if org-catch-invisible-edits worked in
that case...
At any rate, shouldn't "2.2.3 Catching invisible edits" be a little
bit more specific about what kind of invisible edits are concerned?
Or perhaps just a warning that it is not all of them.
> > 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.
>
> The headline still contains newlines.
Right. Thanks.
--
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 prev parent reply other threads:[~2023-02-11 17:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 15:22 Catching invisible edits: problem understanding doc Alain.Cochard
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 [this message]
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=25575.52322.757469.405610@gargle.gargle.HOWL \
--to=alain.cochard@unistra.fr \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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).