unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Juri Linkov <juri@linkov.net>
Cc: emacs-devel@gnu.org
Subject: Re: master 6458e16: New mode outline-cycle-minor-mode with Orgmode-like TAB cycling on headings
Date: Thu, 04 Mar 2021 14:07:55 -0500	[thread overview]
Message-ID: <jwvwnumkai1.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87o8fy7os5.fsf@mail.linkov.net> (Juri Linkov's message of "Thu,  04 Mar 2021 20:12:42 +0200")

>> [ As for how to resolve it (in terms of behavior rather than in terms
>>   of code), I think the cycling should only kick after trying
>>   indentation and the indentation function did not change the buffer.
>>   This is the kind of refinement in behavior which can't be obtained
>>   just by key bindings but is (barely) obtainable via `add-function`.  ]
>
> This fallback-on-no-op logic works for indentation, but not for e.g.
> diff-hunk-next (works only at the last hunk where TAB is no-op).

Indeed, it's no silver bullet.  In the case of `diff-hunk-next` and
`outline-minor-mode-cycle` we really have an irreconcilable
conflict, AFAICT.

> Another idea is to put the cycling keymap only at the beginning of the
> outline heading line.  Then at the beginning of the line TAB will cycle,
> while on the rest of the line TAB will fall back to the default binding
> to indent/navigate etc.

It might be a good idea to restrict the cycling behavior to the case
where we're at BOL, indeed (of course, it still won't help for
`diff-hunk-next`).

> Ah, this explains everything.  Now I tried to put it in the OVERRIDE part,
> and the result is angry fruit salad.

;-)


        Stefan




  reply	other threads:[~2021-03-04 19:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210303191236.24697.93201@vcs0.savannah.gnu.org>
     [not found] ` <20210303191237.2B2D720E1B@vcs0.savannah.gnu.org>
2021-03-03 20:13   ` master 6458e16: New mode outline-cycle-minor-mode with Orgmode-like TAB cycling on headings Stefan Monnier
2021-03-03 20:38     ` Juri Linkov
2021-03-03 21:44       ` Stefan Monnier
2021-03-04  8:58         ` Juri Linkov
2021-03-04 13:20           ` Stefan Monnier
2021-03-04 18:12             ` Juri Linkov
2021-03-04 19:07               ` Stefan Monnier [this message]
2021-03-04 17:03         ` Daniele Nicolodi
2021-03-04 18:06           ` Stefan Monnier
2021-03-04 20:38             ` Juri Linkov
2021-03-04 18:17           ` Juri Linkov
2021-03-04 19:37             ` Daniele Nicolodi
2021-03-04 20:35               ` Juri Linkov
2021-03-04 20:44                 ` Daniele Nicolodi
2021-03-04 20:53                   ` Juri Linkov
2021-03-04 22:57                 ` Stefan Monnier
2021-03-04  0:31       ` Gabriel do Nascimento Ribeiro
2021-03-04  9:05         ` Juri Linkov
2021-03-07 18:54           ` Juri Linkov
2021-03-07 18:53     ` 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=jwvwnumkai1.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.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.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).