From: Juri Linkov <juri@linkov.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: master 6458e16: New mode outline-cycle-minor-mode with Orgmode-like TAB cycling on headings
Date: Sun, 07 Mar 2021 20:53:24 +0200 [thread overview]
Message-ID: <87blbuhk2j.fsf@mail.linkov.net> (raw)
In-Reply-To: <jwvmtvk2eo3.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 03 Mar 2021 15:13:41 -0500")
> This is very welcome functionality (and the highlighting as well).
> I wonder if we really need the new minor modes, tho, instead of just
> sticking to the new `outline-minor-mode-cycle` and
> `outline-minor-mode-highlight` variables (which we could make into
> `defcustom`s).
Now I removed these modes, and replaced them with `defcustom`s.
> IOW, I wonder if there are many use cases where users will want to have
> some `outline-minor-mode` buffers with cycling and others without.
I'm not sure about the default values - the cycling keys still
get in the way in some cases.
prev parent reply other threads:[~2021-03-07 18:53 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
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 [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.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=87blbuhk2j.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=emacs-devel@gnu.org \
--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).