(old)Puppy Linux Discussion Forum

Fvwm95 is very stable. For example (on my system) when I refresh with open programs the programs reappear. With JWM they close down.
That's not a property of JWM but how Barry choosed to set it up. He must have had a good reason.

To have a non destructive reset, you can uncomment this line in the original .jwmrc
<!-- <Restart label="xxx restart" icon="mini-windows.xpm"/> -->
(Of course you may want to change the label)

I can't remember now... there was a reason, I'm not sure, maybe with the
latest version of JWM it isn't a problem. JWM's restart didn't work properly before.

Maybe someone could experiment, find out if JWM's restart feature does
work properly now.

I think there was a bugfix out a short time, I think from toughjourney, and it worked.
Or I installed it from the jwm-homepage? Don't remember.

Just later it did not work, when I installed another bugfix.
Maybe GuestToo did not add that to his Bugfix.

But this is just a guess, I have so many versions around and edited .jwmrc manually, so I can't reproduce it.

Mark

i think someone (ok, it was Lobster) said he preferred the way Puppy 1.0.4 restarted JWM

<Restart label="JWM restart" icon="mini-windows.xpm"/>

Puppy 1.0.5 and 1.0.6 seems to restart JWM by killing X in a script ... the old way, X is not killed, and all the X apps keep running (i prefer this myself ... it is easy to restart or to switch from one wm to another without killing X)

this is what is in Puppy 1.0.6's jwmrc:

<Program label="JWM restart" icon="mini-windows.xpm">restartwm jwm</Program>

i did not put anything in my SP105 bugfix dotpup to change jwmrc because
1) it is not a bug ... it is a feature ... it is simply the way Barry chose to restart JWM
2) i don't like editing jwmrc with sed anyway, because it's easy to corrupt the file, and totally screw up jwm's configuration ... i also avoid editing the files in .package/ from a dotpup script for the same reason, it's very easy to corrupt pupget so that it won't even run

so you can choose to restart JWM by killing X or not ... but this is a design decision, not a bug

I see.
I think it should be default, that JWM restarts without killing X.
If you just install a dotpup, and want to see it in the menue, than it can be quite annoying to restart Mozilla and Dotpupdownloader and other programs again.

Greets, Mark

i prefer restarting wm's without killing X

i thought it was just a design decision, but maybe JWM's restart feature was buggy, and that was why Barry decided to do it the 'kill X' way

Yeah,
there was a bug report posted to Joe's forum about this.
<restart> did not work under certain conditions -- it did nothing at all.

It is probably fixed for v0.24.

Okay, I can't remember any other reason for wanting to kill X, so I'll try
using <restart>.

I just remembered one thing:
If you use the GTK theme selector and change to a different theme, using
<restart> to restart JWM does not change ROX to the new theme -- you have
to kill X.
-- but same for other w.m.'s anyway, so just tell people to quit X entirely
then restart it to apply new theme to ROX
-- okay, I can put that info into the GTK theme selector.