From: Alain.Cochard@unistra.fr
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Alain.Cochard@unistra.fr, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: 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))
Date: Fri, 17 Feb 2023 08:41:01 +0100 [thread overview]
Message-ID: <25583.12173.190743.574315@gargle.gargle.HOWL> (raw)
In-Reply-To: <87v8k1ved2.fsf@localhost>
Ihor Radchenko writes on Thu 16 Feb 2023 15:06:
> As the docstring states, the check is performed at point. Checking
> the actual modifications would be rather tricky. It might be done,
> but there are so many caveats that the code will be fragile.
OK, too bad. Thanks for trying.
--
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-17 7:42 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=25583.12173.190743.574315@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.