Re: Galeon 1.2.7 patch replacing --server with --resident

* Christophe Fergeau <[email protected]> [030120 10:33]:
> > 
> > I can see that.  But removing the possibility to exit galeon is also
> > bad.  Currently, galeon uses 90M of memory on my computer, I need a way
> > to shut it down.
> 
> you still have galeon --quit
> And that seems awkward to launch galeon with --resident and --server
> while wanting to quit it because it eats to much memory

Hehe... yes, I agree.  But I do believe there will be times when you need to
restart galeon.  Galeon will never be «perfect», and even if it is, plugins
may cause bugs themselves.

Thinking about it, I rarely quit Galeon.  If I do, it's either because I want
to free memory, upgrading plugins (I guess maybe I don't need to, will try 
next time) or because it starts behaving strangely (doesn't happen often).

I _do_ end up restarting Galeon often though, because of crashes.  And the
ability to recreate my last session is genious.  Having features that makes
crashes more acceptable is really nice (although it's more important to fix
them).

> > I believe the suggestion was to remove --server and replace it with --resident?
> > Or?  At least that makes most sense to me.
> 
> as I read the patch that was previously posted, it was keeping --server
> and adding --resident, but maybe I'm wrong

I didn't read the actual patch, you may be right, but we should probably try
to keep just one of them.

> I don't know if it handles upgrading plugins, I'd expect it to do so. To
> upgrade galeon, you obviously need to restart it, but I don't expect
> that to happen several times a day :)

Maybe if galeon development really takes off... ;)




Eivind


-------------------------------------------------------
This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your  SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en