From: Denis PILAT <denis.pilat@st.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [TUI] correctly display windows source files
Date: Tue, 10 Oct 2006 13:23:00 -0000 [thread overview]
Message-ID: <452B9EB9.4040709@st.com> (raw)
In-Reply-To: <uwt79jnm4.fsf@gnu.org>
Eli Zaretskii wrote:
>>Date: Mon, 09 Oct 2006 17:21:41 +0200
>>From: Denis PILAT <denis.pilat@st.com>
>>
>>The TUI displays windows source files with and extra blank line between
>>each source line.
>>Line number are wrong and changes when source is moved up and down.
>>
>>This patch fixes this problem and should take the case of MAC OS
>>end-of-line into account.
>>
>>
>
>This is okay with me, but please be sure to test the code near the end
>of the file, because, according to my references, an attempt to ungetc
>EOF is ignored. What happens with a file that ends in a sole `\r'that?
>
>
>
I've tried files with '\r' end-of-lines but there are problems to open
them, in source.c:find_source_lines, only \n are taken as end-of-line.
Therefore the struct symtab given as an input parameter of
tui_set_source_content() function is wrong, that prevents the file to be
read correctly.
I don't want to mix this patch to a patch that may fix the problem in
source.c. I'll have a look at that anyway but I guess there could be a
lot of problem elsewhere to open '\r' only end-of-line files.
About your remark,
I've tried to ungetc(EOF) and I did not get any problem, after
ungetc(EOF) the next call to fgetc is still EOF.
Denis
next prev parent reply other threads:[~2006-10-10 13:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-09 15:25 Denis PILAT
2006-10-09 18:01 ` Mark Kettenis
2006-10-09 19:28 ` Eli Zaretskii
2006-10-10 13:23 ` Denis PILAT [this message]
2006-10-10 15:08 ` '\r' only end-of-line Denis PILAT
2006-10-10 21:34 ` Eli Zaretskii
2006-10-11 10:08 ` Denis PILAT
2006-10-11 13:33 ` Daniel Jacobowitz
2006-10-11 13:57 ` Andrew STUBBS
2006-10-11 14:01 ` Daniel Jacobowitz
2006-10-11 14:44 ` Andrew STUBBS
2006-10-11 15:05 ` Daniel Jacobowitz
2006-10-11 17:47 ` Eli Zaretskii
2006-10-11 17:36 ` Eli Zaretskii
2006-10-16 8:51 ` Denis PILAT
2006-10-10 21:24 ` [TUI] correctly display windows source files Eli Zaretskii
2006-10-11 8:02 ` Denis PILAT
2006-10-11 8:39 ` Eli Zaretskii
2006-10-11 11:23 ` Frederic RISS
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=452B9EB9.4040709@st.com \
--to=denis.pilat@st.com \
--cc=eliz@gnu.org \
--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