From: Bastien <firstname.lastname@example.org>
To: Kyle Meyer <email@example.com>
Cc: Nicholas Savage <firstname.lastname@example.org>, email@example.com
Subject: Re: [PATCH] (org-remove-occur-highlights) Implements option to remove highlights between points
Date: Mon, 14 Dec 2020 07:32:41 +0100 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Kyle Meyer's message of "Tue, 22 Sep 2020 01:22:03 -0400")
Kyle Meyer <firstname.lastname@example.org> writes:
> It might be worth stepping back and describing what your use case for
> this change is, and considering other ways to address it (not
> necessarily as a change to Org itself).
Since the problem needs to be revisited, I've closed this patch.
Nicholas, feel free to tackle the initial issue differently and
to provide another patch in another dedicated thread. Thanks!
prev parent reply other threads:[~2020-12-14 6:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 2:02 [PATCH] (org-remove-occur-highlights) Implements option to remove highlights between points Nicholas Savage
2020-09-22 5:22 ` Kyle Meyer
2020-12-14 6:32 ` Bastien [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).