927e7b2796
This commit adds a way to leverage the xproperty and startup_id APIs to persist an execution token across restarts. It allows to use `awful.rules` on clients that were executed by a previous Awesome instance. The main limitations of these methods is the lack of entropy used to build the token. If the command is the same in multiple `awful.spawn.once`, then it will not work as expected. To mitigate this issue, the system try to concatenate the `awful.rules` table after the command and hash the resulting string. Given rules are a table, it can have loops and/or issues with keys ordering. The hash function sort and limite recursion to prevent a stack overflow. Another issue is the unreliability of startup notifications. |
||
|---|---|---|
| build-utils | ||
| common | ||
| docs | ||
| icons | ||
| lib | ||
| manpages | ||
| objects | ||
| spec | ||
| tests | ||
| themes | ||
| utils | ||
| .busted | ||
| .editorconfig | ||
| .gitignore | ||
| .luacheckrc | ||
| .luacov | ||
| .mergify.yml | ||
| .travis.yml | ||
| awesome-version-internal.h | ||
| awesome.c | ||
| awesome.desktop | ||
| awesome.h | ||
| awesomeConfig.cmake | ||
| awesomerc.lua | ||
| banning.c | ||
| banning.h | ||
| CMakeLists.txt | ||
| color.c | ||
| color.h | ||
| config.h | ||
| dbus.c | ||
| dbus.h | ||
| draw.c | ||
| draw.h | ||
| event.c | ||
| event.h | ||
| ewmh.c | ||
| ewmh.h | ||
| globalconf.h | ||
| ISSUE_TEMPLATE.md | ||
| keygrabber.c | ||
| keygrabber.h | ||
| LICENSE | ||
| luaa.c | ||
| luaa.h | ||
| Makefile | ||
| mouse.c | ||
| mouse.h | ||
| mousegrabber.c | ||
| mousegrabber.h | ||
| Packaging.cmake | ||
| property.c | ||
| property.h | ||
| README.md | ||
| 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
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
NOTE: Awesome uses cmake to build. In case you want to
pass arguments to cmake, please use the CMAKE_ARGS environment variable. For
instance:
CMAKE_ARGS="-DCMAKE_INSTALL_PREFIX=/opt/awesome" make
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.8.0
- 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
- xcb-util-xrm >= 1.0
- 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 >= 2.40 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 - asciidoctor for generating man pages
- gzip for compressing man pages
- ldoc >= 1.4.5 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- GTK+ >= 3.10 for
./themes/gtk/
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 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
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 https://awesomewm.org/apidoc/.
License
The project is licensed under GNU General Publice License v2 or later. You can read it online at (v2 or v3).