From: Andrea Corallo <acorallo@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 73286@debbugs.gnu.org, Stefan Kangas <stefankangas@gmail.com>,
Paul Nelson <ultrono@gmail.com>
Subject: bug#73286: [PATCH] Add foldout command for widening to current fold
Date: Tue, 01 Oct 2024 14:50:24 -0400 [thread overview]
Message-ID: <yp1ikubwtcf.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <86frpk6tj2.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 28 Sep 2024 12:01:53 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Paul Nelson <ultrono@gmail.com>
>> Date: Mon, 16 Sep 2024 01:38:35 +0200
>>
>> The foldout package, which "zooms in" on document sections by
>> narrowing the buffer, doesn't play well with Emacs's other narrowing
>> features: after narrowing further within a fold, there's no easy way
>> to widen back to the fold's boundaries.
>>
>> This patch introduces foldout-widen-to-current-fold, a command that
>> widens to the current fold level (or to the whole buffer if not in a
>> fold).
>>
>> Example usage:
>> - Use foldout-zoom-subtree to zoom in on some section.
>> - Use narrow-to-defun to edit some function.
>> - Use foldout-widen-to-current-fold to return to the scope of the
>> zoomed-in section.
>>
>> Any feedback welcome.
>
> Thanks. This new feature LGTM, but I'm not convinced we should have a
> separate key binding for this new command by default. If we want to
> have a default key binding at all, maybe we should make "C-c C-x"
> invoke this command when given a negative argument.
>
> Stefan and Andrea, WDYT?
I'm happy to have the feature in. I guess we can introduce the
keybinding later in case it's requested.
Andrea
next prev parent reply other threads:[~2024-10-01 18:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-15 23:38 bug#73286: [PATCH] Add foldout command for widening to current fold Paul Nelson
2024-09-28 9:01 ` Eli Zaretskii
2024-10-01 9:46 ` Paul Nelson
2024-10-01 18:50 ` Andrea Corallo [this message]
2024-10-01 19:33 ` Stefan Kangas
2024-10-05 10:20 ` Eli Zaretskii
2024-10-05 11:14 ` Paul Nelson
2024-10-12 11:53 ` Eli Zaretskii
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=yp1ikubwtcf.fsf@fencepost.gnu.org \
--to=acorallo@gnu.org \
--cc=73286@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=stefankangas@gmail.com \
--cc=ultrono@gmail.com \
/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).