unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 61062@debbugs.gnu.org
Subject: bug#61062: 29.0.60; Split Outline Mode node to Outline Minor Mode node
Date: Sat, 28 Jan 2023 19:59:47 +0200	[thread overview]
Message-ID: <86pmay4k18.fsf@mail.linkov.net> (raw)
In-Reply-To: <838rhocs0m.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 27 Jan 2023 10:15:37 +0200")

close 61062 29.0.60
quit

>> Another question that I'm not sure about is whether it makes sense to
>> mention all outline-minor-mode supported modes in etc/NEWS?  I mean
>> that we prepared outline-minor-mode related settings in some modes,
>> but not enabled outline-minor-mode in these modes.
>> 
>> For example, we set such values as outline-search-function,
>> outline-level, outline-minor-mode-use-buttons, etc.
>> in apropos-mode and xref.  So the users could easily enable
>> outline-minor-mode in these modes, and it will work
>> without additional customization.
>> 
>> Does it make sense to list these modes in etc/NEWS, so users will know
>> where they can enable outline-minor-mode?  Probably support for
>> apropos-mode could be mentioned under the section Help mode,
>> and outline-minor-mode for xref under the section Xref?
>
> If the list is not too long, I think listing those modes in NEWS would
> be useful.

Done.

>> BTW, it looks like more links could be added to the manual:
>
> Adding cross-references is always a Good Thing, thanks.  The only
> situation where such cross-references could be inappropriate is if
> some prior text in the same node and close enough already has a
> cross-reference to the same place.  In all other cases, such
> cross-references are most welcome.

Also pushed to emacs-29.





      reply	other threads:[~2023-01-28 17:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-25 17:31 bug#61062: 29.0.60; Split Outline Mode node to Outline Minor Mode node Juri Linkov
2023-01-25 17:51 ` Eli Zaretskii
2023-01-25 18:20   ` Juri Linkov
2023-01-25 19:54     ` Eli Zaretskii
2023-01-27  7:56       ` Juri Linkov
2023-01-27  8:15         ` Eli Zaretskii
2023-01-28 17:59           ` 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=86pmay4k18.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=61062@debbugs.gnu.org \
    --cc=eliz@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).