On 01.01.2013 02:11, Prashanth wrote:
> You're right, Sean. I hadn't noticed that changing the layout to
> vertical requires me to use set_left and set_right. I changed the whole
> thing to just set_first, set_second, set_third, which seems to work with
> both orientations.
>
> However, the tag
Hi,
On 01.01.2013 07:05, Jianjun Mao wrote:
> 3.5 has memory leak? after 11 hours awesome grows to 70MB+
Nothing is impossible. I'm at 76MiB after an uptime of 27h. However, no idea
what the memory usage was right after startup. Might also just be the lua
garbage collector being slower than neede
On 01.01.2013 00:20, Sean Goodwin wrote:
> Thanks for that, although it seems that once the I set the container's
> widget to systray, setting it to nil again does not remove the systray from
> my wibox. Any ideas? Do I have to have the wibox redraw itself or something?
Argh. Stupid bugs. The C AP
On 06.01.2013 19:02, Ignas Anikevičius wrote:
> I was wondering if somebody could explain me how to create a floating
> wibox with a textbox inside?
local foo = wibox{ x = 10, y = 20, width = 30, height = 40, visible = true }
foo:set_widget(bar)
(Perhaps also ontop = true)
(foo.visible = false hi
Hi,
On 08.01.2013 14:37, Max Buelte wrote:
-- Date widget
local datewidget = wibox.widget.textbox()
vicious.register(datewidget, vicious.widgets.date, " %R
", 61)
if screen.count() > 1 then
datewidget:buttons( awful.util.table.join(
awful.button({ }, 1, function () exec(script_pat
Hi,
On 09.01.2013 14:45, Christopher Schmidt wrote:
> 000:<:0006: 8: XKEYBOARD-Request(145,0): UseExtension major=1 minor=0
> 000:>:0006:32: Reply to UseExtension: major=1 minor=0
I hate Xlib. So much. No one should ever use it. We should rip it out of awesome
ASAP again. Luckily, someone is por
Hi,
On 09.01.2013 16:46, Christopher Schmidt wrote:
> Uli Schlachter writes:
[...]
>> I check Xlib's source code and I found some env vars which might be
>> useful. Could someone please start awesome with these variables:
>>
>> XKB_DEBUG=1 XKB_DISABLE=1 a
Hi,
On 10.01.2013 01:27, Shuuichi Nitori wrote:
> hi, I want to be able to change the background colour of mysystraybox and
> mylayoutbox, I can't do it with wibox.widget.backgound(), testing that I
> get this error, so that says to me this is not the way the background is
> set on this widgets:
>
Hi,
On 16.01.2013 20:56, Kasimir Knallkopf wrote:
> With today's wide screen displays the magnifier layout is a nice feature that
> brings the current window into the center. However, is there a way to
> configure the ratio between the x/y lengths for the magnifier?
>
> What I want to do is th
Hi,
On 20.01.2013 09:49, Levent S.B. wrote:
> And yet another question concerning my personal awesome-lxde mix.
> Since upgrading to awesome 3.5, awesome started auto-focusing on
> the lxde-panel if i change to another tag.
Meh. I hate focus bugs. Also, I don't really see why 3.4 would have done
On 21.01.2013 12:26, Marco wrote:
I don't know the internals and the reasons behind this restart. How
likely is it that this issue will be fixed and what does it take to
fix it?
Well, look at your config. What do you see? For example, it takes the number of
screens and creates tags for these s
Hi,
On 25.01.2013 05:57, Kyle Nolan wrote:
> I am having trouble loading a module with 3.5. The module itself depends on
> a program written for lua 5.1 but awesome keeps looking in 5.2 directories.
> Is there anyway to fix that?
Well, which lua version does awesome run with? You can find out lik
Hi,
On 25.01.2013 03:55, J.L.M. wrote:
> I've Googled the error message, and it shows up nowhere. After fixing my
> configuration for Awesome 3.5, I still get an error:
>
> /usr/share/awesome/lib/awful/widget/button.lua:27: cairo.Surface: not
> directly instantiable
Hm, I wonder why lua reports
Hi,
On 25.01.2013 09:10, Uli Schlachter wrote:
local orig_error = error
function error(...)
print(debug.traceback())
require("naughty").notify(text = debug.traceback())
Whoops, this line should be:
require("naughty").notify({text = debug.traceback()})
Hi,
On 29.01.2013 02:40, Sean Goodwin wrote:
> I'm trying to find a way to retrieve the current selected tag for a given
> screen. If screen 1 was on tag 3, this function/whatever would return 3.
> You get the idea. Is there anyway to do this?
$ echo 'local awful = require("awful") ; return
awful
Hi,
On 09.01.2013 17:31, Uli Schlachter wrote:
> On 09.01.2013 16:46, Christopher Schmidt wrote:
>> Uli Schlachter writes:
> [...]
>>> I check Xlib's source code and I found some env vars which might be
>>> useful. Could someone please start awesome with th
Hi,
On 31.01.2013 23:35, Vasya Belkin wrote:
> Hi, is it possible to find out text extents, e.g. width/height of string?
> Because the following code gives segmentation fault & I'm not sure, whether
> this is a bug or not:
>
> local lgi = require 'lgi'
> local cairo = lgi.cairo
> local cr = cairo
Hi,
On 01.02.2013 13:07, Vasya Belkin wrote:
[...]
> The thing with cairo's toy font API: I have no idea what is that :)
Cairo has several toy APIs. These are things which are "nice to have", but
shouldn't really be used by applications. For example, cairo can directly read
and write PNG files, b
Hello,
On 02.02.2013 04:02, Kasimir Knallkopf wrote:
> Awesome doesn't refresh my window. Try this:
A window manager has nothing to do with the window content. It just tells the
X11 server where to place the window and the rest works auto-magically.
> $ R
>
> plot (1:10,1:10)
> # should see a p
esome.naquadah.org/download/awesome-3.4.15.tar.bz2
md5: 63bbc25691254d04b96c00ba46b9ae59
sha1: d282080bde91dabbece211608c390d5ae826bc2f
number of changes
- -
2
number of commiters
- -------
1
shortlog
-
Uli Schlachter (2):
Fix keyboard layou
Hi,
On 14.02.2013 20:08, Daniel wrote:
> At some point after start up awesome, my wm log (I run awesome >&.wm.log
> in .xinirc) begins to fill up with the following. I comes every second
> or so.
>
> W: awesome: luaA_dofunction:78: error while running function
> stack traceback:
> /usr/sh
Hi,
On 15.02.2013 15:18, WaawWayne Werner wrote:
[...]
> I've cloned the git repo and I'm at commit
> f86a9c896cddc215704ddfe3779ad03545e71e72
>
> When I run `make` I get the following error:
>
> lua: (command line):1: lgi too old, need at least version 0.6.1
> stack traceback:
> [C]:
Hi,
On 20.02.2013 13:41, WANG Chao wrote:
[...]
> After some work, any X client's DPI is 120 except Awesome WM itself.
> Fonts on taglist/tasklist/wibox/naughty/... still uses DPI 96.
How are you setting the DPI everywhere else?
[...]
> Does anyone know how to setup the Awesome WM's DPI? Any com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
On 28.02.2013 03:40, Alfredo Palhares wrote:
[...]
> Awesome ready for tests. PID is 21426 masterkorp awesome (awesome-3.5) $ W:
> awesome: luaA_dofunction:78: error while running function stack traceback:
> /usr/share/awesome/lib/awful/widget/
Hi,
On 05.03.2013 20:10, Alan Warren wrote:
> I recently updated my Gentoo system, and the fonts used in my blingbling
> widgets have visually degraded quite a bit. Neither awesome (3.4.11), nor
> blingbling itself were changed, but I think my oocairo was updated from 1.3
> -> 1.4.
Well, could yo
On 06.03.2013 15:20, Alan Warren wrote:
[...]
> All of the packages you mentioned were updated. (pango, fontconfig,
> freetype) I'm using the lcd-filtering overlay for the infinality font
> rendering patches to both freetype + fontconfig. My ~/.fonts.conf has not
> changed though.
[...]
Hm. My b
Hi,
On 08.03.2013 10:21, Adam Nielsen wrote:
[...]
> I am wondering why Arch upgraded to 3.5 if it is not ready for production use
> yet?
Well, it's Arch, the distro for beta testers. :-P
[...]
> Some of the issues I am experiencing are:
>
> - Switching focus between monitors with keyboard s
On 29.01.2013 09:19, Adam Nielsen wrote:
[...]
> But if anyone knows how to stop Awesome from trying to resize urxvt each time
> the window is focused or unhidden (when changing tags) let me know! This only
> happens on a tiled layout FWIW, and it's most noticeable with a background
> image set to
Hi,
On 02.02.2013 22:39, Alexander Koch wrote:
[...]
> 1) Creating a textbox widget that doesn't change its width, no matter
> whether the content has two or three characters.
> Speaking a bit complicated, I just want to create a right-aligned
> textbox for holding a percentage value that does not
On 27.02.2013 09:46, Daniel wrote:
>> What's the first error that you have in your log? Is it different?
>>
>> My only guess so far is that an error occurred while creating a notification
>> which is now half-broken. It is broken enough that the timer which is
>> supposed
>> to destroy it errors o
Hi,
On 11.03.2013 06:50, Campbell Barton wrote:
[...]
> However from looking through the awesome codebase I couldn't see what
> determines when a new window is floating,
> Since from what I can tell this isnt a 1:1 mapping with a NETWM
> property or something blender may have set incorrectly.
If
On 16.03.2013 12:37, Lampros Liontos wrote:
> Whenever I switch desktop tags, the focus remains on a window in the tag
> I left, because the mouse, while overtop a window, did not actually
> enter the window by crossing its border. This can be fixed by leaving
> and returning to a window, but can
Hi,
On 21.03.2013 14:34, fREW Schmidt wrote:
> I use dmenu, like I'm sure many of you do as well. When I run dmenu
> from the console it starts immediately. When I run it from awesome
> there is a brief (maybe 50-75ms?) that means I can't just start
> typing, the first key I press tends to get l
Hi,
On 21.03.2013 05:22, Ole Johan Væringstad wrote:
[...]
> My question is "How do I launch/spawn a program on a given display on
> xinerama"
That's a good question. Once you figured it out, please tell me. The problem is
that the window manager has no "good" way to find a connection between "I
Hi,
On 25.03.2013 21:46, Levent Burggraef wrote:
[...]
> Still, an annoying problem which stays is that the panel -though
> displayed correctly on every tag- is always displayed on the first tag
> in the taglist as an open client. You can imagine that I don't want it
> to be displayed in the tagli
Hi,
On 26.03.2013 22:02, Louis MARIE wrote:
> Next to my clock i want to show a status.
>
> I've a shell script which show it.
>
> #!/bin/bash
> myStatus=`cat '~/.status'`
> # many treatment on it
> print $myStatus
>
> I want to show the result of the script next to the clock
>
> Does somebody
fcefcac89985e00c7c6d2659282187b08e34
number of changes
- -
62
number of commiters
- ---
14
shortlog
-
Uli Schlachter (31):
wibox.layout.base: Use math.min/max
wibox.layout.rotate: Add some good constructor arguments
Fix mouse.object_under_cursor() with draw
Hi,
On 25.04.2013 09:16, Daniel wrote:
[...]
I would like to avoid starting a program and then finding its window (by
pid; i.e. wmctrl can do this) and moving it in place.
[...]
In theory, a new window which appears can tell awesome on which tag it wants to
be visible. However, there is no un
Hi,
On 25.04.2013 12:07, Daniel wrote:
>> So there are some programs that takes a common argument for setting
>> workspace? Perhaps like the classic geometry -g of X? But yeah, I cant
>> remember having seen that. Maybe it's rather a function on the X
>> protocol level or so?
>
> Commenting mysel
Hi,
On 26.04.2013 13:35, Daniel wrote:
>> Yeah, that's what I meant (Oh, EWMH calls them desktops, not workspaces).
>> However, I haven't ever seen a single program which let's you specify this
>> property with a command line switch.
>
> I will have a go with _NET_WM_DESKTOP. At first try however
On 27.04.2013 16:50, Daniel wrote:
> On 2013-04-25, Uli Schlachter wrote:
>> P.S.: You don't need wmctrl to find a window by pid:
>>
>> function find_by_pid(pid)
>>for _, c in pairs(client.get()) do
>> if c.pid == pid then return c end
>>e
Hi,
On 11.05.2013 01:19, Knut Halvor Skrede wrote:
> I would like to add a margin option to the awesome theming by updating the
> layout files.
Margin option? Margin on what? I am looking forward to the patches which will
answer these question and which hopefully explain what all of this is about
Hi,
On 06.06.2013 04:25, kardan wrote:
[...]
and have some strange effects. when a window is redrawn. for ~some
moments it looks like switching display in framebuffer mode.
for xterm this becomes static when the window is maximized und
demaximized again. Half of the screen shows vertical yellow
Hi,
On 06.06.2013 05:42, kardan wrote:
[...]
Regarding the config changes I wonder what could be a proper solution
to deal with this in the future. Maybe it is possible to break down all
changes to patches that are applied to during package installation.
You mean changes to the default config?
On 06.06.2013 17:31, Monkey Pet wrote:
I don't know what key sequence I pressed, but on a workspace, my
application are now maximized. I tried using the max/unmaximized key
binding, but that doesn't work. I cycled through all the layout, that
didn't work. I tried restarting the application als
Hi,
On 11.06.2013 21:42, kardan wrote:
[...]
> -if(lua_pcall(globalconf.L, 0, LUA_MULTRET, 0))
> +/* Move error handling function before function */
> +lua_pushcfunction(globalconf.L, luaA_dofunction_on_error);
> +lua_insert(globalconf.L, -2);
> +
On 12.06.2013 14:27, kardan wrote:
> From 386ad6bfd134833a19e40c1920975e100f207a51 Mon Sep 17 00:00:00 2001
> From: kardan
> Date: Wed, 12 Jun 2013 14:15:54 +0200
> Subject: [PATCH] honor appended -c option for --check
>
> ---
> awesome.c | 31 ---
> 1 file changed,
Hi,
On 12.06.2013 23:55, kardan wrote:
Am Wed, 12 Jun 2013 22:41:23 +0200
schrieb Uli Schlachter :
Have you read the linux kernel's coding style document? It suggests
to print out the GNU coding style and burn it as a symbolic gesture...
Not yet, but will do! I assume you refer to
On 19.06.2013 00:25, Manuel Kasser wrote:
> I just wondered what a client's leader_id contains (or, to be more
> precise, in which circumstances there IS a leader_id). I couldn't
> produce a scenario where a client's leader_id is set, but maybe I just
> tried out the wrong scenarios.
Urgh. There i
On 28.06.2013 00:59, John Yates wrote:
Any thoughts about supporting awesome on Surface or Mir?
http://lwn.net/Articles/554758/
"Surface" as in "SurfaceFlinger"? What? Why?
I know little about XCB.
"XCB" stands for "X11 C Bindings".
> I know that it encapsulates the godawful X semantics.
On 06.07.2013 19:26, debecio wrote:
> Hello, I'm finding the way to show a logout/shutdown dialog window on all
> tags. Do it exists anything like:
>
> { rule = { class = {"Logout"} },
> properties = {
> floating = true,
> ontop = true,
> tag = tags[1][*] } },
Hi,
On 17.07.2013 02:58, Gerald Klein wrote:
[..]
> 1. how to get the current screen object
What exactly is "current" for you?
If you want the mouse's screen, you can use mouse.screen and
screen[mouse.screen] turns that into a screen object.
If you want the currently focused client (if there is
Hi,
On 25.07.2013 11:12, Marshall Mason wrote:
> I'm a heavy user of dmenu and dzen2. I'm trying to figure out how to
> configure Awesome so the clients move down and back up in the brief moments
> that dmenu and dzen2 show up rather than just covering them over.
[...]
> However, this is very klud
Hi,
On 15.08.2013 23:18, luke bonham wrote:
Hi everyone, I was trying to get to work 'termfair' layout from this
good old module: https://github.com/vain/awesome-vain
This is what I got: http://pastebin.com/gecFkxj0
However I keep getting this error:
"/usr/share/lua/5.2/lgi/override/Pango.lua
Hi,
On 18.08.2013 14:56, Adrian C. wrote:
> Hello, is someone using awesome v3.5 willing to rewrite "Usage examples"
> section[1] and the next section "Format functions" of the documentation
> for the new widget API? Thanks.
attached patch should help anyone who wants to work on this. I just we
Hi,
On 04.09.2013 17:30, Csaba Dunai wrote:
[...]
> a = wibox({})
> a.screen = 1
> a.visible = true
> a.ontop = true
> a.x = 10
> a.y = 10
> a.width = 100
> a.height = 100
> a:set_bg("#ffa500")
> a.screen = nil
> a = nil
Wiboxes no longer have a .screen property, because there is just a single, "
Hi,
On 05.09.2013 12:24, Vincent Bernat wrote:
> Some programs like to resize and replace themselves after start. This is
> annoying as they may move to another screen. For example, Wireshark is
> like that.
>
> It uses GTK but ultimately, this is the call to XResizeWindow or
> XMoveResizeWindow
On 11.10.2013 12:40, Andrey V Golovin wrote:
> Hi all
> I made simple cairo drawing in widget area.
> http://imgur.com/pIGDMXP.png
>
> But, these one pixel lines between drawings looks bad. I played with cairo
> colors it does not help. Is somebody has an idea how to fix it would be
> very nice to
On 11.10.2013 23:04, Andrey V Golovin wrote:
> Thanks for swift reply, Uli
>
>
> The function to draw is:
> colors for bg and fg are taken from array
>
> function sep(fg,bg)
>sp = wibox.widget.base.make_widget()
>sp.fit = function(mycross, width, height)
>local size = math.min(wi
2: http://awesome.naquadah.org/download/awesome-3.5.2.tar.bz2
md5: 575b2c2a6d38510c6d059dca09bc269f
sha1: 5617b51733142dfcabdc7ac2c5bcdd293964a85a
number of changes
- -
32
number of commiters
- -------
5
shortlog
-
Uli Schlachter (28):
Implement window gr
Hi,
On 13.10.2013 19:28, Raphael Cervantes wrote:
> Hi,
> I was unable to get it to compile on arch linux. I'm attaching the error
> messages I get when I run make. I'll be greatful of any help or advice.
Did you build awesome yourself before, too?
I guess that awesome was compiled against the
Hi,
On 22.10.2013 21:14, Rena wrote:
> Since a GPU upgrade, I have 3 screens, and xrandr sees them individually,
> but awesome only sees a single large screen.
What exactly is a GPU upgrade?
Could you provide the output of "xrandr" and "xdpyinfo -ext XINERAMA"? Which
awesome version are you using
Hi,
On 30.10.2013 03:37, Andre Klärner wrote:
> as my setup at home is a bit more complex than the one on the go and at
> work I had to modify the xrandr screen table function a bit. To not keep it
> just for me I updated the wiki page for it.
>
> https://awesome.naquadah.org/wiki/XRandR_Screen_T
Hi again,
On 30.10.2013 18:42, Andre Klärner wrote:
> On Wed 30.10.2013 18:00:33, Uli Schlachter wrote:
>> On 30.10.2013 03:37, Andre Klärner wrote:
>>> as my setup at home is a bit more complex than the one on the go and at
>>> work I had to modify the xrandr screen t
Good Morning,
On 31.10.2013 05:46, Andre Klärner wrote:
> On Wed 30.10.2013 20:28:32, Uli Schlachter wrote:
[...]
>> Having written this mail and re-reading it before sending it, I notice that
>> you
>> mentioned awesome 3.4.15. A quick look confirms that 3.4 does not hav
Hi,
On 06.11.2013 03:40, Alfredo Palhares wrote:
> Apps like Skype, Steam, network manager, dropbox or anything really
> do not show on the systray on my config. There is absoluty nothing
> in the tty. Would a someone give a look? The wibox is created on
> cfg/wibox.lua.
>
>
> Here is the git r
Hi,
On 19.11.2013 14:03, Kasimir Knallkopf wrote:
> I would like to use askpass to enter passwords through the gui. When I
> start /usr/lib/ssh/x11-ssh-askpass, then the askpass window will not appear
> *and* the screen focus will be locked to the terminal from which I started
> askpass. It see
Hi,
On 20.11.2013 11:12, Dong Zhu wrote:
[...]
on awesome 3.5 I change the codes as below:
membar = awful.widget.progressbar()
membar:set_width(50)
membar:set_height(8)
membar:set_vertical(false)
membar:set_background_color("#3F3F3F")
membar:set_border_color(nil)
membar:set_color({ type = "linea
On 20.11.2013 09:43, Namikaze Minato wrote:
> Well, something similar is happening to me when I use evince with the
> mozilla plugin for reading PDFs on chromium and that I click on the
> PDF viewer (scrolling is fine), but it's too much of an edge case for me
> to report it as a bug. (awesome com
On 20.11.2013 05:42, Kasimir Knallkopf wrote:
>> Which awesome version are you running?
>
> awesome v3.5.2 (The Fox)
> ⢠Build: Oct 13 2013 01:33:36 for x86_64 by gcc version 4.8.1 (nobody@)
> ⢠Compiled against Lua 5.2.2 (running with Lua 5.2)
> ⢠D-Bus support: â
>
> So it's a new bug th
On 23.11.2013 03:49, Kasimir Knallkopf wrote:
>> sudo apt-get install ssh-askpass
>>
>> DISPLAY=:1 ssh-askpass
>>
>> The askpass window appeared, I entered foobar, pressed enter and the window
>> disappeared.
>
> I can reproduce this bug on the default configuration of awesome
> on archlinux. I e
Hi,
On 02.12.2013 22:18, Stanislav Ochotnicky wrote:
> First my use case (perhaps someone will suggest a different way to deal with
> this):
> I use dynamic tagging facilities in awesome (and tyrranical). I have
> configuration for most applications that I use but I often connect to several
> host
On 02.12.2013 23:50, Jason Hunt wrote:
> Afternoon. I created a new wibox in rc.lua for supplemental statusbar:
>
> mywibox2 = {}
> mywibox2 = awful.wibox({ position = "bottom", screen = 1, border_width = 0,
> height = 16 })
>
>
> Currently, it is just an empty status bar. I commented out the
On 03.12.2013 08:44, Vincent Bernat wrote:
> ❦ 2 décembre 2013 22:57 CET, Uli Schlachter :
>
>>> [1] xprop -f WM_AWESOME_TAGS 8s -set WM_AWESOME_TAGS tag1,tag2
>>
>> Such a property (almost) already exists and is called _NET_WM_DESKTOP. It is
>> used for sav
On 02.12.2013 23:39, Stanislav Ochotnicky wrote:
> Quoting Uli Schlachter (2013-12-02 22:57:58)
[...]
>> I hope this clears up the current state. Feel free to come up with
>> suggestions
>> on how to improve this.
>
> Thanks for quick reply. I don't think i
Hi,
On 03.12.2013 11:06, Stanislav Ochotnicky wrote:
> Quoting Uli Schlachter (2013-12-03 08:54:22)
>> On 02.12.2013 23:39, Stanislav Ochotnicky wrote:
>>> Quoting Uli Schlachter (2013-12-02 22:57:58)
>> [...]
>>>> I hope this clears up the curr
Hi,
On 01.01.2014 19:42, Csaba Dunai wrote:
> Uli Schlachter znc.in> writes:
[...]
> Thanks for the quick reply. Unfortunately my problem is still not solved. My
> point is not only to make the wibox disappear but also to free up the memory
> it occupies.
>
> I have r
Hi,
On 28.01.2014 17:57, wu, sa wrote:
> Is it possible to force windows spawned by
> programs/processes/scripts, to stick to its parents workspace/tag?
What exactly do you mean by programs/processes/scripts? Script sounds like a
shell script to me and shell scripts don't really have a tag.
> I
Hi,
On 19.02.2014 21:45, Manuel Kasser wrote:
> I was wondering whether awesome behaves correctly on receiving SIGTERM,
> i. e. doing (more or less) awesome.quit(). I'm not sure how to check
> that myself.
>From awesome.c (all code can be found in the released tarballs or on
git.naquadah.org):
Hi again,
On 19.02.2014 22:18, Manuel Kasser wrote:
[...]
> And if X dies ealier: if that means all graphical processes get
> SIGTERMed, it shouldn't be a problem anyways, even if they didn't
> receive the SIGTERM originally intended for them by the shutdown
> procedure but another one, should it?
On 21.02.2014 23:52, Manuel Kasser wrote:
> Hi,
>
> I'm a little confused with a detail in the titlebar-implementation in
> awesome.
> I took the titlebar-code from the reference-rc.lua.
> Now I want to work on titlebar-stuff and noticed that the titlebar is
> set by setting the widget of the wibo
Hi,
On 23.02.2014 09:13, David Sorkovsky wrote:
[...]
> Dual monitors both working well with Awesome - like the independence, but
> sometimes I use the RHS for my laptop and want to move apps to the LHS at
> that time.
>
> Wondering if there is something I needed to setup in Awesome?
>
>
> xr
Hi,
On 05.12.2013 22:16, Uli Schlachter wrote:
> On 03.12.2013 11:06, Stanislav Ochotnicky wrote:
>> Quoting Uli Schlachter (2013-12-03 08:54:22)
>>> On 02.12.2013 23:39, Stanislav Ochotnicky wrote:
>>>> Quoting Uli Schlachter (2013-12-02 22:57:58)
>>>
On 23.02.2014 19:15, Elv1313 . wrote:
[...]
> But would it be better to simply be able to access random xprops from lua
> rather than having to patch awesome everytime we want a new one?
[...]
The problem with accessing random X11 properties is that most random properties
have random formats. I ca
evil magic, and it is, but so is adding a single BLOB
> property. The use case your patch try to allow cannot be fixed using a
> single BLOB. I understand X11 is fragile, but do we really have a choice
> here?
Hm, yeah...
> On 23 February 2014 13:59, Uli Schlachter wrote:
[...]
Cheers,
Uli
who is just thinking out loud right now
--
Happiness can't be found -- it finds you.
- Majic
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Hey,
On 22.03.2014 11:30, Dan Milon wrote:
> I installed archlinux & awesome on a macbook pro with a retina
> display. As you can imagine everything was super tiny. I added "Xft.dpi
> = 196" to xrdb and now gtk, qt etc apps display normally, but the awesome
> status bar still shows tiny.
>
> It s
number of commiters
- ---
11
shortlog
- ----
Uli Schlachter (71):
luadoc: Document screen outputs
Print libxcb error codes for broken connections
tasklist: Add default colors for broken themes
Really ignore loops in transient_for (FS#1124)
awful.tag.del
Hi,
On 30.03.2014 12:24, Quan Guo wrote:
> Congratulations! I'm wondering how I can get the newest codes from
> git.naquadah.org, if possible.
>
> I tried to pull the newest master branch. But I still get awesome 3.5.2?
> Any ideas?
[...]
There is a 3.5 branch and a master branch (and lots of o
Hi,
On 31.03.2014 04:06, Harvey wrote:
> I'm still a little confused as to why the move to lgi was considered to
> be necessary at all.
[...]
I never liked some of the hacks that the widget layout code needed to do. It got
some nested tables containing widgets as arguments and had to return a fla
Hi,
On 31.03.2014 11:06, Eugen Dedu wrote:
> I have been using awesome since a few months now, but there is one thing
> I really miss: sloppy focus with autoraise after some delay.
>
> I modified rc.lua from
> client.connect_signal("focus", function(c) c.border_color =
> beautiful.border_focus
rtlog
- ----
Uli Schlachter (8):
gears.surface: Cache files from disk
gears.color: Add a pattern cache
awful.tooltip: Small reorganization
awful.tooltip: Add (and use) :set_markup() function
systray: Don't set WM_STATE on embedded windows (FS#1246)
Revert &
Hi,
On 02.04.2014 23:08, Manuel Kasser wrote:
I want to create/spawn a new client (a new urxvt) and hold it/catch it
in a variable to do some stuff with it afterwards.
The way I am doing this now is by spawning, catching the pid and then
find the client with this pid:
clpid = awful.util.s
On 03.04.2014 17:40, Manuel Kasser wrote:
> Am 03.04.2014 07:50, schrieb Uli Schlachter:
[...]
>> [awesome awesome-code]
>> Why is this better than just finding the new urxvt by pid in the manage
>> hook? Dunno. It just gets more browny points for using some fancy API..
-
Uli Schlachter (7):
imagebox: Don't try to scale by infinite (FS#1248)
gears.color: Handle nil arguments correctly again
naughty: Don't use the cache when loading icons (FS#1253)
gears.surface: Handle the cache more intelligently
awful.tag.move: Fix
o the awesome
devel mailing list or submitting pull requests on github.
> H
Uli
> On 04/11/2014 05:20 AM, Uli Schlachter wrote:
>> Guys,
>>
>> could you please stop reporting bugs *after* a new release?
>>
>> Uli
>>
>
>
>
--
"Are you p
Hi,
On 16.04.2014 20:54, david cobac wrote:
> Some precisions :
> it seems it finally interacts but not the whole widget...
> Since i have two of these widgets side by side, it appears that sensitive
> area overlaps on the other : it's like the area of the widget is on its
> bottom right and inclu
Hi,
On 17.04.2014 10:40, Thorsten Jolitz wrote:
> having used Tmux on the console and Stumpwm with X quite some time now,
> I got used to have the same prefix (C-o) and more or less the same
> keybindings for both WM's, so I don't have think about being on the
> console or in an X session.
>
> N
On 17.04.2014 17:55, david cobac wrote:
> Hi,
> i have a png image file which periodically updates.
>
> I've tried to display it with an imagebox and a timer but there's actually
> no updates in the display, here is a complete minimal (i hope) code :
>
> function imagew_icon()
>local fic ="/t
On 21.04.2014 09:50, david cobac wrote:
> Hi,
>
> i'm trying to bind mouse wheel with a wibox just like :
>
> mywibox:buttons(awful.util.table.join(
> awful.button({ }, 4, function () naughty.notify({ text="roulette 4" })
> end),
> awful.button({ }, 5, function () naughty.notify({ text="roul
Hi,
On 17.05.2014 21:11, Peter Schroeder wrote:
> I am attempting to modify the taskbar to function like screen/tmux. I have
> figured out how to modify the text of the taskbar buttons to include a
> number to the left of it, but I can't figure out what variable or function
> to use to get the ord
301 - 400 of 448 matches
Mail list logo
