all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Third <alan@idiocy.org>
To: Richard M Stallman <rms@gnu.org>
Cc: 2350@debbugs.gnu.org, erich@cozi.com,
	Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#2350: 23.0.90; compilation-mode inserts output in the wrong location
Date: Thu, 21 Jan 2016 19:54:35 +0000	[thread overview]
Message-ID: <m2fuxq7lok.fsf@galloway.idiocy.org> (raw)
In-Reply-To: <E1LZvTw-0005tW-TE@fencepost.gnu.org> (Richard M. Stallman's message of "Wed, 18 Feb 2009 18:05:32 -0500")

Richard M Stallman <rms@gnu.org> writes:

>     But what isn't clear is whether it's always the right thing to do: it's
>     clear in this particular use of narrow, but there might be other uses of
>     narrow in conjunction with compilation buffers where it would be the
>     wrong thing to do.
>
> I looked at the code, and I think it is clear what to do: make sure
> that narrowing does not prevent insertion at the specified insertion point.
>
> Does this change make it work?

<snip diff>

I can't replicate this behaviour in Emacs 25 and the patch provided in
this email was applied in 2009:


commit 0b508a27360a82763d4d7256b4cd526f9d3514aa
Author: Richard M. Stallman <rms@gnu.org>
Date:   Mon May 18 16:30:59 2009 +0000

    * progmodes/compile.el (compilation-filter): If inserting at end
    of accessible part of buffer, keep end of output visible.


I believe we can close this bug report.

-- 
Alan Third





      reply	other threads:[~2016-01-21 19:54 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
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 [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2fuxq7lok.fsf@galloway.idiocy.org \
    --to=alan@idiocy.org \
    --cc=2350@debbugs.gnu.org \
    --cc=erich@cozi.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=rms@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 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.