Re: Do we still need color-limit/visual options in fvwm?

2016-05-07 Thread Dan Espen
Thomas Adam <tho...@fvwm.org> writes:

> Hi all,
>
> Just looking through a few things, and I thought I'd ask whether fvwm needs to
> stlil support color limiting, and color depths for XServers with less than
> TrueColor?
>
> These days, 24-bit seems to be the standard, and indeed, I've never yet come
> across a server still using only 256 colours.  Whilst I appreciate you can
> still go and find such things, do we actually need fvwm to supprort it?

It's not the server, it's the hardware in the workstation
graphics card.

Back when I was using Sun hardware it was required.
I put the original code in that tried to force colors to
familiar named colors with the idea that colors with common
names would be already be in use.

A while later the old code was ifdef'd with the current
color cube logic.  I think there is no risk in removing
the common name logic but that won't reduce executable size.

I don't think the color limiting stuff is large enough to
make any difference.  If you think otherwise, consider
making it a build option.

-- 
Dan Espen



Re: Some advices about the new static website

2016-04-08 Thread Dan Espen
Thomas Funk <t.f...@web.de> writes:

> On 04/08/2016 11:08 PM, Thomas Adam wrote:
>> On Fri, Apr 08, 2016 at 09:44:48PM +0200, Thomas Funk wrote:
>>> What about the perlib pages and the ... uhm ... 'unstable' documentation
>>> pages (http://fvwm.org/doc/unstable/index.html)? Will they appear again
>>> in the future?
>>
>> perllib maybe (althought woefully out of date, and it's on my TODO list to
>> look at).
>
> I could help you if you like as I did much inside Fvwm-Nightshade with
> perllib.
>
>>  As for unstable man pages, no.  There's no such thing any more, and
>> hasn't been for a long time now.
>
> 'unstable' was only used as example. As I remember the same pages exists
> on 'stable', too. But it would be a shame to lost those pages. Also Dan
> did much work on the linking on the FVWM page.

We don't have stable and unstable anymore so references to
stable and unstable should be removed.


-- 
Dan Espen



Re: FVWM website: WAS: [Re: FVWM code moved to Github]

2016-04-02 Thread Dan Espen
Jaimos Skriletz <jaimosskril...@boisestate.edu> writes:

> Also I am unsure if these various markdown files, FAQ.md, AUTHORS.md,
> DEVELOPERS.md, etc should be located and maintained on the webpage or
> in $FVWM.GIT source. I think either can work with git.io so it is
> probably a matter of preference. But agreed, these markdown files
> should all be collected and maintained in a single place.

If I recall  correctly, we created Changelog, and AUTHORS  in the source
tree because its a recommended part of a GNU source tree.
(Similar to INSTALL, README, NEWS.)

-- 
Dan Espen



Re: FVWM website: WAS: [Re: FVWM code moved to Github]

2016-03-25 Thread Dan Espen
Thomas Adam <tho...@fvwm.org> writes:

R> On 23 March 2016 at 22:21, Dan Espen <des...@verizon.net> wrote:
> Excellent.  Then set yourself up with a Github account, and let me
> know your username, and I'll add you to the fvwmorg and you can do
> something with the website repository.

My account is named "danespen".

> Note that I'm getting married this weekend and will then be away on
> honey moon for two weeks.

Enjoy and don't even think about Fvwm.

I've no specific plans for retirement.
I'm on my own and starting over.

-- 
Dan Espen



Re: FVWM website: WAS: [Re: FVWM code moved to Github]

2016-03-25 Thread Dan Espen
Jason L Tibbitts III <ti...@math.uh.edu> writes:

>>>>>> "JS" == Jaimos Skriletz <jaimosskril...@boisestate.edu> writes:
>
> JS> who controls the domain name fvwm.org,
>
> A whois query shows that it's me.

Not sure why, maybe I paid, but paid for you?

  From: Gandi <support-re...@gandi.net>
  Subject: [GANDI] fvwm.org domain name renewed
  To: des...@verizon.net
  Date: Fri, 26 Jul 2013 16:58:29 +0200 (2 years, 34 weeks, 4 days ago)


  Dear Customer,

  We are pleased to confirm that you have successfully renewed the following 
domain that is registered at Gandi:

  fvwm.org

  This domain has been renewed for 3 year(s), and the new the new expiration 
date is therefore 2017-12-29 05:00:00

  As a reminder for your records, the handle that you used to renew this domain 
is XX.


-- 
Dan Espen



Re: FVWM website: WAS: [Re: FVWM code moved to Github]

2016-03-25 Thread Dan Espen
Thomas Adam <tho...@fvwm.org> writes:

> On Wed, Mar 23, 2016 at 09:19:18PM -0400, Dan Espen wrote:
>> Yep, I'm referring to the web pages.
>> I have some CSS based pages at work using themes.
>> The themes aren't really important to me, but since
>> I doubt GIT is going to give us PHP I think we'll be better off without
>> the PHP.
>
> Have a look at this:
>
> https://help.github.com/articles/about-github-pages-and-jekyll/
>
> I think this would be a good way to go, and would reduce the need for us to
> potentially write any HTML.
>
> I'm all for using Jekyll in this case!

My first impression, it's Github only.
I lean toward writing plain HTML/CSS with a little JavaScript for
maximum portability and familiarity.

Meanwhile, I committed fvwm-web changes yesterday, but those
changes have not shown up at fvwm.org.

Jason, what's up?

-- 
Dan Espen



Re: FVWM website: WAS: [Re: FVWM code moved to Github]

2016-03-23 Thread Dan Espen
Thomas Adam <tho...@fvwm.org> writes:

> On 23 March 2016 at 22:21, Dan Espen <des...@verizon.net> wrote:
>> I think we're embarking on a lot of work.
>
> Which aspect, specifically?  Note that if you're referring just to the
> website, then you might be right---I don't know enough about HTML/CSS
> to make that call.  However, it requires someone with enough
> understanding to put in place something static which can be hosted on:
>
> https://github.com/fvwmorg/fvwmorg.github.io
>
> Note that this repository as-named, assumes hosting under github.io,
> which as I understand it makes thing a lot easier.  Certainly,
> removing PHP at this point is definitely a good idea, as we're not
> gaining anything from its use any more that CSS can't provide.  I
> consider this a good thing.

Yep, I'm referring to the web pages.
I have some CSS based pages at work using themes.
The themes aren't really important to me, but since
I doubt GIT is going to give us PHP I think we'll be better off without
the PHP.

>> As a start I've updated the download instructions to send users to GIT.
>
> OK.
>
>> I know you have the web stuff on GIT but if I make changes there they
>> won't get to fvwm.org.
>
> That's OK -- because we can leave what's hosted on fvwm.org
> as-is---and start to do something proper with fvwmorg.github.io --
> that's your play area.  Go forth and have a blast.  Note that I'm
> envisaging something which is self-hosting.  That is to say, something
> we can redirect to from fvwm.org -- I see that as a positive thing
> indeed.

We own the domain name, I'm not clear on the details but I think once
we move the pages we can just make Fvwm.org be the git pages.

>> Jason, let us know if/when you start pulling the web pages from GIT.
>
> See previous paragraph, I do not think this is the right approach at all.

I don't see the difference.
Right now Jason pulls from CVS to build the pages at fvwm.org.
He said he's willing to pull from Git instead.
So, the fvwm-web can be in CVS or GIT, it doesn't matter,
we just need Jason to decide where he wants to pull from.

>> I'm pretty good with HTML/CSS.  PHP gives us some nice stuff, but I
>> guess we can live without it.
>
> Excellent.  Then set yourself up with a Github account, and let me
> know your username, and I'll add you to the fvwmorg and you can do
> something with the website repository.

Okay, will get to that sometime.

> Note that I'm getting married this weekend and will then be away on
> honey moon for two weeks.

Well, CONGRATULATIONS.
That's just great.
I was married in 1964.
I'm retiring as of March 31.

-- 
Dan Espen



Re: FVWM website: WAS: [Re: FVWM code moved to Github]

2016-03-23 Thread Dan Espen
Thomas Adam <tho...@fvwm.org> writes:

> On Sun, Mar 20, 2016 at 08:16:13PM -0400, Dan Espen wrote:
>> Moving the Fvwm-web source to Github won't help if we still need to
>> publish using Jason's services.
>
> So I've taken a look at this, and have noted the following:
>
> * PHP is used to regenerate the theming components of the site;
> * PHP is used to render in from the fvwm repo, the contents of files from:
>   
>   NEWS
>   FAQ
>
> * PHP is used to ensure the theme is applied consistently for the borders for
>   "window" (the default theme).
>
> What happens via github.io pages is that static content can be used for this.
>
> I'm starting to think that we have no desire or need for PHP at all for the
> website.  Before the use of static HTML generators, etc., it made a lot of
> sense.  Additionally, there's a lot one can do with CSS which mitigates the
> need for PHP as we're currently using it for the website.
>
> As for the linking in NEWS/FAQ -- the NEWS file in particular is obsoleted,
> given that git commit logs can be used to gather the same information.  That
> said, if we do retain NEWS for releases, we can just upload a separate set of
> notes for that against each release in the releases area of Github [1].  It's
> a part of the process.
>
> The FAQ therfore, is part of the website and it should be moved into that
> repository.
>
> I've since renamed the fvwm-web repository [2] to match the expectations of
> what github.io expects.
>
> I'd really (REALLY!) be interested in someone coming up with a proof of
> concept on what a FVWM website might look like using a static HTML generator
> that github.io accepts, just to prove my points above.  I won't be doing that
> work, however, but if someone does want to give this a go, do please let us
> know!
>
> Kindly,
> Thomas Adam
>
> [1]  https://github.com/fvwmorg/fvwm/releases
> [2]  https://github.com/fvwmorg/fvwmorg.github.io

I think we're embarking on a lot of work.
As a start I've updated the download instructions to send users to GIT.
I know you have the web stuff on GIT but if I make changes there they
won't get to fvwm.org.

Jason, let us know if/when you start pulling the web pages from GIT.

I'm pretty good with HTML/CSS.  PHP gives us some nice stuff, but I
guess we can live without it.

-- 
Dan Espen



Re: FVWM code moved to Github

2016-03-20 Thread Dan Espen
Thomas Adam <tho...@fvwm.org> writes:

> Hi all,
>
> I know we've had these discussions in the past, but I think now is the time we
> actually do something about them.
>
> I appreciate I've swooped in here, and just done this, but the discussion[0]
> happened once before, and given the recent circumstances with the borked CVS
> repository, it seemed unfair to leave an impending release hanging.
>
> To that end, I have therefore created an organisation on Github[1] which at
> the moment houses what I'm now calling the "official" FVWM repository [2].
> This has been converted from the existing FVWM CVS repository (branch-2_6).
>
> The 2.6.6 release now has a tarball uploaded and can be found here[3].
>
> I've not changed fvwm-web, but this will likely be converted as well and put
> on [1] in due course.
>
> Note that as an organisation on Github, we have a lot more freedom, in that
> more than one person who is a member of the fvwmorg organisation will be able
> to do things like handle releases, etc., and that should something happen,
> it's not anything in our control that we'd need to worry about.
>
> This has absolutely *no* reflection on Jason at all.  He's spent the last
> twenty odd years managing this, and to have all of this go through one person
> is not scalable, especially when something goes wrong.  So we should be really
> thankful indeed for Jason's efforts, and to note that I hope he continues to
> manage the hosting/mailing lists, but the code... that's now better handled by
> us.  Moving away from CVS is also long overdue.
>
> So what happens next?  Well, I need existing fvwm-workers who had commit-bit
> access to let me know so I can add you to the organisation.
>
> Additionally, I have the following outstanding items:
>
> * Convert fvwm-web, and add to fvwmorg on GH;
> * Rip out the existing CVS docs and put something else in place;
> * Update the release procedure
> * Put our logo on the front of the landing page for fvwmorg on GH
>
> Any questions, do please let me know.

I'm not clear on what we can do with Github.
You mention leaving the web pages and mailing lists on fvwm.org.

For that we need Jason.

Is it possible to move the whole project to github or some other hosting site?

Moving the Fvwm-web source to Github won't help if we still need to
publish using Jason's services.


-- 
Dan Espen



Re: Release 2.6.6?

2016-03-13 Thread Dan Espen
Thomas Adam <tho...@fvwm.org> writes:

> Hi,
>
> I'm getting quite a few emails off-list, asking me when 2.6.6 is going to be
> released.  I know it's been a while, so I'm thinking of doing this this
> evening at some point.
>
> Any objections?  The CVS branch seesm stable enough to me.

No objections at all.
It's long overdue.

Every time I look I get distracted by the 2.7 branch, which should be
eliminated.  But I don't know how to turn 2.6 into the new head.
So, just doing 2.6.6 would be fine.

-- 
Dan Espen



Re: CVS dane: new file ChangeLog-pre-2.6.6

2014-09-15 Thread Dan Espen
Thomas Adam tho...@fvwm.org writes:

 On 15 Sep 2014 18:30, c...@math.uh.edu wrote:

 CVSROOT: /home/cvs/fvwm
 Module name: fvwm
 Changes by: dane 14/09/15 12:30:08

 Modified files:
 . : Tag: branch-2_6 ChangeLog
 Added files:
 . : Tag: branch-2_6 ChangeLog-pre-2.6.6

 Log message:
 new file ChangeLog-pre-2.6.6

 Ah. I was just about to do this and now you've saved me the bother.
 Thanks. :-)

No problem.
Not sure I want to work in the mvwm tree.
Not fond of the name, and don't want to see FvwmCPP go away.

BTW, I keep multiple versions of Fvwm installed and can pick which
one I want to use.  Simply a matter of a startup script that puts
the right version of Fvwm in my $PATH.

-- 
Dan Espen



Re: Snapshots

2012-08-14 Thread Dan Espen
Thomas Adam tho...@fvwm.org writes:

 On 14 August 2012 15:23, Jason L Tibbitts III ti...@math.uh.edu wrote:
 OK, snapshots are back.  At least they appear to be working OK, though
 ChangeLog and NEWS don't seem to have been updated in quite some time.

 Please ensure you're creating snapshots off branch-2_6.

Yep, that must be 2.7 since the NEWS isn't current.

Maybe we should take steps to remove 2.7?

-- 
Dan Espen



Re: ChangeLog vs modules/ChangeLog ?

2006-07-11 Thread Dan Espen
seventh guardian [EMAIL PROTECTED] writes:
 Hi.
 
 I have a question regarding the use of the ChangeLogs.
 
 Obviously, changes to the fvwm core are reported in the root
 ChangeLog. But what about changes to modules? I ask this because I've
 allways logged my changes to the root one, but now think I should have
 done it to modues/ChangeLog. On the other hand, there are lots of
 module changes in the root changelog..
 
 So, what is our ChangeLog policy?
 
 If it is module stuff - modules/ChangeLog, rest - ChangeLog, then I
 guess module stuff should be moved to the correct modules/ChangeLog.
 If not, then we would be better served with just one ChangeLog, in
 wich case we should merge both.

The Changelogs were getting huge so they were split up.
Using Emacs, you find the right one using C-x 4 a.
Otherwise it's the first one above the directory your in.

-- 
Dan Espen   E-mail: [EMAIL PROTECTED]



Re: debug.c still useful?

2006-07-07 Thread Dan Espen
seventh guardian [EMAIL PROTECTED] writes:
 Hi.
 
 After some checking around, it seems that the file libs/debug.c isn't
 used anymore. The file was created in 1998 as a debuging library, but
 it seems to have been replaced by simpler solutions.
 
 It's part of libfvwm.a, and the *.c code is surrounded by a #ifdef
 DEBUG, so never gets compiled. The whole file is empty at the
 moment, except for an int variable that is there (outside the #ifdef)
 expressly to prevent an empty file, as some compilers don't like that
 (it's written on the coments). On the other hand, the header file
 fvwmlib.h has its macros and structs allways defined, (but there is no
 compiled code!). Nothing is ever used, so I think it's safe to remove
 it.
 
 These are the only places where you find the macros (which need to be removed
 ):
 - DB() is in a #if 0 part of module_interface.c (but the rest of the
 file already uses the DBUG macro) and in focus.
 - __FILE__ and __LINE__ is in a ifdef'ed to 0 part of focus.h where
 alternative debuging macros are defined.
 
 It's a big decision to remove a whole file, so I need a second
 opinion.. Is the file still useful or may I remove it?

The whole debug facility is rarely used, and I can't remember
it ever being useful.

I find the stuff in FvwmAnimate/FvwmForm suits my own personal needs.

-- 
Dan Espen   E-mail: [EMAIL PROTECTED]



Re: Libtool ltdl on fvwm

2006-07-07 Thread Dan Espen
Dominik Vogt [EMAIL PROTECTED] writes:
 
 --KsGdsel6WgEHnImy
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On Fri, Jul 07, 2006 at 11:05:36PM +0100, seventh guardian wrote:
  It all starts with this snip from docs/TODO:
 =20
  - Implement (or at least investigate) dynamic loading of functions
 on systems that support it?
 =20
  (There is more on that on that file. These are just the first two lines)
 =20
  Recently I began testing GNU's Libtool on a project of mine,
  particulary using Ltdl. Ltdl is a dynamic library loading framework.
  It allows dynamic loading of modules for an application, or or as a
  last resort for systems not supporting it, either preloading (linking
  just before execution) or static linking (during the compilation
  time). It's very portable and flexible, as you can see from here:
  http://www.gnu.org/software/libtool/manual.html#Tested-platforms
 =20
  Anyway, it would be great to have the facility to load new styles or
  functions from a library (a ltdl module). Minimalistic systems would
  just load (or compile, depending on the arch) the very basic functions
  and styles, while more feature-rich systems would load all of them.
  The unoficial feature patchsets would be replaced by style modules
  (it has nothing to do with the current fvwm modules).. And so on. The
  text on docs/TODO explains the whole idea.
 
  For those interested in this, you can find libtool's manual here:
  http://www.gnu.org/software/libtool/manual.html
 =20
  For now I'm studying the fvwm code to see where this fits. I'm
  thinking of trying it out (in a my local private branch, as this is
  definitely not a 2.5 feature).  If I get to do anything I'll inform
  you.
 
 Paul added this TODO item ages ago.  Specifically he suggested to
 make libfvwm a shared library.  I am well aware of Libtool's
 capabilities, but never was very fond of the idea to use it.  No
 matter how portable it is, we'd ask for a lot of problems with
 library versioning (modules finding a wrong version of the lib).
 
 The idea to allow dynamic loading of features is nice.  But frankly
 I think the fvwm core is nowhere near as modular to allow features
 being taken out of it.  (And even this is an euphemism for the
 state of the code).

The TODO item is for modules.

-- 
Dan Espen   E-mail: [EMAIL PROTECTED]



Re: debug code cleanup patch #1

2006-07-06 Thread Dan Espen
Bob Woodside [EMAIL PROTECTED] writes:
 On Thursday 06 July 2006 16:19, Dominik Vogt wrote:
  On Thu, Jul 06, 2006 at 08:23:50PM +0100, seventh guardian wrote:
   On 7/6/06, Dominik Vogt [EMAIL PROTECTED] wrote:
   The patch looks fine.  I'll commit it.  By the way, do you have
   commit privileges for CVS?
  
   No, I don't.. Am I ready for it? :)
 
  I think so :-)
 
  Any second vote for Renato?
 
   I'll cast a second .

Third.

Renato, if you haven't seen it already, check
the Fvwm web site Developer section for getting commit access.

-- 
Dan Espen   E-mail: [EMAIL PROTECTED]



Re: Periodic command

2006-07-05 Thread Dan Espen
Viktor Griph [EMAIL PROTECTED] writes:
 On Wed, 5 Jul 2006, Scott Smedley wrote:
 
  Hi Dominik,
 
  Can you have multiple peridic commands or just one?
 
  Multiple.
 
  I suggest to replace the command Periodic with some option to the Schedu
 le
  command
 
  The current specification for Schedule is:
 
  Schedule delay_ms [command_id] command
 
  So, would something like the following do?
 
  Schedule delay_ms [command_id] [Periodic] command
 
  Perhaps someone has a better suggestion?
 
 
 I think the above is good. The only problem with it is that if someone has 
 a function named Periodic and use to execute that with Schedulte the above 
 will break that config. One way to avoid that, and also give room for more 
 possible options to Schedule in the future, is to put options before the 
 delay. That way any string before the delay number could be read as an 
 option. So
 
 Schedule [Periodic] delay_ms [command_id] command
 
 would be a possible easier to parse syntax.

How about:

Schedule delay_ms x repeat_ms [command_id] command

Ie:

Schedule 1000 x 2000 
Schedule x 5000 

-- 
Dan Espen   E-mail: [EMAIL PROTECTED]



Re: Title font color broken

2006-06-06 Thread Dan Espen
Serge (gentoosiast) Koksharov [EMAIL PROTECTED] writes:
 On Sun, Jun 04, 2006 at 11:15:29AM +0200, Dominik Vogt wrote:
  Unfortunately I never got any feedback on this from the person who
  reported it first.  The problem was that in some cases the GC used
  to draw the title was not set before drawing, but it seems the old
  code relied on this not being done.
  
  I'd be grateful if someone could look into this problem or at
  least give me a minimal config to reproduce it.
 
   I can confirm Dan's bugreport. And it easily reproducable with minimal
   config:
 
   I compile FVWM like this:
 
 aclocal
 autoheader
 automake --add-missing
 autoreconf
 ./configure  --prefix=$HOME/usr --oldincludedir=$HOME/usr/include \
 --enable-xft --disable-xinerama --enable-iconv --disable-bidi \
 --enable-perllib --enable-nls --enable-gtk --with-x
 --without-rplay-library \
 --without-gnome
 make  make install
 
   Then I move entire ~/.fvwm directory somewhere:
 
   $ mv ~/.fvwm ~/usr/src
 
   Create new empty directory:
 
   mkdir ~/.fvwm
 
   Create '~/.fvwm/config' file consisting of two lines:
 
   Style * ForeColor red
   Style * HilightFore red
 
   Launch FVWM and see that titles of both active and inactive windows
   are black, but not red.
 
   I hope you can reproduce it as well and fix this bug. If not, you can
   provide me with instructions what to do next and I'll be more than
   glad to help.

Dominik posted a patch containing the commit that caused the
problem.  He asked for help trying to recreate the original
problem he was trying to patch.

We could just revert his patch, but the original problem would
remain unsolved.

I haven't had any time to look into this yet.

-- 
Dan Espen   E-mail: [EMAIL PROTECTED]



Title font color broken

2006-06-03 Thread Dan Espen

It's been a while since I've updated to CVS.
Maybe a month or 2.

After the last update, the text in my window titles is black.
These commands have no effect:

Style * ForeColor white
Style * HilightFore white

So far, I don't see the change that broke this.

-- 
Dan Espen   E-mail: [EMAIL PROTECTED]



Re: Title font color broken

2006-06-03 Thread Dan Espen
Thomas Adam [EMAIL PROTECTED] writes:
 On Sat, Jun 03, 2006 at 11:57:58AM -0400, Dan Espen wrote:
  
  It's been a while since I've updated to CVS Maybe a month or 2   .
 
  After the last update, the text in my window titles is black. These
  commands have no effect:
 
  Style * ForeColor HilightFore
 
 Last I heard those commands were being deprecated in favour of using
 colorsets.

Good thing someone is still using them so we don't break things that
are only deprecated.

Actually, I don't see anything in the man page about colorsets being
required.

-- 
Dan Espen   E-mail: [EMAIL PROTECTED]



Re: Project Support Open Source (SOS) wanted to donation to your project

2006-05-25 Thread Dan Espen

Any opinions on this?

Bob Mutch [EMAIL PROTECTED] writes:
 Hi Dan,
 
 Sent it to the list if that will help and to the top contributors also.
 
 Current we are donating $10,000 to 200 projects which is $50 per project.
 
 Please let me know what license your project is under and the page and
 location in the page where this is stated.
 
 We will be asking other companies to donate to the list we are compiling
 also.
 
 This is the acknowledgement I would like placed.
 
 a href=http:/www.seocompany.ca/SEO Company/a financially supports the
 free and open source software (FOSS) 
 
 community with Project SOS (Support Open Source). 
 
 Find below the 5 requirements and 7 questions I need answers for.  Sorry to
 have to send you a form letter like this 
 
 but I am currently over 100 emails behind on this project.
 
 Requirements:
 1. The project must have a website.
 2. You must place an acknowledgment of the each donation on your site.
 3. Your project must be currently active and has produced a software
 product.
 4. Your software product must be released under a free open source software
 license and this must be stated somewhere 
 
 on your site.
 5. You must have a PayPal address or PayPal service that donations can be
 sent to.
 
 
 Questions:
 1. Will you be able to place an acknowledgement of each donation on your
 website?
 2. What page would you be putting the acknowledgement on?
 3. What is your PayPal account email?
 4. What license is your software project released under (GPL, LGPL, BSD,
 GNU, OSI approved, or what ever) and what is 
 
 the URL of the page where the license information is posted?
 5. What was the date of the first version of your software?
 6. How many different versions of the projects software have been released?
 7. Is your project currently active?
 
 
 Also check out my Project SOS page.
 http://www.seocompany.ca/project-support-open-source.html
 
 If you don't mind you can digg me at digg.com and even leave a comment after
 you get a donation.
 http://digg.com/software/Company_throwing_money_at_open_source_projects
 
 If you blog or have friends that blog you may want to ask them to blog up on
 the project.  The more noise we make the 
 
 more companies that will use my list to make donations and the more money
 that will be sent to support your project.
 
 Thanks!
 
 Bob Mutch
 519-636-6663
 [EMAIL PROTECTED]
 http://www.seocompany.ca/project-support-open-source.html
 bobmutchseo -- Yahoo IM
 [EMAIL PROTECTED] -- MSN Messenger
 bobmutchseo -- AIM
 
 -Original Message-
 From: Dan Espen [mailto:[EMAIL PROTECTED] 
 Sent: May 19, 2006 5:30 PM
 To: [EMAIL PROTECTED]
 Subject: Re: Project Support Open Source (SOS) wanted to donation to your
 project 
 
 Bob Mutch [EMAIL PROTECTED] writes:
  Hi my name is Bob Mutch and I am the owner of Solutions with Service, a 
  Canadian company that uses open source software products.
  
  I have started a project called Project SOS (Support Open Source) to 
  help fund free and open source software projects.
  
  I would like to make a donation to your open source work 
  http://www.fvwm.org/ though our project.
  
  Here is the page that how the donations work.
  
  http://www.seocompany.ca/project-support-open-source.html
 
 Seems to be a broken link.
 
  There has been a post on digg.com with a few comments from open source 
  developers that have received donations already.
  
  http://digg.com/software/Company_throwing_money_at_open_source_projects
  
  Do you have a page where you give acknowledgement to your sponsors?
  
  Let me know!
 
 Fvwm is far from 'my' project.
 I'm an occasional contributor.
 If you don't mind this being mentioned in a public mail list,
 send this mail to [EMAIL PROTECTED]
 
 Otherwise, I can send you a list of a few of the top contributors.
 
 -- 
 Dan Espen   E-mail: [EMAIL PROTECTED]
 
 
 

-- 
Dan Espen   E-mail: [EMAIL PROTECTED]



Re: yet another documentation fixes

2006-03-28 Thread Dan Espen
Thomas Adam [EMAIL PROTECTED] writes:
 On Wed, Mar 29, 2006 at 02:21:05AM +0400, Serge (gentoosiast) Koksharov wrote
 :
Greetings everyone,
 
  As promised, I found and corrected another bunch of typos and other
  inconsistencies in the docs. Apply against the latest CVS sources of
  the 2.5 branch. But that's not all, more will follow when I find time
  to check remaining part of the docs. See you later.
 
 There's a mistake in one of your fixes:
 
 @@ -36,7 +68,7 @@
 * sample.fvwmrc/system.fvwm2rc-sample-1:
 replaced all mentions of `rsh' with `ssh'. rsh is obsolete and
 inherently insecure. We shouldn't teach our users bad things,
 -   should we?
 +   shouldn't we?
 
 The phrase:  We shouldn't teach our users bad things, should we? is the
 correct one.  The negation of NOT teaching the users bad things has
 already been done.  It is neither correct English or grammatically
 correct to say:
 
 We shouldn't teach our users bad things, shouldn't we?

Check what got checked in.  I made a fix in that area.

 I need to review some of your other fixes --- whilst you've made a
 fantastic effort in doing so, I can already see one or two technical
 mistakes that need changing.  I'll have to apply this patch and somehow
 reverse engineer your changes.
 
 But thank you ever so much for your efforts.

Gee, I hope all the mistakes aren't my fault.

-- 
Dan Espen   E-mail: [EMAIL PROTECTED]



Re: fvwm 2.5.x (bug|spell)fixing patch

2006-03-25 Thread Dan Espen
Dan Espen [EMAIL PROTECTED] writes:
 Serge (gentoosiast) Koksharov [EMAIL PROTECTED] writes:
Hi, dear FVWM developers,
  
  I created this patch which should apply cleanly against FVWM CVS sources
  of the 2.5 development branch. It mostly fixes documentation typos,
  mispellings, formatting errors, etc... Also it fixes delay in one of the
  FvwmAnimate animations. Please keep in mind, that I'm FVWM newbie, so
  doublecheck my work. I'll keep an eye on your project and try to help as
  much as I can.
 
 Thanks.  You sure found a lot of spelling errors.
 It might take me a while, but I'll apply the patch.
 In fvwm-perllib.in explicitely' should be explicitly.
 
  Best wishes!
  
  P.S. could my name be added to the AUTHORS file? There already one guy
  who helped with documentation fixing.
 
 Sure.

I applied that patch a couple of days ago, but I never saw the email
from the CVS update.

The amount of errors you found in the documentation was impressive.
No only did you find spelling errors, and grammatical errors, but
also just plain wrong things, and misplaced things.
I wonder, how did you do that?

-- 
Dan Espen   E-mail: [EMAIL PROTECTED]



Re: fvwm 2.5.x (bug|spell)fixing patch

2006-03-22 Thread Dan Espen
Serge (gentoosiast) Koksharov [EMAIL PROTECTED] writes:
   Hi, dear FVWM developers,
 
 I created this patch which should apply cleanly against FVWM CVS sources
 of the 2.5 development branch. It mostly fixes documentation typos,
 mispellings, formatting errors, etc... Also it fixes delay in one of the
 FvwmAnimate animations. Please keep in mind, that I'm FVWM newbie, so
 doublecheck my work. I'll keep an eye on your project and try to help as
 much as I can.

Thanks.  You sure found a lot of spelling errors.
It might take me a while, but I'll apply the patch.
In fvwm-perllib.in explicitely' should be explicitly.

 Best wishes!
 
 P.S. could my name be added to the AUTHORS file? There already one guy
 who helped with documentation fixing.

Sure.

-- 
Dan Espen   E-mail: [EMAIL PROTECTED]



Re: Module.h bug and sugestion

2006-02-10 Thread Dan Espen
Dominik Vogt [EMAIL PROTECTED] writes:
 
 The -audio option and invoking it as FvwmAudio is the result or
 merging the old FvwmAudio module back into FvwmEvent.  It was once
 split from FvwmEvent (I think) and shared most of the code.
 Probably FvwmAudio did not support module aliases, so there is no
 mode to have both.

FvwmAudio was written long before FvwmEvent.
Like some of other modules, it never needed aliases.

-- 
Dan Espen   E-mail: [EMAIL PROTECTED]



Re: Patch: FvwmAnimate using ParseModuleArgs() - NOT WORKING YET

2006-02-04 Thread Dan Espen

I think you need to keep the asterisk at the front of the name.
There are times when you need it there, and times when you don't.
It's easier to put it there in the first place rather than trying
to stick it back when you need it.


Since I put the macros there and I like to use macros,
I have to ask what you think is wrong with them.
Personally, I find that the more compact the code is,
the easier it is to read.

Inline functions for C are not portable.

-Original Message-
Date: Sat, 4 Feb 2006 14:29:17 +
From: seventh guardian [EMAIL PROTECTED]
To: FVWM Workers fvwm-workers@fvwm.org
Subject: Patch: FvwmAnimate using ParseModuleArgs() - NOT WORKING YET
Sender: [EMAIL PROTECTED]

On 2/2/06, Dominik Vogt [EMAIL PROTECTED] wrote:
 So, the work can be split into several smaller steps:

 1. Make all the modules use ParseModuleArgs() and copy the fds
from the ModuleArgs struct to the arrays that are currently
used by the modules.
 2. Remove the fd arrays in the modules and use the fds in the
ModuleArgs instead.
 3. Make the service functions in Module.c use a (const ModuleArgs *)
instead of passing individual arguments and adapt the modules.


FvwmAnimate is mostly done for the 1st item in the list. I also made
the code use the struct-name instead of the char *MyName global var.

As for what isn't done yet in this module: FvwmAnimate uses some
macros (yuch!) for the communication with fvwm. I used CatString3()
for the places where we need the * char before the module name, but I
really don't know what to do in with the macros. I thought of making
them inline functions, but I would like to know what you think..
Search for these macros are not done yet in the patch and you will
find it.

With that problem aside, I hope FvwmAnimate users could test the new
code to see if it works ok. Note that it is _not_ working right now
because of those macros.

Cheers!
  Renato Caldas





Re: Patch: FvwmAnimate using ParseModuleArgs() - NOT WORKING YET

2006-02-04 Thread Dan Espen
seventh guardian [EMAIL PROTECTED] writes:
 On 2/4/06, Dan Espen [EMAIL PROTECTED] wrote:
 
  I think you need to keep the asterisk at the front of the name.
  There are times when you need it there, and times when you don't.
  It's easier to put it there in the first place rather than trying
  to stick it back when you need it.
 
 Yes, it is far more efficient that way. But the problem is that the
 existing structure only stores the name, and not the asterisk. Of
 course we could use the existing char* MyName, but that would defeat
 the whole purpose of using the ModuleArgs struct.
 
 I wonder if we need the asterisk in the first place. Wouldn't it be
 easyer new-code-wise to use only the name for pattern matching? It
 could be stripped off by fvwm or simply not used in the config files.
 
 (since this is only experimental code we are allowed to forget
 backward compatibility issues)

Eventually you have to deal with compatibility.

FvwmAnimate mallocs the storage for MyName and never frees it.
I don't consider that a leak since it does it one time.
We could arrange to free it though.
You can change ParseModuleArgs to malloc the space for the name
including the *.

Then you have 2 choices:

Pass the address of the second byte and
change FvwmAnimate to refer to the full name as name-1

or

Pass the address of the first byte and change all the modules
that want the name without the asterisk to reference name+1.

  Since I put the macros there and I like to use macros,
  I have to ask what you think is wrong with them.
  Personally, I find that the more compact the code is,
  the easier it is to read.
 
 Sorry, it's just my personal liking. Macros are also ok, what I don't
 like in macros is that the code appears to be standard C but it's not
 (it has its own syntax..).

C macros are part of standard C.

 And if it worked perfectly with the old code, it's puzling me with the new =
 one:
 
 Assuming we are to replace char* MyName with the struct, I currently
 don't know what to do with one of the existing macros (the one that
 uses the asterisk'ed name). Forgive my macros' ignorance, but I don't
 know what to do to call CatString3() from within the macro.

Since CatString3 returns the addess of the static buffer,
it should work fine.
Yep, just tested it, it works just like you are using it
with macros.
I think you have something else going on.

-- 
Dan Espen   E-mail: [EMAIL PROTECTED]



Re: Patch: FvwmAnimate using ParseModuleArgs() - NOT WORKING YET

2006-02-04 Thread Dan Espen
Mikhael Goikhman [EMAIL PROTECTED] writes:
 On 04 Feb 2006 16:56:47 +, seventh guardian wrote:
  
existing structure only stores the name, and not the asterisk. Of
course we could use the existing char* MyName, but that would defeat
the whole purpose of using the ModuleArgs struct.
   
I wonder if we need the asterisk in the first place. Wouldn't it be
easyer new-code-wise to use only the name for pattern matching? It
could be stripped off by fvwm or simply not used in the config files.
   
(since this is only experimental code we are allowed to forget
backward compatibility issues)
  
   Eventually you have to deal with compatibility.
  
  Yes, but unless there's a reason for the use of the asterisk, it is
  cleaner not to have it. Configuration keywords are changing all the
  time, it won't be that difficult to strip the * from the config files.
 
 Here you speak about the fvwm configuration. You can't omit the asterisk
 without inventing a new syntax that does not conflict with the syntax of
 fvwm commands and functions. I see no problem in the asterisks syntax, it
 seems to be more optimal than other possible syntaxes for module configs.

The asterisk tells Fvwm to save up the module config commands,
not parse them.  It then sends out the commands to a module
when the module asks for them.

There's more to it than what I just described.
Check the module documentation.

-- 
Dan Espen   E-mail: [EMAIL PROTECTED]



Re: PATCH: menu drawing fixes

2005-11-25 Thread Dan Espen
Dominik Vogt [EMAIL PROTECTED] writes:
 The attached patch fixes various menu drawing problems. 
 Would someone be so kind and commit it to CVS, please?

Did you post the whole patch?
menu_expose in menu.h still returns void.
I got:

../../fvwm2_5_15/fvwm/menus.c:6814: error: conflicting types for 'menu_expose'
../../fvwm2_5_15/fvwm/menus.h:355: error: previous declaration of 'menu_expose' 
was here

-- 
Dan Espen   E-mail: [EMAIL PROTECTED]



Re: PATCH: menu drawing fixes

2005-11-25 Thread Dan Espen
Dan Espen [EMAIL PROTECTED] writes:
 Dominik Vogt [EMAIL PROTECTED] writes:
  The attached patch fixes various menu drawing problems. 
  Would someone be so kind and commit it to CVS, please?
 
 Did you post the whole patch?
 menu_expose in menu.h still returns void.
 I got:
 
 ../../fvwm2_5_15/fvwm/menus.c:6814: error: conflicting types for 'menu_expose
 '
 ../../fvwm2_5_15/fvwm/menus.h:355: error: previous declaration of 'menu_expos
 e' was here

More errors after fixing that:

../../fvwm2_5_15/fvwm/menus.c: In function 'make_menu':
../../fvwm2_5_15/fvwm/menus.c:2675: warning: implicit declaration of function 
'MR_USED_MINI_ICONS'
../../fvwm2_5_15/fvwm/menus.c:2675: error: invalid lvalue in assignment
../../fvwm2_5_15/fvwm/menus.c: In function 'get_menu_paint_item_parameters':
../../fvwm2_5_15/fvwm/menus.c:3355: error: 'struct anonymous' has no member 
named 'used_mini_icons'

-- 
Dan Espen   E-mail: [EMAIL PROTECTED]



Re: Fvwm and xcompmgr (the composite extension)

2005-11-09 Thread Dan Espen
seventh guardian [EMAIL PROTECTED] writes:
 On 11/7/05, Dan Espen [EMAIL PROTECTED] wrote:
  seventh guardian [EMAIL PROTECTED] writes:
   Hi
  
   I've already posted a bug report on the fvwm mailing list some weeks
   ago regarding this, but no one answered. Today I switched to
   xorg-7.0.0 and the problem is still there, so it must be fvwm.
  
   The problem I found is related to the composite extension of xorg:
   when I run xcompmgr (the composite manager) fvwm looses the
   screen-scrolling abillity to the right and down. I mean, after running
   xcompmgr from the command line, you can no longer scroll (by placing
   the cursor on the screen edge) to the right or down. And even after
   killing the composite manager the problem persists. The left and up
   scrolling work fine.
  
   Also, if you restart fvwm, even with xcompmgr running, things go back
   to normal. So it must be something on the start of xcompmgr... Other
   wm's work flawlessly.
  
   I'm using a patched version of fvwm from the gentoo portage: it has
   the translucency patch applied. So if any of you are using a
   composite manager and it works ok with the unpatched fvwm, please let
   me know.
  
   Is there anything else I can do to help tracking the bug?
 
  Edge scrolling works by Fvwm creating invisible windows around the
  screen borders.  xcompmgr must be interferring with them somehow.
 
  Try changing the 'edgethickness' to see if that helps.
 
 
 No, it's the same. I forgot to mention, I can drag windows between
 screens and it works fine. Only the empty handed scroll doesn't
 work.
 
  Run xwininfo -root -all to see if there is a window in the way.
 
 I really don't know how to read the output, and as it is quite large,
 here's a diff from both before and after running xcompmgr (command:
 diff before after -U 10)
...
 
 As I can see, the exposure thing is related to the composite
 manager, so that part shouldn't matter. Appart from that, I can only
 say that some things, I supose they are windows, are disapearing when
 xcompmgr is executed. Restarting fvwm makes them come back..
 
 What do you think the problem is?

I have no clue.

I tried running it on my system.
Everything slowed down, the root turned black,
it continually printed error messages,
menus wouldn't clear when they displayed.
When I moved the mouse to the screen edge, the
pointer changed as it should but it didn't look like it scrolled.

I can't use the system while it's running, so I don't think I can
find out much more.

-- 
Dan Espen   E-mail: [EMAIL PROTECTED]



Re: gnome menus in fvwm

2005-11-04 Thread Dan Espen
Dan Barber [EMAIL PROTECTED] writes:
 Hi all,
 
 I build the Mutagenix LiveCD Suite(http://mutagenix.org) which provides 
 fvwm as an alternate to GNOME for the desktop CD.  I wanted to be able to 
 provide an fvwm menu which would give access to all the GNOME programs 
 already installed on the CD.

Take a look at fvwm-menu-directory.

-- 
Dan Espen   E-mail: [EMAIL PROTECTED]



Re: gnome menus in fvwm

2005-11-04 Thread Dan Espen
Dan Barber [EMAIL PROTECTED] writes:
 
 
 On Fri, 4 Nov 2005, Dan Espen wrote:
 
  Dan Barber [EMAIL PROTECTED] writes:
  Hi all,
 
  I build the Mutagenix LiveCD Suite(http://mutagenix.org) which provides
  fvwm as an alternate to GNOME for the desktop CD.  I wanted to be able to
  provide an fvwm menu which would give access to all the GNOME programs
  already installed on the CD.
 
  Take a look at fvwm-menu-directory.
 
 Well, it seems that would work, but would just give a huge menu of all the 
 executables in a directory with no heierarchy.  The script I sent copies 
 pretty closely the GNOME menu layout (ie subdirectories for office, 
 multimedia, etc)
 
 Unless I'm missing something...?

Oops, I should have written:

fvwm-menu-desktop

-- 
Dan Espen   E-mail: [EMAIL PROTECTED]



Re: Sidepic with new logo

2005-08-06 Thread Dan Espen
Dominik Vogt [EMAIL PROTECTED] writes:
 On Fri, Aug 05, 2005 at 07:34:47PM -0400, Dan Espen wrote:
  Dominik Vogt [EMAIL PROTECTED] writes:
   I've converted the new logo to sidepic format (attached).  I'm not
   sure where we're keeping fvwm-related images.
 =20
  You can reach them from this page:
 =20
  http://www.fvwm.org/download/icons.php
 =20
  We had a request (years ago) that if we ever re-released
  the icons package that we give it a version number of
  some sort (perhaps a date).
 
 Ah, yes.  But how is the tarball generated?

The command to generate the tarball is in the comments in

fvwm-web/icons/Icon_Screenshots.ksh

of course the command should be modified to add a version
number or date.

-- 
Dan Espen   E-mail: [EMAIL PROTECTED]



Re: Sidepic with new logo

2005-08-05 Thread Dan Espen
Dominik Vogt [EMAIL PROTECTED] writes:
 I've converted the new logo to sidepic format (attached).  I'm not
 sure where we're keeping fvwm-related images.

You can reach them from this page:

http://www.fvwm.org/download/icons.php

We had a request (years ago) that if we ever re-released
the icons package that we give it a version number of
some sort (perhaps a date).

-- 
Dan Espen   E-mail: [EMAIL PROTECTED]



Re: patch for manpage of fvwm

2005-06-02 Thread Dan Espen

 Hi everybody.
 
 In fvwm manpage, someplaces, the word condition in written contition. 

Fixed in CVS.

Thanks.

-- 
Dan Espen   E-mail: [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: Windows unmapped with desktop switch?

2005-06-02 Thread Dan Espen
Nick Johnson [EMAIL PROTECTED] writes:
 Hello all,
 
 I was reading over virtual.c (very recent version from CVS), and I
 just wanted to check if I am reading it correctly:  does fvwm unmap
 windows when it changes desk?

Yes.

 How about when it changes page?

I believe it moves the window offscreen in that case.

Does the difference cause any problems for you?

-- 
Dan Espen   E-mail: [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: Bug#287588: fvwm crashes on 1-bpp and 4-bpp displays

2005-03-20 Thread Dan Espen
Manoj Srivastava [EMAIL PROTECTED] (va,manoj) writes:
 Hi,
 
  [Please retain the CC to [EMAIL PROTECTED]
   so that the Debian BTS has a record of your input]
 
  This was reported by a Debian user.
 
 Hi
  When run on a 1 BPP or 4 BPP display, FVWM crashes on startup with
  the following output : 

I'd like to take a look at this problem, but everything I've
tried so far refuses to work with depth 1 or 4 visuals.

X itself won't start that way, it says the drivers don't support
the depth.  I'm using S3 and I860.  Xnest doesn't want to
start that way either.  The man page says the server needs
to support that depth.  Even Xvfb, which doesn't have to
display anything gives me:

home Xvfb :2 -screen 0 1024x768x4
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/home-1:2
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6

Fatal server error:
Couldn't add screen 0


I'm using the latest Xorg release 6.8.2.

-- 
Dan Espen   E-mail: [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: Bug#293368: fvwm: 'Mouse 1 T A Move' does not work as expected

2005-03-17 Thread Dan Espen
Tavis Ormandy [EMAIL PROTECTED] writes:
 On Thu, Mar 17, 2005 at 12:38:26PM -0600, Manoj Srivastava wrote:
  Package: fvwm
  Version: 2.5.12-4
  Severity: normal
  
  When you push mouse 1 on title bar and try to move a window the
  movement is delayed for a while. Indeed, it appears to wait until
  button release, which is very disconcerting.
  
 
 This is expected behaviour, the user probably wants something like this:
 
 AddToFunc MoveWindow I Move
 Mouse 1 T A MoveWindow

The built in binding is:

Mouse 1 T   A FuncFvwmRaiseLowerX
AddToFunc FuncFvwmRaiseLowerX
+ I Raise
+ M Move
+ D Lower

Even with a double click binding in the function and clicktime set
to a high value, Fvwm starts moving the window as soon as
it detects motion.

-- 
Dan Espen   E-mail: [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: root window keybindings

2005-03-16 Thread Dan Espen
Dan Espen [EMAIL PROTECTED] writes:
 
 Lately I've been having problems with root window key bindings.
 I don't think it was due to Fvwm changes, I think it might
 have started with a Mozilla upgrade.
 
 I can produce this pretty consistently:
 
 I use MouseFocus.
 Switch to another page with mozilla on it and operate the Mozilla menus.
 Then switch to a page using the keyboard that puts the pointer
 over the root.
 
 Root keybindings won't work.
 
 Click on the root and they start to work again.

Strangely enough, xaniroc was the cause of this problem.

-- 
Dan Espen   E-mail: [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: FVWM: PeriodicTasks bug?

2005-02-05 Thread Dan Espen
Bjoern Steinbrink [EMAIL PROTECTED] writes:
 Hello,
 
 On 2005.02.04 14:38:59 -0800, [EMAIL PROTECTED] wrote:
  While I was playing around with some ideas for FvwmScript, I noticed an
  odd behavior that I was unable to explain by reading the man pages. I
  suspect its a bug tickled by improper usage, but I'll leave that up to
  you folks to decide. I've written and attached a small test script that
  shows the problem.
  
  Basically by my understanding, the attached script should advance the
  red background one button every 5 seconds. However what actually happens
  is that for one second out of 5 the red background cycles as fast as my
  machine can make it go.
  
  If I add a Title line to each widget, the script works predictably and
  only advances once every 5 seconds. Seems like the interpreter doesn't
  like empty buttons too well.
 
 FvwmScript contains a bug that executes the periodic tasks too often
 when there are pending events. The following patch fixes this.
...
  P.S.: There is a typo in the man page for FvwmScript where
  PeriodicTasks is spelled Periodic Task in the example.

The patch has been applied and the man page corrected.

Thanks.
-- 
Dan Espen   E-mail: [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: segfault: Key without any arguments

2005-01-19 Thread Dan Espen
Frank Gruellich [EMAIL PROTECTED] writes:
 Hello,
 
 I dunno, maybe I've done something really bad but I think, it shouldn't
 crash.  I disabled all configurations (no .fvwm2rc) and at the default
 Issue FVWM command I issued Key (or Mouse).  I forgot the
 arguments and fvwm segfaults.

I've applied your patch to CVS.

Thanks.
-- 
Dan Espen   E-mail: [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]


unclutter gtk2

2005-01-06 Thread Dan Espen

It looks like fvwm, gtk2 and unclutter don't get along.

Run unclutter.
Set Fvwm to use MouseFocus or SloppyFocus
Start a gtk2 program, for example

/usr/bin/gtk-demo

double click stock item browser

move the pointer to the window background area,
in this case its on the right.

Wait for unclutter to try to hide the pointer.

The pointer will start to move up and down as fast as it can.

This doesn't happen with other window managers, I tried twm.

So far I'm having no luck trying to figure out how to
get a trace.

We had previous problems with unclutter in May 2001,
July 2001, and Jan 2002.

-- 
Dan Espen   E-mail: [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]


root window keybindings

2005-01-06 Thread Dan Espen

(Ok in my last mail I said 3rd problem, and it looks like it
might be the 4th.)


Lately I've been having problems with root window key bindings.
I don't think it was due to Fvwm changes, I think it might
have started with a Mozilla upgrade.

I can produce this pretty consistently:

I use MouseFocus.
Switch to another page with mozilla on it and operate the Mozilla menus.
Then switch to a page using the keyboard that puts the pointer
over the root.

Root keybindings won't work.

Click on the root and they start to work again.

-- 
Dan Espen   E-mail: [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: unclutter gtk2

2005-01-06 Thread Dan Espen
Thomas Adam [EMAIL PROTECTED] writes:
 On Thu, Jan 06, 2005 at 03:17:45PM -0500, Dan Espen wrote:
  
  It looks like fvwm, gtk2 and unclutter don't get along.
 
 That's interesting. This problem doesn't happen in gvim (gtk2 version),
 or gaim. But one interesting effect I have observed with GTK2 programs
 in general is that if the mouse is placed in certain areas of widgets,
 the CPU goes to 100%, and the mouse flickers back and forth.

You need a background area, not a text widget.
Bring up the gvim open file dialog and use one of the
background areas.

 Until now, I had considered it to be a GTK2 bug. But thinking about the
 delay, it could also be an unclutter issue (I too, run it). I'll see
 what I can dig up about this.

The Gnome/Gtk folks say there is no XWarpPointer in gtk.
There's none in unclutter either so Fvwm is the likely
culprit.

-- 
Dan Espen   E-mail: [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: unclutter gtk2

2005-01-06 Thread Dan Espen
Paul Smith [EMAIL PROTECTED] writes:
 I had to give up unclutter due to this bug.  I still miss it terribly :-(.
 
 It would be nice if someone figured out what the problem is.

Here's what I just got from [EMAIL PROTECTED]:

I  could trigger this  with metacity.  However, when running unclutter
-noeventsit  doesn't  happen.   Without  -noevents,  it  fakes  an
EnterNotify event on  the  window, in an   attempt  to fake  out  some
ancient emacs version's focus/nonfocused cursor changing.

I'm not sure why the faked EnterNotify  causes the cursor to flip out,
but  unclutter should probably  default  to this  hack off since emacs
doesn't seem to need this anymore.


Seems to solve the problem for me.

-- 
Dan Espen   E-mail: [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: Notification: incoming/1537 glade docking

2004-12-26 Thread Dan Espen
[EMAIL PROTECTED] writes:
 FVWM Bug Tracking notification
 
 new message incoming/1537
 
 Message summary for PR#1537
   From: [EMAIL PROTECTED]
   Subject: undocking crashes fvwm2
   Date: Sat, 25 Dec 2004 19:35:31 -0600
   0 replies   0 followups
 
  ORIGINAL MESSAGE FOLLOWS 
 
 From [EMAIL PROTECTED] Sat Dec 25 19:35:32 2004
 Date: Sat, 25 Dec 2004 19:35:31 -0600
 From: [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Subject: undocking crashes fvwm2
 
 Full_Name: Neil Zanella
 Version: 2.4.19
 
 Hello,
 
 I am running fvwm2 2.4.19 on Fedora Core 2. I am experiencing several
 freezes
 under fvwm2 when I undock/dock the toolbar from glade or dock/undock a
 window
 from JDeveloper. This forces me to have to log out of fvwm2 with
 ctrl-alt-del.
 This is the only time I experience fvwm2 freezes.

Neil,

I don't know if this will help you, but I just tried
undock/dock in glade with current CVS and had no problems.

-- 
Dan Espen   E-mail: [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: Single click RootMenu, double click WindowList

2004-12-13 Thread Dan Espen
William Paul Vrotney [EMAIL PROTECTED] writes:
 
 This function works fine if bound to almost anything (like a button):
 
 Single click RootMenu, double click WindowList
 DestroyFunc RootMenu-or-WindowList
 AddToFunc RootMenu-or-WindowList
 + I Menu Root-Menu mouse -1p -1p
 + D WindowList mouse -1p -1p NoGeometry
 
 If bound to mouse 1 on the root plane
 
 Mouse 1   R   N   Menu Root-Menu mouse -1p -1p
 
 it also works fine but, after executing it successfully, fvwm hangs until
 the mouse is moved.  For example if you launch an application using this it
 will not come up until the mouse is moved.
 
 Is this a bug? Is there another way of achieving this?  It seems like a bug
 because it seems to imply that one can not have a flawless binding to a
 single and double click on the root plane.

It looks like earthlink put my reply in your suspect email folder.

Here is one more attempt to reach you and my original reply:

Both those functions menu and windowlist are meant to grab the
xserver and cause the hang that you observed.

There has been some experimental code developed for tear off menus which
would be a prerequiste for solving this problem with menus.

You might try the Module FvwmWindowList instead of using the built in
windowlist.  The FvwmGtk might serve as a substitute for the menu.

I've closed your problem report as not a problem. Send mail to
fvwm-workers@fvwm.org if you feel this is still a problem.


-- 
Dan Espen   E-mail: [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: Left Mouse double click root later hangs (PR#1528)

2004-12-12 Thread Dan Espen
Both those functions menu and windowlist are meant to grab the
xserver and cause the hang that you observed.

There has been some experimental code developed for tear off menus which
would be a prerequiste for solving this problem with menus.

You might try the Module FvwmWindowList instead of using the built in
windowlist.  The FvwmGtk might serve as a substitute for the menu.

I've closed your problem report as not a problem. Send mail to
fvwm-workers@fvwm.org if you feel this is still a problem.
--
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 olicha: * Added a set of functions for implementing tool tips

2004-12-08 Thread Dan Espen
Olivier Chapuis [EMAIL PROTECTED] writes:
 On Sun, Dec 05, 2004 at 07:44:40PM -0500, Dan Espen wrote:
  FVWM CVS fvwm-workers@fvwm.org writes:

  For FvwmIconMan, I adjusted the first  paragraph, but got stuck on the
  second:
 
 ManWidth is the width of the full FvwmIconMan. For example if the
 width of the FvwmIconMan manager is 1024, MaxButtonWidthByColumns 4
 is equivalent to MaxButtonWidth 256. This is useful when you do not
 know, at config time, the width of the manager (e.g., for swallowed
 IconMan). In a certain sense you will never have less than 4 columns.
 So maybe, MinColumns is good. I used MaxButtonWidthByColumns to say
 that the MaxButtonWidth is expressed in terms of columns (or computed
 from a number of columns. I like the idea to use something like
 MaxButtonWidth_something_good to express the fact that this option
 is just an other way to set the MaxButtonWidth option.

I think I have it now.  Please check and see.

In another part of the same man page, I don't follow
part of the TipsJustification description.  The part
between the lang_check markers (which I did modify a little):

.IP *FvwmIconMan: [id] TipsJustification \fIvalue\fP
where \fIvalue\fP can be leftup, rightdown or center.
Specifies
the justification (direction) of the tips window relative to its button after
the tips window has been placed.
\.#needs_lang_check
Default is leftup which means that if a tip is placed above or below
(respectively, on the left or on the right of)
its button, 
then the left
(respectively, the top)
border of the tip 
and of the button are aligned.
\.#end_needs_lang_check
The alignment is adjusted by the TipsOffset option.
See next option.


The way you use respectively is very hard to read
in english.
Just describe leftup then
start a new sentence and say
rightdown and center work like leftup but in different directions.

I tried to read it ignoring the repectively stuff and
still couldn't follow it.
If you just expand on it or give an example like you
did above that would help.

-- 
Dan Espen   E-mail: [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 olicha: * Added a set of functions for implementing tool tips

2004-12-05 Thread Dan Espen
FVWM CVS fvwm-workers@fvwm.org writes:
 CVSROOT:  /home/cvs/fvwm
 Module name:  fvwm
 Changes by:   olicha  04/12/03 02:47:49
 
 Modified files:
   .  : ChangeLog NEWS 
   libs   : Makefile.am defaults.h 
   modules: ChangeLog 
   modules/FvwmIconMan: FvwmIconMan.1.in FvwmIconMan.c 
FvwmIconMan.h fvwm.c globals.c readconfig.c 
x.c xmanager.c xmanager.h 
 Added files:
   libs   : FTips.c FTips.h 
 
 Log message:
 * Added a set of functions for implementing tool tips
 * Implemented tips in IconMan
 * New options IconMan MaxButtonWidth and MaxButtonWidthByColumns
 * Fixed bug #1480 by updating EWMHUseStackingOrderHints documentation
 * One needs_lang_check in fvwm.1.in and one in FvwmIconMan.1.in

fvwm.1.in is not checked in.  Did you really change it?

For FvwmIconMan, I adjusted the first  paragraph, but got stuck on the
second:

.IP *FvwmIconMan: [id] MaxButtonWidth \fIwidth\fP
Defines a maximum for the width of a button (in pixels). By default there
is no maximum. A value of 0 resets the default. The maximum is only used
with a non growing manager (the ManagerGeometry option
specifies non zero width and height).

.IP *FvwmIconMan: [id] MaxButtonWidthByColumns \fIcol\fP
This is equivalent to MaxButtonWidth ManWidth/col where ManWidth is
the width of the Manager. 


What is ManWidth?

Should this be MaxWidthInColumns, or just MaxColumns?

-- 
Dan Espen   E-mail: [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: Fvwm bug 1135 keysym documentation, not a bug

2004-11-29 Thread Dan Espen
Emmanuel Thomé [EMAIL PROTECTED] writes:
 On Fri, Nov 26, 2004 at 09:35:06PM -0500, Dan Espen wrote:
  I've closed this problem as not a bug.
 
 you seem to miss the point.
 
  I found this comment in the keysymdef.h from the current Xorg release:
  
  ! The definitions here should match X11/XF86keysym.h
  XF86AudioLowerVolume:1008FF11
 
 This can't be in keysymdef.h ; it's in XKeysymDB. XKeysymDB is a better
 reference to look into, IMHO, when looking for keysyms.
 
 The point is that not only the entries from keysymdef.h can be used, but
 also those from XF86keysym.h (with XK_ stripped out in the middle) ; The
 alternative I suggest is to direct the user to XKeysymDB instead, which
 contains all possible keysyms with correct spelling.
 
 Note that as the man page currently contains no reference to XKeysymDB,
 it's not obvious that one should look into it.

I think you missed my point.

From the header file, I surmised that the X developers mean to keep
XKeysymDB and keysymdef.h in sync.

It looks like they've failed.  What you have is a bug in X, not
in Fvwm.

I believe removing the XK_ from the middle is also a bug.

This whole thing with X keysyms is bad enough (using a header file
as documentation).  It shouldn't get any worse than it is.

(Just my opinion.)

-- 
Dan Espen   E-mail: [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: Fvwm bug 1135 keysym documentation, not a bug

2004-11-29 Thread Dan Espen
Emmanuel Thomé [EMAIL PROTECTED] writes:
 On Fri, Nov 26, 2004 at 09:35:06PM -0500, Dan Espen wrote:
  I've closed this problem as not a bug.
 
 you seem to miss the point.
 
  I found this comment in the keysymdef.h from the current Xorg release:
  
  ! The definitions here should match X11/XF86keysym.h
  XF86AudioLowerVolume:1008FF11
 
 This can't be in keysymdef.h ; it's in XKeysymDB. XKeysymDB is a better
 reference to look into, IMHO, when looking for keysyms.
 
 The point is that not only the entries from keysymdef.h can be used, but
 also those from XF86keysym.h (with XK_ stripped out in the middle) ; The
 alternative I suggest is to direct the user to XKeysymDB instead, which
 contains all possible keysyms with correct spelling.
 
 Note that as the man page currently contains no reference to XKeysymDB,
 it's not obvious that one should look into it.

Sorry, the man page for xmodmap explains it this way:

   The KEYSYMNAME on the left hand side is translated
   into matching keycodes used to perform the  corre­
   sponding  set of keycode expressions.  The list of
   keysym names may  be  found  in  the  header  file
   X11/keysymdef.h  (without the XK_ prefix) or the
   keysym   database/usr/X11R6/lib/X11/XKeysymDB.
   Note  that if the same keysym is bound to multiple
   keys, the expression is executed for each matching
   keycode.

They still refer to an XK_ prefix, but it looks like
having 2 files to refer to is intentional.

I'll update the man page.

-- 
Dan Espen   E-mail: [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]


bug report FvwmForm non-reproducible

2004-11-26 Thread Dan Espen

I've moved this problem to unreproducible.
The action with the button not activating is a feature.
Using the Form FvwmForm-Defaults, you can change buttons
so they activate on a press.

I could not reproduce the button with two labels.

If you have questions about this, respond to fvwm-workers.

Bug report:

Full_Name: Sergey Prohorenko
Version: 2.5.7
CVS_Date: 
OS: Debian Unstable
X_Server: x-window-system_4.2.1-12.1
Submission from: (NULL) (212.44.95.112)


The form is called using:
*FvwmButtons(1x1, Title Logout, Icon 48x48-gnome/window-destroy.xpm, Action
`Module FvwmForm FvwmForm-QuitVerify`) 
(Using modified Debian-blue setup from
http://themes.freshmeat.net/projects/debian-blue/?topic_id=929)

So, after QuitVerify form appears, I press any button (Logout for example)
with left mouse button and then, not releasing it, move mouse cursor
outside the form button. And when it returns to unpressed state, text on
it becomes distorted, as if the old one hasn't been cleared. That is, two
labels, one on top of the other, are displayed.
I did not test it with other FvwmForm forms/buttons.

fvwm 2.5.7 is self-compiled using hand-tuned debian build rules (just some
minor tweaking).

-- 
Dan Espen   E-mail: [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]


Fvwm bug 1135 keysym documentation, not a bug

2004-11-26 Thread Dan Espen

I've closed this problem as not a bug.


I found this comment in the keysymdef.h from the current Xorg release:


! The definitions here should match X11/XF86keysym.h
XF86AudioLowerVolume:1008FF11


Therefore I am closing this problem.  The header file should be
updated, not the Fvwm man page.


Date: Fri, 13 Feb 2004 03:37:32 -0600
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: XF86 custom keysyms are also usable

Full_Name: Emmanuel Thom..
Version: 2.4.x and 2.5.x
CVS_Date: 
OS: fedora core 1, kernel 2.6
X_Server: XFree86 4.3
Submission from: (NULL) (152.81.8.127)


Excerpt from the fvwm man page:

Key Keyname Context Modifiers Function
   [...]
   The Keyname is one of the entries from
/usr/include/X11/keysymdef.h,
   with the leading XK_ omitted.
   [...]

This is correct, but under XFree86, it turns out that the XF86
vendor-specific keysyms also work. These are defined in
/usr/include/X11/XF86keysym.h (or, as far as Xlib is concerned, in
/usr/X11R6/lib/X11/XKeysymDB). For example, I have successfully set up the
following binding:

Key XF86AudioLowerVolumeA A Function MMK AudioLowerVolume

This means that when you read along the lines of XF86keysym.h,
XF86XK_AudioLowerVolume should really be read as XF86AudioLowerVolume ; the
XK_ prefix isn't in XKeysymDB.

Of course, this is only possibly useful if the running X server does
generate such keysyms, which require some configuration work.

In short, I suggest augmenting the quoted sentence above by  the
following:

Under XFree86, you can also use any of the keysyms listed in
/usr/X11R6/lib/X11/XKeysymDB. You are responsible of having your X
server generating such events.

-- 
Dan Espen   E-mail: [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: System tray in FvwmTaskBar ?

2004-10-15 Thread Dan Espen
Gilles Foucault fvwm-workers@fvwm.org writes:
  On Thu, Oct 14, 2004 at 05:08:50PM -0400, Gilles Foucault wrote:
  Dear Fvwm hackers,
 
  I'd like to ask you if there is ongoing work about the implementation of
  the freedesktop.org's System tray (notification area) inside
  FvwmTaskBar:
  http://freedesktop.org/Standards/systemtray-spec
 
  Currently, nobody is doing much with the taskbar.  A patch would
  be welcome, though.
 
 I'd enjoy writing this hack using the code of peksystray
 (http://sourceforge.net/projects/peksystray).
 
 I should maybe get some knowledge about FVWM module writing and X
 programming. I already did some code with X/OpenMotif but I'm not an
 expert at X programming.
 
 Do you have any reference documentation to FVWM module programming
 (communication protocol, events)  ? and X programming ?

Start here:

http://www.fvwm.org/documentation/developers.php

The module interface section specifically.

-- 
Dan Espen   E-mail: [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: * Updated for 2.4.19.

2004-09-30 Thread Dan Espen

I've put the 2.4.19 announcement on Freshmeat.

I've posted announcements for 2.4.19 and 2.5.11
on news://comp.windows.x.apps.

Thanks Dominik.

-- 
Dan Espen   E-mail: [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: FVWM: Parsing window_flags in perl

2004-09-16 Thread Dan Espen
Mikhael Goikhman [EMAIL PROTECTED] writes:
 On 16 Sep 2004 15:11:56 -0400, Salvatore Domenick Desiano wrote:
  
  I reiterate the suggestion that this be done on module startup, rather
  than by file generation. Then, rather than adding a file to the
  distribution, you simply generate a set of M_CONFIG_INFO messages
 This is a good suggestion, but it adds more than 300 events to modules
 even if they are not interested in window flag bits.

I think that is too many messages.
The module should request the messages.
That is the only time the messages should be sent.

-- 
Dan Espen   E-mail: [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: Solaris Xinerama support

2004-08-26 Thread Dan Espen
Dominik Vogt [EMAIL PROTECTED] writes:
 Note that this nesting of AC_CHECK_LIB calls did not work with my
 autoconf/automake versions.  I have split it in two separate
 calls.

Darn.  And I tested this on Linux and Solaris.


I woke up in the middle of the night and it dawned on me that I never
updated NEWS.  I figured no one would notice and I could
take care of it when I got up.

-- 
Dan Espen   E-mail: [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: configure extra cflags?

2004-08-26 Thread Dan Espen
Chris Ross [EMAIL PROTECTED] writes:
 
Hey there.  I have a small problem, that will require
 changes to configure to solve.  On my Solaris machine,
 there are #pragma's in some of the openwin X headers
 that gcc (3.3.2) doesn't like.  This is easily solvable
 with -wunknown-pragmas, but if I put that in CFLAGS
 on the configure command-line environment, it will
 append -Wall, thus cancelling it out.
 
I thought it might be more useful to be able to
 put arbitrary things on the CFLAGS (and/or CPPFLAGS),
 but have them go after the -Wall.
 
Anyone else have any thoughts on this issue?

If I understand the question, I'd ifdef in the pragmas,
only when the sun compiler is being used.

-- 
Dan Espen   E-mail: [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: Solaris Xinerama support

2004-08-16 Thread Dan Espen
Chris Ross [EMAIL PROTECTED] writes:
 Dan Espen wrote:
  I guess I can answer my own question, it configures but doesn't
  compile:
  
  gcc -DHAVE_CONFIG_H -I. -I../../version-2_5_11/libs -I.. -I../../version-2_
 5_11 -I/opt/public/include  -I/usr/openwin/include  -I/opt/public/include
  -g -O2 -Wall -Wno-implicit-int -c ../../version-2_5_11/libs/FScreen.c
  ../../version-2_5_11/libs/FScreen.c:74: X11/extensions/xinerama.h: No such 
 file or directory
  
  You can send any additional patches to the list.
 
I'm not sure what to do to fix that.  I suppose there may
 be some way to check for the header in configure, and if
 it's not present (Solaris 7 11/99, or Solaris 8) I could
 just sub in the contents.  They're quite minimal.
 
This seem to objectionable to people?

I don't see any problem with Xinerama only working on only Sol 9 or later.
In other words, requiring the header.

Getting compile errors on a default configure on Sol 8 is no good.

-- 
Dan Espen   E-mail: [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: Solaris Xinerama support

2004-08-16 Thread Dan Espen
Chris Ross [EMAIL PROTECTED] writes:
 Dan Espen wrote:
  
  Didn't you say the Sol 9/10 header would work on Sol 8.
  Why not make the header required.  If someone wants Xinerama
  on Sol 8, make them supply the header.
 
It does, but it seems like having the xinerama support enabled
 with no user effort for Solaris 8 users would be worth having.
 You don't need to be an admin, or even very smart, to build
 a window manager.  Making sure you can put an extension somewhere
 and have auto-conf'd programs find them requires more of the
 user.
 
It only requires putting 4 lines in FScreen.c.  One #def,
 and three prototypes.  Actually, we're only using two of the
 functions, so we could take out the other prototype.

If the #define'd stuff is only used on Solaris, when the header
isn't there, and the library support is there,  I'd say that was
OK.

-- 
Dan Espen   E-mail: [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: Solaris Xinerama support

2004-08-15 Thread Dan Espen
Chris Ross [EMAIL PROTECTED] writes:
 Chris Ross wrote:
  
Okay.  I don't know how many of you know this, but Solaris ships
  an Xsun that has Xinerama support in it (as of the last dist.
  of Solaris 7).  *But*, in typical Sun Microsystems style, there
  is no Xinerama library, nor header file.
 
Oops.  I should've mentioned that this patch was tested
 with Solaris 8, but will only work on Solaris 8 with
 the X11/extensions/xinerama.h header copied from Solaris 9.
 Solaris' 9 and 10 ship with this header in place, so
 will work with no additional effort.

On my Solaris 8 machine without that header, I got:

With Xinerama multi-head support?   yes (Using Solaris Xinerama calls)

In what sense won't it work?

-- 
Dan Espen   E-mail: [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: Solaris Xinerama support

2004-08-15 Thread Dan Espen
Dan Espen [EMAIL PROTECTED] writes:
 Chris Ross [EMAIL PROTECTED] writes:
  Chris Ross wrote:
   
 Okay.  I don't know how many of you know this, but Solaris ships
   an Xsun that has Xinerama support in it (as of the last dist.
   of Solaris 7).  *But*, in typical Sun Microsystems style, there
   is no Xinerama library, nor header file.
  
 Oops.  I should've mentioned that this patch was tested
  with Solaris 8, but will only work on Solaris 8 with
  the X11/extensions/xinerama.h header copied from Solaris 9.
  Solaris' 9 and 10 ship with this header in place, so
  will work with no additional effort.
 
 On my Solaris 8 machine without that header, I got:
 
 With Xinerama multi-head support?   yes (Using Solaris Xinerama calls)
 
 In what sense won't it work?

I guess I can answer my own question, it configures but doesn't
compile:

gcc -DHAVE_CONFIG_H -I. -I../../version-2_5_11/libs -I.. -I../../version-2_5_11 
-I/opt/public/include  -I/usr/openwin/include  -I/opt/public/include -g 
-O2 -Wall -Wno-implicit-int -c ../../version-2_5_11/libs/FScreen.c
../../version-2_5_11/libs/FScreen.c:74: X11/extensions/xinerama.h: No such file 
or directory

You can send any additional patches to the list.

-- 
Dan Espen   E-mail: [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: matchVersion() compile problems

2004-07-11 Thread Dan Espen
Dominik Vogt [EMAIL PROTECTED] writes:
 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.
   =20
 if (1)
 {
   foo;
 }
   =20
   not
   =20
 if (1)
   foo;
...
  From docs/CONVENTIONS:
 
   o Always place curly braces on a separate line.  In some cases,
 placing braces on the same line as other code confuses
 (x)emacs.
 
  Wouldn't it be prudent to fix Emacs?
 
 The question is:  who is going to do it?  I don't know how to fix
 it.  One case in which xemacs misbehaves is when you have such a
 function:
 
   void foo(void) {
 ...
   }
 
 If you press C-x 4 a to generate a ChangeLog entry, it does not
 find the function's name.

So thats why a few things I try to do in Emacs don't work.
The underlying brokenness is in beginning-of-defun which is
widely used, for example, by C-x 4 a.
Emacs often has to go back to the beginning of
the function to figure out what it is looking at.

The default pattern for beginning-of_defun is to just look for
{ in the first column.  That can be overridden by setting
defun-prompt-regexp but my few attempts were failures.

I see this is a known issue, and after reading this:

http://w3.pppl.gov/info/ccmode/Performance_Issues.html

I'm pretty much convinced that the curly brace in column 1 for
functions is an Emacs requirement.

-- 
Dan Espen   E-mail: [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: matchVersion() compile problems

2004-07-10 Thread Dan Espen
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 behind this? I must confess I'm not particularly fond
  of this restriction but I will, of course, follow any FVWM coding standards
 .
 
  o Always place curly braces on a separate line.  In some cases,
placing braces on the same line as other code confuses
(x)emacs.
 
 Wouldn't it be prudent to fix Emacs?
 
 (That's an honest question, not trying to start an xemacs-vs-gvim war.)

I don't think Emacs has anything to do with it.
As far as I can tell, Emacs has no problems with either format.
Certainly someone would submit a bug report if there was a problem.

I think the above choices are personal preference.
Personally, I like curly braces to NOT take an extra line.
There are sound arguments to be made on both sides.

This is what I put in my .emacs to allow Emacs to follow the
fvwm standard for fvwm work, and for me to use my own rules for
everything else:

;set my defaults for c
(defun my-c-mode-hook ()
  (if (string-match fvwm buffer-file-name) ;fvwm project settings:
  (progn
(setq
 c-indent-level 8
 c-basic-offset 8
 c-brace-offset 0
 c-continued-brace-offset 0
 c-brace-imaginary-offset 0
 c-continued-statement-offset 0
 c-label-offset 0
 c-argdecl-indent 0
 c-auto-newline nil
 c-tab-always-indent t
 indent-tabs-mode t)
 (c-set-offset 'substatement-open 0))
;; Local site default settings
(setq 
 c-indent-level 2
 c-basic-offset 2
 c-brace-offset 0
 c-continued-brace-offset 0
 c-brace-imaginary-offset 0
 c-continued-statement-offset 2
 c-label-offset -2
 c-argdecl-indent 0
 c-auto-newline nil
 c-tab-always-indent t
 indent-tabs-mode nil
 comment-column 40)))
(add-hook 'c-mode-hook 'my-c-mode-hook t)


-- 
Dan Espen   E-mail: [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: fvwm-bug account (Was: TODO 2.6)

2004-06-27 Thread Dan Espen
Scott Smedley [EMAIL PROTECTED] writes:
 
  You may go to http://www.fvwm.org/cgi-bin/fvwm-bug.private (password
  needed) and manage bugs.
 
 Username 'scott'  my CVS password don't appear to work.
 
 Who should I see about this? Jason?

You don't appear in the pull down list of people with access.
I think you need Jason to add you.

-- 
Dan Espen   E-mail: [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: Proposal: new default config

2004-06-21 Thread Dan Espen
Scott Smedley [EMAIL PROTECTED] writes:
 I guess I'm trying to guard against this situation:
 
 Newbie tries FVWM for the first time. Starts it up. YUK!. (never
 uses FVWM again)
 
 Maybe it doesn't happen as much as I think it does.

If you start fvwm without a config, you should end up finding the menu
that lets you choose a starting config.  Right now, that will lead you to the
Setup Form of the Setup Script.  From there you make choices about
the setup you want.

-- 
Dan Espen   E-mail: [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: Proposal: new default config

2004-06-21 Thread Dan Espen
Dan Espen [EMAIL PROTECTED] writes:
 Scott Smedley [EMAIL PROTECTED] writes:
  I guess I'm trying to guard against this situation:
  
  Newbie tries FVWM for the first time. Starts it up. YUK!. (never
  uses FVWM again)
  
  Maybe it doesn't happen as much as I think it does.
 
 If you start fvwm without a config, you should end up finding the menu
 that lets you choose a starting config.  Right now, that will lead you to the
 Setup Form of the Setup Script.  From there you make choices about
 ^^ or
 the setup you want.

-- 
Dan Espen   E-mail: [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 write access for Scott?

2004-06-03 Thread Dan Espen
Dominik Vogt [EMAIL PROTECTED] writes:
 I think we should give CVS write access to Scott.  Anybody to
 second that opinion?

Mikhael proposed this on 31-May so you've just seconded it.

-- 
Dan Espen   E-mail: [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]


Remove FvwmTheme?

2004-05-31 Thread Dan Espen
FVWM CVS fvwm-workers@fvwm.org writes:
 * fvwm/fvwm.1.in (COLORSETS): Moved FvwmTheme description of colorsets
 into fvwm man page.

Any reason why the FvwmTheme module should not be completely
removed?

-- 
Dan Espen   E-mail: [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: PATCH: New style, CenterPlacement. This patch is as complete as I can make it.

2004-05-27 Thread Dan Espen
Francis Litterio [EMAIL PROTECTED] writes:
 
 --=-=-=
 
 Per Dan's request that I submit a complete patch, I've updated my recent
 CenterPlacement patch to be as complete as I can make it.  The attached
 file contains changes to these files:
 
   AUTHORS
   ChangeLog
   NEWS
   fvwm/fvwm.1.in
   fvwm/fvwm.h
   fvwm/placement.c
   fvwm/style.c
   sample.fvwmrc/system.fvwm2rc-sample-1
 
 I was unable to figure out how to write a test for the CenterPlacement
 style, so I didn't change tests/purify/purify.fvwm2rc.


I'll take a close look at the patch, probably this weekend.
For the purify.fvm2rc, all that is needed is an invocation of
the command.  We run that file under a debugger that checks
for memory leaks and uninitialized variables.  No need to resubmit
for that, I'll take care of it.

I've been wondering if CenterPlacement isn't a special case of something
else, like TopCenterPlacement or UpperRightCornerPlacement but so far,
no useful insight has come to me so I think this is OK.


-- 
Dan Espen   E-mail: [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: Patch: New style, CenterPlacement, places new windows in center of screen

2004-05-26 Thread Dan Espen
Francis Litterio [EMAIL PROTECTED] writes:
 This is the first time I've ever submitted a patch to FVWM, so if I've
 missed something, please let me know.

Patches should be complete.

Missing from this patch are updates to:

 fvwm/fvwm.1.in
 AUTHORS
 NEWS
 ChangeLog

For extra credit, update:

 sample.fvwmrc/system.fvwm2rc-sample-1 Line 56 to use CenterPlacement
 tests/purify/purify.fvwm2rc to add centerplacement test(s)


I'd like to see centerplacement added, if none of the other
developers object, I might apply the patch.  Preferably a complete
patch...

-- 
Dan Espen   E-mail: [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: zh_CN translation wanted

2004-05-21 Thread Dan Espen
Funda Wang [EMAIL PROTECTED] writes:
 Hello,
 
 I'm a member of I18n/zh_CN team, while we had done a lot of work on GNU
 soft/KDE/GNOME. We're now want to get fvwm localized to zh_CN. If it is
 possible, it would be better that issue a cvs account for me.
 
 We'll maintain our works through a web interface, which is located at
 i18n.ricetons.com.

You may send patches.  I don't know if someone will commit them.

Why is the web interface you mention, http://i18n.ricetons.com,
password protected?

-- 
Dan Espen   E-mail: [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 server

2004-05-08 Thread Dan Espen
Marcus Lundblad [EMAIL PROTECTED] writes:
 What's up with the CVS server?
 I keep getting:
 Message: cvs [update aborted]: recv() from server cvs.fvwm.org:
 Connection timed out
 When checking out from CVS

Install a more recent version of CVS.

 Is it just me?

Nope.

-- 
Dan Espen   E-mail: [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: wm

2004-04-28 Thread Dan Espen
Philip Lewis [EMAIL PROTECTED] writes:
 I can't find any docs about changing wm's. I get an error message
 that says another WM is Running when i try to launch fvwm2.

Possibly question 2.7 in the FAQ will help:

http://www.fvwm.org/documentation/faq/#2.7

For what you tried to do above, this would work:

fvwm -replace

-- 
Dan Espen   E-mail: [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: Help

2004-04-28 Thread Dan Espen
[EMAIL PROTECTED] writes:
 Hi,
 
 I have some problem with my fvwm95 in fedora core, the description is:
 
 /usr/X11R6/lib/X11/fvwm95//FvwmTaskBar: can`t load library `libXpm.so.4`
 
 This library is in /usr/X11R6/lib/libXpm.so.4, the same happend with the othe
 r modules: FvwmButtons, because of that this doesn`t work..
 
 Thanks for your help... what i can do??

This list does not support fvwm95.

Fvwm95 is a fork.  My advice is to use Fvwm instead.  Fvwm does a good
fvwm95 imitation.  See also fvwm-themes.

You've got some kind of LD_LIBRARY_PATH or -rpath issue.

-- 
Dan Espen   E-mail: [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: FVWM: debian

2004-04-16 Thread Dan Espen
Glaser, Ben I [EMAIL PROTECTED] writes:
 I'm trying to install on Solaris 8.  I get the following when running a
 make.
 
 make: Fatal error in reader: Makefile, line 333: Badly formed macro
 assignment
 Current working directory /var/tmp/fvwm-2.5.10/debian
 *** Error code 1
 make: Fatal error: Command failed for target `install-recursive'
 
 Any ideas?

The Makefile in the debian directory is broken.
You can avoid it by changing the Makefile in the top directory.
Remove debian from the list assigned to SUBDIR.


At least these 2 lines in debian/Makefile.am are gnumake only:

arch ?= $(shell dpkg-architecture -qDEB_BUILD_ARCH)
fullinstdir ?= $(shell cd $(top_srcdir)  pwd)/$(instdir)

-- 
Dan Espen   E-mail: [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: FVWM: debian

2004-04-16 Thread Dan Espen
Dan Espen [EMAIL PROTECTED] writes:
 Glaser, Ben I [EMAIL PROTECTED] writes:
  I'm trying to install on Solaris 8.  I get the following when running a
  make.
  
  make: Fatal error in reader: Makefile, line 333: Badly formed macro
  assignment
  Current working directory /var/tmp/fvwm-2.5.10/debian
  *** Error code 1
  make: Fatal error: Command failed for target `install-recursive'
  
  Any ideas?
 
 The Makefile in the debian directory is broken.
 You can avoid it by changing the Makefile in the top directory.
 Remove debian from the list assigned to SUBDIR.
 
 
 At least these 2 lines in debian/Makefile.am are gnumake only:
 
 arch ?= $(shell dpkg-architecture -qDEB_BUILD_ARCH)
 fullinstdir ?= $(shell cd $(top_srcdir)  pwd)/$(instdir)

Since I don't have a debian system I'll let someone else
fix this.  It looks like '=' and backticks will work.

In the future, before we create a release, ask me and I'll
try a build on Solaris with Sun's make and cc.  I can do AIX
and HP too, but my guess is just Solaris will handle most of
these problems.

-- 
Dan Espen   E-mail: [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]


cvs down

2004-03-27 Thread Dan Espen

Good morning Jason:

cvs update
cvs [update aborted]: recv() from server cvs.fvwm.org: Connection timed out


-- 
Dan Espen   E-mail: [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 down

2004-03-27 Thread Dan Espen
Jason L Tibbitts III [EMAIL PROTECTED] writes:
  DE == Dan Espen [EMAIL PROTECTED] writes:
 
 DE cvs update cvs [update aborted]: recv() from server cvs.fvwm.org:
 DE Connection timed out
 
 Not sure why; everything seems fine from work and from home.  I see
 that connections have been coming in from various places without
 interruption pretty much as far back as I have logs.

I'm not getting in from home or work.

Is this the right IP addr:

dane-2.cc ping cvs.fvwm.org
PING util1.math.uh.edu (129.7.128.22) from 128.96.196.27 : 56(84) bytes of data.

(Can't seem to ping it either.)

-- 
Dan Espen   E-mail: [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 down

2004-03-27 Thread Dan Espen
Jason L Tibbitts III [EMAIL PROTECTED] writes:
  DE == Dan Espen [EMAIL PROTECTED] writes:
 
 DE I'm not getting in from home or work.
 
 Can you traceroute?  (Note the next-to-last hop is supposed to be
 null; the router is not on the public Internet.)


From work with the internal stuff removed:

dane-2.cc traceroute cvs.fvwm.org
 6  s2-0-10.hsa1.nwr1.bbnplanet.net (64.156.0.5)  4.968 ms  4.996 ms  4.875 ms
 7  so-5-2-0.bbr1.NewYork1.Level3.net (4.68.113.45)  5.578 ms  5.601 ms  5.168 
ms
 8  ge-2-0.core2.NewYork1.Level3.net (64.159.17.6)  5.533 ms  12.701 ms  5.457 
ms
 9  oc12.Level3.nycmny01.us.bb.verio.net (209.244.160.150)  6.182 ms  5.629 ms  
5.475 ms
10  p16-1-1-0.r21.nycmny01.us.bb.verio.net (129.250.3.48)  5.776 ms  5.966 ms  
5.978 ms
11  p16-1-0-1.r21.asbnva01.us.bb.verio.net (129.250.5.99)  13.023 ms  12.400 ms 
 11.874 ms
12  p64-0-0-0.r20.asbnva01.us.bb.verio.net (129.250.2.34)  17.087 ms  12.197 ms 
 12.023 ms
13  p16-0-0-0.r00.atlnga03.us.bb.verio.net (129.250.2.49)  48.716 ms  48.763 ms 
p16-0-1-1.r21.dllstx09.us.bb.verio.net (129.250.5.34)  44.056 ms
14  p16-2-0-0.r01.atlnga03.us.bb.verio.net (129.250.5.17)  48.589 ms 
p16-6-0-0.r02.hstntx01.us.bb.verio.net (129.250.5.101)  50.374 ms  50.270 ms
15  p16-1-0-2.r20.dllstx09.us.bb.verio.net (129.250.4.194)  48.327 ms 
ge-0-2-0.a03.hstntx01.us.ra.verio.net (129.250.29.89)  51.526 ms 
p16-1-0-2.r20.dllstx09.us.bb.verio.net (129.250.4.194)  48.162 ms
16  p16-5-0-0.r02.hstntx01.us.bb.verio.net (129.250.5.41)  54.796 ms 
a1-1-2-0-2.a03.hstntx01.us.ce.verio.net (128.241.11.50)  52.428 ms 
p16-5-0-0.r02.hstntx01.us.bb.verio.net (129.250.5.41)  54.033 ms
17  vespasian-vlan10.gw.uh.edu (129.7.254.254)  56.439 ms  53.569 ms 
ge-0-2-0.a03.hstntx01.us.ra.verio.net (129.250.29.89)  53.575 ms
18  * a1-1-2-0-2.a03.hstntx01.us.ce.verio.net (128.241.11.50)  58.992 ms *
19  vespasian-vlan10.gw.uh.edu (129.7.254.254)  61.755 ms util1.math.uh.edu 
(129.7.128.22)  51.958 ms vespasian-vlan10.gw.uh.edu (129.7.254.254)  54.865 ms

-- 
Dan Espen   E-mail: [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 down

2004-03-27 Thread Dan Espen
Jason L Tibbitts III [EMAIL PROTECTED] writes:
  DE == Dan Espen [EMAIL PROTECTED] writes:
 
  From work with the internal stuff removed:
 
 Your traceroute output looks weird to me, but it seems that you're
 reaching the site OK.  Which means I'm confused; there aren't any
 restrictions on the server with regards to which addresses can
 connect, and the logs show continued connections from various places.
 
 I suppose you could run nmap against 129.7.128.22 to see if you can
 reach any ports there.

From home:

home nmap 129.7.128.22

Starting nmap V. 2.54BETA22 ( www.insecure.org/nmap/ )
Interesting ports on util1.math.uh.edu (129.7.128.22):
(The 1512 ports scanned but not shown below are in state: closed)
Port   State   Service
21/tcp openftp 
22/tcp openssh 
25/tcp opensmtp
53/tcp opendomain  
79/tcp openfinger  
80/tcp openhttp
111/tcpopensunrpc  
135/tcpfilteredloc-srv 
136/tcpfilteredprofile 
137/tcpfilterednetbios-ns  
138/tcpfilterednetbios-dgm 
139/tcpfilterednetbios-ssn 
194/tcpfilteredirc 
445/tcpfilteredmicrosoft-ds
707/tcpfilteredunknown 
873/tcpopenrsync   
974/tcpopenunknown 
991/tcpopenunknown 
994/tcpfilteredircs
1013/tcp   openunknown 
1433/tcp   filteredms-sql-s
1434/tcp   filteredms-sql-m
1723/tcp   openpptp
2003/tcp   opencfingerd
2048/tcp   filtereddls-monitor 
2401/tcp   opencvspserver  
3306/tcp   openmysql   
6699/tcp   filterednapster 
/tcp   filteredsun-answerbook  
32771/tcp  opensometimes-rpc5  


Nmap run completed -- 1 IP address (1 host up) scanned in 76 seconds


I see the cvspserver port 2401 is open.
I tried to telnet to that port, but so far it's hanging
just like it does when I try CVS.

-- 
Dan Espen   E-mail: [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 down

2004-03-27 Thread Dan Espen
Jason L Tibbitts III [EMAIL PROTECTED] writes:
  DE == Dan Espen [EMAIL PROTECTED] writes:
 
 DE I see the cvspserver port 2401 is open. I tried to telnet to that
 DE port, but so far it's hanging just like it does when I try CVS.
 
 Still can't find anything wrong; just did another full checkout from
 yet another location and it went fine.  There are no hung CVS
 processes on the server and no error messages in any logs.  Other
 users seem to be connecting fine.  Nothing has changed on the server
 recently that would cause problems.

Just tried from my Solaris machine at work.
Works fine from there.

Just checked my home and work Linux machines, same problem.

 If anyone else is having problems, please speak up.

Think I'll go do some RW stuff.

-- 
Dan Espen   E-mail: [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 down

2004-03-27 Thread Dan Espen
Jason L Tibbitts III [EMAIL PROTECTED] writes:
  DE == Dan Espen [EMAIL PROTECTED] writes:
 
 DE Just checked my home and work Linux machines, same problem.
 
 Do the Linux machines share a common CVS version?  The server is
 running 1.11.1p1 plus security patches.  This hasn't changed since the
 last CVS security hole.  My home machine is running 1.11.2, but I also
 checked 1.11.5 and it works fine as well.  A long time ago we had a
 problem with the version of CVS on the server causing client hangs but
 that was resolved, and in any case the versions on the server haven't
 changed so this has got to be either a networking or client issue.

The linux machines are both 1.11.1p1.
The solaris machine is 1.10.

I just strace/trussed both of them and they both do this:

connect(3, {sin_family=AF_INET, sin_port=htons(2401), 
sin_addr=inet_addr(129.7.128.22)}}, 16) = 0
send(3, BEGIN AUTH REQUEST\n, 19, 0)  = 19
send(3, /home/cvs/fvwm, 14, 0)= 14
send(3, \n, 1, 0) = 1
send(3, dane, 4, 0)   = 4
send(3, \n, 1, 0) = 1
send(3, XXX, 7, 0)= 7
send(3, \n, 1, 0) = 1
send(3, END AUTH REQUEST\n, 17, 0)= 17
recv(3, 0xb57b, 1, 0)   = -1 ETIMEDOUT (Connection timed out)


6187:   connect(3, 0xFFBED368, 16, 1)   = 0
6187:   send(3, 0x001345D8, 19, 0)  = 19
6187:  B E G I N   A U T H   R E Q U E S T\n
6187:   send(3, 0x0013D933, 14, 0)  = 14
6187:  / h o m e / c v s / f v w m
6187:   send(3, \n, 1, 0) = 1
6187:   send(3,  d a n e, 4, 0)   = 4
6187:   send(3, \n, 1, 0) = 1
6187:   send(3,  X X X X X X X, 7, 0) = 7
6187:   send(3, \n, 1, 0) = 1
6187:   send(3, 0x001345EC, 17, 0)  = 17
6187:  E N D   A U T H   R E Q U E S T\n
6187:   recv(3,  I, 1, 0) = 1
6187:   recv(3,   , 1, 0) = 1
6187:   recv(3,  L, 1, 0) = 1
6187:   recv(3,  O, 1, 0) = 1
6187:   recv(3,  V, 1, 0) = 1
6187:   recv(3,  E, 1, 0) = 1
6187:   recv(3,   , 1, 0) = 1
6187:   recv(3,  Y, 1, 0) = 1
6187:   recv(3,  O, 1, 0) = 1
6187:   recv(3,  U, 1, 0) = 1
6187:   recv(3, \n, 1, 0) = 1

Interesting, who knew that's the way the CVS server responds. 
Obviously I replaced the encrypted password, but they were the
same.

 Also check /proc/sys/net/ipv4/tcp_ecn; make sure it's off.

I don't know what that is but here it is:

home cat /proc/sys/net/ipv4/tcp_ecn 
0


I'll see about changing the cvs version I'm using later but
it doesn't look like that's the problem to me.

-- 
Dan Espen   E-mail: [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: fvwm-2.4.18 and fvwm-2.5.10 have been released

2004-03-23 Thread Dan Espen
Jason L Tibbitts III [EMAIL PROTECTED] writes:
  OC == Olivier Chapuis [EMAIL PROTECTED] writes:
 
 OC It seems that the fvwm-2.4.18 release has not been announced (fvwm
 OC users list and freshmeat).
 
 A message was sent to fvwm-announce on March 19 at 10:55AM CST.  The
 message ID was [EMAIL PROTECTED].  The subject
 was fvwm 2.4.18.  I received it back from the list.  fvwm 2.5.10 was
 announced in the same manner at essentially the same time.

Sorry, I won't be able to get to freshmeat for a while.
Hopefully tonight.

-- 
Dan Espen   E-mail: [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: fvwm-2.4.18 and fvwm-2.5.10 have been released

2004-03-23 Thread Dan Espen
Dan Espen [EMAIL PROTECTED] writes:
 Jason L Tibbitts III [EMAIL PROTECTED] writes:
   OC == Olivier Chapuis [EMAIL PROTECTED] writes:
  
  OC It seems that the fvwm-2.4.18 release has not been announced (fvwm
  OC users list and freshmeat).
  
  A message was sent to fvwm-announce on March 19 at 10:55AM CST.  The
  message ID was [EMAIL PROTECTED].  The subject
  was fvwm 2.4.18.  I received it back from the list.  fvwm 2.5.10 was
  announced in the same manner at essentially the same time.
 
 Sorry, I won't be able to get to freshmeat for a while.
 Hopefully tonight.

Done.

-- 
Dan Espen   E-mail: [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: Solaris 8 and Iconv

2004-03-08 Thread Dan Espen
Marcus Lundblad [EMAIL PROTECTED] writes:
  Markus can you check that all the new (vs 2.5.7) text conversion
  stuff are not used too often?
 
 
 I removed some redundant calls.
 Actually for example when drawing underlines, the width (in pixels) of one
 character is computed. In this case, if the character consists of one byte
 (ISO-8859-x) I make the assumption that the width is equal to the raw
 character corresponding to that byte. This will work exept for ISO-8859-6
 (8-bit Arabic) which we don't support anyway (this would need joining
 characters using UTF-8 internally).
 I also included a check in the drawing routine so that character positions
 is only computed when combining characters are actually present in the
 string (redundant otherwise).
 
 Could somebody try this out in Solaris 8?

It's definitely faster.
The menus come up blank and the text appears 1/4 second later.
On larger menus, I can see the text appear in blocks.

If I had to use a Solaris system, I would still want to disable iconv.

-- 
Dan Espen   E-mail: [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: Solaris 8 and Iconv

2004-03-08 Thread Dan Espen
Marcus Lundblad [EMAIL PROTECTED] writes:
 On Mon, 8 Mar 2004, Dan Espen wrote:
 
  Marcus Lundblad [EMAIL PROTECTED] writes:
Markus can you check that all the new (vs 2.5.7) text conversion
stuff are not used too often?
   
  
   I removed some redundant calls.
   Could somebody try this out in Solaris 8?
 
  It's definitely faster.
  The menus come up blank and the text appears 1/4 second later.
  On larger menus, I can see the text appear in blocks.
 
 How about using UTF-8 locale on Solaris 8?

I went back to the console prompt, then did:

export LANG=en_US.UTF-8

then I started up xwindows and fvwm.
I didn't see any speed difference.

The Ultra 5 that I have is 270MHz with 128Meg.

-- 
Dan Espen   E-mail: [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: Solaris 8 and Iconv

2004-03-05 Thread Dan Espen
Marcus Lundblad [EMAIL PROTECTED] writes:
  Markus can you check that all the new (vs 2.5.7) text conversion
  stuff are not used too often?
 
 
 I removed some redundant calls.
 Actually for example when drawing underlines, the width (in pixels) of one
 character is computed. In this case, if the character consists of one byte
 (ISO-8859-x) I make the assumption that the width is equal to the raw
 character corresponding to that byte. This will work exept for ISO-8859-6
 (8-bit Arabic) which we don't support anyway (this would need joining
 characters using UTF-8 internally).
 I also included a check in the drawing routine so that character positions
 is only computed when combining characters are actually present in the
 string (redundant otherwise).
 
 Could somebody try this out in Solaris 8?

Not before monday for me.

-- 
Dan Espen   E-mail: [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: Titlebar text templates

2004-03-03 Thread Dan Espen
Mikhael Goikhman [EMAIL PROTECTED] writes:
 On 03 Mar 2004 19:44:54 +0100, Arne Georg Gleditsch wrote:
  
  * Mikhael Goikhman
   With my suggestion you don't need to modify FvwmWindow structure.
  
   The suggested WindowNameFormat may be either a global command or a style
   option, but not a window context command like yours. Then this format
   string would be stored either globally or in style structure.
  
   visible_name contains the final name after expansion just like now.
  
  Hm.  Perhaps I've been unclear.  I use this functionality to assign
  every window a different title suffix, where the contents of this
  suffix indicate which hotkey will bring focus to the window in
  question.  The hotkeys are assigned from a arbitrary range; at the
  moment I'm using the letters A..Z, and Win-A will bring focus to the
  window marked with the suffix [A].  This hotkey/enumerated id/suffix
  _is_ a window context property, and I can't see how to make the final
  visible_name contain this without storing it in the window context
  somehow.
 
 I think, this is pretty uncommon situation, to give unique name format
 to every window.

I think it is very common.
That's what the -name argument to xterm/rxvt is for.

To get the above behavior, I use a Perl/Gtk GUI to manage my list of
systems that I normally login to and assign the hotkeys.

-- 
Dan Espen   E-mail: [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: PATCH: window-specific key/mouse bindings

2004-03-02 Thread Dan Espen
Dominik Vogt fvwm-workers@fvwm.org writes:
 On Wed, Mar 03, 2004 at 01:03:03AM +1100, scott wrote:
  Hi Dominik,
  
   ... and possibly people connected to the X server by a phone line.
   What I'm worried about is the latency by grabbing or ungrabbing
   bindings over a slow connection.
  
  I assume you're talking about grabbing the X server whenever a new
  window is created to GrabWindowKey() for each applicable binding?
 
 No, I mean the underlying calls to XGrabKey()/XUngrabKey() in
 libs/bindings.c.  These calls require contacting the X server.  If
 you have lots of bindings that change and/or an application with a
 frequently changing title, this can be a problem.  I vaguely
 remember an old bug in that area that slowed down startup
 dramatically because of unnecessary grabs.

I believe that was around the time IgnoreModifiers was invented.
I was running Fvwm remotely over dialup with lots of key bindings
in my .fvwm2rc.

-- 
Dan Espen   E-mail: [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: disallow posting for non-members?

2004-02-23 Thread Dan Espen
Dominik Vogt fvwm-workers@fvwm.org writes:
 It is sad that I have to ask.  What do you think about allowing
 only members to post on the fvwm mailing lists in the future?  The
 amount of spam has got out of control.

I agree, it is very sad.

Since I applied the SA rule that I posted, nothing has gotten thru
here.

Requiring subscription is OK with me if it will help others.

-- 
Dan Espen   E-mail: [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: AutoReply: test

2004-02-04 Thread Dan Espen
[EMAIL PROTECTED] writes:
 
 
 Dear fvwm-workers@fvwm.org,
 
 This is an automated response to let you know that we have successfully
 received your e-mail with the subject test.
 
 You will be receiving a response from us shortly.

Jason,

  Personally I doubt we'll be able to deal with the millions
of variations on these auto-responses.  This virus will just have
to run its course.

  For my personal account I need auto-responses to come in but I am
giving them a couple of points:

body MY_AUTO_RESP /automated response/
describe MY_AUTO_RESP Auto Responder
score MY_AUTO_RESP 2

-- 
Dan Espen   E-mail: [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: is the iconv crash fixed?

2003-12-11 Thread Dan Espen
Marcus Lundblad [EMAIL PROTECTED] writes:
 
 
 On Thu, 11 Dec 2003, Dominik Vogt wrote:
 
  I remember we had a crash with Marcus' iconv patches a couple of
  weeks ago.  Has it been fixed?  I can't conclude that from the
  NEWS and the ChangeLog.
  
 I got the impression this was a problem the configure, and that it was
 fixed. Is the bug still in there?
 How can it be reproduced?

I was wondering why we hadn't heard from you...

all you need is  --disable-iconv

Then operate a menu.

Dominik's fix was to make --disable-iconv work.

-- 
Dan Espen   E-mail: [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: tear off menus

2003-10-21 Thread Dan Espen
Dominik Vogt fvwm-workers@fvwm.org writes:
 On Wed, Oct 15, 2003 at 09:12:09PM -0400, Dan Espen wrote:
  
  Anyone have any ideas about a syntax for disabling button 2 doing
  a menu tear off?
  
  It doesn't look like we have any comands for controlling button
  or key action on menus.
  
  It looks like context M (menu) could be used:
  
  Mouse 2 M N TearOff
  Mouse 2 M N -
  
  Key BackSpace M N TearOff
  Key BackSpace M N -
  
  But that would create a pretty substantial change in the menu code.
 
 Yes - as the menu code is unable to handle normal bindings.  I
 once made an attempt to make the menu code able to run
 concurrently to the normal event loop.  In the end I concluded
 that it's better to dump fvwm and write something new.

Is something like this too brutal for your tastes:



menu.patch
Description: Binary data

-- 
Dan Espen   E-mail: [EMAIL PROTECTED]


Re: Download web page and snapshots

2003-10-20 Thread Dan Espen
Mikhael Goikhman [EMAIL PROTECTED] writes:
 On 20 Oct 2003 11:27:08 -0400, Dan Espen wrote:
  
  The web page has a link to alpha versions.
  This seems to be the 2.1.0 thru a 2.4.0 version.
  I don't think these files serve a useful purpose.
  Anyone disagree?
 
 Yes, the alpha link may be removed from the web.

Done.

Jason,

You may want to remove everything in:

/pub/fvwm/version-2/testing

I don't think there is anything using these files anymore.

-- 
Dan Espen   E-mail: [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]


tear off menus

2003-10-15 Thread Dan Espen

Anyone have any ideas about a syntax for disabling button 2 doing
a menu tear off?

It doesn't look like we have any comands for controlling button
or key action on menus.

It looks like context M (menu) could be used:

Mouse 2 M N TearOff
Mouse 2 M N -

Key BackSpace M N TearOff
Key BackSpace M N -

But that would create a pretty substantial change in the menu code.

-- 
Dan Espen   E-mail: [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 migo: * set the version to 2.4.18

2003-10-10 Thread Dan Espen
FVWM CVS fvwm-workers@fvwm.org writes:
 Log message:
 * set the version to 2.4.18

Freshmeat announcment done.

-- 
Dan Espen   E-mail: [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: vim and 2.5.7 crash

2003-09-20 Thread Dan Espen
Eduardo Alvarez [EMAIL PROTECTED] writes:
 
 --AqsLC8rIMeq19msA
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 
 As requested by Dan Espen, I am sending to you a core dump of fvwm 2.5.7
 which crashes when the following happens:
 
 I call 'aterm -name vim -e vim' either via a different aterm or by a
 keyboard shortcut, as so:
 
 Key v  A  SCM Exec exec aterm -name vim -e vim
 
 The interesting thing is, if I call it, then immediately quit, nothing
 happens.  However, if I  edit a buffer, whether I save it or not, fvwm
 crahses with a signal 11, dumping core.  It is noted that, if I open an
 aterm an THEN call vim, there's no problem.  Also, other applications
 called similarly (eg: aterm -name mutt -e mutt), cause no problem on exit.

I've installed aterm 0.4.2.

I started an aterm, then typed:

aterm -name vim -e vim xxx

That gave me a new window running vim.
I typed a few characters, then saved the file and exited with ZZ.

No problem.

I notice that aterm can be compiled with Afterstep support.
When I configured aterm, it didn't use that option.

I'm not sure if that would be shown with --help.  Here's what I get:

[EMAIL PROTECTED] tmp]$ aterm --help

Usage v0.4.2 :(XPM,transparency,no fading,NeXT scrollbar,.Xdefaults)
aterm [options] [-e command args]


As far as the stack dump showing meaningless information,
all I can suggest for that is to build fvwm yourself if you
haven't done that already.

-- 
Dan Espen   E-mail: [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]


  1   2   3   4   5   6   >