From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Eric Hanchrow <erich@cozi.com>
Cc: 2350@emacsbugs.donarmstrong.com, emacs-pretest-bug@gnu.org
Subject: bug#2350: 23.0.90; compilation-mode inserts output in the wrong location
Date: Tue, 17 Feb 2009 11:42:41 -0500 [thread overview]
Message-ID: <jwvhc2t9fya.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <86ab8l3ody.fsf@ubuntu-erich.corp.cozi.com> (Eric Hanchrow's message of "Mon, 16 Feb 2009 16:20:25 -0800")
> This is arguably not a bug, but the behavior I'd expected is indeed
> useful: sometimes when a compilation is running, I want to study just
> part of the output, and it's convenient to narrow to just the part I
> want. With the current behavior, though, in order to avoid getting the
> *compilation* buffer's lines all mixed up, I must copy the interesting
> region to another buffer.
This is a fundamental problem in `narrow': its meaning is ambiguous.
Sometimes it is used to pretend that the buffer is really smaller than
it is, and other times it's used just to "focus" on a subpart.
The implementation (i.e. most of the C and Elisp code) tend to take the
first point of view, but sometimes users intend the other.
Maybe a good way to provide what the user wants is to introduce
a notion of window-local narrowing, or a visual-narrowing.
Stefan
next prev parent reply other threads:[~2009-02-17 16:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 0:20 bug#2350: 23.0.90; compilation-mode inserts output in the wrong location Eric Hanchrow
2009-02-17 16:42 ` Stefan Monnier [this message]
2009-02-18 12:09 ` Richard M Stallman
2009-02-18 14:25 ` Stefan Monnier
2009-02-18 23:05 ` Richard M Stallman
2009-02-18 23:52 ` Stefan Monnier
2009-02-18 23:05 ` Richard M Stallman
2016-01-21 19:54 ` Alan Third
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=jwvhc2t9fya.fsf-monnier+emacsbugreports@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=2350@emacsbugs.donarmstrong.com \
--cc=emacs-pretest-bug@gnu.org \
--cc=erich@cozi.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).