1. clear out environment as best is possible before executing
anything. especially PATH and IFS are set to minimal base defaults.
also use clearenv() if available and unsetenv()
2. remove gdb method as it's just too dangerous. run it as normal as
the user and if the kernel / distro dny that - then sorry. too bad.
this will shut coverty up (hopefully). it doesn't know that a re-exec
of the process will mean the code never gets out of the if ()...
unless the restart action is never found... and that never happens.
efreet still has lots of problems somewhere (unknown where) with
threaded use. it's just not safe even now. i'm seeing insanely
easy-to-reproduce issues every time i bring up a menu. since this is
unlikely to be solved in efreet before release, don't depend on efreet
being threadsafe and go back to the non-threaded code.
Revert "e: No need to check MINOR twice"
This reverts commit 97dd1d7486.
Revert "app menu parsing is now async with efreet 1.8"
This reverts commit 3989e54e21.
if someone were to ... replace the default theme... and would be missing
groups... in theory the min size calc may fail thus leaving min w/h
unset, so just set them anyway.
Before this commit, this would not always be the case.
I added a "scroll to cursor" for every change in entry size.
This is a further fix to T169. It's not exactly what described there,
but it's a similar issue I found while fixing it.
Somehow of a stage 2 for commit 80844cbcd7.
This also adds changelog and news entries, as this issue is now fully fixed.
Before this commit, setting the text of an entry after the entry
has already been placed and sized, would cause the inside entry
(the one inside of the scroller) size to be the size of the viewport
instead of the real size. This would make some parts of the entry
unreachable.
This fixes T169.
thise commit added focus_policy member to E_Border as something to be used for setting a per-window focus policy. setting it on each window is a huge pain if the global policy ever changes, so it's better to use this member only as an override for the global policy which can be checked to see if it's been set