On 28 Jul 01 at 18:15, [EMAIL PROTECTED] wrote:
[SNIP]
The point is not cleaning the code, but a correct operation of modules
--
do you need a pager on non-primary screen?
I don't quit understand the question. Of course I'd usually
prefer the pager on the primary screen, but
On Fri, Jul 27, 2001 at 09:35:49PM +0700, Dmitry Yu. Bolkhovityanov wrote:
On 27 Jul 01 at 11:56, fvwm-workers@fvwm.org wrote:
- Code is written with 80 characters per line, a basic
indentation width of 2.
- Always compile the code with and without your ifdefs. Remove
all
On Sat, Jul 28, 2001 at 09:42:42PM +0700, Dmitry Yu. Bolkhovityanov wrote:
Content-Description: Mail message body
On 28 Jul 01 at 13:07, [EMAIL PROTECTED] wrote:
- Please keep in mind that that fvwm is controlled and configured
by configuration commands, not by environment
On 28 Jul 01 at 13:07, [EMAIL PROTECTED] wrote:
- Please keep in mind that that fvwm is controlled and configured
by configuration commands, not by environment variables. It's
not necessary to make features configurable via the
environment. (I'll remove the corresponding
On Thu, Jul 26, 2001 at 05:43:39PM +0700, Dmitry Yu. Bolkhovityanov wrote:
Content-Description: Mail message body
Hi!
That's part 1 of XineramaSupport v2 merger. It contains
libs/XineramaSupport.[ch] as drop-in replacements. Next part will be
configure script, followed by modules.
On 27 Jul 01 at 11:56, fvwm-workers@fvwm.org wrote:
- Code is written with 80 characters per line, a basic
indentation width of 2.
- Always compile the code with and without your ifdefs. Remove
all warnings (compile with 'make CFLAGS=-Wall -Werror -g).
Okay. I usually set
Hi!
That's part 1 of XineramaSupport v2 merger. It contains
libs/XineramaSupport.[ch] as drop-in replacements. Next part will be
configure script, followed by modules.
The only change required is to fvwm/menus.c -- to use
XiSuppClipToScreenAt() instead of XiSuppClipToScreen() (the
