On Tue, Jul 06, 2004 at 10:58:11PM -0700, Jason Weber wrote:
> On Tue, Jul 06, 2004 at 11:32:49AM +0200, Dominik Vogt wrote:
> > On Mon, Jul 05, 2004 at 11:43:25AM -0700, Jason Weber wrote:
> > > Maybe I need an example. Do you mean to deactivate it or change
> > > the command string dynamically?
On Sat, Jul 10, 2004 at 12:42:52AM +, Mikhael Goikhman wrote:
> At least one change (order of arguments in CONFIGURE_WINDOW) is bad.
> The flags are of the variable size and thus should be last.
I can change that. But why are the flags "variable size"?
> If you ever change any event argument
On Sat, Jul 10, 2004 at 06:42:24PM +1000, Scott Smedley wrote:
> > > * Please put single statements in loops or if clauses in curly
> > >braces, i.e.
> > >
> > > if (1)
> > > {
> > >foo;
> > > }
> > >
> > >not
> > >
> > > if (1)
> > >foo;
> >
> > Wha
http://www.readme.co.il/pikanti/index.html
--
Visit the official FVWM web page at http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PRO
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: domivogt04/07/10 15:03:21
Modified files:
. : ChangeLog
fvwm : module_interface.c
libs : vpacket.h
Log message:
* Reordered ConfigWinPacket members.
--
Visit th
Mikhael Goikhman <[EMAIL PROTECTED]> wrote:
>Like other posters, I don't quite like that names are sudently work
>using logical OR while all other options in conditional commands work
>using logical AND. And the nagations of names work using AND again.
>
>Here is the proposal that should solve all
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: scott 04/07/10 12:35:44
Modified files:
modules: ChangeLog
modules/FvwmButtons: FvwmButtons.1 FvwmButtons.c FvwmButtons.h
button.c draw.c icons.c parse.c
Log message:
More
Scott Smedley <[EMAIL PROTECTED]> writes:
> > > * Please put single statements in loops or if clauses in curly
> > >braces, i.e.
> > >
> > > if (1)
> > > {
> > >foo;
> > > }
> > >
> > >not
> > >
> > > if (1)
> > >foo;
> >
> > What's the rationale beh
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: scott 04/07/10 04:13:25
Modified files:
. : ChangeLog NEWS
modules: ChangeLog
modules/FvwmButtons: FvwmButtons.1 FvwmButtons.c FvwmButtons.h
button.c d
> > * Please put single statements in loops or if clauses in curly
> >braces, i.e.
> >
> > if (1)
> > {
> >foo;
> > }
> >
> >not
> >
> > if (1)
> >foo;
>
> What's the rationale behind this? I must confess I'm not particularly fond
> of this restricti
Hi Dominik, :)
> To avoid problems with comiling / reading the fvwm sources, please
>
> * adhere to the ANSI-C 88 standard, not the new one.
>Specifically,
>
> - Don't use C++-like comments with //
> - Declare variables only at the beginning of a block.
>
> * limit your lines to 7
11 matches
Mail list logo
