From: Josh <josh@foxtail.org>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: 17401@debbugs.gnu.org, contact@zaneashby.co.nz
Subject: bug#17401: 24.4.50; Narrow to {region,page,defun} in an indirect clone buffer in the other window
Date: Sat, 10 May 2014 13:57:43 -0700 [thread overview]
Message-ID: <CANdFEAH-xPB+0Jtfr3ZMBn9fUMJB_ZKX5ebxKk-g1nHWRdW4Aw@mail.gmail.com> (raw)
In-Reply-To: <536E2451.3090808@orcon.net.nz>
On Sat, May 10, 2014 at 6:06 AM, Phil Sainty <psainty@orcon.net.nz> wrote:
> I've also noticed there are some org-mode specific narrowing
> commands as well, which should probably be supported. I did
> consider whether we could support all existing narrowing commands
> automagically with some trickery, but I concluded that the only
> approach I could think of was too convoluted and brittle for its
> own good, so I think simply adding a new function alongside each
> existing one is still the most practical way to go.
>
> Do we want both a `narrow-to-*-indirect' and an `...-other-window'
> variant for each case? I think the latter works very nicely with
> the C-x 4 n prefix (as per the initial patch), but I can see the
> utility in providing both functions.
What about doing something like `append-next-kill', for example a
new `next-narrow-indirect' command bound to `C-x n i'?
next prev parent reply other threads:[~2014-05-10 20:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-04 10:38 bug#17401: 24.4.50; Narrow to {region,page,defun} in an indirect clone buffer in the other window Phil Sainty
2014-05-04 13:43 ` Drew Adams
2014-05-08 0:05 ` Lennart Borgman
2014-05-10 13:06 ` Phil Sainty
2014-05-10 20:57 ` Josh [this message]
2014-05-11 4:12 ` Drew Adams
2020-09-18 13:57 ` Lars Ingebrigtsen
2020-09-18 16:02 ` Drew Adams
2020-09-18 21:22 ` Zane Ashby
2020-09-19 14:14 ` Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANdFEAH-xPB+0Jtfr3ZMBn9fUMJB_ZKX5ebxKk-g1nHWRdW4Aw@mail.gmail.com \
--to=josh@foxtail.org \
--cc=17401@debbugs.gnu.org \
--cc=contact@zaneashby.co.nz \
--cc=psainty@orcon.net.nz \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.