public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Tom Tromey <tom@tromey.com>,  gdb-patches@sourceware.org
Subject: Re: [RFC] Fix pager bugs with style output
Date: Tue, 12 Feb 2019 17:13:00 -0000	[thread overview]
Message-ID: <87o97h6ibv.fsf@tromey.com> (raw)
In-Reply-To: <20190210123813.GA31881@adacore.com> (Joel Brobecker's message of	"Sun, 10 Feb 2019 16:38:13 +0400")

>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:

Joel> As for the second one, I can present the symptoms here, but so far,
Joel> my efforts to reproduce it with a piece of code we can share here,
Joel> has remained fruitless :-(. Only with the example we have, which
Joel> unfortunately is code sent to us by a customer, can I reproduce.
Joel> In our testsuite, we named the testcase XXXX-XXX__separate. It uses
Joel> the "list" command, and it's as if the source had some extra empty
Joel> lines that are not there.
[...]
Joel> Not sure if it makes a difference or not, but I'm not using
Joel> GNU Highlight (yet).

It does make a difference, thanks for noting that.
It's easy to see the bug with a short C file that uses \r\n line endings.

Tom

  parent reply	other threads:[~2019-02-12 17:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-09 18:37 Tom Tromey
2019-02-10 12:38 ` Joel Brobecker
2019-02-12 13:53   ` Andrew Burgess
2019-02-12 17:08     ` Tom Tromey
2019-02-14  3:34       ` Joel Brobecker
2019-02-12 17:13   ` Tom Tromey [this message]
2019-02-12 18:22   ` Tom Tromey
2019-02-17 12:31     ` Joel Brobecker
2019-02-17 15:34       ` Tom Tromey

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=87o97h6ibv.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.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.
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).