Michael Hughes wrote:
Morten
> e16 had its executable renamed to e16 to allow exactly this...
I think that this is new for 0.16.8. Is it possible to use this name
with 0.16.7? I have never found out where the initial value for
ECONFDIR is set. It looks like the executable has to be renamed to
"e16" as well. I wonder if there are not other conflicts. It looks
like a lot of the changes to 0.16.8 were made for this reason.
It should be possible to rename the e16 binary (any version) to whatever
you want.
If you want a non-default configuration directory use -econfdir (<16.8)
or -P/--econfdir (>= 16.8).
The primary reasons why it is recommended not to rename .enlightenment
to .e16 when switching to e16.8 is that cached theme/config files from
older versions may cause trouble, and that an old custom menus.cfg most
likely will not work without adjustments.
Almost all themes should be compatible with 16.8, also if there are
cusomized theme files in the user configuration directory. The
exceptions are that the theme files can no longer contain configuration
settings (I think I have seen one theme using this), and they can no
longer contain menu definitions, which would have to be removed or
moved/merged into a custom menus.cfg (I'm only aware of two themes doing
this, one being Ganymede which I have fixed up, and the other being
Aqua+clones which includes a menus.cfg in menustyles.cfg).
/Kim
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users
