unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Gabriel do Nascimento Ribeiro <gabriel376@hotmail.com>
To: emacs-devel@gnu.org
Subject: Re: master 6458e16: New mode outline-cycle-minor-mode with Orgmode-like TAB cycling on headings
Date: Wed, 03 Mar 2021 21:31:04 -0300	[thread overview]
Message-ID: <CH2PR01MB5879B9A80590AA91D24CDE558B979@CH2PR01MB5879.prod.exchangelabs.com> (raw)
In-Reply-To: <87zgzkug5d.fsf@mail.linkov.net> (Juri Linkov's message of "Wed,  03 Mar 2021 22:38:22 +0200")


This is a great feature, thank you!  I could replace all my custom elisp
code that handles outline cycle/highlight on my init.el with the new
minor-modes, and everything has been working fine so far.

I think that having only the variables is fine, I can't see any special
need for the minor-modes.

> 4. (advice-add 'xref--insert-xrefs :after
>             (lambda (&rest _args)
>               (setq-local outline-regexp "/")
>               (outline-cycle-minor-mode +1)))
>    using file names as headings where S-TAB could provide
>    an overview of all found files

The use of outline-minor-mode + cycle on xref buffers is one of my main
use cases. However, having to setup the outline-regexp and to add a
defadvice seems a dirty hack.  Should Emacs provide better defaults for
xref and other modes (like Gnus) for an easier integration with
outline-minor-mode ?

As another suggestion, would be nice to add more keybidings, for
example, to navigate between headers. The name 'cycle', however, maybe
not be a good choice in case Emacs offers more keybidings for
outline-minor-mode.



  parent reply	other threads:[~2021-03-04  0:31 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 [this message]
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=CH2PR01MB5879B9A80590AA91D24CDE558B979@CH2PR01MB5879.prod.exchangelabs.com \
    --to=gabriel376@hotmail.com \
    --cc=emacs-devel@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.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).