Still, I cannot understand the point of this feature...
This means you need two different shortcuts for the same thing :
- one to display the tag, if the tag you want to display in the
current screen is owned by this screen
- one to move a tag from another screen to the current screen, otherwise
M
On Thu, Apr 08, 2010 at 06:24:19PM +0200, Gabriel Fornaeus wrote:
> This is actually a feature. You can move windows back and forth between
> your screens with modkey+o in the default config. Not sharing tags is
> great, since you can easily view different tags on each monitor and
> switch tags on
> Sorry, I linked to the wrong commit, but the message was OK, and that
> commit is present in 3.4.4. If you are willing to run a test it would be
> much appreciated, just check (this time correct link hopefully) the
> changes in that commit:
>
> http://git.naquadah.org/?p=awesome.git;a=commit;h=3e
On Thu, Apr 08, 2010 at 05:21:29PM +0200, Emmanuel Beffara wrote:
> [...]
> By the way, this reminds me of a question: what is the proper way to
> start programs at startup?
> [...]
The proper way (tm) would be to use a custom ~/.xsession. AFAIK, gdm
(and kdm, and wdm, and slim, and ...) allow se
This is actually a feature. You can move windows back and forth between
your screens with modkey+o in the default config. Not sharing tags is
great, since you can easily view different tags on each monitor and
switch tags on one monitor but not the other and so forth.
On Thu, Apr 08, 2010 at 04:44:
On Thu, 8 Apr 2010, Yves Frederix wrote:
> The commit you refer to seems to be quite recent. I'll give the latest
> version from git a try later tonight.
Sorry, I linked to the wrong commit, but the message was OK, and that
commit is present in 3.4.4. If you are willing to run a test it would b
Hi,
> I was the last one that touched the awful.autofocus code, fixed a user
> reported bug, in commit
> http://git.naquadah.org/?p=awesome.git;a=commit;=3e6d333a
>
> awful.autofocus: improve client focus with multiple screens
>
> Changing screen focus to an empty tag leaves focus on a client on
Le 06/04/2010 15:26, Fernando C.V. a écrit :
One problem I've perceived, though, is that some applications, like
nm-applet, won't store properly the passwords configuration when I'm
using awesome as a DE. I believe this is related to gnome-keyring, but
I'm not sure what to do to fix this, since e
On Thu, 8 Apr 2010, Yves Frederix wrote:
> I noticed some unexpected behavior in a dual-monitor setup. When
> moving a floating window from one monitor to the other (using
> modifier+mouse drag), the focus on the second screen jumps to the
> previously focused application on the screen. Or in o
Hi,
I have been looking at awesome, and consider switching to this window manager.
But, after a few tests, I find out that in a dual-screen setup, each
screen has its sets of tags, and therefore, a window belongs to one
screen.
Is there a way to share the set of tags between the screens ? (as is
Hi all,
I noticed some unexpected behavior in a dual-monitor setup. When
moving a floating window from one monitor to the other (using
modifier+mouse drag), the focus on the second screen jumps to the
previously focused application on the screen. Or in other words, the
window being dragged loses i
Hello,
I want to add some keybindings like:
awful.key( {}, "Menu", "a",
function ()
local screen = mouse.screen
if tags[screen][10] then
awful.tag.viewonly(tags[screen][10])
end
Hello,
I want to add some keybindings like:
awful.key( {}, "Menu", "a",
function ()
local screen = mouse.screen
if tags[screen][10] then
awful.tag.viewonly(tags[screen][10])
end
13 matches
Mail list logo
