On Thu, Apr 18, 2002 at 12:10:01PM -0400, Dan Espen wrote:
Where do I specify default options for colours, such as -bg gray? I tried
xterm*bg: grey
in .Xdefaults, but that has no effect.
XTerm*background: black
To apply changes in .Xdefaults to a running X-server you need to run
On Thu, Apr 18, 2002 at 01:46:21PM -0600, Gregg Dameron wrote:
Dan Espen wrote:
Oops, looks like someone top posted:
snip
I would vote in favor of an increase.
You might get your increase, but I don't really favor it.
It just uses up some memory for an extreme case that can
--- Victor Eijkhout [EMAIL PROTECTED] a écrit :
Not really an fvwm Q, but ...
In .Xdefaults I can specify
xterm*geometry: et cetera
Where do I specify default options for colours, such
as -bg gray? I tried
xterm*bg: grey
in .Xdefaults, but that has no effect.
should be
This is a fvwm2-Newbie query and the header says it all - assuming that
I have got at least the name right.
I am referring to the bottom right-hand part of the sticky window that
is displayed (in some configurations) when fvwm2 loads (the top part
notifies the arrival of mail and the time).
I
Hi Dominik, all,
A few weeks back you had the following advice for me and I finally got to
taking a look at some things around ReleiveRectangle.
I found that RelieveRectangle and RelieveRectangle2 both call
do_relieve_rectangle. In looking at do_relieve_rectangle I found that
XDrawSegments is
Hi Dominik, all,
A few weeks back you had the following advice for me and I finally got to
taking a look at some things around ReleiveRectangle.
I found that RelieveRectangle and RelieveRectangle2 both call
do_relieve_rectangle. In looking at do_relieve_rectangle I found that
XDrawSegments is
Configuration Information [Automatically generated, do not change]:
uname: SunOS silver 5.5.1 Generic_103640-39 sun4u sparc SUNW,Ultra-5_10
compiler flags: gcc -g -O2 -Wall -Wno-implicit-int
FVWM Version: 2.5.1
FVWM_MODULEDIR: /u/phippst/sunos/libexec/fvwm/2.5.1
FVWM_DATADIR:
On 18 Apr 2002 13:46:21 -0600, Gregg Dameron wrote:
My motivation is to minimize disk reads after the configuration is
loaded. True, reading and executing a short script from disk is a small
price to pay; on an idle system you'd never know the difference. But
the system here on which fvwm
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: migo02/04/19 06:41:00
Modified files:
. : ChangeLog configure.in
Log message:
* improved $PERL detection, the used value is printed now
--
Visit the official FVWM web page at URL:http://www.fvwm.org/.
[EMAIL PROTECTED] wrote:
On 18 Apr 2002 13:46:21 -0600, Gregg Dameron wrote:
Bottom line - PipeRead is brilliant, indispensable - I'd like to see itbe more
so.
My guess is that calling many shell utilities (read: many processes) is
sometimes more expensive than one perl script doing the
Configuration Information [Automatically generated, do not change]:
uname: SunOS silver 5.5.1 Generic_103640-39 sun4u sparc SUNW,Ultra-5_10
compiler flags: gcc -g -O2 -Wall -Wno-implicit-int
FVWM Version: 2.5.1
FVWM_MODULEDIR: /u/phippst/sunos/libexec/fvwm/2.5.1
FVWM_DATADIR:
[EMAIL PROTECTED] wrote:
I still don't use fvwm-themes but I can confirm core dumps at least a
few times. However only if the config file contains the gradients, if I
use FvwmConsole to dump in the colorsets I get same errors, and the
gradients are changed, but they are not really gradients,
On Fri, Apr 19, 2002 at 04:01:48PM +0100, tim phipps wrote:
Configuration Information [Automatically generated, do not change]:
uname: SunOS silver 5.5.1 Generic_103640-39 sun4u sparc SUNW,Ultra-5_10
compiler flags: gcc -g -O2 -Wall -Wno-implicit-int
FVWM Version: 2.5.1
FVWM_MODULEDIR:
Dominik Vogt fvwm-workers@fvwm.org writes:
On Fri, Apr 19, 2002 at 04:01:48PM +0100, tim phipps wrote:
Configuration Information [Automatically generated, do not change]:
uname: SunOS silver 5.5.1 Generic_103640-39 sun4u sparc SUNW,Ultra-5_10
compiler flags: gcc -g -O2 -Wall
On 19 Apr 2002 14:09:18 +0100, Tim Phipps wrote:
[EMAIL PROTECTED] wrote:
On 18 Apr 2002 13:46:21 -0600, Gregg Dameron wrote:
Bottom line - PipeRead is brilliant, indispensable - I'd like to see
itbe more so.
My guess is that calling many shell utilities (read: many processes)
Mikhael Goikhman [EMAIL PROTECTED] writes:
I learned it 7 years ago using man pages. You may start with perlsyn(1),
perlop(1), perldata(1) and then continue with perlfunc(1), perlvar(1),
perlmod(1) and other 150 supplied man pages. :)
I learned it the same way, although I did borrow
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: migo02/04/19 14:40:18
Modified files:
. : ChangeLog
fvwm : colorset.c
libs : Colorset.c
Log message:
* fixed running out of colors on 8bpp with ReadWriteColors, by
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: migo02/04/19 21:09:11
Modified files:
. : ChangeLog
modules: ChangeLog
modules/FvwmPerl: FvwmPerl.1 FvwmPerl.in
perllib: ChangeLog
perllib/FVWM :
18 matches
Mail list logo
