awesome | 27 Nov 11:39 2014

[awesome bugs] #982 - Mouse events under non-English keyboard layout (Attachment added)

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#982 - Mouse events under non-English keyboard layout
User who did this - Damjan (gdamjan)

----------
The above patch applies to 1.3.0 too if modified slightly (attached).
----------

One or more files have been attached.

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=982#comment4195

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you
did not expect this message or don't want to receive mails in future, you can change your notification
settings at the URL shown above.

awesome | 27 Nov 09:33 2014

[awesome bugs] #982 - Mouse events under non-English keyboard layout

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#982 - Mouse events under non-English keyboard layout
User who did this - Galkin Vasily (galkin-vv)

----------
Having this issue on Debian when synergy 1.6.1 (input devices sharing utility) is running in server mode.
awesome 3.5.5

After executing 
xkbcomp $DISPLAY - | egrep -v "group . = AltGr;" | xkbcomp - $DISPLAY
awesome become reacting to mouse clicks in any layout.

Problem doesn't appear while synergy server is not running.
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=982#comment4194

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you
did not expect this message or don't want to receive mails in future, you can change your notification
settings at the URL shown above.

Julien Danjou | 24 Nov 11:04 2014

awesome moving to GitHub

Hi there,

Long time now see! I'm pleased to announce that awesome is moving to
GitHub for its code and issue hosting starting from now.

The code is now hosted at:

  https://github.com/awesomewm/awesome

The organization also has a few other repositories, such as the Web
site, check https://github.com/awesomeWM

The bug tracker (FlySpray) has been set into a partial read-only mode,
e.g. it's not possible to open new bug on it, but you can still comment
the old ones. New issues should be opened on GitHub at:

  https://github.com/awesomeWM/awesome/issues

I don't think it's necessary to precise that you can also open pull
requests instead of sending patches on the awesome-devel mailing list.

Let me know if you have any question and/or suggestions.

Happy hacking,

--

-- 
Julien Danjou
;; Free Software hacker
;; http://julien.danjou.info
(Continue reading)

awesome | 20 Nov 15:35 2014

[awesome bugs] #1314 - Chromium tabs on secondary screens

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1314 - Chromium tabs on secondary screens
User who did this - Von Random (von)

----------
There is some weirdness in dwm's behaviour (once I start dragging the tab the whole window disappears), but
the tab reattaches nevertheless.
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1314#comment4193

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you
did not expect this message or don't want to receive mails in future, you can change your notification
settings at the URL shown above.

awesome | 20 Nov 15:20 2014

[awesome bugs] #1314 - Chromium tabs on secondary screens

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1314 - Chromium tabs on secondary screens
User who did this - yauhen (actionless)

----------
my bad, i did not read the list carefully enough,

i was asking because i tried on clean dwm 6.0 and had almost the same behavior (the only difference what in dwm
dragged window was displayed at the big distance from mouse pointer)
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1314#comment4192

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you
did not expect this message or don't want to receive mails in future, you can change your notification
settings at the URL shown above.

awesome | 20 Nov 14:14 2014

[awesome bugs] #1314 - Chromium tabs on secondary screens

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1314 - Chromium tabs on secondary screens
User who did this - Von Random (von)

----------
> every other window manager I've tried works fine (i3, openbox, xfwm4, kwin, dwm).
i3 and dwm were tiling last time I checked
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1314#comment4191

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you
did not expect this message or don't want to receive mails in future, you can change your notification
settings at the URL shown above.

awesome | 20 Nov 11:05 2014

[awesome bugs] #1314 - Chromium tabs on secondary screens

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1314 - Chromium tabs on secondary screens
User who did this - yauhen (actionless)

----------
can u compare the behavior against awesome wm and other tiling wm-s?

i suspect it's a chrom.* issue
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1314#comment4190

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you
did not expect this message or don't want to receive mails in future, you can change your notification
settings at the URL shown above.

awesome | 20 Nov 10:44 2014

[awesome bugs] #1314 - Chromium tabs on secondary screens

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened.  Details are below. 

User who did this - Von Random (von) 

Attached to Project - awesome
Summary - Chromium tabs on secondary screens
Task Type - Bug Report
Category - Core
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Normal
Reported Version - 3.5.5
Due in Version - Undecided
Due Date - Undecided
Details - Chromium tabs will not reattach to the windows outside the main screen on multi monitor setups.

The problem is unique to Awesome WM, every other window manager I've tried works fine (i3, openbox, xfwm4,
kwin, dwm).

How to reproduce: open a Chromium-based browser window (Chromium, Google Chrome and Yandex Browser Beta
have this issue, but Opera Beta does not), then move it to the secondary screen, grab a tab and drag it. That
will spawn a new window with only that tab attached. Any attempts to move that tab back into the original
window within the secondary screen will fail, but if you move both windows to the main screen, the tab will
successfully reattach.

% uname -a
(Continue reading)

awesome | 20 Nov 08:28 2014

[awesome bugs] #1313 - tags file (Makefile): does not contain full name of functions

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened.  Details are below. 

User who did this - Daniel Hahler (blueyed) 

Attached to Project - awesome
Summary - tags file (Makefile): does not  contain full name of functions
Task Type - Feature Request
Category - Build system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Normal
Reported Version - git/master
Due in Version - Undecided
Due Date - Undecided
Details - The "tags" target (generated via "make tags") does not contain the full name of the functions.

Instead of:

  tag.incmwfact	lib/awful/tag.lua.in	/^function tag.incmwfact(add, t)$/;"	f	language:Lua

it should be:

  awful.tag.incmwfact	lib/awful/tag.lua.in	/^function tag.incmwfact(add, t)$/;"	f	language:Lua

There is an active fork of exuberants-ctags (https://github.com/fishman/ctags), which would likely
accept a patch for this, but I am unsure how this should get addressed.
(Continue reading)

awesome | 16 Nov 14:14 2014

[awesome bugs] #1312 - Initial fullscreen with mpv not working (Attachment added)

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1312 - Initial fullscreen with mpv not working
User who did this - Sven Greiner (SammysHP)

----------
Output of xprop for the client. It's the same output with initial fullscreen and after toggling.
----------

One or more files have been attached.

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1312#comment4189

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you
did not expect this message or don't want to receive mails in future, you can change your notification
settings at the URL shown above.

awesome | 16 Nov 14:09 2014

[awesome bugs] #1312 - Initial fullscreen with mpv not working

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened.  Details are below. 

User who did this - Sven Greiner (SammysHP) 

Attached to Project - awesome
Summary - Initial fullscreen with mpv not working
Task Type - Bug Report
Category - Core
Status - Unconfirmed
Assigned To - 
Operating System - Linux
Severity - Low
Priority - Normal
Reported Version - 3.5.5
Due in Version - Undecided
Due Date - Undecided
Details - Play a video with mpv in fullscreen mode:

$ mpv --fs <some video file>

You'll notice that the wibox is still visible and the fullscreen video is moved down by exactly the height of
the wibox.
Toggle the fullscreen mode by pressing f twice. Now the video covers the whole screen.

During my research I found this comment, maybe it is related: https://github.com/mpv-player/mpv/issues/431#issuecomment-58489165

> Note that we do indeed use a different method for the initial fullscreen setting, because 
> that allows us to atomically create a fullscreen window without flicker. We do this by 
(Continue reading)


Gmane