24.09.2015 22:09, catch-...@draigwen.com пишет:
Thanks Uli,
No luck I'm afraid, it still just appears on the first tag on screen 2.
My rules definitely seem to be obeying the screen bit. When I restart
awesome to test, clients that I'd moved move back to the first tag on
the screen they sh
Thanks Uli,
>
> Am 20.09.2015 um 13:25 schrieb Fran:
> > It happens with everything. I just used Inkscape for testing purposes as I
> > was trying a more complicated rule matching instance and class which is
> > where I noticed the problem.
> [...]
>
> Ok, another quick idea: Move it to screen
Hi,
Am 20.09.2015 um 13:25 schrieb Fran:
> It happens with everything. I just used Inkscape for testing purposes as I
> was trying a more complicated rule matching instance and class which is where
> I noticed the problem.
[...]
Ok, another quick idea: Move it to screen 2 first.
callback = fun
It happens with everything. I just used Inkscape for testing purposes as I was
trying a more complicated rule matching instance and class which is where I
noticed the problem.
Sent from TypeMail
On 20 Sep 2015 12:21, at 12:21, Uli Schlachter wrote:
>Hi,
>
>Am 18.09.2015 um 10:18 schrieb Fran
Hi,
Am 18.09.2015 um 10:18 schrieb Fran Thomson:
[...]
> { rule = { class = "Inkscape" },
> properties = { tag = tags[2][2], },
> }
>
> and
>
> { rule = { class = "Inkscape" },
> callback = function (c) c:tags({tags[2][2]}) end
> }
>
> If I change the first index of tags[2][2]
t; I don't forget.
>
> To create tags without Tyrannical, just call awful.tag.add{name =
> "foo"} from a callback inside a custom awful.rule
>
> Good luck
>
> On 16 September 2015 at 16:04, Fran Thomson wrote:
> > Hiya,
> >
> > I'm curr
om a callback inside a custom awful.rule
Good luck
On 16 September 2015 at 16:04, Fran Thomson wrote:
> Hiya,
>
> I'm currently trying to use tyrannical to do some dynamic tagging but I have
> a couple of problems.
>
> 1) It seems to be ignoring the "screen" optio
Hiya,
I'm currently trying to use tyrannical to do some dynamic tagging but I have a
couple of problems.
1) It seems to be ignoring the "screen" option. I've got a tag called "www"
which begins on init and should just be on screen 1, but when firefox runs
(whic
Sorry wrong thread
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
re popular though.
lastly another question, do we only want to look in the apps folder?
or do you also want to look at actions, categories, emblems,
mimetypes status, devices, extras, places, stock??
Thanks...
H
On 04/07/2014 11:48 AM, Wei Peng wrote:
> Hi All,
>
> My v3.5.2+ based
Hi All,
My v3.5.2+ based config with *persistent dynamic tagging* (inspired by the
fine Shifty) is released. One thing of note (comparing with other fine
configs) is the accompanied doc in the form of github README.md.
Comments welcomed:
https://github.com/pw4ever/awesome-wm-config
It is a full
Thanks for the tips.
I've got a proper rule now,
{ rule = { class = "Houdini", instance = "MPlay" }, properties = {tag =
tags[2][2]}},
Mplay does spawn on tag 2 of my second monitor, and it stays put for a
breif period of time, but as soon as pixels are rendered it snaps back
to my
I personally use the following function in my rc.lua, mapped to
[modkey][i]. It outputs the info in naughty.
Why use an external program when you can have awesome give you the info ? :)
function client_prop(c)
f = function (prop, str)
return
prop and
( str
On Fri, 23 Jul 2010, Alan Warren wrote:
> is the first the "class" ? I believe I've got this correct as I've
> got mplay to behave
No.
http://awesome.naquadah.org/wiki/FAQ#How_to_find_window.27s_class_and_other_identifiers.3F
http://awesome.naquadah.org/wiki/FAQ#How_to_start_clients_on_specif
Thanks,
I was unaware of xprop. Very helpful info.
Unfortunately my app still "snaps" back to it's window. I set a similar rule
for
firefox and it does what it's supposed to, so it must just be an issue with
one
app calling another.
The apps are Houdini and it's image viewer, MPlay. I'm trying t
On Fri, Jul 23, 2010 at 09:27:33AM -0500, Alan Warren wrote:
> Hello,
>
> Does anyone know if there's a way to restrict an application to a single
> monitor on a specific tag with lua? Or more specifically, with shifty?
>
> I have an app that opens another small app and sends data to it on a regu
Hello,
Does anyone know if there's a way to restrict an application to a single
monitor on a specific tag with lua? Or more specifically, with shifty?
I have an app that opens another small app and sends data to it on a regular
basis. I would like to place this small app's window on my second mon
17 matches
Mail list logo
