From: Harald Hanche-Olsen <hanche@math.ntnu.no>
To: John Wiegley <jwiegley@gmail.com>, Eli Zaretskii <eliz@gnu.org>
Cc: "ahyatt@gmail.com" <ahyatt@gmail.com>,
"1452@debbugs.gnu.org" <1452@debbugs.gnu.org>
Subject: bug#1452: Acknowledgement (23.0.60; Problem with nextstep, longlines-mode,)
Date: Tue, 5 Jan 2016 21:15:48 +0000 [thread overview]
Message-ID: <etPan.568c3282.2c2f61c1.bc30@frigg> (raw)
In-Reply-To: <831t9v4uwc.fsf@gnu.org>
-----Original Message-----
From: Eli Zaretskii <eliz@gnu.org>
Date: 5 January 2016 at 21:46:40
> FWIW, I cannot reproduce this bug on my system. Note that the OP
> explicitly said that he only see this in the NS build, not on X. So I
> think this is indeed an NS specific bug related to display. Only
> someone who has access to NS can debug it.
The OP stopped using longlines-mode an eternity ago. 8-)
But when I try out my recipe in a recent nextstep build, I can’t reproduce it either.
At least not the visual aspect; after I disable longlines-mode, the newlines are still “decorated” with the properties (hard t read-nonsticky (hard)). But that has no consequences visually, as far as I can tell.
So I guess it’s okay to close the bug, with a slightly different rationale than the one given.
– Harald
next prev parent reply other threads:[~2016-01-05 21:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-29 13:53 bug#1452: 23.0.60; Problem with nextstep, longlines-mode, Harald Hanche-Olsen
[not found] ` <handler.1452.B.122796683914175.ack@emacsbugs.donarmstrong.com>
2008-11-29 14:52 ` bug#1452: Acknowledgement (23.0.60; Problem with nextstep, longlines-mode,) Harald Hanche-Olsen
2008-11-29 15:11 ` Harald Hanche-Olsen
2016-01-05 4:10 ` Andrew Hyatt
2016-01-05 17:32 ` Glenn Morris
2016-01-05 17:39 ` Andrew Hyatt
2016-01-05 17:53 ` Harald Hanche-Olsen
2016-01-05 18:38 ` Eli Zaretskii
2016-01-05 18:29 ` Eli Zaretskii
2016-01-05 20:38 ` John Wiegley
2016-01-05 20:46 ` Eli Zaretskii
2016-01-05 21:15 ` Harald Hanche-Olsen [this message]
2016-01-05 21:12 ` Andrew Hyatt
2016-01-05 21:34 ` John Wiegley
2016-01-05 21:50 ` Dmitry Gutov
2016-01-06 1:47 ` Andrew Hyatt
2016-01-06 1:53 ` Dmitry Gutov
2016-01-06 3:45 ` Eli Zaretskii
2016-01-07 1:42 ` Andrew Hyatt
2016-01-07 3:42 ` Eli Zaretskii
2016-01-07 3:54 ` Andrew Hyatt
2016-01-07 16:02 ` Eli Zaretskii
2016-01-06 8:28 ` Xue Fuqiao
2016-01-06 18:16 ` Glenn Morris
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=etPan.568c3282.2c2f61c1.bc30@frigg \
--to=hanche@math.ntnu.no \
--cc=1452@debbugs.gnu.org \
--cc=ahyatt@gmail.com \
--cc=eliz@gnu.org \
--cc=jwiegley@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).