public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: "Dave Bryan" <dave.bryan@gmail.com>
To: "Keith Seitz" <keiths@redhat.com>
Cc: insight@sources.redhat.com, "Duane Ellis" <duane_ellis@franklin.com>
Subject: Re: Insight EOL display
Date: Thu, 08 Jun 2006 09:23:00 -0000	[thread overview]
Message-ID: <op.tatlo4p2010v0s@samsung> (raw)
In-Reply-To: <44870F0E.6070208@redhat.com>

Keith,

I'm seeing these markers part way through a file. In particular when I've  
edited a file thats part of a gcc project using Visual Studio. It seems to  
save the parts I've edited with \r\n eols but retains the original eols  
for the parts I haven't edited (I typically wouldn't edit the beginning of  
the file).  This confirms the suspicions that Duane mentioned about in his  
email so it looks as it is safer to parse the whole source when loading.

Off-subject but do you know how to get a hex display in the balloon popups  
when hovering over a variable ?

Regards
Dave

> Dave Bryan wrote:
>
>> I'm using Insight under Windows and I'm seeing end of line square  
>> markers in the source window.
>> Is there any way to get Insight to not display these markers ?
>
> Are you sure they are carriage returns? The function gdb_loadfile in  
> gdbtk-cmds.c already strips the carriage return:
>
>            /* Look for DOS style \r\n endings, and if found,
>             * strip off the \r.  We assume (for the sake of
>             * speed) that ALL lines in the file have DOS endings,
>             * or none do.
>             */
>
> Do you see these markers on EVERY line (in particular, the first)? Can  
> you find out what the value of the char is that is causing problems?
>
> Keith


      reply	other threads:[~2006-06-08  9:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-28 10:35 Dave Bryan
2006-06-07 17:38 ` Keith Seitz
2006-06-08  9:23   ` Dave Bryan [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=op.tatlo4p2010v0s@samsung \
    --to=dave.bryan@gmail.com \
    --cc=duane_ellis@franklin.com \
    --cc=insight@sources.redhat.com \
    --cc=keiths@redhat.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.
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).