-
Notifications
You must be signed in to change notification settings - Fork 0
1. Setup
Assembly may be required.
Before installing this configuration, you will need to have the dependencies installed or it will not work properly, while the names on your distribution are probably different the following is required to be present and on the path locally:
| blueman | bluetoothctl | upower | gettext | gom |
| i3lock-fancy | inotify-tools | kitty | libnotify | libpeas |
| light | lm_sensors | lua | lua-cjson | lua-lgi |
| lua-lpeg | luarocks | luasocket | mupdf | pamixer |
| rofi | ruby-asciidoctor | speedtest-cli | startup-tools | xautolock |
| xcb-util-cursor | xcb-util-keysyms | xclip | xsettingsd | awesome-luajit-git |
| xterm |
NOTE: I am using the awesome-luajit-git package from the AUR which I have also built (relatively easily) using the source repository, its a minor difference but yields an overall more repsonsive system in my experience and reloads slightly faster. You may be able to get away with using the Git version of AwesomeWM without the luajit build option enabled, but no promises if you do (or if you don't really)
As you can imagine, replace your current $HOME/.config/awesome directory with this repository (make a backup of your old one first please)
mv $HOME/.config/awesome $HOME/.config/awesome-backup
git clone https://github.com/the-Electric-Tantra-Linux/awesome/ $HOME/.config/awesome
Now to make sure you have the fonts you need, copy those included with this repo into the system directory (or user directory if you can't access the system directory) then run the font cache update command to get those fonts loaded where they can be used!
cp -rnv $HOME/.config/awesome/themes/fonts/* /usr/share/fonts
sudo fc-cache -vf
Then either restart AwesomeWM if that's what you are currently using or login to an Awesomewm session and now its installed and running.
Two alternative means exist of running getting to a running variant of this configuration
The ISO file contains this configuration as its core component and feature. Once completed, this will be available and you can demo the system accordingly until I finish the Calamares project enabling you to fully install it from the ISO.
While this method is bound to come with a lot of things no one needs (including me), my dotfiles contain an installation script(s) that will install the needed dependencies and situate the configuration on the system for you, in a nice and menu driven way that is how I have been getting the configuration set up personally for years. If opting for this option it is the first and second menu items you will need to run through to get this to work and its highly reccomended that this be run on a bare install.
-
This may be due to a dependency I forgot to list, feel free to open an issue with the sailent details from the log or error message and I can probably tell you what one, if that's the issue.
-
See Alternative Options Above
-
Sometimes just refreshing it if its doing this at first boot has fixed issues on the ISO test builds, so maybe this will help you. If this happens, please still file an issue as I am primarily interested in preventing as much.
-
Errors during runtime (or startup if the interface still gets drawn on screen instead of the awful default) will print the error to a dashboard widget so you don't need to trip if it times out.
-
The best means of capturing error logs, as well as testing changes you may want to make locally, is with
awmtt, available here, which will open a nested X server running awesome and prints the error logs to the terminal window as the startup process is underway (note, some of those error messages I am aware of and working out, or don't find harmful enough to do anything about. Deprecation notices means little when its been 2 years since a point version change).