Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 94976 - aterm does not support --scrollColor and --troughColor features
Summary: aterm does not support --scrollColor and --troughColor features
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo Afterstep Maintainers (OBSOLETE)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-03 21:36 UTC by Matthew Stewart
Modified: 2012-01-29 02:19 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matthew Stewart 2005-06-03 21:36:53 UTC
The --scrollColor and --troughColor options of aterm are documented in the man
file that comes with this version (0.4.2-r11), and aterm does not complain that
they are illegal options, however they do nothing: the scrollbar and trough
remain the default color (grey).

Reproducible: Always
Steps to Reproduce:
1.aterm --scrollColor red --troughColor blue

Actual Results:  
The scrollbar and trough are both grey.

Expected Results:  
The scrollbar should be red, and the trough should be blue.

I am using the Fluxbox window manager.
Comment 1 Aaron Walker (RETIRED) gentoo-dev 2005-10-27 15:07:17 UTC
Does aterm-1.0.0 solve this issue?
Comment 2 Nathan Mahon 2005-10-30 15:01:14 UTC
two comments:
1.) those things are not commandline flags, but resources. so you'd not be able
to specify them like that, but rather into an ~/.Xdefaults file.
2.) unless i'm mistaken, they're part of the removed xterm scrollbar support,
and are not functional in either 0.4.2 nor in 1.0.0.  However, a similar result
shouldn't be too difficult if you use 1.0.0 with the libAfterImage dependency. 
I'll check.  I'm not sure if the manpage is erroneous in 1.0.0 as well.
Comment 3 Michael Orlitzky gentoo-dev 2011-05-12 00:13:35 UTC
True, these shouldn't work as command-line parameters anyway (and aren't documented as such). However, aterm doesn't complain that they're invalid options. That appears to be an upstream bug.