Thanks a lot, Kay!
I know different labs handle their operator accounts very differently,
but I would still have to be convinced that scrambling the workspace is
a reasonable option in any of these setups.
On 02.03.2012 16:06, Kasemir, Kay wrote:
> [...]
>
> In case your workspace _does_ get corrupted,
> in many cases all you need to do is:
> Delete the ".metadata" directory.
> All your files will still be there.
> What's lost is
> * the last window location - no big deal.
Unless you are on a 4-wide-screen console with ~10 windows open, each
showing a specific set of panels.
In that case: Yes big deal.
> * your preferences modifications
> - should also not be a big deal because ideally
> the product for your site has all essential settings
> "built in", or you use a -pluginCustomization file
> that has them, so end users don't need to bother
>
> with EPICS CA addr list, archive data sources, ...
You also lose the setup of all imported projects from shared locations,
linked directories, etc.
In my case, the workspace is practically empty except for ".metadata",
so the loss is almost complete.
Thanks again,
~Ralph
- Replies:
- Re: CSS workspace lock, prompt Re: BOY FAQ Kasemir, Kay
- References:
- CSS workspace lock, prompt Re: BOY FAQ Kasemir, Kay
- Navigate by Date:
- Prev:
CSS workspace lock, prompt Re: BOY FAQ Kasemir, Kay
- Next:
Re: CSS workspace lock, prompt Re: BOY FAQ Kasemir, Kay
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
<2012>
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
CSS workspace lock, prompt Re: BOY FAQ Kasemir, Kay
- Next:
Re: CSS workspace lock, prompt Re: BOY FAQ Kasemir, Kay
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
<2012>
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|