On 12/28/06, Dominik Vogt [EMAIL PROTECTED] wrote:
On Thu, Dec 28, 2006 at 11:25:01PM +, seventh guardian wrote:
Hi
I'm puzzled by this piece of code:
FD_SET(i, init_fdset);
where i is the integer representing the module index (used for
accessing elements of readPipes, writePipes
Hello
Following Dan Espen's comment on module_interface.h:
* There really should be a module structure. Ie. the readPipes,
* writePipes, pipeName, arrays should be members of a structure.
* Probably a linklist of structures. Note that if the OS number of file
* descriptors gets
On 12/30/06, seventh guardian [EMAIL PROTECTED] wrote:
On 12/29/06, seventh guardian [EMAIL PROTECTED] wrote:
On 12/29/06, seventh guardian [EMAIL PROTECTED] wrote:
On 12/29/06, seventh guardian [EMAIL PROTECTED] wrote:
On 12/29/06, Dominik Vogt [EMAIL PROTECTED] wrote:
On Fri, Dec 29
On 12/30/06, Dominik Vogt [EMAIL PROTECTED] wrote:
On Sat, Dec 30, 2006 at 03:01:22PM +0100, Dominik Vogt wrote:
On Sat, Dec 30, 2006 at 12:57:20PM +0100, Dominik Vogt wrote:
On Sat, Dec 30, 2006 at 02:13:29AM +, seventh guardian wrote:
[snip]
Ok, here goes the patch
On 12/30/06, Dominik Vogt [EMAIL PROTECTED] wrote:
On Sat, Dec 30, 2006 at 03:11:27PM +, seventh guardian wrote:
On 12/30/06, FVWM CVS fvwm-workers@fvwm.org wrote:
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: domivogt06/12/30 09:08:21
Modified files
Hello.
Inside module_interface there are lots of duplicated functions, some
old and some new. It would be expected that the new functions were
used instead of the old ones, but strangely they are both used in
different places. It seems that the migration never finished..
So are the new
On 9/1/06, Viktor Griph [EMAIL PROTECTED] wrote:
I've been doing some tests, and the problem is partly fixed in the current
version. Keybindings no longer stop working as in the bug description, but
the focused window decorations are still incorrect in the same way as
reported.
sliderall is an
On 12/31/06, Dominik Vogt [EMAIL PROTECTED] wrote:
On Sat, Dec 30, 2006 at 11:35:21PM +, seventh guardian wrote:
The DeadPipe signal handling is actually done by an empty function. Is
there any future use for it? Or is it just a relic and may be removed
from the code?
It may or may
On 12/31/06, Dominik Vogt [EMAIL PROTECTED] wrote:
On Sun, Dec 31, 2006 at 12:48:08AM +, seventh guardian wrote:
On 12/31/06, Dominik Vogt [EMAIL PROTECTED] wrote:
On Sat, Dec 30, 2006 at 11:35:21PM +, seventh guardian wrote:
The DeadPipe signal handling is actually done by an empty
Hello
If I understand correctly, inline functions weren't allowed some
time ago, right? I say this because macros were used instead of small
(not inlined) functions.
I've searched for the story of IS_MESSAGE_SELECTED macro and the
defunct is_message_selected() function, and found that at some
On 12/31/06, seventh guardian [EMAIL PROTECTED] wrote:
Hello
If I understand correctly, inline functions weren't allowed some
time ago, right? I say this because macros were used instead of small
(not inlined) functions.
I've searched for the story of IS_MESSAGE_SELECTED macro and the
defunct
On 12/31/06, Dan Espen [EMAIL PROTECTED] wrote:
seventh guardian [EMAIL PROTECTED] writes:
Hello
If I understand correctly, inline functions weren't allowed some
time ago, right? I say this because macros were used instead of small
(not inlined) functions.
...
Now that the use of inline
On 1/1/07, Dominik Vogt [EMAIL PROTECTED] wrote:
On Sat, Dec 30, 2006 at 02:47:37PM +, seventh guardian wrote:
On 12/30/06, Dominik Vogt [EMAIL PROTECTED] wrote:
On Sat, Dec 30, 2006 at 03:01:22PM +0100, Dominik Vogt wrote:
On Sat, Dec 30, 2006 at 12:57:20PM +0100, Dominik Vogt wrote
On 1/1/07, Dominik Vogt [EMAIL PROTECTED] wrote:
On Mon, Jan 01, 2007 at 02:41:24PM -0600, fvwm-workers wrote:
CVSROOT: /home/cvs/fvwm
Module name: fvwm
Changes by: renato 07/01/01 14:41:24
Modified files:
. : ChangeLog
fvwm : module_interface.c
On 1/2/07, seventh guardian [EMAIL PROTECTED] wrote:
On 1/1/07, Dominik Vogt [EMAIL PROTECTED] wrote:
On Mon, Jan 01, 2007 at 02:41:24PM -0600, fvwm-workers wrote:
CVSROOT: /home/cvs/fvwm
Module name: fvwm
Changes by: renato 07/01/01 14:41:24
Modified files
On 1/2/07, FVWM CVS fvwm-workers@fvwm.org wrote:
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: renato 07/01/01 19:45:51
Modified files:
. : ChangeLog
fvwm : events.c module_interface.c module_interface.h
Log message:
* Created
On 1/1/07, Jacob Bachmeyer [EMAIL PROTECTED] wrote:
seventh guardian wrote:
On 12/31/06, seventh guardian [EMAIL PROTECTED] wrote:
Hello
[snip]
Please note that just making them inline doesn't allow us to hide
msg_masks_t right away. But it would if we hide the module struct
On 1/3/07, Dominik Vogt [EMAIL PROTECTED] wrote:
On Wed, Jan 03, 2007 at 12:02:34PM +0100, Dominik Vogt wrote:
With the introduction of the of the module_add_to_fdsets()
function the code is now moving into a very unfortunate direction.
When fvwm is busy, that function might be called
On 1/3/07, Dominik Vogt [EMAIL PROTECTED] wrote:
On Wed, Jan 03, 2007 at 12:03:18AM +, seventh guardian wrote:
On 1/2/07, Dominik Vogt [EMAIL PROTECTED] wrote:
In the tests I'm calling the function GetFdWidth() twice for every
module, which may incur in a bit overhead..
There's
On 1/3/07, Jesús Guerrero [EMAIL PROTECTED] wrote:
Hello, I am new to the list and my first question is this.
I am not new to C but I am new to the fvwm sources, so I am
a bit loss. In the rounded corners patch someone used
fw-frame_g.width and fw-frame_g.height to access
I-dont-know-what-info.
On 1/3/07, seventh guardian [EMAIL PROTECTED] wrote:
On 1/3/07, Jesús Guerrero [EMAIL PROTECTED] wrote:
Hello, I am new to the list and my first question is this.
I am not new to C but I am new to the fvwm sources, so I am
a bit loss. In the rounded corners patch someone used
fw
On 1/6/07, Serge (gentoosiast) Koksharov [EMAIL PROTECTED] wrote:
On Sat, Jan 06, 2007 at 12:55:07PM +0100, Dominik Vogt wrote:
On Fri, Jan 05, 2007 at 11:15:35PM +0300, Serge (gentoosiast) Koksharov wrote:
Please see attached patch's ChangeLog.
Very good patches. I'll apply them.
Thanks.
On 1/7/07, FVWM CVS fvwm-workers@fvwm.org wrote:
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: domivogt07/01/07 07:34:05
Modified files:
. : ChangeLog
libs : Makefile.am
modules: ChangeLog
Hello
I've started doing a separation between module handling stuff and
packet sending stuff. The logic of this separation is simple:
* The module exec/kill code and record keeping doesn't need to know
the actual protocol. It just stores a bunch of data and does the
procedures for setting up
Hello
I've came across two very similar functions in module_interface.c, one
of which was introduced recently during the module struct change. They
are:
static void set_message_mask(msg_masks_t *mask, unsigned long msg)
{
if (msg M_EXTENDED_MSG)
{
mask-m2 = (msg
On 1/10/07, FVWM CVS fvwm-workers@fvwm.org wrote:
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: griph 07/01/09 18:34:27
Modified files:
. : ChangeLog NEWS
fvwm : fvwm.1.in menuitem.c
libs : Colorset.c Colorset.h
On 1/10/07, seventh guardian [EMAIL PROTECTED] wrote:
On 1/10/07, FVWM CVS fvwm-workers@fvwm.org wrote:
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: griph 07/01/09 18:34:27
Modified files:
. : ChangeLog NEWS
fvwm : fvwm.1
Hello.
The NEWS entry is getting large, so I wonder if we should make a new
release. Are the recent changes stable enough?
This is a concern to me, as the work I'm doing splitting the
module_interface.ch files is going to make the code a bit messy at
first. I'm holding back committing because I
On 1/10/07, Viktor Griph [EMAIL PROTECTED] wrote:
On Wed, 10 Jan 2007, seventh guardian wrote:
Hello.
The NEWS entry is getting large, so I wonder if we should make a new
release. Are the recent changes stable enough?
I'd like to wait until the weekend at least. I'd like to do
Hello.
In the process of adding the module_list.c file to Makefile.am I've
reorganized the c files by size (things change..). I've noticed that
the headers are put in fvwm_SOURCES, while now they should go on
fvwm_INCLUDES.
Is there any issue with older supported versions of automake preventing
On 1/13/07, FVWM CVS fvwm-workers@fvwm.org wrote:
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: renato 07/01/13 17:05:01
Modified files:
. : ChangeLog
fvwm : module_interface.c module_list.h
Log message:
* reused the
On 1/14/07, Dominik Vogt [EMAIL PROTECTED] wrote:
I don't understand what your problem is. When I start xterm like
this:
$ xterm -g 80x24+0+0
I get an 80x24 xterm at +0+0. FvwmIdent says:
X: 0 (frame x position)
Y: 0 (frame y position)
Width: 587 (frame width)
Height: 342 (frame
Hello.
Here's the dubious part of the man page entry:
This command is intended for use with the (currently hypothetical)
module that should be in place before other modules are started.
What is this hypothetical module?
Cheers
Renato
On 1/14/07, Dominik Vogt [EMAIL PROTECTED] wrote:
On Sun, Jan 14, 2007 at 08:36:31PM +, seventh guardian wrote:
Hello
I have a question regarding one aspect of the coding: is it better to
use big do-everything functions or do-one-thing ones?
It's better to use do-one-well-defined-thing
On 1/16/07, FVWM CVS fvwm-workers@fvwm.org wrote:
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: renato 07/01/15 18:21:52
Modified files:
. : ChangeLog
fvwm : events.c module_list.c module_list.h
Log message:
Replaced the big
On 1/16/07, Dominik Vogt [EMAIL PROTECTED] wrote:
On Tue, Jan 16, 2007 at 12:10:59AM +, seventh guardian wrote:
* remove NEWS about fixing pan frames. I did move the tag on stack.c and
ChangeLog and uploaded new tar-balls. The bug was simply too annoying.
I was hoping someone would say
Hello
Considering the future, I think there would be an advantage on using
an existing image library:
First of all, it's usually mature code, and it usually has a larger
testing user-base. We get a full-featured library with little
debugging effort.
Second, an external library usually has lots
On 1/23/07, Simon Griph [EMAIL PROTECTED] wrote:
On 1/23/07, Viktor Griph [EMAIL PROTECTED] wrote:
On Mon, 22 Jan 2007, seventh guardian wrote:
Hello
Considering the future, I think there would be an advantage on using
an existing image library:
I think that the fvwmlib picture code
On 4/14/07, Jesús Guerrero [EMAIL PROTECTED] wrote:
Localization for the More... string in the menus.
http://jesgue.homelinux.org/fvwm-files/gtMore.patch
Seems ok, can you provide a ChangeLog entry?
Cheers,
Renato
On 4/17/07, Jesús Guerrero [EMAIL PROTECTED] wrote:
El Tue, 17 Apr 2007 09:30:57 +0100
seventh guardian [EMAIL PROTECTED] escribió:
On 4/17/07, seventh guardian [EMAIL PROTECTED] wrote:
On 4/14/07, Jesús Guerrero [EMAIL PROTECTED] wrote:
Localization for the More... string in the menus
On 4/17/07, Jesús Guerrero [EMAIL PROTECTED] wrote:
El Tue, 17 Apr 2007 14:22:27 +0200
Jesús Guerrero [EMAIL PROTECTED] escribió:
The patch has been attached to this mail.
We were on the Workers-list, not on the General-list. Please pay
attention to that to avoid cross messages.. They get
On 4/17/07, seventh guardian [EMAIL PROTECTED] wrote:
On 4/17/07, Jesús Guerrero [EMAIL PROTECTED] wrote:
El Tue, 17 Apr 2007 14:22:27 +0200
Jesús Guerrero [EMAIL PROTECTED] escribió:
The patch has been attached to this mail.
We were on the Workers-list, not on the General-list. Please pay
On 4/19/07, Scott Smedley [EMAIL PROTECTED] wrote:
Please update the XML documentation. See doc/README file for more info.
In this instance, you will need to edit: doc/fvwm/menus.xml
Oh sorry, I forgot that.. Corrected now.
I have one question though: is the fvwm.1.in still needed? I
On 4/19/07, Jesús Guerrero [EMAIL PROTECTED] wrote:
Hello,
El Thu, 19 Apr 2007 03:01:46 -0500
Jason L Tibbitts III [EMAIL PROTECTED] escribió:
rm -f fvwm.ar.gmo /usr/bin/msgfmt -c --statistics -o fvwm.ar.gmo
fvwm.ar.po fvwm.ar.po:57:10: invalid multibyte sequence
fvwm.ar.po:57:12: invalid
On 4/19/07, FVWM CVS fvwm-workers@fvwm.org wrote:
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: renato 07/04/19 13:15:47
Modified files:
po : ChangeLog fvwm.ar.po
Log message:
Removed the arabic translation for More... due to encoding errors
rm -f fvwm.sv_SE.gmo /usr/bin/msgfmt -c --statistics -o fvwm.sv_SE.gmo
fvwm.sv_SE.po
fvwm.sv_SE.po:56:2: parse error
fvwm.sv_SE.po:56: keyword fvwm unknown
fvwm.sv_SE.po:61:2: parse error
fvwm.sv_SE.po:63: duplicate message definition
fvwm.sv_SE.po:59: ...this is the location of the first
On 6/4/07, Viktor Griph [EMAIL PROTECTED] wrote:
I've been thinking some of this docbook documentation, and I think that it
would be better to generate the man-page during make dist, or when asked
for.
The generation process takes quite some time, and requires extra tools. It
will however still
On 7/6/07, Scott Smedley [EMAIL PROTECTED] wrote:
Hi Dominik,
Should we upgrade to the GPLv3?
I'm happy for any of my contributions to be licensed using GPLv3.
(not that permission is required with the v2 or any later version
clause in the existing GPLv2 licence.)
Me too.
I'd like to see
Hello Dominik,
On 7/12/07, Dominik Vogt [EMAIL PROTECTED] wrote:
I've just committed the new command EchoFuncDefinition which
prints a function definition to the console (useful for debugging
functions).
Nice addition, it should be useful.
But I've no idea what I have to do to write the
On 7/12/07, Viktor Griph [EMAIL PROTECTED] wrote:
On Thu, 12 Jul 2007, seventh guardian wrote:
About the doc page creation, it seemed simple at first, but I had to
search hard for the relevant info. Maybe a clearer how-to should be
created? This is the first time I'm creating a manual entry
On 7/16/07, seventh guardian [EMAIL PROTECTED] wrote:
On 7/16/07, Scott Smedley [EMAIL PROTECTED] wrote:
But I'm still getting lots of errors in libs/FRender.c.
The fix requires that I link with -lXrender.
Yeah.. It seems that Viktor already fixed the compilation error, so
the patches
On 7/16/07, Dominik Vogt [EMAIL PROTECTED] wrote:
On Mon, Jul 16, 2007 at 05:03:59PM +0100, seventh guardian wrote:
Oh my... this is bad..
In current cvs, this causes a segmentation fault:
Open FvwmConsole
Type cursorstyle ROOT 10
(repeat the style if necessary)
Close the FvwmConsole
On 7/22/07, Viktor Griph [EMAIL PROTECTED] wrote:
On Tue, 17 Jul 2007, seventh guardian wrote:
On 7/16/07, Dominik Vogt [EMAIL PROTECTED] wrote:
On Mon, Jul 16, 2007 at 05:03:59PM +0100, seventh guardian wrote:
Oh my... this is bad..
In current cvs, this causes a segmentation fault
Following Viktor Griph's bug-solving changes to the module list
mechanism, I'm unifying the module list handling.
Things are currently like this:
* there is a main list embedded in the module struct. These modules
are always read from, and commands are only sent if they aren't dead.
* there is
On 8/5/07, Viktor Griph [EMAIL PROTECTED] wrote:
On Sun, 5 Aug 2007, FVWM CVS wrote:
CVSROOT: /home/cvs/fvwm
Module name: fvwm
Changes by: renato 07/08/05 15:49:11
Modified files:
. : ChangeLog
fvwm : events.c modconf.c module_interface.c
On 8/5/07, FVWM CVS fvwm-workers@fvwm.org wrote:
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: renato 07/08/05 17:19:21
Modified files:
. : ChangeLog
fvwm : events.c
Log message:
moved module_cleanup to after
On 8/5/07, Viktor Griph [EMAIL PROTECTED] wrote:
On Sun, 5 Aug 2007, seventh guardian wrote:
(...)
I've checked, it only frees the main list fmodule_store container, not
the fmodule itself. The fmodule struct is still kept on the death-row,
just like it did before..Am I missing something
On 8/5/07, seventh guardian [EMAIL PROTECTED] wrote:
On 8/5/07, Viktor Griph [EMAIL PROTECTED] wrote:
On Sun, 5 Aug 2007, seventh guardian wrote:
(...)
I've checked, it only frees the main list fmodule_store container, not
the fmodule itself. The fmodule struct is still kept
Hello,
The NEWS file is getting long, so I believe a new release would be
good. Should we wait a couple of days for testing the recent changes
to the module code? Is there any other issue that may prevent the
release?
Cheers,
Renato
On 8/7/07, Scott Smedley [EMAIL PROTECTED] wrote:
It is run manually (usually be me) anytime a new command is documented.
So, no need to worry about Perl dependencies.
1) I think this is not acceptable. It's too difficult to add new
commands right now.
Difficult to document new
On 8/8/07, Jesús Guerrero [EMAIL PROTECTED] wrote:
Hello,
Something strange is happening since a few days.
There has been some movement in the CVS lately so I did not want to
report this too soon in case it was something that was momentarily
broken or something like that.
I have one
On 8/8/07, Jesús Guerrero [EMAIL PROTECTED] wrote:
Begin forwarded message:
Date: Wed, 8 Aug 2007 04:03:43 +0200
From: Jesús Guerrero [EMAIL PROTECTED]
To: seventh guardian [EMAIL PROTECTED]
Subject: Re: 1-2 minutes to load FvwmButtons on latest CVS
On Wed, 8 Aug 2007 02:40:21 +0100
On 8/8/07, seventh guardian [EMAIL PROTECTED] wrote:
On 8/8/07, Jesús Guerrero [EMAIL PROTECTED] wrote:
On Wed, 8 Aug 2007 03:15:31 +0100
seventh guardian [EMAIL PROTECTED] wrote:
(snip)
Can you please check if this solves your problem?
(snip)
I just recompiled
On 8/11/07, FVWM CVS fvwm-workers@fvwm.org wrote:
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: renato 07/08/11 15:07:03
Modified files:
fvwm : events.c
Log message:
Startup modules fix (partial)
Now startup modules won't make fvwm hang, but
On 8/11/07, seventh guardian [EMAIL PROTECTED] wrote:
On 8/8/07, Jesús Guerrero [EMAIL PROTECTED] wrote:
On Wed, 8 Aug 2007 08:51:32 +0100
seventh guardian [EMAIL PROTECTED] wrote:
On 8/8/07, Jesús Guerrero [EMAIL PROTECTED] wrote:
On Wed, 8 Aug 2007 03:15:31 +0100
seventh
On 8/10/07, Serge (gentoosiast) Koksharov [EMAIL PROTECTED] wrote:
Hello,
This minor patch fixes issue with not working window proxy groups when
FvwmProxy module compiled with PROXY_GROUP_DEBUG directive set to False.
Nice patch! Applied.
Thanks,
Renato
On 8/13/07, seventh guardian [EMAIL PROTECTED] wrote:
On 8/6/07, Dominik Vogt [EMAIL PROTECTED] wrote:
On Mon, Aug 06, 2007 at 02:02:35PM +0100, seventh guardian wrote:
The NEWS file is getting long, so I believe a new release would be
good.
Yes.
Ok, so where do we stand now
I'm localy starting to change the tree to gpl v3. As I said, maybe a
branch would be helpful in allowing everyone to participate without
messing with the main tree.
On the other hand, fvwm is still copyrighted by Rob Nation, even
though he's not really involved right now. It should be wise to add
On 8/13/07, Viktor Griph [EMAIL PROTECTED] wrote:
On Mon, 13 Aug 2007, seventh guardian wrote:
On 8/6/07, Dominik Vogt [EMAIL PROTECTED] wrote:
On Mon, Aug 06, 2007 at 02:02:35PM +0100, seventh guardian wrote:
The NEWS file is getting long, so I believe a new release would be
good
Hello,
I must confess I'm not very fond of listen only modules. I believe it
is more of a hack than a long term solution to the shell script
module problem. And I would really like it removed, and for that the
sooner the better.
So I was messing around to see if it was really needed, and it's
On 8/14/07, seventh guardian [EMAIL PROTECTED] wrote:
On 8/14/07, Dominik Vogt [EMAIL PROTECTED] wrote:
On Tue, Aug 14, 2007 at 09:15:21AM -0400, Dan Espen wrote:
seventh guardian [EMAIL PROTECTED] writes:
I must confess I'm not very fond of listen only modules. I believe it
is more
On 8/13/07, Viktor Griph [EMAIL PROTECTED] wrote:
On Mon, 13 Aug 2007, Dominik Vogt wrote:
On Mon, Aug 13, 2007 at 11:08:57AM +0100, seventh guardian wrote:
On 8/6/07, Dominik Vogt [EMAIL PROTECTED] wrote:
On Mon, Aug 06, 2007 at 02:02:35PM +0100, seventh guardian wrote:
The NEWS file
On 8/15/07, seventh guardian [EMAIL PROTECTED] wrote:
On 8/15/07, Cameron Simpson [EMAIL PROTECTED] wrote:
On 14Aug2007 19:11, seventh guardian [EMAIL PROTECTED] wrote:
|Running FvwmCommandS is a security exposure.
|Some users might be reluctant to use it.
|
| I don't use
On 8/16/07, Dominik Vogt [EMAIL PROTECTED] wrote:
On Thu, Aug 16, 2007 at 07:06:13PM +0100, seventh guardian wrote:
On 8/16/07, Dominik Vogt [EMAIL PROTECTED] wrote:
On Thu, Aug 16, 2007 at 11:14:58AM +0200, Dominik Vogt wrote:
By the way, I really don't understand why anybody considers
On 8/18/07, Dominik Vogt [EMAIL PROTECTED] wrote:
On Fri, Aug 17, 2007 at 09:22:44PM +0100, seventh guardian wrote:
I don't like ListenOnly modules because it's dependent on how modules
talk with fvwm at present. I'd really prefer a mechanism that can't
cripple us in the future. And IMHO
On 8/18/07, Dominik Vogt [EMAIL PROTECTED] wrote:
On Fri, Aug 17, 2007 at 09:22:44PM +0100, seventh guardian wrote:
I don't like ListenOnly modules because it's dependent on how modules
talk with fvwm at present. I'd really prefer a mechanism that can't
cripple us in the future. And IMHO
On 8/28/07, Dominik Vogt [EMAIL PROTECTED] wrote:
On Tue, Aug 21, 2007 at 11:34:55AM +0200, Dominik Vogt wrote:
By the way, there's another issue with the build process:
* The documentation has a build error when building on a multi
core machine with -j 2.
I think there are some
On 8/28/07, seventh guardian [EMAIL PROTECTED] wrote:
OOPS:
$ make CFLAGS=-g -O2 -Wall -Wpointer-arith -fno-strict-aliasing -Werror
make all-recursive
make[1]: Entering directory `/home/renato/apps/cvs/fvwm'
Making all in libs
make[2]: Entering directory `/home/renato/apps/cvs/fvwm/libs
OOPS:
$ make CFLAGS=-g -O2 -Wall -Wpointer-arith -fno-strict-aliasing -Werror
make all-recursive
make[1]: Entering directory `/home/renato/apps/cvs/fvwm'
Making all in libs
make[2]: Entering directory `/home/renato/apps/cvs/fvwm/libs'
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I/usr/include
On 8/28/07, Viktor Griph [EMAIL PROTECTED] wrote:
On Tue, 28 Aug 2007, seventh guardian wrote:
On 8/28/07, Dominik Vogt [EMAIL PROTECTED] wrote:
On Tue, Aug 28, 2007 at 02:13:20PM +0100, seventh guardian wrote:
On 8/28/07, seventh guardian [EMAIL PROTECTED] wrote:
OOPS:
$ make CFLAGS
On 8/28/07, seventh guardian [EMAIL PROTECTED] wrote:
On 8/28/07, seventh guardian [EMAIL PROTECTED] wrote:
On 8/28/07, Dominik Vogt [EMAIL PROTECTED] wrote:
On Tue, Aug 28, 2007 at 02:13:20PM +0100, seventh guardian wrote:
On 8/28/07, seventh guardian [EMAIL PROTECTED] wrote:
OOPS
On 8/28/07, Dominik Vogt [EMAIL PROTECTED] wrote:
On Tue, Aug 28, 2007 at 02:55:26PM +0100, seventh guardian wrote:
On 8/28/07, seventh guardian [EMAIL PROTECTED] wrote:
On 8/28/07, Dominik Vogt [EMAIL PROTECTED] wrote:
On Tue, Aug 28, 2007 at 02:13:20PM +0100, seventh guardian wrote
On 8/28/07, Viktor Griph [EMAIL PROTECTED] wrote:
On Tue, 28 Aug 2007, Dominik Vogt wrote:
On Tue, Aug 28, 2007 at 02:55:26PM +0100, seventh guardian wrote:
On 8/28/07, seventh guardian [EMAIL PROTECTED] wrote:
(...)
cc1: warnings being treated as errors
Flocale.c: In function
On 8/29/07, FVWM CVS fvwm-workers@fvwm.org wrote:
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: renato 07/08/29 06:39:20
Modified files:
modules: ChangeLog
modules/FvwmButtons: button.c
modules/FvwmTaskBar: Start.c
Log message:
fix
On 8/29/07, Viktor Griph [EMAIL PROTECTED] wrote:
On 8/29/07, seventh guardian [EMAIL PROTECTED] wrote:
Ok, everything is done except putting the tarballs in the ftp dir (I
seem to have forgotten my password.. already emailed Jason about
this).
there is no password for the incoming folder
On 8/30/07, Thomas Adam [EMAIL PROTECTED] wrote:
On Wed, Aug 29, 2007 at 06:24:52PM -0500, FVWM CVS wrote:
Log message:
updated for 2.6.22 release
Either we keep skipping a version, or you've mistyped again. ;)
Duhh! 2.6.22 is the kernel... I hope either fvwm or linux speeds up
and the
On 8/30/07, Thomas Adam [EMAIL PROTECTED] wrote:
On Thu, Aug 30, 2007 at 12:35:19AM +0100, seventh guardian wrote:
On 8/30/07, Thomas Adam [EMAIL PROTECTED] wrote:
On Wed, Aug 29, 2007 at 06:24:52PM -0500, FVWM CVS wrote:
Log message:
updated for 2.6.22 release
Either we keep
On 8/30/07, seventh guardian [EMAIL PROTECTED] wrote:
On 8/30/07, Viktor Griph [EMAIL PROTECTED] wrote:
On Thu, 30 Aug 2007, seventh guardian wrote:
On 8/30/07, seventh guardian [EMAIL PROTECTED] wrote:
On 8/29/07, seventh guardian [EMAIL PROTECTED] wrote:
On 8/29/07, Viktor Griph
On 9/1/07, Dominik Vogt [EMAIL PROTECTED] wrote:
On Sat, Sep 01, 2007 at 05:24:26AM -0500, fvwm-workers wrote:
CVSROOT: /home/cvs/fvwm
Module name: fvwm
Changes by: domivogt07/09/01 05:24:26
Modified files:
. : AUTHORS ChangeLog NEWS
On 9/1/07, Dominik Vogt [EMAIL PROTECTED] wrote:
This warning fix introduced a real bug to FvwmButtons:
-if(numold || old+32old)
+if(numold || old(old+=32))
^
Since this is part of 2.5.22 we've got to release 2.5.23
immediately. I'll take care of this.
On Feb 2, 2006 1:23 PM, Dominik Vogt [EMAIL PROTECTED] wrote:
On Thu, Feb 02, 2006 at 01:42:44PM +0100, Marc Lehmann wrote:
On Thu, Feb 02, 2006 at 09:11:40AM +0100, Dominik Vogt [EMAIL PROTECTED]
wrote:
http://data.plan9.de/fvwm-2.5-argb-visual.patch
Small to medium sized
Hello,
I've been diving in fvwm core code for the last days trying to get
argb visuals to work. One thing I've noticed is that while the menu
code is mostly separated from the rest of the code, some parts of it
are still everywhere.
IMHO it makes sense to have the menus separated, as they are
Hello,
This is about support for argb visuals in fvwm windows (decors, menus,
modules, etc).
Surprisingly (or not), one can already specify that (s)he wants an
ARGB visual for fvwm windows. First you have to run xdpyinfo to copy
the id of the appropriate visual (tipically the last one). Then
On Feb 9, 2008 11:39 PM, Dominik Vogt [EMAIL PROTECTED] wrote:
On Sat, Feb 09, 2008 at 11:01:15PM +, seventh guardian wrote:
This is about support for argb visuals in fvwm windows (decors, menus,
modules, etc).
To clarify myself, I mean selective transparency, each pixel having
its own
On Feb 10, 2008 12:20 AM, seventh guardian [EMAIL PROTECTED] wrote:
On Feb 9, 2008 11:39 PM, Dominik Vogt [EMAIL PROTECTED] wrote:
(...)
The first problem we have is that the user needs to manually specify
the visual id, which changes with the xorg setup. Most users would
expect some
On Wed, Mar 26, 2008 at 4:23 PM, julio teca [EMAIL PROTECTED] wrote:
Hello,
Yesterday, I installed the application cairo-clock that, as you know, is a
clock for the xorg-x11 based on SVG that uses the composite extension to
X11. The clock is working perfectly, but when I try to swallow it
On Thu, Mar 27, 2008 at 9:50 PM, julio teca [EMAIL PROTECTED] wrote:
Renato, thank you for your answer.
It's more or less what I supposed. Are all the modules affected, or is this
a particular
aspect of FvwmButtons?
All modules. It's pretty simple actually, all fvwm windows are not
On Fri, Apr 4, 2008 at 4:33 PM, julio teca [EMAIL PROTECTED] wrote:
Renato, thank you so much for your detailed answer. Now I understand
better the problem. I will take a look at the code as soon as I have
some free time. Would you tell me where could I find the patch you
mentioned?
It is
98 matches
Mail list logo
