forked from enlightenment/enlightenment
in the case where an ANY context action exists and a SPECIFIC context action also exists for the exact same binding (eg. alt+click), the action which was added to the config first would be activated this is unreliable and confusing since it's impossible for users to determine the order without either manually examining the config or clearing all bindings and starting over, and this presupposes that the user is even aware of such an issue instead, now the most specific binding context will be chosen, with ANY used only as a fallback in the case where no other binding could be activated for a given scenario |
||
---|---|---|
config | ||
data | ||
doc | ||
m4 | ||
pkgbuild | ||
po | ||
src | ||
.arcconfig | ||
.gitignore | ||
.mailmap | ||
AUTHORS | ||
BUGS | ||
COPYING | ||
ChangeLog | ||
INSTALL | ||
Makefile.am | ||
NEWS | ||
README | ||
README.wayland | ||
autogen.sh | ||
configure.ac | ||
e19_workdir_setup.sh | ||
enlightenment.pc.in | ||
enlightenment.spec.in | ||
netwm.txt | ||
x-ui.sh | ||
xdebug.sh |
README
Please report bugs and send patches to phab.enlightenment.org Enlightenment 0.19.0 Requirements: ------------- Must: efl elementary libc libm libX11 libXext xcb xcb-shape xcb-keysyms Heavily suggested: evas_generic_loaders (all loaders) NOTE: Users of DR16 will need to rename the $prefix/bin/enlightenment file prior to installing DR19 or it will be overwritten. You can also use the configure --prefix option to put enlightenment in a separate tree of its own (recommended) like: ./configure --prefix=/usr/local/e19 You will, as usual, need to add the subsequent bin dir to your $PATH etc. NOTES: * if you do not want security issues make sure sysactions.conf is in /etc/enlightenment (not PREFIX/etc/enlightenment) as this is the first place it looks at. This file is intended to be customized by packagers and system integrators to match your policies and scripts/tools.