unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Phil Sainty <psainty@orcon.net.nz>
To: Lennart Borgman <lennart.borgman@gmail.com>
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: Sun, 11 May 2014 01:06:25 +1200	[thread overview]
Message-ID: <536E2451.3090808@orcon.net.nz> (raw)
In-Reply-To: <CANbX365u-6RuzYVUD1nQvEb2_vEaRgmm3C+JqJEJa6ktWBjLbw@mail.gmail.com>

On 8/05/2014 12:05, Lennart Borgman wrote:
> Here is my current version (which I think perhaps Phil can
> make something better of)

I was initially against the idea of naming the indirect buffer
according to the narrowed region, for the simple reason that the
name stops making sense as soon as you widen the buffer.

However, I expect that people are far less likely to widen these
buffers (as opposed to simply killing them); and this naming
approach would certainly be useful in the buffer list, so I think
it's a good idea after all.

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.


-Phil







  reply	other threads:[~2014-05-10 13:06 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 [this message]
2014-05-10 20:57     ` Josh
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

  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=536E2451.3090808@orcon.net.nz \
    --to=psainty@orcon.net.nz \
    --cc=17401@debbugs.gnu.org \
    --cc=contact@zaneashby.co.nz \
    --cc=lennart.borgman@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).