Hot answers tagged

21

From man awesome there doesn't seem to be a default key binding to close all windows of an application. It might be possible to manually add such a binding. There is, however, a default key binding to close the one focused window*: Mod4-Shift-c. This will leave other windows (if any) of the application intact. It does not work for sub-windows ("logical" ...


12

Add to ~/.config/gtk-3.0/gtk.css: .window-frame { box-shadow: none; margin: 0; } (via https://bbs.archlinux.org/viewtopic.php?pid=1416334#p1416334) I had to restart X for it to take effect - SIGHUP awesome was not sufficient.


11

You can simply place code in a separate file and include it with dofile("somefile.lua") Note: The working directory is $HOME. To specify a file relative to rc.lua you can use dofile(awful.util.getdir("config") .. "/" .. "somefile.lua") If it's more than just some code and it might be used by others as well, it might make sense to create a lua module ...


11

You can set up a compose key for all sorts of different key sequences. There are specific instructions for Ubuntu, but they assume that you are running a Desktop Environment like Gnome or Xfce. If you are using awesome as a standalone window manager, you can set a compose key in your .xinitrc file like so (this example uses the right Alt key): setxkbmap -...


11

I am not sure if you have created the string following xrandr --newmode by yourself or have you copied it from somewhere else, but it won't work in its current form. I recommend to do it step by step. First, you need to generate the new mode. I recommend using 60Hz with LCD or 85Hz with CRT monitor gtf 1280 1024 60 You will get something like: # ...


10

By default there is no such key binding (in 3.5.1, see other answer for 4.1). But you can create one. Use this snippet (or better add the key binding to your existing configuration) for your rc.lua file: clientkeys = awful.util.table.join( awful.key({ modkey }, "F7", function(c) c.maximized_horizontal = not c.maximized_horizontal end), awful.key({ ...


9

awesome is in the repositories, so sudo apt-get install awesome fonts-font-awesome awesome-extra For additional information see http://laputa.io/blog/2012/09/02/using-awesome-in-ubuntu-12.04/ , http://www.neowin.net/forum/topic/901758-how-to-awesome-wm-with-debianubuntu/ and the awesome documentation http://awesome.naquadah.org/wiki/Main_Page http://...


8

Xwrits works with Awesome. It's a simple command line program. Here's an example for a five-minute break with screen lock every 55 minutes: xwrits breaktime=5:00 typetime=55:00 +mouse +lock


8

With awesome 4.0 on Debian stretch, no patch as in the answer of Sardathrion is needed, that is to change your dpi to get a proper screen setup, you need to 1) Create the .Xresources file with your settings, that is Xft.dpi: 192 If you are wondering about the right DPI value, see this post. I used the next value that was a multiple of 96. For more ...


8

Yes there should be. Try Mod+Ctrl+j to focus the next screen. Then Mod+Ctrl+k should focus the previous screen.


6

In addition to the Compose key, you can also set up a key to select the so-called ‘third level’ by selecting one of the ‘international’ keyboard layouts. On Debian, I use ‘English (international AltGr dead keys)’. On PC keyboards, AltGr is actually meant for this purpose, and X likes to assign it to the third level shift by default. You can also do this ...


6

You could use xautolock: Xautolock monitors console activity under the X window system, and fires up a program of your choice if nothing happens during a user configurable period of time. You can use this to automatically start up a screen locker in case you tend to forget to do so manually before having a coffee break. Something along the lines of: ...


6

I have this problem as well. I think it's related to the bug herein: http://osdir.com/ml/blfs-support/2011-12/msg00059.html The problem seems to be related to specific functionality in gtk 3.0, likely related to resizing the window or making the resize grip appear: I've gotten this behavior when I use Meta-Mouse2 to resize in Awesome. I've also seen it ...


6

I would suggest using the utility xkill in this case. If it didn't work, it would at least probably give some information explaining why.


6

~/.xinitrc is only read when you start a GUI session with startx (or otherwise calling xinit) after logging in in text mode. So that won't help you. Whether ~/.bash_profile, ~/.profile, ~/.xprofile and ~/.xsessionrc are read when logging in with a display manager depends on how the display manager is configured and what session type you select when logging ...


6

from https://awesomewm.org/wiki/Awesome_and_Xfce4 Go to: Settings -> Session and Startup -> Session And change Restart Style of xfwm4 to Never Then go to Application Autostart and add awesome It should work after restarting xfce


5

To move code into a different file, you create a module and require the module in the rc.lua. To create a module, you simply call module (name [, ···]) in the script that has the code you pulled out of the original script. Lua reference - module. To use the module you created, you just call require (modname). Lua reference - require. There is an excellent ...


5

You would do this via Xmodmap and not via your window manager. This is directly related to your keyboard layout/keymap and not your window manager. To change your xmodmap create a file named ~/.Xmodmap and add the following content. This should allow you to to type üäöß directly with altgr+u keysym a = a A adiaeresis Adiaeresis keysym o = o O odiaeresis ...


5

I couldn't make the viewidx method working but I ended up doing the following, which worked: awful.key({ modkey, }, "a", function () local screen = mouse.screen if tags[screen][10] then awful.tag.viewonly(tags[screen][10]) end end),


5

I'm pretty sure that your lid callback is going to be called every time the lid is closed as well as opened. The sleep.sh file here states: # if launched through a lid event and lid is open, do nothing echo "$1" | grep "button/lid" && grep -q open /proc/acpi/button/lid/LID/state && exit 0 the "lid open" scenario is one your script is not ...


5

Adding the following rule to your rc.lua config file (in ~/.config/awesome/) should fix the problem: { rule = { instance = "plugin-container" }, properties = { floating = true, focus = yes } }, It keeps the focus on the flash plugin, so the full screen mode is never canceled (until you press Esc).


5

This is possible to do in several ways. In X11 Xmodmap is probably one of the easier ways, for a simple change like this. Wikipedia article about Irony punctuation: This character can be represented using the reversed question mark (⸮) found in Unicode as U+2E2E; another character approximating it is the Arabic question mark (؟), U+061F. Xmodmap manual: ...


5

I prefer using the Compose key system, I've just checked and it seems I've had Compose-/-? (and Compose-?-/) set to output U+2E2E for some time now (? reflected off the /) My .XCompose file looks like this: # # add in the original stuff (what's usually there) include "%L" # # Compose key sequences # # generate PI char <Multi_key> <p> <i> ...


5

I recently solved this problem myself on Arch Linux. I used the program xss-lock from the AUR found here. I was trying to set up a service to lock the screen on sleep but for some reason I couldn't get it to work. I ended up using xss-lock and it worked very easily. Install xss-lock from the AUR. Add one of the commands below to your .xprofile or ...


5

For me, the xautolock process was still running in the background, but it wasn't listening to any xautolock -locknow commands. As mentioned by @jrm, an application must be suppressing the "screensaver". For both of us, this was due to mpv (video player) disabling the screensaver. For mpv, the fix is to add the following to ~/.config/mpv/config or ~/.mpv/...


5

The default keyboard shortcut is ModCtrlN. (Source) The API function being used is awful.client.restore().


4

It's a bit tricky: You're right "plugin-container" looks quite like firefox. Unfortunately you cannot distinguish the newly spawned yt-client by "instance" since it's simply an empty string, which matches more clients than you want. I have found another way: The "class" property of that client is "Luakit" instead of "luakit" for normal luakit-clients. So ...


4

The mouse grab when clicking on any empty area in the title/menu bar in nautilius/evince/gnome-terminal/etc. happens for me on Ubuntu 11.10 / libgtk-3-0 3.2.0-0ubuntu6 / awesome 3.4.10-1 as well. A killall nautilus or so on the console releases the mouse grab; with Nautilus, just closing the window with a Meta-c does not help. There seems to be a fix for ...


4

Your keyboard bindings are not working because your keyboard no longer has those keysyms. If you want to have, for example, Alt+F do something, then you need "F" in some key. But if you load "ru" alone, then there is no "F" at all (nor any latin letter). I think, specially when you need to handle multiple layouts, that it is much better to let X11 (through ...


4

i had this BadMatch Error problem until i deleted a previously added "1280x1024_60.00" because it could never use the double quoted mode successfully. Eventually, realized a better name for the mode helped. So i deleted "1280x1024_60.00" by running the following as a normal user: $ xrandr --version reports 1.4.0 and 1.4 $ xrandr | grep 1280 #Do you see ...


Only top voted, non community-wiki answers of a minimum length are eligible