[awesome bugs] #765 - clean/escape unknown tags from notifications

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#765 - clean/escape unknown tags from notifications User who did this - Gregor Best (farhaven) -- Hmm, i think the principle Be conservative in what you send, be tolerant in what you receive

[awesome bugs] #235 - Print a list of propositions when writing the first letters in the auto-complete prompt.

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#235 - Print a list of propositions when writing the first letters in the auto-complete prompt. User who did this - Julien Danjou (jd) -- Roman, this is a different issue. You should open another

[awesome bugs] #762 - mozplugger freezes desktop (works in wmii)

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#762 - mozplugger freezes desktop (works in wmii) User who did this - Uli Schlachter (psychon) -- Awesome doesn't lock up (e.g. use notify-send to send a notification, it will work). It's just

[awesome bugs] #765 - clean/escape unknown tags from notifications

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#765 - clean/escape unknown tags from notifications User who did this - Uli Schlachter (psychon) -- The specs say this for summary and body of a notification: This is a single line overview of

[awesome bugs] #564 - Awesome and KDE 4.3 systray

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#564 - Awesome and KDE 4.3 systray User who did this - Uli Schlachter (psychon) -- As for me, I dont' use a lot of KDE stuff, but all icons it seems like always appeared (awesome 3.4, KDE 4.4.5,

[awesome bugs] #672 - Maximazed flash video doesn't cover a bottom wibox

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#672 - Maximazed flash video doesn't cover a bottom wibox User who did this - Uli Schlachter (psychon) -- I guess this means this bug can be closed as invalid? -- More information can be

[patch] textbox/naughy: behave nicer when incorrect markup is received

Hi people, the attached two patches fix a little issue some people had with naughty. When a notification with broken markup was received, naughty only displayed a little empty box and issued a warning about broken pango markup on stderr. The first patch adds a new read-only textbox property

Re: [patch] textbox/naughy: behave nicer when incorrect markup is received

Am 16.07.2010 12:34, Gregor Best wrote: Hi people, the attached two patches fix a little issue some people had with naughty. When a notification with broken markup was received, naughty only displayed a little empty box and issued a warning about broken pango markup on stderr. The first patch

Re: [patch] textbox/naughy: behave nicer when incorrect markup is received

Am 16.07.2010 13:52, Uli Schlachter wrote: textbox.text = foo if textbox.text == do print(foo is invalid) end Anyone wants to test if this already works? If yes, we can make that expected behavior and (ab)use it for this. A quick google for the documentation of pango_parse_markup() found

Re: [patch] textbox/naughy: behave nicer when incorrect markup is received

On Fri, Jul 16 2010, Uli Schlachter wrote: (Also, according to the docs, print(textbox.text) will return the text with all attributes stripped. Does this qualify as a bug?) Yes. -- Julien Danjou // ᐰ jul...@danjou.info http://julien.danjou.info pgpSoWYhwKpl6.pgp Description: PGP

Re: [patch] textbox/naughy: behave nicer when incorrect markup is received

On Fri, Jul 16 2010, Uli Schlachter wrote: I don't really like this approach, but I guess it works... Neither do I. I think we should raise a Lua error if `textbox.text = foo' cannot be parsed by Pango. Looks possible, doesn't it? -- Julien Danjou // ᐰ jul...@danjou.info

Re: [patch] textbox/naughy: behave nicer when incorrect markup is received

Am 16.07.2010 13:59, Julien Danjou wrote: On Fri, Jul 16 2010, Uli Schlachter wrote: I don't really like this approach, but I guess it works... Neither do I. I think we should raise a Lua error if `textbox.text = foo' cannot be parsed by Pango. Looks possible, doesn't it? +1 That might

[awesome bugs] #778 - Clients with nofocus hint but with TAKE_FOCUS protocol doesn't hit into focus history

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#778 - Clients with nofocus hint but with TAKE_FOCUS protocol doesn't hit into focus history User who did this - Ivan Lyapunov (dront78) -- netbeans doesn't work without MToolkit on awesome but

[awesome bugs] #778 - Clients with nofocus hint but with TAKE_FOCUS protocol doesn't hit into focus history

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#778 - Clients with nofocus hint but with TAKE_FOCUS protocol doesn't hit into focus history User who did this - Anton Bobrov (baverman) -- Also you can try solutions in

Re: [patch] textbox/naughy: behave nicer when incorrect markup is received

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am 16.07.2010 13:59, Julien Danjou wrote: On Fri, Jul 16 2010, Uli Schlachter wrote: I don't really like this approach, but I guess it works... Neither do I. I think we should raise a Lua error if `textbox.text = foo' cannot be parsed by

[awesome bugs] #765 - clean/escape unknown tags from notifications

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#765 - clean/escape unknown tags from notifications User who did this - Uli Schlachter (psychon) Reason for closing: Fixed Additional comments about closing: commit 6fa27c7b482ab78d13eed3d71e259e04f85af587 Author:

[awesome bugs] #762 - mozplugger freezes desktop (works in wmii)

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#762 - mozplugger freezes desktop (works in wmii) User who did this - Yaroslav Halchenko (yarikoptic) -- If it would be of help: