On 10/06/2016 08:15 PM, XSign wrote:
> Hi there,
>
> I’m using archlinux, lightdm+awesomeWM as my work environment.
>
> And I found if I startup awesome with lightdm, the environment
> DBUS_SESSION_ADDRESS is set to /tmp/dbus-xxx
>
> But this environment should be point to /run/dbus/system_d
Willy Malvault (vlamy) wrote:
> *Warning* : this way you will spawn an extra process, as urxvt would be
> child process of /bin/myshell (like we say in french : "ça m'en touche
> une sans faire bouger l'autre" translated to "nevermind the bollo").
>
If this is an issue to you, you ca
Uli Schlachter wrote:
> Hi,
>
> On 21.10.2012 20:47, Uli Schlachter wrote:
>> On 14.10.2012 16:12, Alexander Yakushev wrote:
>>> In order to start writing real titlebar widgets first we should decide
>>> what for people want titlebars in first place. Minimize/maximize/close
>>> buttons? Moving/r
Uli Schlachter wrote:
> On 14.10.2012 16:12, Alexander Yakushev wrote:
> [...]
>> In order to start writing real titlebar widgets first we should decide
>> what for people want titlebars in first place. Minimize/maximize/close
>> buttons? Moving/resizing windows by titlebar? Something else, more
Alexander Yakushev wrote:
> On 10/13/2012 11:38 AM, "Jérôme M. Berger" wrote:
>> Wrong. I want titlebars and I use awesome (v3.4.13). I'd be pretty
>> unhappy if the next stable release didn't have them.
>>
>> Updating my config files does not
Alexander Yakushev wrote:
> What is so important with those titlebars? I mean everyone (wild guess)
> who wanted titlebars in their WM had already moved to Openbox or
> something; or at least they use their own half-baked titlebars.
Wrong. I want titlebars and I use awesome (v3.4.13). I'd
Jérôme M. Berger wrote:
> Jérôme M. Berger wrote:
>> Leo L. Schwab wrote:
>>> I just installed Awesome 3.4.12 from Debian unstable, and noted an
>>> unfortunate change in behavior.
>>>
>>> In 3.4.11, when you changed tags, the window that was
Julien Danjou wrote:
> Hey folks,
>
> A new awesome arrives! This is mainly to fix a regression introduced
> while fixing FS#1011 in v3.4.12.
>
> Happy hacking,
Great, thanks!
And I can confirm that this release doess fix FS#1011. Thanks again.
Jerome
--
mailto:
Jérôme M. Berger wrote:
> Leo L. Schwab wrote:
>> I just installed Awesome 3.4.12 from Debian unstable, and noted an
>> unfortunate change in behavior.
>>
>> In 3.4.11, when you changed tags, the window that was focused was,
>> in general, the window
Leo L. Schwab wrote:
> I just installed Awesome 3.4.12 from Debian unstable, and noted an
> unfortunate change in behavior.
>
> In 3.4.11, when you changed tags, the window that was focused was,
> in general, the window with that tag that last had focus. That is, I could
> switch away
Tim Johnson wrote:
> * Gregor Best [100720 23:55]:
>> keep in mind though that this starts nm-applet whenever awesome is
>> restarted. That also includes screen geometry changes (i.e. xrandr
>> events), such as connecting another screen.
> Is there a command to first shut down nm-applet (and th
Noah Meyerhans wrote:
> On Sun, Jul 04, 2010 at 12:49:10PM +1000, Adam Nielsen wrote:
>>> Nothing. I even did a cold reboot. It seems as if .xinitrc isn't actally
>>> being executed on startup, because 'sh .xinitrc' gets everything running
>>> great.
>> Might depend on your system config, I've
Perry Hargrave ; wrote:
On Fri, Oct 23, 2009 at 10:28:59PM +0200, "Jérôme M. Berger" wrote:
- How can I set the default layout for my tags? Right now it starts
in "floating" layout, which is about the worst possible choice (if I
wanted a floating wm I wouldn't be usi
Hi,
I've just upgraded to awesome 3.4 and I have a couple of
issues/questions:
- I have a vertical xfce panel on the left of my screen. With
awesome 3.3 all was fine, but now the left part of the wibox is
hidden behind the panel. (Note that I had the opposite issue with an
older ve
Bruno Vernay wrote:
So, I tested the proposed solutions.
- first mapping the tag_keys =
{"&","#11",'"',"'","(","-","#16","_","#18"} as they appear on an
azerty keyboard and then uses tag_key[i] instead of i.
- second, uses tag_keys = { '#10', '#11', '#12', '#13', '#14', '#15',
'#16', '#17', '#
Bruno Vernay wrote:
Awesome uses combo like:
Mod4 + 1-9 : Switch to tag 1-9.
Mod4 + Shift + 1-9 :Tag client with tag.
Mod4 + Control + 1-9 : Toggle tag view.
Mod4 + Shift + Control + 1-9 : Toggle tag on client.
It wasn't working on my config. I found out on IRC (thanks tyk) that I
need
Jhonny Boy wrote:
Hello everyone
I am using a dvorak bépo keyboard. I try to configured the 1,2,3,4,5,6,7,8,9 keys of
the keyboard to switch Desktop but in bépo it's a ",«,»,(,),@,+,-,/,*
but some key doesn't work. Is there any way in awesome 3.2 to identify the key
by a number?
Best regard
H
Hi,
Key bindings specified with key names do not work:
key({ modkey, }, "Left", awful.tag.viewprev)
However bindings specified with key codes do work:
key({ modkey }, '#1' .. i-1,
function ()
local screen = mouse.screen
if tags[screen][i] then
18 matches
Mail list logo