Dear Tim,
I think you may misunderstand my situation or just starting to reproduce the
issue.
My configuration result is NO NLS support, that means 'USE_NLS_PROGRESS_BAR'
is undefined.
I guess screenshot is necessary at this time.
And it will always fall to the 'else' case of
Hi Guys,
The algorithm to locate the string sequence, which is for scrolling long
file name in the downloading progress animation, is hard ;p
The only problem is the 'cols_to_bytes' function for no NLS feature, which
returns wrong bytes number should be copied! I guess.
Will some body take a
Hi Tim,
On Thu, Feb 16, 2017 at 09:33:08AM +0100, Tim Ruehsen wrote:
> Please try this patch, it works out for me even with your additional timing
> (thanks for that !)
> It fixes 504 handling in src/url.c and additionally adds Content-Length to
> error responses that come with a body.
That
On Thursday, February 16, 2017 4:10:22 PM CET YX Hao wrote:
> My bad! I made a stupid mistake!
> Then, how can Tim's case pass the 'iconv' function? Maybe the
> 'from_encoding' in 'convert_fname' function is the same as the
> 'to_encoding'. Did he download from a same encoding server???
>
On Thursday, February 16, 2017 4:10:22 PM CET YX Hao wrote:
> My bad! I made a stupid mistake!
> Then, how can Tim's case pass the 'iconv' function? Maybe the
> 'from_encoding' in 'convert_fname' function is the same as the
> 'to_encoding'. Did he download from a same encoding server???
>
My bad! I made a stupid mistake!
Then, how can Tim's case pass the 'iconv' function? Maybe the 'from_encoding'
in 'convert_fname' function is the same as the 'to_encoding'. Did he download
from a same encoding server???
在2017年02月16 14时07分, "Eli Zaretskii"写道:
> Date: Thu, 16
On Tuesday, February 14, 2017 4:20:26 PM CET Adam Sampson wrote:
> On Tue, Feb 14, 2017 at 04:03:13PM +, Adam Sampson wrote:
> > Your patch compiles, but doesn't fix the broken test. tcpdump traces
> > attached of the test succeeding and failing with the patch applied (it's
> > exactly the