emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: alain.cochard@unistra.fr
Cc: 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: Mon, 17 Apr 2023 13:40:07 +0000	[thread overview]
Message-ID: <87bkjm1vbc.fsf@localhost> (raw)
In-Reply-To: <87wn4mgb5k.fsf@localhost>

Ihor Radchenko <yantar92@posteo.net> writes:

> Subject: [PATCH] org-fold: Allow customizing commands where invisible edits
>  are checked

Applied, onto main.

-- 
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>


      parent reply	other threads:[~2023-04-17 14:24 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
2023-04-17 13:39             ` Ihor Radchenko
2023-04-17 13:40           ` Ihor Radchenko [this message]

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=87bkjm1vbc.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=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).