Janne Hyvärinen wrote:
> Sorry for spamming but I noticed one more display glitch while doing
> further testing. It could leave old status messages at the end of the
> line while printing status messages if initial status fit on one line
> and new status text required new line.
Patches applied
Cristian Rodríguez wrote:
> ---
> src/libFLAC++/Makefile.am | 2 +-
> src/libFLAC/Makefile.am | 2 +-
> src/metaflac/Makefile.am | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
Applied. Thanks.
Erik
--
--
Erik de
Janne Hyvärinen wrote:
> Small change to metaflac hexdump function. Changed so utf-8 decoding is
> only used for filename printing and changed hex output printing to not
> rely only on isprint. That function seems to return true for tabulator
> control character under Windows when application i
Martijn van Beurden wrote:
> I just saw I forgot to fix the feed on the news page. Here's a patch for
> that one as well.
All four patches applied and pushed. Thanks.
Erik
--
--
Erik de Castro Lopo
http://www.mega-nerd.com/
__
Martijn van Beurden wrote:
> Hi,
>
> I was wondering how much worse FLAC performance would be if it was
> compiled integer-only, but while trying to do so (by adding #define
> FLAC__INTEGER_ONLY_LIBRARY 1 to config.h, just on x86_64-linux) I got
> this error
>
> > ./include/private/bitmath.h:
On 21.4.2013 10:25, Erik de Castro Lopo wrote:
Janne Hyvärinen wrote:
Sorry for spamming but I noticed one more display glitch while doing
further testing. It could leave old status messages at the end of the
line while printing status messages if initial status fit on one line
and new status t
Janne Hyvärinen wrote:
> Either I sent a wrong patch or the last fix didn't make it in. Here's a
> patch to git version to fix old status print staying on the wrong line
> with certain filename length.
Applied, thanks.
Erik
--
--
This patch fixes the issue mentioned below.
On 09-04-13 21:18, Martijn van Beurden wrote:
Hi all,
For testing a few mingw-builds I tried to use ./configure
--disable-thorough-testing (because testing in a virtual machine
through mingw isn't really fast) but it turned out this setting
doesn't
Hi all,
After fixing --enable-valgrind-testing with the previous patch, I
installed valgrind to give it a try. It turns out the switches used by
the test scripts are not accepted. I assume it was valid in a previous
version of valgrind, but mine says 50 is maximum. Patch attached.
>From a3b054
