Re: workspace_state

• Messages sorted by: [ date ][ subject ][ author ]
• Next message: "Re: Why AS"
• Previous message: Darren Eckhoff "Re: Why AS"

On Fri, 13 Aug 1999, David Mihm wrote:

> On 13 Aug 1999, Christian B. Wiik wrote:
> 
> >[Frederick Bruckman <fb@enteract.com>]
> >| AFAIK, there are no session managers that do a perfect job of saving
> >| state. The nice thing about Afterstep is that .workspace_state is a
> >| shell script, which can be edited. I find it easy enough to twiddle it
> >| to do exactly what I want, and then lock it down with "chmod a-r". Of
> >| course it never changes unless I want it to. Works for me.
> >
> >In other words: I can empty the file and remove the read-rights? Wont
> >this produce some error messages?

Yes, it logs an error. So?

> 	While "locking the file down" will work, You can simply edit the
> autoexec file and have it not sh the script.

I guess I missed the point. Yes, if all he wants is an empty file, he
may as well disable it.



--
   WWW:   http://www.afterstep.org/
   FTP:   ftp://ftp.afterstep.org/
   MAIL:  http://www.calderasystems.com/linuxcenter/forums/afterstep.html

• Next message: "Re: Why AS"
• Previous message: Darren Eckhoff "Re: Why AS"