Bug#580827: aumix: -C option docs and opening uninit

2010-05-17 Thread Kevin Ryde
Stefan Ott ste...@ott.net writes:

 Thanks for reporting this. Version 2.9.1 (currently in unstable)
 should fix that - could you give it a try?

Yes, it takes a filename ok.

I think though that having aumix -C vt100 look first for a vt100 file
in the current directory is not a great idea.  If you want to sure of
getting the supplied /usr/share/aumix colour schemes you'd have to write
a full path.

Unless it's just a matter of how the man page describes the way the
option works.  I see it's unchanged, I still think it's unclear :-).



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#580827: aumix: -C option docs and opening uninit

2010-05-11 Thread Stefan Ott
Hi

Thanks for reporting this. Version 2.9.1 (currently in unstable)
should fix that - could you give it a try?

cheers
Stefan



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#580827: aumix: -C option docs and opening uninit

2010-05-08 Thread Kevin Ryde
Package: aumix
Version: 2.9-1
Severity: normal

I found the aumix man page on the -C option a bit unclear.  I read it as
something like

aumix -C /tmp/myfile

with something or other in that file, but doing so gets

aumix:  unable to open settings file


Nosing around InitColors() it looks like the first fopen() is on the
filename[] variable and that variable has not been initialized at that
point.  I wonder if it's meant to be the `scheme' parameter instead, to
allow a filename for that -C.

I see otherwise files under /usr/share/aumix are opened.  That could be
described in the aumix man page, so you know there's some supplied
colours, and can look there for something to copy to some preferred
colour scheme.

Mind you, if that first fopen() did what it looks like it was meant to,
then -C ansi would look first for a file called ansi in the current
directory, and then in /usr/share/aumix.  It could be very bad if there
was a random file called ansi in the current directory.  It could be
much better to have a separate option for a user filename versus a
supplied ansi etc scheme.  If -C never worked for user filenames then
there'd be no incompatibility.



-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-1-486
Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages aumix depends on:
ii  aumix-common  2.9-1  Simple text-based mixer control pr
ii  libc6 2.10.1-3   GNU C Library: Shared libraries
ii  libgpm2   1.20.4-3.3 General Purpose Mouse - shared lib
ii  libncurses5   5.7+20100313-1 shared libraries for terminal hand

aumix recommends no packages.

aumix suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org