Re: Condition Visible does not seem to work when xcompmgr is running.
On 02Jul2007 22:32, Dominik Vogt [EMAIL PROTECTED] wrote: | The Visible condition works perfectly if xcompmgr is not running | though. I do not know if it is FVWM or xcompmgr that is at fault. | | I can only guess that xcompmgr suppresses VisibilityNotify events | for windows. I expect the behind windows are Visible because they are needed for transparency - alpha compositing will require the window to maintain its entire surface as though it were on top. -- Cameron Simpson [EMAIL PROTECTED] DoD#743 http://www.cskk.ezoshosting.com/cs/ Hello, my name is Yog-Sothoth, and I'll be your eldritch horror today. - Heather Keith [EMAIL PROTECTED]
Re: style matching in current CVS
On 06Apr2006 12:58, mikhael goikhman [EMAIL PROTECTED] wrote: | So, how about this: | | When two opposite style options are specified for the same window | (like Sticky and Slippery), then the last specified option wins. Please say opposing instead of opposite. Opposite suggests exact opposites (Thing vs NoThing). Opposing just implies conflict i.e. style options that have multiple effects, with overlapping effects in reverse sense (yes, this sentence itself reads badly). Clarification: suppose style option foo sets behaviours A and B, bah sets not-A and not-B, and baz sets A and not-B. foo and bah are opposite. foo and baz are opposing or conflicting. Cheers, -- Cameron Simpson [EMAIL PROTECTED] DoD#743 http://www.cskk.ezoshosting.com/cs/ Churchill's Commentary on Man: Man will occasionally stumble over the truth, but most of the time he will pick himself up and continue on.
Re: Quite old patch adding new Test condition
On 09Aug2005 11:16, Mikhael Goikhman [EMAIL PROTECTED] wrote: | On 09 Aug 2005 08:47:10 +0200, Rafal Bisingier wrote: | I personaly don't like perl's string operators (eq, ne, etc.) | | Is it because of perl or because of eq, ne names? These names are | also tcl's expr operators, and you may find them in the test(1) man page. Where they are conveniently swapped in application. The -lt etc are numeric operators in test(1), because = and != are already taken for lexical comparison. -- Cameron Simpson [EMAIL PROTECTED] DoD#743 http://www.cskk.ezoshosting.com/cs/ What I want is Facts. Teach these boys and girls nothing but Facts. Facts alone are wanted in life. Plant nothing else, and root out everything else. - Charles DickensJohn Huffam 1812-1870 Hard Times [1854]
Re: Peace agreement
On 21:39 02 Apr 2003, Dominik Vogt fvwm-workers@fvwm.org wrote: | Assuming I decide to forget all that has happened and stay in this | place. How am I going to resolve the conflict between my | conscience and publishing my work without restrictions? I believe | the fact that this conflict exists did not get the attention it | should have in the argument we had. Every act one performs has has effects, including non-acts. Not working on FVWM has effects. And so forth. A window manager, like most productivity tools, is a neutral tool in that any evil facilitated by it is a product of the evil of the work of the user. Conversely, any good it does is a product of the good of the work of the user. One the whole I would expect that users of free software are idealogically pro-cooperation and against conflict. Probably moreso than the general population. The mere possibility that FVWM may be used by someone who contributes to violence and death, however indirectly (or directly) is not of itself sufficient reason to cease distribution of the tool. This is because even if you take the line that there is NO justification for death and/or violence (which I gather is more or less your standard) it is not sufficient because war and violence are not the ONLY causes of death. The flipside is that disease and preventable accident also contribute to death. It is therefore arguable that aiding the good (by whatever criteria) users of FVWM may contribute to saving more lives than are cost by aiding the bad users, given the (estimated) statistical moral predisposition of the likely FVWM users. Such an argument is of course dependent on the uses of the work of the FVWM user population, and that is something you must estimate for yourself. However, if you take the view that an evil user of FVWM is aided by FVWM, thus placing a moral burden on you - one of its authors, you must also accept the logic that good users of FVWM, deprived of it by your withdrawal, are thus less effective and that this also places a moral burden on you. Weighing these two effects is of course something only you can do for yourself, but both effects exist. For myself, I think FVWM is a net win for good. I can't prove it. I hope this gives you something new and useful to consider. Cheers, -- Cameron Simpson, DoD#743[EMAIL PROTECTED]http://www.zip.com.au/~cs/ Washing one's hands of the conflict between the powerful and the powerless means to side with the powerful, not to be Neutral. - Quote by Freire. Poster by OXFAM. -- Visit the official FVWM web page at URL: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 PROTECTED]
Re: Ethics and some straight talking
On 20:14 31 Mar 2003, Bob Woodside [EMAIL PROTECTED] wrote: | On Tue, 1 Apr 2003 00:43:31 +0200 | [EMAIL PROTECTED] wrote: | | ...who of the subscribers of the original message would sign | it and who would not? | |This release is dedicated to the victims of the war in Iraq that |began in March, 2003. The following people, many of them users |or developers of fvwm, would like to express their sympathies to |those affected: | | I would subscribe that without a heartbeat's hesitation. So would I. -- Cameron Simpson, DoD#743[EMAIL PROTECTED]http://www.zip.com.au/~cs/ War doesn't prove who's right, only who's left. - BDD Games' Fortune -- Visit the official FVWM web page at URL: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 PROTECTED]
Re: The fvwm Ethical License
On 12:50 29 Mar 2003, Mikhael Goikhman [EMAIL PROTECTED] wrote: | Not me I'm afraid, I'm British and I agree with the war against | the Iraqi dictatorship. | | I do not understand this. In how far does being British, German, | American, Chinese or Martian affect ethics? | | If this does not affect ethics, how can you explain that most of the | people choose (agree to) the position of their countries? After all | these people elected their politicians or are forced by their dictator. Bosh. In a democracy you don't get to pick policies. The best you get to do is vote for whatever power group least offends you. And in most systems, if that's not one of the few major groups your vote gets discarded. There are preferential scheme, but that basicly means your voite gets moved to another power group. And once they're in they can basicly do as they please. The current agression in Iraq supplies a classic example: in Oz, if pretty clear that the majority of the population oppse the war and our role in it. Our glorious leader basicly has the view that it's his prerogative to go forth anyway. The US leader has the same attitude: he's asserted the power to make war without going through his Congress. Anyway, I support Dominik's approach: it doesn't require people to take his views or even to support pacifistic organisations as he wishes. Merely to get people to think seriously about it and consider some/all of the wishes of the code authors. Personally I think FVWM is a neutral tool. Very unlike, say, a gun, whole purpose is to kill or injure others - it is fundamentally a weapon, whatever the mindset of the person brandishing it. But I'll support Dominik's approach here. Cheers, -- Cameron Simpson, DoD#743[EMAIL PROTECTED]http://www.zip.com.au/~cs/ Your modesty is typically human, so I will overlook it. - a Klingon -- Visit the official FVWM web page at URL: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 PROTECTED]
Re: Determining if a window is iconified.
On 22:47 27 Jan 2003, Marcus Lundblad [EMAIL PROTECTED] wrote: | Is there some good way (from a shell script) to determine if a window is | iconified? | I'm writing tests for the new Closable, Maximizable etc. styles. | | xwininfo gives the geometry of the windows normal size, so there is no | difference when iconifiying. | | I guess an alternative is to have an interactive script where the user is | asked wuestions interactivly. Maybe a tiny C program to check if the window id is mapped? -- Cameron Simpson, DoD#743[EMAIL PROTECTED]http://www.zip.com.au/~cs/ Don't close your eyes for the crash; you'll miss the best part. - Bruce MacInnes, Skip Barber Driving School instructor -- Visit the official FVWM web page at URL: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 PROTECTED]
Re: Non-printable Website pages - why?
On 10:52 13 Jan 2003, Ethan Blanton [EMAIL PROTECTED] wrote: | jrc spake unto us the following wisdom: | However, I would like to print various things from your site | - especially some of the text advice and so forth. But, your | pages are all white text on black background - which does not | show up as anything readable on my printer. May I humbly | suggest that I am not the only one who has pointed this out to | you? | May I ask why you intentionally make it harder for people to | use fvwm ? You _can_ make your browser render in white on black you know... | What web browser are you using? Your browser should take care of this | and print the page as black text on a white background regardless. I | suggest trying mozilla or a mozilla derivative. [...] Mozilla doesn't do this as far as I can tell. It's VERY annoying. Netscape used to, and I do all my printing from netscape. -- Cameron Simpson, DoD#743[EMAIL PROTECTED]http://www.zip.com.au/~cs/ I guess this is what you get for being on the leading edge, you get cut sometimes. - Douglas Rand -- Visit the official FVWM web page at URL: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 PROTECTED]
Re: New non-window conditional command On
On 10:26 07 Jan 2003, Dominik Vogt fvwm-workers@fvwm.org wrote:
| On Tue, Jan 07, 2003 at 08:57:04AM +, Mikhael Goikhman wrote:
| On 07 Jan 2003 06:51:41 +0100, Dominik Vogt wrote:
|
| On Tue, Jan 07, 2003 at 12:18:08PM +1100, Cameron Simpson wrote:
|On 22:50 06 Jan 2003, Marcus Lundblad [EMAIL PROTECTED] wrote:
|| My plan is to remove the unnessesay
|| Closable,Maximizable,Iconifiable and AllowMaximizeFixedSize
|| since they correspond to ! variants of
|| Unclosable,Unmaximizable,Uniconifiable and
|| DisallowMaximizeFixedSize
[...]
|Could I cast a vote for NOT doing it this way?
|You should keep Closable and discard Unclosable, using !Closable
|and so forth. All these attributes should be positive statements.
|Likewise there shouldn't be any Disallow* options, just Allow*
|and !Allow*.
|
|This issue is entirely separate from what the defaults are.
|
| I agree 100%.
|
| The weak side of this is that a user has no any indication of what is the
| normal window behaviour. Other than this I have no problem to name options
| regardless of their default.
|
| The default is written out in the man page. It is always the last
| style of all the alternatives. For example,
|
| !AllowMaximize / Allow Maximize
|
| means that AllowMaximize is the default.
I have to say I've never realised this. Could someone (Dan?) put a paragraph
break
after the words:
options is a comma separated list containing one or more of the
following keywords. Each group of style names is separated by
slashes ('/'). The last style in these groups is the
default.
I know I for one missed this. My fault of course.
Cheers,
--
Cameron Simpson, DoD#743[EMAIL PROTECTED]http://www.zip.com.au/~cs/
A good newspaper is never good enough, but a lousy newspaper is a joy
forever.- Garrison Keillor
--
Visit the official FVWM web page at URL: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 PROTECTED]
Re: New non-window conditional command On
On 22:50 06 Jan 2003, Marcus Lundblad [EMAIL PROTECTED] wrote: | My plan is to remove the unnessesay | Closable,Maximizable,Iconifiable and AllowMaximizeFixedSize | since they correspond to ! variants of | Unclosable,Unmaximizable,Uniconifiable and | DisallowMaximizeFixedSize | | Does it make sence to let the non-default styles be the only ones, and | have the opposite styles as the default? | | I guess this should be done for all styles. But I guess this will be done | for 3.0, since it breaks backwards compatablility. | | Also, I might add a DisallowIconifyFixedSize to complement | DisallowMaximize fixed size. But I guess this would also call for a | DisallowShadeFizedSize. Could I cast a vote for NOT doing it this way? You should keep Closable and discard Unclosable, using !Closable and so forth. All these attributes should be positive statements. Likewise there shouldn't be any Disallow* options, just Allow* and !Allow*. This issue is entirely separate from what the defaults are. -- Cameron Simpson, DoD#743[EMAIL PROTECTED]http://www.zip.com.au/~cs/ If people were meant to run around naked, they'd have been born that way. - Rico the Masher, [EMAIL PROTECTED] -- Visit the official FVWM web page at URL: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 PROTECTED]
Re: compiler warning/bug in FvwmScript/script.y
On 10:00 15 Nov 2002, Dominik Vogt fvwm-workers@fvwm.org wrote: | On Thu, Nov 14, 2002 at 06:50:47PM -0500, Paul Smith wrote: | %% Cameron Simpson [EMAIL PROTECTED] writes: || Sorry, I somehow missed that paragraph. I just can't operate info || :-/ |cs You may want my man script, which presents info as one of the |cs choices for manual pages. More to the point, it parses info files |cs and turns them into a single flat text document, which of course |cs you browse with your pager as with ordinary manual entries. | | Yes, please! That's exactly what I need! Start here: http://www.zip.com.au/~cs/css/index.html#s-text-info2x and get the info2man.tar.gz file and also fetch: http://www.zip.com.au/~cs/scripts/man which is the script itself. You then add the info dirs to your $MANPATH and go. It may have a few dependencies on my environment which I'd be happy to iron out, so let me know if it gives you trouble. In particular it expects the envvar $OS to be linux on linux systems (well, actually groff-based systems). Hmm, I see there's now an nroff on my redhat box, so maybe you won't need the groff incantation at all. [...] | In particular, the s (search) and i (index lookup) are critically | important to know. Once you know these you can do more with Info that | you can do with either man pages or HTML. | | I really don't want to rant about the interface of info here. Let | it suffice to say that I absolutely *hate* hierarchical documents. | And info operates a bit like vi, a bit like lynx and a bit like | emacs, but not quite. That totally confuses me. I would second that hierachical remark - I also really hate limping through HOWTO web documents which are typically presented in pieces :-( And I generally want a big document in the pager my fingers know. Cheers, -- Cameron Simpson, DoD#743[EMAIL PROTECTED]http://www.zip.com.au/~cs/ ... that, in a few years, all great physical constants will have been approximately estimated, and that the only occupation which will be left to men of science will be to carry these measurements to another place of decimals. - James Clerk Maxwell (1813-1879) Scientific Papers 2, 244, October 1871 -- Visit the official FVWM web page at URL: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 PROTECTED]
Re: compiler warning/bug in FvwmScript/script.y
On 17:44 14 Nov 2002, Dominik Vogt fvwm-workers@fvwm.org wrote: | On Thu, Nov 14, 2002 at 11:04:59AM -0500, Paul Smith wrote: | %% Dominik Vogt fvwm-workers@fvwm.org writes: |dv Heck! Why isn't that mentioned in the gcc info page?! | | You mean like this: | These warnings are possible only in optimizing compilation, [...] | ? :) | | Sorry, I somehow missed that paragraph. I just can't operate info | :-/ You may want my man script, which presents info as one of the choices for manual pages. More to the point, it parses info files and turns them into a single flat text document, which of course you browse with your pager as with ordinary manual entries. It's certainly made info accessable for me. To be sure, there are no hyperlinks, but the link targets _are_ presented in the text, and the your pager's search function should find them fairly well. Just FYI. Cheers, -- Cameron Simpson, DoD#743[EMAIL PROTECTED]http://www.zip.com.au/~cs/ I'd hate to be one to quibble over grammar, but your statement above is fallacious even if true.- [EMAIL PROTECTED] (Bill Conner) -- Visit the official FVWM web page at URL: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 PROTECTED]
Re: Rules for files installed into bindir
On 09:02 10 Nov 2002, Mikhael Goikhman [EMAIL PROTECTED] wrote: | With that preamble, in my shells I expect to be able to go | foo -? | to most programs and get a usage message _because_ -? is not a valid | option. And I insist on my shells letting me type an unescaped -?, | and take care not to make stupidly named -* files. | | You know, zsh and tcsh by default give you an error on unescaped -?. I'm a zsh user myself, and turn that behaviour off. I consider it a sop to [t]csh users (zsh has extensive pretend to be csh customisation options). | So, what's I'm asking here is that: | - whether you implement an actual -? option doesn't |bug me, provided that _any_ bad option elicits the |full usage string | | It is good that you said GNU tells to print 2 lines only in this case, | so I don't need to add more than several paragraphs of reasonings. :) | I am against dumping the whole usage (that is usually more than 24 lines | since all my programs are very configurable) every time a user makes a | typo. For long usage messages, I agree. For short (eg up to, say, 12 lines?) I'd much rather get a usage message than have to invoke the program yet again. [...] | The only correct way to handle a bad option is to print 2 lines: | | program: unrecognized option '-o' (or: missing file argument after -o) | Run --help to get the list of all recognized options. For many-option commands, again I agree. But _please_, support '-h' in addition to '--help'; --help is a pain to type for such a trivial task. | A user knows what he does if he specified -o option, he wants the result | now. Or to see the diagnostic error line to know what he did wrong. He is | not interested in anything forced like copyright/license/--version/--help. Speaking as a user: agree/agree/maybe/disagree. Unless the help is very long. | (In fact, IMHO the only place for copyrights is the man page and sources.) Yep. | And I would prefer these two lines to be dumped to stderr like gcc does it | and not stdout like gnome-terminal does it. Because stdout should contain | the result of the program's run designed to be parsable/piped, an error | option should not damage the expectations of the following piped program. And also, not only does error-stdout bugger the pipeline, it swallows the error message from the user's eyes! | In any case, I would not blindly follow all GNU standards, only the | reasonable ones. Even GNU projects do not follow all of them. Hear hear! Cheers, -- Cameron Simpson, DoD#743[EMAIL PROTECTED]http://www.zip.com.au/~cs/ Pardon my driving, I'm trying to reload. -- Visit the official FVWM web page at URL: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 PROTECTED]
Re: Rules for files installed into bindir
On 20:33 09 Nov 2002, Mikhael Goikhman [EMAIL PROTECTED] wrote: | On 09 Nov 2002 18:24:18 +0100, Dominik Vogt wrote: | 3) We don't install any program to bindir without --help and --version. | And -h, -? and -V please. In the long run I would like to | switch to GNU style long options. | I think -V is a historical casus and it should better be -v, but let it | be -V... But not -?, it is not even inputable in many shells, should be | escaped as -\?. I beg to differ here. Well, not entirely, but slightly. My personal opinion is that a program should _always_ emit the usage listing if it gets a bad option. The GNU behaviour of bad option, tell them to run with --help enrages me. It is only sensible for programs with very many options; most programs' usage listing will happily fit on a single 24 lines screen. With that preamble, in my shells I expect to be able to go foo -? to most programs and get a usage message _because_ -? is not a valid option. And I insist on my shells letting me type an unescaped -?, and take care not to make stupidly named -* files. So, what's I'm asking here is that: - whether you implement an actual -? option doesn't bug me, provided that _any_ bad option elicits the full usage string - if you do implement -?, I request that it definitely emits a usage message | 4) The programs in the system's bindir should not have any extension. | | Extensions like .sh or .pl are good for files without +x permissions | so that a user could know what interpretter to run on these files. | Additional reasoning: | My /usr/bin has 2002 files. From 280 sh/bash scripts only 11 are *.sh. And extensions as _so_ tacky. | 5) The programs should have the fvwm- prefix for consistency. | | Additional reasoning: | My /usr/bin has 242 files in the dash form like gnome-bug and | and only 95 files in the underscore form like pg_dump. Besides, on most keyboards - doesn't need shift, and _ does. Easier to type. -- Cameron Simpson, DoD#743[EMAIL PROTECTED]http://www.zip.com.au/~cs/ Third, I propose prompt action on legislation extending and reforming the state's asset seizure law. The current law, which is a valuable tool for law enforcement in its fight against drug criminals, is set to expire on January 1st. This law provides over $30 million a year to law enforcement agencies, and should be quickly renewed. - Kathy Brown -- Visit the official FVWM web page at URL: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 PROTECTED]
Re: CVS dane fvwm-web: * screenshots/index.html: Screenshot by Cameron Simpson.
On 20:15 09 Nov 2002, FVWM CVS fvwm-workers@fvwm.org wrote: | Log message: | * screenshots/index.html: Screenshot by Cameron Simpson. Thanks! -- Cameron Simpson, DoD#743[EMAIL PROTECTED]http://www.zip.com.au/~cs/ -- Visit the official FVWM web page at URL: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 PROTECTED]
Re: Renamings
On 14:05 02 Nov 2002, Mikhael Goikhman [EMAIL PROTECTED] wrote: | Also, I think the arguments of the EwmhBaseStrut command should | use percent of screen size as the default unit, not pixels, | since virtually all other commands work like this. The new | syntax would the be | |EwmhBaseStrut 0p 576p 0p 432p | | To be honest, I would break compatibility (maybe in 3.0?) and use points | for numbers without suffix and percents for numbers with '%' suffix. I.e.: | | 48 - 48 points (currently percents) | 48p - 48 points | 48% - 48 percents (currently not really supported, but it works) | | I think, it is good to add support for '%' in our geometry too. While renaming thing, could we say pixels when we mean pixels? points is a printing measure, about 1/72nd of an inch. Since it _is_ a unit of measure, and used in font size specs (yea, even in X11 font specs), could we avoid the word points. Cheers, -- Cameron Simpson, DoD#743[EMAIL PROTECTED]http://www.zip.com.au/~cs/ I'll keep repeating this as long as I have to: Insult is the tactic of a man without an argument.- Andrew Stephen Damick, alt.config Repetition is the tactic of a mandy patinkin fan with wood chips between his ears. - Peter Berger, alt.config -- Visit the official FVWM web page at URL: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 PROTECTED]
Re: PATCH: bin/fvwm-root.1: missing option documentation ...
On 07:21 16 Oct 2002, Olivier Chapuis [EMAIL PROTECTED] wrote: | Anyone with any comments of the set the Esetroot X11 property option? | Should I bother? | | But I've answer this question and more (To: you and the fvwm-workers | list). Maybe this mail never arrive (can one see this mail in the | workers list?). Race conditions - found your reply after posting the above :-( Thanks. Will read and then code. Cheers, -- Cameron Simpson, DoD#743[EMAIL PROTECTED]http://www.zip.com.au/~cs/ Because of its special customs, crossposting between alt.peeves and normal newsgroups is discouraged. - Cameron Spitzer -- Visit the official FVWM web page at URL: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 PROTECTED]
PATCH: bin/fvwm-root.1: missing option documentation ...
I spent this morning making my set the root background work properly, and was looking at fvwm-root. I noticed that the manual doesn't match the code. Appended is a patch for the manual (against current CVS) to address this lack. The color-limit stuff is a bit vague because I didn't read that code in depth. While on this topic, I'm using Esetroot instead of fvwm-root. Why? Purely because it sets the ESETROOT_PMAP_ID pixmap property, and aterms listen for that. I notice fvwm-root can _clear_ this property but not set it. Is there any special reason for this? Merely that you use a different property for this? I was thinking of adding this facility (as an option, like -fe, since it is otherwise a resource waste). I presume it's a bad bad idea to hand the same pixmap to both properties, yes? -- Cameron Simpson, DoD#743[EMAIL PROTECTED]http://www.zip.com.au/~cs/ --- fvwm-root.1.origTue Oct 15 10:13:10 2002 +++ fvwm-root.1 Tue Oct 15 10:19:27 2002 @@ -10,6 +10,8 @@ .B fvwm-root .RB [ \-d ] .RB [ \-fe ] +.RB [ \-dither ] +.RB [ \-no-dither ] .I image_file .SH DESCRIPTION @@ -33,6 +35,21 @@ Causes fvwm-root to free the memory associated with the ESETROOT_PMAP_ID property. This is useful if you alternately use fvwm-root and an Esetroot compatible program. +.TP +.BI -dither +Causes fvwm-root to dither images for smoother rendition on displays +with color depth of 16 or lower. +.TP +.BI -no-dither +Causes fvwm-root NOT to dither images. +.TP +.BI -color-limit ncolors +Causes fvwm-root to limit its color use to +.I ncolors +(if specified). +.TP +.BI -no-color-limit +Causes fvwm-root NOT to limit its color use. .SH COMPATIBILITY In the past this utility was called -- Visit the official FVWM web page at URL: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 PROTECTED]
Re: PATCH: bin/fvwm-root.1: missing option documentation ...
On 16:54 15 Oct 2002, IPM Return requested [EMAIL PROTECTED] wrote: | I spent this morning making my set the root background work properly, | and was looking at fvwm-root. I noticed that the manual doesn't match | the code. Appended is a patch for the manual (against current CVS) | to address this lack. [...] | .RB [ \-fe ] | +.RB [ \-dither ] | +.RB [ \-no-dither ] | .I image_file I must be low on blood sugar. Of course, please also add: +.RB [ \-color-limit [ \fIncolors\fP ] ] +.RB [ \-no-color-limit ] to the SYNOPSIS. Doh. -- Cameron Simpson, DoD#743[EMAIL PROTECTED]http://www.zip.com.au/~cs/ What's the point of having Nebraska if we can't put it to its highest and best use? - Patrick Bedard arguing for a 100 mph speed limit -- Visit the official FVWM web page at URL: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 PROTECTED]
Re: PATCH: bin/fvwm-root.1: missing option documentation ...
On 11:02 15 Oct 2002, Dominik Vogt fvwm-workers@fvwm.org wrote: | Can you please re-post the complete patch, preferrably as an | attachment? Sure. Attached below. -- Cameron Simpson, DoD#743[EMAIL PROTECTED]http://www.zip.com.au/~cs/ In My Egotistical Opinion, most people's C programs should be indented six feet downward and covered with dirt.- Blair P. Houghton --- bin/fvwm-root.1.origTue Oct 15 10:13:10 2002 +++ bin/fvwm-root.1 Tue Oct 15 20:31:07 2002 @@ -10,6 +10,11 @@ .B fvwm-root .RB [ \-d ] .RB [ \-fe ] +.RB [ \-dither ] +.RB [ \-no-dither ] +.RB [ \-color-limit +.RI [ ncolors ] ] +.RB [ \-no-color-limit ] .I image_file .SH DESCRIPTION @@ -33,6 +38,21 @@ Causes fvwm-root to free the memory associated with the ESETROOT_PMAP_ID property. This is useful if you alternately use fvwm-root and an Esetroot compatible program. +.TP +.BI -dither +Causes fvwm-root to dither images for smoother rendition on displays +with color depth of 16 or lower. +.TP +.BI -no-dither +Causes fvwm-root NOT to dither images. +.TP +.BI -color-limit ncolors +Causes fvwm-root to limit its color use to +.I ncolors +(if specified). +.TP +.BI -no-color-limit +Causes fvwm-root NOT to limit its color use. .SH COMPATIBILITY In the past this utility was called
Re: PATCH: bin/fvwm-root.1: missing option documentation ...
On 13:00 15 Oct 2002, Dominik Vogt fvwm-workers@fvwm.org wrote: | On Tue, Oct 15, 2002 at 08:34:57PM +1000, Cameron Simpson wrote: | On 11:02 15 Oct 2002, Dominik Vogt fvwm-workers@fvwm.org wrote: | | Can you please re-post the complete patch, preferrably as an | | attachment? | Sure. Attached below. | Applied. Thanks. Anyone with any comments of the set the Esetroot X11 property option? Should I bother? -- Cameron Simpson, DoD#743[EMAIL PROTECTED]http://www.zip.com.au/~cs/ ERROR 155 - You can't do that. - Data General S200 Fortran error code list -- Visit the official FVWM web page at URL: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 PROTECTED]
Re: no edge resistance?
On 18:15 25 Apr 2002, Richard Lister [EMAIL PROTECTED] wrote: | From: Mikhael Goikhman [EMAIL PROTECTED] |http://www.hpc.uh.edu/fvwm/archive/0204/msg00192.html | | Great, thanks. I should have checked the archive. Is there a way to | disable Alt's new behaviour? Me too! I use Alt-M2 to move, and find this, well, disconcerting. I don't use snap attraction myself, but I use EdgeResistance. Can this be modified to - be off altogether - be attached to something else: a different modifier maybe - just be an attribute of move eg Move (NoConstraints) or something so people can just pick one move or other? Is this documented? I spent quite some time today rereading the manual, but it is quite long and I could have missed it. | I think this one may catch out a few people who originally came from twm. Heh. People who came from Fvwm 2.4.4 too. -- Cameron Simpson, DoD#743[EMAIL PROTECTED]http://www.zip.com.au/~cs/ I'm a 47-year-old middle-class male with a job. Every hippy-dippy thing that's thought up--from heroin addiction to special vegan lunch lines in the high school cafeteria--I get to pay for. Of course I'm Republican. - P. J. O'Rourke -- Visit the official FVWM web page at URL: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 PROTECTED]
Re: test -e not supported on Solaris (configure.in perl test)
On 11:21 19 Apr 2002, tim phipps [EMAIL PROTECTED] wrote: | Description: | configure bombs out becasue /bin/sh on Solaris 2.5 doesn't | do [ -e $PERL ] | | -f works for me but it's probably not the right thing because | that just tests for a regular file. -x (executable regular file) and -d (directory) are also fairly specific and portable, depending what you're testing. -- Cameron Simpson, DoD#743[EMAIL PROTECTED]http://www.zip.com.au/~cs/ ..to know him was to love him. And to love him was to know him. Those who know him LOVED him - while those who did not know him, loved him from afar... - Data/Graves, The Schizoid Man, stardate 42437.5 -- Visit the official FVWM web page at URL: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 PROTECTED]
Re: Naming problems
On 21:41 06 Apr 2002, Mikhael Goikhman [EMAIL PROTECTED] wrote: | On 06 Apr 2002 22:48:33 +0200, Olivier Chapuis wrote: | 3 - Now that xpmroot support PNG (and XBM) should we rename it (with a | symbolic link from xpmroot to the new name)? If yes one may think | that fvwm-root is a good name, but I do not think so because in fvwm | - separated names are scripts. FvwmRoot is obviously bad, but what | about fvwmroot ? | | If you ask me, I think every executable we install except for fvwm itself | (current fvwm2) should be prefixed with fvwm-. fvwm-bug, fvwm-root, | fvwm-convert-2.4. fvwm-convert-2.6, fvwm-config. I second this opinion. It shouldn't matter whther something's implementation is a script or not. -- Cameron Simpson, DoD#743[EMAIL PROTECTED]http://www.zip.com.au/~cs/ Heaven could change from chocolate to vanilla without violating perfection. - [EMAIL PROTECTED] (Ken Arromdee) -- Visit the official FVWM web page at URL: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 PROTECTED]
Re: CVS domivogt: * New command Schedule that executes commands delayed. May be used to
On 15:57 30 Jan 2002, Dominik Vogt fvwm-workers@fvwm.org wrote: | Yes. At the moment, there are no guarantees when the scheduled | code is executed though. The schedule table is processed only when | no X events or module input is coming in. In theory it could take | hours before the code is actually executed. Wouldn't it be work at least polling it every 100 or 1000 input events when busy? -- Cameron Simpson, DoD#743[EMAIL PROTECTED]http://www.zip.com.au/~cs/ Politics - From the Greek Poly, meaning many, and the English Tics, meaning little blood sucking insects. - copyright 1991, Joshua J. Fielek, DoD#385, [EMAIL PROTECTED] -- Visit the official FVWM web page at URL: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 PROTECTED]
Re: CVS domivogt: * New command Schedule that executes commands delayed. May be used to
On 12:10 31 Jan 2002, Cameron Simpson [EMAIL PROTECTED] wrote: | On 15:57 30 Jan 2002, Dominik Vogt fvwm-workers@fvwm.org wrote: | | Yes. At the moment, there are no guarantees when the scheduled | | code is executed though. The schedule table is processed only when | | no X events or module input is coming in. In theory it could take | | hours before the code is actually executed. | | Wouldn't it be work at least polling it every 100 or 1000 input events -- worth | when busy? Whoops. -- Cameron Simpson, DoD#743[EMAIL PROTECTED]http://www.zip.com.au/~cs/ The way to control people's thoughts is not to lock them out of information, but feed them a steady diet of dross. - Clifford Stoll -- Visit the official FVWM web page at URL: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 PROTECTED]
Re: Exec in fvwm
On 17:13 13 Jan 2002, Alexander Kotelnikov [EMAIL PROTECTED] wrote: | BTW, I was surprised finding out fvwm use fork instead of vfork for | Exec. There is a note about that not all platforms support vfork butwe | can easily check it in configure time. Or just stay the hell away from it. It's evil. Even the BSD man pages (where it originated) said it was a temporary kludge until they had fork() being more efficient, which it is on all modern systems. | Dmitry vfork() is a disaster and shouldn't be used. For a historic | Dmitry description, read the Linux manpage for vfork(2), especially the 2nd | Dmitry paragraph in the BUGS section. | | both setpgrp and vfork are *standard*, if the implemented or not. But I | have to admit that vfork hurts me badly on Debian unstable. And in what standard is vfork() specified? AFAIK, none, because it's an ugly kludge. Now fork(), _that's_ standard. Maybe you meant common. -- Cameron Simpson, DoD#743[EMAIL PROTECTED]http://www.zip.com.au/~cs/ It is the cunning of form to veil itself continually in the evidence of content. It is the cunning of the code to veil itself and to produce itself in the obviousness of value. - Baudrillard -- Visit the official FVWM web page at URL: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 PROTECTED]
