At 1230227859 time_t, Maxime COSTE wrote:
This patch add a bash_escape function for bash completion, at the moment it
only escape spaces, other escaping may easily be added
Pushed.
--
Julien Danjou
// ᐰ jul...@danjou.info http://julien.danjou.info
// 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E
At 1230357156 time_t, m h wrote:
Just following up on this. So is it a bug in awesome, if manual
movement to the other screen seems to work?
Should I file a bug?
It's a bug, and I just fixed it.
The problem is that awesome move windows on their startup to the screen
the mouse is. That's a
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#385 - passing keypresses to a client
User who did this - Julien Danjou (jd)
Reason for closing: Implemented
Additional comments about closing: commit
d6dbb00f101789b690101ba44fadc4c0504b7cb2
Author: Julien Danjou
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#409 - Client windows fail to re-focus after moving to a tab without a client
and then back again.
User who did this - Julien Danjou (jd)
Reason for closing: Fixed
Additional comments about closing: commit
Using the API function prevents the compiler warning
awesome-client.c:200: warning: ignoring return value of 'asprintf',
declared with attribute
warn_unused_result. Besides from that it is a good idea to use the
API-version because it checks for malloc-problems.
---
awesome-client.c |2 +-
1
Using warn(foo %s, strerror(errno)); does not make sense because it
produces error messages
twice.
From man warn:
The err(), verr(), warn(), and vwarn() functions append an error
message obtained from strerror(3) based on a code or the
global variable errno, preceded by another colon and
At 1230571696 time_t, Roland Kammerer wrote:
Using warn(foo %s, strerror(errno)); does not make sense because it
produces error messages
twice.
From man warn:
The err(), verr(), warn(), and vwarn() functions append an error
message obtained from strerror(3) based on a code or the
On Mon, Dec 29, 2008 at 4:30 AM, Julien Danjou jul...@danjou.info wrote:
At 1230357156 time_t, m h wrote:
Just following up on this. So is it a bug in awesome, if manual
movement to the other screen seems to work?
Should I file a bug?
It's a bug, and I just fixed it.
Great! Thanks much.
On Mon, Dec 29, 2008 at 17:12, Julien Danjou jul...@danjou.info wrote:
At 1230295231 time_t, Nicolau Werneck wrote:
I am using teamspeak, and I would like to select a certain key so that
whenever I press it, awesome just behave as if I were focused in that
program's window, sending it to the
Hey all-
Xine doesn't want to play fullscreen in awesome (3.1-r1 gentoo).
Toggling to fullscreen crashes X. I'm not sure if this is an awesome
bug or an XCB problem. Searching doesn't help much for those terms.
At first I thought it was a driver issue (running intel) but I tried
xine in twm and
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - matt h (mharrison)
Attached to Project - awesome
Summary - Xine full screen crashes X
Task Type - Bug Report
Category - Core
Status - Unconfirmed
Assigned To -
Operating
11 matches
Mail list logo