From: Yuan Fu <casouri@gmail.com>
To: Juri Linkov <juri@linkov.net>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: Duplicated outline-cycle binding, and problems with the new one
Date: Mon, 3 Jan 2022 17:40:22 -0800 [thread overview]
Message-ID: <F386EF2F-DEFC-430B-BAF3-D5C1B8EC07BE@gmail.com> (raw)
In-Reply-To: <86mtke3q0z.fsf@mail.linkov.net>
> On Jan 2, 2022, at 11:18 AM, Juri Linkov <juri@linkov.net> wrote:
>
>>>> Overall, from my limited knowledge, I think the old approach is more
>>>> reliable: I wouldn’t have this problem with the old approach. And the
>>>> new functionality added by the new approach and
>>>> outline-minor-mode-cycle-filter can be easily implemented in the old
>>>> approach. We don’t need to fiddle with font-lock-keywords with the
>>>> old approach, either. How about we go back to the old approach?
>>>
>>> Some time ago we discussed this possibility, but it will require writing
>>> too many wrappers for different modes, for example, for diff-mode:
>>>
>>> (defvar-keymap diff-mode-shared-map
>>> "TAB" (lambda () (interactive)
>>> (if (and outline-minor-mode (outline-on-heading-p))
>>> (outline-cycle)
>>> (diff-hunk-next)))
>>> ...
>>
>> Why? The old approach used a conditional binding, so it should "just
>> work" without the major modes knowing about it.
>
> Then maybe something like this (not tested):
[…]
This looks really good to me, for what it’s worth.
Yuan
next prev parent reply other threads:[~2022-01-04 1:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-31 23:32 Duplicated outline-cycle binding, and problems with the new one Yuan Fu
2022-01-02 18:25 ` Juri Linkov
2022-01-02 19:07 ` Stefan Monnier
2022-01-02 19:18 ` Juri Linkov
2022-01-04 1:40 ` Yuan Fu [this message]
2022-01-05 18:35 ` Juri Linkov
2022-01-05 19:21 ` Stefan Monnier
2022-01-06 18:56 ` Juri Linkov
2022-01-09 22:55 ` Yuan Fu
2022-01-10 8:21 ` Juri Linkov
2022-01-10 18:30 ` Juri Linkov
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F386EF2F-DEFC-430B-BAF3-D5C1B8EC07BE@gmail.com \
--to=casouri@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=monnier@iro.umontreal.ca \
/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.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).