> Perhaps there's a BLODA issue? Though I didn't see anything in cygcheck.out.
I have Google Desktop on one of the machine where the bad behavior
happens, but the other machine has none of the softwares in the BLODA
list.
> Are the characters are not printing at all, or are they perhaps being
> o
On Jan 4 21:05, Eduardo D'Avila wrote:
> Using the %s didn't solve the problem:
>
>
> erdav...@antares ~/perl/feedbacks
> $ cat BUG.c
> #include
>
> int main() {
> const char * str =
> "0123456789"// 0 - 9
> "0123456789"// 10 - 19
>
On Tue, Jan 5, 2010 at 8:15 AM, Eduardo D'Avila wrote:
>> What terminal are you using, what is your encoding set to, etc?
>
> I'm not sure what you mean here. I run the terminal by clicking on the
> Start menu shortcut "Cygwin Bash Shell" that was created by setup.exe.
OK, so you're using the stan
> What terminal are you using, what is your encoding set to, etc?
I'm not sure what you mean here. I run the terminal by clicking on the
Start menu shortcut "Cygwin Bash Shell" that was created by setup.exe.
There is an environment variable "TERM" with "cygwin" as value.
> I've tried creating the
On Mon, Jan 4, 2010 at 6:24 PM, Eduardo D'Avila wrote:
> I confirmed the bug on two different versions of Windows XP (Home and
> Professional Editions) at my home and my workplace. I've just checked
> also on a Windows Vista notebook and the bug didn't happen.
What terminal are you using, what is
The script I use displays string from an IMAP server. The best
solution would be splitting every string in pieces of at most 127
chars. This is a workaround, but the bug is still there and can show
up on other applications.
I confirmed the bug on two different versions of Windows XP (Home and
Prof
Using the %s didn't solve the problem:
erdav...@antares ~/perl/feedbacks
$ cat BUG.c
#include
int main() {
const char * str =
"0123456789"// 0 - 9
"0123456789"// 10 - 19
"0123456789"// 20 - 29
"01234567
On Mon, Jan 4, 2010 at 5:35 PM, Eric Blake wrote:
> What you've found is a bug in your own program, at lesat for the BUG.c version
> of your report.
The Perl and Python programs are not buggy, but they also don't
exhibit the behavior for me. Although I'm still running a prerelease
1.7.0
Both als
Eduardo D'Avila gmail.com> writes:
> I've found a bug that happens when the 128th (index 127 on a 0-based
> string) char of a string is a multibyte char. When I print such
> string, only the multibyte char and the chars after it are displayed.
What you've found is a bug in your own program, at l
9 matches
Mail list logo