From: npostavs@users.sourceforge.net
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Stefan-W. Hahn" <stefan.hahn@s-hahn.de>, 25246@debbugs.gnu.org
Subject: bug#25246: 25.1.90; Buffer not responsible with overlay at buffer end.
Date: Fri, 23 Dec 2016 09:14:02 -0500 [thread overview]
Message-ID: <87oa02ag2d.fsf@users.sourceforge.net> (raw)
In-Reply-To: <83oa02zr2h.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 23 Dec 2016 15:57:10 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Fri, 23 Dec 2016 14:36:47 +0100
>> From: "Stefan-W. Hahn" <stefan.hahn@s-hahn.de>
>> Cc: 25246@debbugs.gnu.org, npostavs@users.sourceforge.net
>>
>> > If the change below, when applied to the master branch, gives good
>> > results, I will install it.
>>
>> tried this on Linux and Windows. Works really good.
>
> Thanks for testing.
>
>> The problem only arises if a single line of output in compilation buffer was
>> bigger then the screen width (and I have truncates-lines set to t) and had
>> no LF.
>
> Yes, this is because the after-string ends in a newline, so it causes
> the cursor to be displayed in a different screen line.
>
>> > Is this satisfactory enough to install this simple change?
>>
>> As said. It works very well.
>
> OK, thanks. Noam, do you agree?
Yes, this looks like a clear improvement.
next prev parent reply other threads:[~2016-12-23 14:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-22 9:13 bug#25246: 25.1.90; Buffer not responsible with overlay at buffer end Stefan-W. Hahn
2016-12-22 13:55 ` npostavs
2016-12-22 17:04 ` Eli Zaretskii
2016-12-23 0:01 ` npostavs
2016-12-23 7:33 ` Stefan-W. Hahn
2016-12-23 9:21 ` Eli Zaretskii
2016-12-23 11:08 ` Eli Zaretskii
2016-12-23 13:36 ` Stefan-W. Hahn
2016-12-23 13:53 ` npostavs
2016-12-23 14:16 ` Stefan-W. Hahn
2016-12-23 13:57 ` Eli Zaretskii
2016-12-23 14:14 ` npostavs [this message]
2016-12-23 14:19 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87oa02ag2d.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=25246@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=stefan.hahn@s-hahn.de \
/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.