WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: duplicate watchers  (Read 1953 times)

Offline N. Carigon

  • Newbie
  • *
  • Posts: 3
duplicate watchers
« on: October 14, 2009, 07:11:49 PM »
I apologize if this has already been brought up in the past (I can't seem to find it if it has).

Ever since watcher was pulled out of jwm as a separate extension, I get two watchers when I start up microcore with the jwm and watcher extensions. I believe this is due to the following line in /etc/skel/.xsession:

  [ $(which watcher) ] && watcher -g +0-0 &

which could instead be:

  [ $(which watcher) ] && [ -z $(which jwm) ] && watcher -g +0-0 &

Jwm swallows watcher within its configuration file already so the entry in .xsession is redundant (and ugly) when using jwm. Is this a change that could be added to the next TinyCore/MicroCore patch? Or I am just doing something wrong?

Offline roberts

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: duplicate watchers
« Reply #1 on: October 14, 2009, 07:26:40 PM »
Some of these "issues" boils down to personal settings.
Some may want watcher swallowed and some may not. Sawllowing takes up space that could be used for the display of other tasks.

I don't really want to try coding for every possbile window manger extension with the base scripts.
Nor should base scripts be expected too.

The scripts in your home directory should be available for your custom and additional settings.  We also have fluxbox, openbox, hackedbox, icewm, window makers, and still others.

The extensions should play nice with the OS and not the OS try to accomodate every possible window manager.

I would think it cleaner to remove or comment out the jwm swallow statement,
Letting the use decide to comment out .xsession and uncomment jwm swallow statement.
10+ Years Contributing to Linux Open Source Projects.

Offline N. Carigon

  • Newbie
  • *
  • Posts: 3
Re: duplicate watchers
« Reply #2 on: October 15, 2009, 01:36:09 AM »
Thank you for the explanation; I see your point and editing my profile's .xsession file is a good solution.

However, with that in mind, I think it would make more sense to completely remove the watcher line from .xsession and have each window manager handle it on their own. That way it shouldn't become an issue for anyone using a WM other than flwm and wouldn't require end users to edit files (unless they want to). Also, since watcher is no longer part of the base it doesn't seem like the base should contain watcher configuration lines.