Igor Kolar wrote:
On 3/17/06, *Kim Woelders* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:
Look in /usr/share/e16/config/bindings.cfg.
Please, do not change these locations any more. I myself have had loads
of problems with it - and have found .e16 purely by chance. And now, it
is by NO means possible to copy the configuraction of my home pc
(./enlightenment) to my working pc. This makes me angry. Why the fuck
should I have to configure twice and in different formats?
All I can say is sorry about the inconvenience. Consider it the price of
having e16 maintained at all. Accept it, stick with version 0.16.7, use
e17, or go elsewhere.
I'll try to motivate various changes again:
- Binary name changed from enlightenment to e16.
This one should be obvious. The e17 binary name is also enlightenment.
If e16 should continue to exist the name had to be changed in order to
avoid endless amounts of confusion.
- Data install path changed from <datadir>/enlightenment to
<datadir>/e16 (<datapath> typically being /usr/share).
Again, e17 by default installs to <datadir>/enlightenment, so this had
to be changed.
- Default user config directory changed from ~/.enlightenment to ~/.e16.
Due to the changes in config files there is nothing in ~/.enlightenment
that e16.8 should use (except backgrounds/, themes/, and
epplet_config/). At best you would have a messy ~/.enlightenment
directory. At worst e16.8 would use incompatible custom user stuff from
earlier versions, causing weird problems and general unhappiness.
With this change it is also possible to have e16.7 and e16.8 coexisting
without trouble, and if ever it was decided that e17 should move to
~/.enlightenment in stead of ~/.e it would not be a problem either.
- New configuration settings files/format.
It was a major PITA to maintain the old way of doing things, supporting
people having trouble with it, and adding new features.
My alternatives were to run away screaming or change it.
I have no intentions of making further changes to installation paths or
file names.
I totally agree that it would be nice if e16.8 provided a script or
something to convert the old stuff. However, during the long period of
time (>1 year) where e16.8 was under development nobody bothered enough
to contribute a migration script. Since nobody bothered I saw no reason
to bother either.
Fwiw, I don't think I have missed many oportunities to warn about these
changes and to suggest reading README-0.16.8.
The change of package name from enlightenment to e16 should by itself be
a warning signal.
Is there a migration script, by the way?
Can I write it (fluent in perl, sed, bash ..) - where do I find the main
points?
Well, for starters...
Assuming you are using DISPLAY=:0 and screens S (S=0,1,...):
~/.enlightenment/...e_session-XXXXXX split/convert->
~/.e16/e_config--0.S.cfg # Configuration settings
~/.e16/e_config--0.S.backgrounds # Background definitions
~/.e16/e_config--0.S.buttons # Button definitions
~/.e16/e_config--0.S.ibox # Iconbox configurations
~/.e16/e_config.bindings # Keybindings set by e16keyedit
~/.enlightenment/...e_session-XXXXXX.snapshots.S ->
~/.e16/e_config--0.S.snapshots # Remembered settings
~/.enlightenment/...e_session-XXXXXX.groups.0 ->
~/.e16/e_config--0.S.groups # Group configurations
~/.enlightenment/keybindings.cfg (if exists) convert->
~/.e16/bindings.cfg # Mouse- and keybindings
~/.enlightenment/menus.cfg (if exists) convert->
~/.e16/menus.cfg # Custom menus
Some of the migration can be performed by trivial copying of (parts of)
old files to new files. The rest, particularly extracting/converting
stuff to generate e_config--0.S.cfg, e_config.bindings, bindings.cfg,
and menus.cfg, requires some parsing.
Then there are the menus which moved from ~/.enlightenment to
~/.e16/menus. This was done as suggested by somebody, and I still think
it's cleaner this way. However, this may have been a bad move since it
may cause major annoyance for users having custom stuff in there.
Hmm.. With a few changes it may be possible to make it less painful to
move the menu files...
I'd definitely be happy to include a migration script, and if you really
do intend to contribute I'll provide whatever additional information you
need :)
using e16keyedit.
Cool :)
~/.e16/e_config.bindings is loaded next, and will override settings
defined in bindings.cfg.
Dumbass idea to have a duplicate set of config files in the home dir.
What's ok is first look in home dir (one location) and then look into
/usr for defaults. A number of X apps have 3 or 4 config file locations
(xkb, gdm, ..), which makes it extremely difficult to find the offending
settings or put proper ones in place.
This is no different than in earlier e16 versions, which would first
read key AND button bindings from ~/.enlightenment/keybindings.cfg if
existing and otherwise fall back to the default
/usr/share/enlightenment/config/keybindings.cfg.
After that it would read any keybindings set by e16keyedit from
~/.enlightenment/...e_session-XXXXXX, overriding the ones found in
keybindings.cfg.
The latter bit has always been very confusing and there have been
countless questions about where these keybindings were hidden and how to
remove them.
But you are right. It would probably be better to save the modified
keybindings as well as the buttonbindings to ~/.e16/bindings.cfg.
I myself have a problem with the iconbox. I turn it off, but after
relogin, its back again (the snapshot windows aren't). Duplicate config
files might be the reason why. I'll look into it this afternoon, when I
get to work.
This is a bug in 0.16.8. It's fixed in 0.16.8.1 (CVS).
I intend to release 0.16.8.1 after the ongoing CVS move has been
completed, along with e16keyedit 0.3 (CVS) which should work with e16.8.
I love e, but am seriously considering swithing to flux or something
because of these problems ..
-i
:(
/Kim
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
enlightenment-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-users
