bc75ef5689
When awesome calls any Lua code, it does so with a protected call. This means that any kind of Lua error should (there are exceptions) just result in an error message being printed and everything continuing as usual. When LGI calls Lua code, it uses a normal call. This means that in an asynchronous context, that is, when there is no more call generated by awesome's C code on the call stack, we must be careful, since any error results in Awesome's unprotected error handler to be called which restarts the WM. menubar.utils.parse_dir() asynchronously parses a directory containing .desktop files. This means that it is no longer in a protected call context. Let's assume that the code itself is fine. However, the callback that the caller provided for handling the results can be quite arbitrary. Make sure that it is run in a protected context. Helps-with: https://github.com/awesomeWM/awesome/issues/1173 Signed-off-by: Uli Schlachter <psychon@znc.in> |
||
|---|---|---|
| build-utils | ||
| common | ||
| docs | ||
| icons | ||
| lib | ||
| manpages | ||
| objects | ||
| spec | ||
| tests | ||
| themes | ||
| utils | ||
| .editorconfig | ||
| .gitignore | ||
| .luacheckrc | ||
| .luacov | ||
| .travis.yml | ||
| CMakeLists.txt | ||
| ISSUE_TEMPLATE.md | ||
| LICENSE | ||
| Makefile | ||
| Packaging.cmake | ||
| README.md | ||
| awesome-version-internal.h | ||
| awesome.c | ||
| awesome.desktop | ||
| awesome.h | ||
| awesomeConfig.cmake | ||
| awesomerc.lua | ||
| banning.c | ||
| banning.h | ||
| color.c | ||
| color.h | ||
| config.h | ||
| dbus.c | ||
| dbus.h | ||
| draw.c | ||
| draw.h | ||
| event.c | ||
| event.h | ||
| ewmh.c | ||
| ewmh.h | ||
| globalconf.h | ||
| keygrabber.c | ||
| keygrabber.h | ||
| luaa.c | ||
| luaa.h | ||
| mouse.c | ||
| mouse.h | ||
| mousegrabber.c | ||
| mousegrabber.h | ||
| property.c | ||
| property.h | ||
| root.c | ||
| selection.c | ||
| selection.h | ||
| spawn.c | ||
| spawn.h | ||
| stack.c | ||
| stack.h | ||
| strut.c | ||
| strut.h | ||
| systray.c | ||
| systray.h | ||
| xkb.c | ||
| xkb.h | ||
| xrdb.c | ||
| xrdb.h | ||
| xwindow.c | ||
| xwindow.h | ||
README.md
Readme
About awesome
awesome is a highly configurable, next generation framework window manager for X.
Building and installation
After extracting the dist tarball, run:
make
This will create a build directory, run cmake in it and build awesome.
After building is finished, you can either install via make install:
make install # you might need root permissions
or by auto-generating a .deb or .rpm package, for easy removal later on:
make package
sudo dpkg -i awesome-x.y.z.deb
# or
sudo rpm -Uvh awesome-x.y.z.rpm
Build dependencies
Awesome has the following dependencies (besides a more-or-less standard POSIX environment):
- CMake >= 3.0.0
- Lua >= 5.1.0 or LuaJIT
- LGI >= 0.7.1
- xproto >= 7.0.15
- libxcb >= 1.6 with support for the RandR, XTest, Xinerama, SHAPE and XKB extensions
- libxcb-cursor
- libxcb-util >= 0.3.8
- libxcb-keysyms >= 0.3.4
- libxcb-icccm >= 0.3.8
- libxkbcommon with X11 support enabled
- libstartup-notification >= 0.10
- cairo with support for XCB and GObject introspection
- Pango with support for Cairo and GObject introspection
- GLib with support for GObject introspection
- GIO with support for GObject introspection
- GdkPixbuf
- libX11 with xcb support
- Imagemagick's convert utility
- libxdg-basedir >= 1.0.0
Additionally, the following optional dependencies exist:
- DBus for DBus integration
and the
awesome-clientutility - asciidoc and xmlto for generating man pages
- gzip for compressing man pages
- ldoc for generating the documentation
- busted for running unit tests
- luacheck for static code analysis
- LuaCov for collecting code coverage information
- libexecinfo on systems where libc does not provide
backtrace_symbols()to generate slightly better backtraces on crashes XephyrorXvfbfor running integration tests
Running awesome
You can directly select awesome from your display manager. If not, you can
add the following line to your .xinitrc to start awesome using startx
or to .xsession to start awesome using your display manager:
exec awesome
In order to connect awesome to a specific display, make sure that
the DISPLAY environment variable is set correctly, e.g.:
DISPLAY=foo.bar:1 exec awesome
(This will start awesome on display :1 of the host foo.bar.)
Configuration
The configuration of awesome is done by creating a
$XDG_CONFIG_HOME/awesome/rc.lua file, typically ~/.config/awesome/rc.lua.
An example configuration named awesomerc.lua.in is provided in the source.
Troubleshooting
On most systems any message printed by awesome (including warnings and errors)
is written to ~/.xsession-errors.
If awesome does not start or the configuration file is not producing the desired results the user should examine this file to gain insight into the problem.
Debugging tips
You can call awesome with gdb like this:
DISPLAY=:2 gdb awesome
Then in gdb set any args and run it:
(gdb) set arg --replace
(gdb) run
Inside gdb you can use the following to print the current Lua stack traceback:
(gdb) print luaL_dostring(globalconf.L.real_L_dont_use_directly, "print(debug.traceback())")
Reporting issues
Please report any issues you may find on our bugtracker. You can submit pull requests on the github repository. Please read the contributing guide for any coding, documentation or patch guidelines.
Status
Documentation
Online documentation is available at http://awesome.naquadah.org/doc/ for the
stable branch and at http://awesomewm.github.io/apidoc/ for the master branch.
It can be built using make ldoc.
License
The project is licensed under GNU General Publice License v2 or later. You can read it online at (v2 or v3).