RE: UPS Status [NUT]
Hi Aleksei, I looked at most of the battery monitor widgets but the seemed to be for Laptops The UPS is external (before) the PC and "NUT" runs to get status (upsc) Just as an FYI, upower returns the following wether the UPS is powered or on battery... Daemon: daemon-version: 0.9.23 can-suspend: no can-hibernate: no on-battery: no on-low-battery: no lid-is-closed: no lid-is-present: no is-docked: yes Wondering if anyone has a widget the processes the info "upsc" provides (or do I write one) Wondering if there is a way to get Awesome to show system messages from a script as notifications Regards, Dave -Original Message- From: Aleksei Fedotov [mailto:l...@cfotr.com] Sent: Tuesday, 26 July 2016 11:01 PM To: David Sorkovsky <davidsorkov...@hotmail.com> Cc: awesome@naquadah.org Subject: Re: UPS Status [NUT] Hi David, Could you check if upowerd could see your UPS ? Run 'upower -d' in your terminal and look if it has information about UPS status. If upower provides information about UPS status, you can use widget https://github.com/lexa/awesome_upower_battery . It grabs information from upowerd via DBus and displays battery status and charge percentage. On 7/26/16, David Sorkovsky <davidsorkov...@hotmail.com> wrote: > Hi All, > > Anyone display information on a UPS [I am using NUT to monitor it]? > > Wanted: Widget? > Notification popup? > > > Regards, > > Dave > > > --- > This email has been checked for viruses by Avast antivirus software. > https://www.avast.com/antivirus > > -- Kind Regards, Aleksei --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
UPS Status [NUT]
Hi All, Anyone display information on a UPS [I am using NUT to monitor it]? Wanted: Widget? Notification popup? Regards, Dave --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
RE: advice
G'Day Ray, As a point of introduction, I use awesome for pretty much all the reasons you note and most have been answered, but I'd like to add that you need not be put off if you are NOT looking for a tiling window manager. I don't often use the advance features - I usually just use "Floating" most of the time with one app per tag Thanks to the lua config I have some applications that automatically maximize to a "tag" which I then use just like it was on its own "desktop" PS: For multiple monitors I played a bit and ended up with a really simply xorg.conf - Two monitors with a "virtual" desktop of the total area [and you can even place floating windows so they overlap both screens (not that you'd really want to) Regards Dave _ From: Ray Andrews [mailto:rayandr...@eastlink.ca] Sent: Wednesday, 9 September 2015 3:59 AM To: awesome@naquadah.org Subject: advice Gentlemen, I use xfce, it's fine, but I want something lighter.B All I really want is the xfwm part of it, and even that window manager has its defects. I have dual monitors, and I can't drag anything between monitors.B I hate trying to configure things using those stupid pop up dialogue boxes.B I'd like text configuration files that I can edit, save, backup and restore. Awesome seems well spoken of.B What can you guys tell me?B I can't think what to specifically ask.B It would be nice if it worked sensibly out of the box.B I don't need fancy effects.B I want windows on screens that I can resize, maximize, minimize, etc.B Nice if they snap to borders to avoid wasted space.B Xfce gives normally six or so desktops than you can change to, that's good.B The mouse has to work.B I need custom keyboard shortcuts.B Basically nothing strange.B I don't want to have to spend six months learning Lua.B I want a simple, predictable, configurable WM that is usable but doesn't bother me with bells and whistles. Advice?
RE: show a wibox with a timeout
Are you aware of... naughty.notify({ title=Hi, text=Howdy, timeout = 3
})
-Original Message-
From: cedlemo [mailto:cedl...@gmx.com]
Sent: Sunday, 21 December 2014 1:04 AM
To: awesome@naquadah.org
Subject: show a wibox with a timeout
Hi,
I want to display a wibox (with my taglist) just for 2 or 3 seconds when
the current desktop change.
I have already a working solution but I would like to know if there is
another way to do it.
here is the function that I use:
function taglist_wibox_show_hide(box)
mytimer = timer({ timeout = 0 })
mytimer:connect_signal(timeout, function ()
print(show)
box.visible=true
mytimer:stop()
end
)
mytimer:start()
mytimer1 = timer({ timeout = 2 })
mytimer1:connect_signal(timeout, function ()
print(hide)
box.visible=false
mytimer1:stop()
end
)
mytimer1:start()
end
Any ideas ?
cedlemo
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
RE: Remove titlebar in some applications (awesome 3.5)
I'm still on the Ubuntu Server 14.04 package version of Awesome (3.4.15),
but for what it's worth...
I used to do this (may work for you)...
cut
client.add_signal(manage, function (c, startup)
cut
if not startup then
-- Test
-- naughty.notify({ title=Signal: .. c.name,
text=c.class .. , .. c.type .. , .. c.instance, timeout = 5 })
-- Add a titlebar
if c.name ~= mythfrontend.real and c.class ~=
Remmina then
awful.titlebar.add(c, { modkey = modkey })
end
cut
Thanks to your email I now do this...
-- Add titlebar to windows
cut
{ rule = {},
except_any = { name = { mythfrontend.real } },
callback = awful.titlebar.add
}
cut
-Original Message-
From: Zum Testen [mailto:zum.tes...@yahoo.de]
Sent: Wednesday, 15 October 2014 8:15 PM
To: awesome@naquadah.org
Subject: Remove titlebar in some applications (awesome 3.5)
I would like to exclude some of my applications to have a title bar. For
example, chromium should have no title bar but all other applications should
have one.
I found this thread:
https://bbs.archlinux.org/viewtopic.php?id=142862
Unfortunately, the solutions seem to be a little bit outdated. I couldn't
port them to awesome 3.5
What would be the appropriate way to remove the title bar for specific
applications in awesome 3.5?
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
RE: Automatically open processes on startup
Have you considered Rules?
Default rc.lua - Note the firefox entry.
-- {{{ Rules
awful.rules.rules = {
-- All clients will match this rule.
{ rule = { },
properties = { border_width = beautiful.border_width,
border_color = beautiful.border_normal,
focus = true,
keys = clientkeys,
buttons = clientbuttons } },
{ rule = { class = MPlayer },
properties = { floating = true } },
{ rule = { class = pinentry },
properties = { floating = true } },
{ rule = { class = gimp },
properties = { floating = true } },
-- Set Firefox to always map on tags number 2 of screen 1.
-- { rule = { class = Firefox },
-- properties = { tag = tags[1][2] } },
}
_
From: Maytar Byle [mailto:mayt...@gmail.com]
Sent: Monday, 6 October 2014 12:06 AM
To: awesome@naquadah.org
Subject: Automatically open processes on startup
Hello!
I'm running awesome 3.4 and i wanted to add a feature that on startup - a
list of processes will be loaded to their designated tags.
For example: terminal will be loaded to the first tag, music player will be
loaded to the fifth etc..
The code i added to rc.lua goes like this:
tag_apps = { { terminal, terminal } , { terminal } }
for i = 1, #tag_apps do
for j = 1, #tag_apps[i] do
awful.util.spawn(tag_apps[i][j])
--awful.client.movetotag(i, c)
end
end
teminal is the terminal command.
My problems are those:
1. spawn makes the xserver crash and i don't understand why.
2. Even if it would work, how do i get the client object for the process i
just opened so i can move it to the correct tag with movetotag?
Thank you!
Command to get current window to fill screen area while in floating layout
Hi All, I'm looking for a command to get the current window [with a title bar] to fill the screen area [below the tray] while in a floating layout?
RE: Command to get current window to fill screen area while in floating layout
That was it - can't believe I missed it - thanks! _ From: William Tomlinson [mailto:watomlin...@gmail.com] Sent: Saturday, 27 September 2014 11:58 PM To: David Sorkovsky Cc: awesome Subject: Re: Command to get current window to fill screen area while in floating layout On Sep 27, 2014 9:14 AM, David Sorkovsky davidsorkov...@hotmail.com wrote: Hi All, I'm looking for a command to get the current window [with a title bar] to fill the screen area [below the tray] while in a floating layout? Mod + M would maximize the window in floating layout. Is that what you are looking for? -Will
RE: Awesome Menu Applicaions
Categorized / Grouped? Here's part of mine...
MythTVMenu ={
{ Play, mythfrontend },
{ Stop, sudo stop
mythtv-backend },
{ Start, sudo start
mythtv-backend },
{ Restart, sudo restart
mythtv-backend },
{ Setup, sudo
mythtv-setup }
}
TVMenu ={
{ MythTV, MythTVMenu },
{ XBMC, xbmc },
{ Kaffeine, kaffeine }
}
AwesomeMenu = {
{ Debian,
debian.menu.Debian_menu.Debian },
{ manual, terminal .. -e
man awesome },
{ edit config, editor_cmd
.. .. awful.util.getdir(config) .. /rc.lua },
{ edit theme, editor_cmd
.. .. awful.util.getdir(config) .. /theme.lua },
{ restart, awesome.restart
},
{ quit, awesome.quit }
}
mymainmenu = awful.menu({
items = {
{ Web Browser (Firefox), /usr/bin/firefox },
{ File Manager (Xfe), /usr/bin/xfe, /usr/share/pixmaps/xfe.xpm },
{ Drives, sudo gnome-disks },
{ Text Editor (from Xfe), /usr/bin/xfwrite, /usr/share/pixmaps/xfw.xpm
},
{ Terminal (from Xfe), terminal },
{ Mixer, terminal .. alsamixer },
{ VLC, myMenu4 },
{ TV, TVMenu },
{ awesome, AwesomeMenu, beautiful.awesome_icon }
}
})
-Original Message-
From: Kevin Clay [mailto:kclayengin...@cableone.net]
Sent: Sunday, 14 September 2014 6:47 PM
To: awesome@naquadah.org
Subject: Awesome Menu Applicaions
I have been through the wiki on installing Awesome for the first time
and I see screenshots in which the awesome menu has categorized lists of
applications. The wiki doesn't explain how to do this or if it supposed
to do this automagically. My menu doesn't show any applicaions and I was
wondering how to get it to do this.
Thanks.
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
RE: Windows opening on wrong screen
Hi Andre, I also had a lot of trouble getting my system just right. I did lots of playing with xorg.conf and with two screens from the built in graphics controller of my CPU and this is my final config (two monitors but just one screen)... Section Monitor Identifier HDMI1 VendorName Samsung ModelName ? Option PreferredMode 1920x1080 Option RightOf HDMI2 EndSection Section Monitor Identifier HDMI2 VendorName BenQ ModelName ? Option PreferredMode 1920x1080 Option LeftOf HDMI1 EndSection Section Device Identifier MotherboardVideo Driver intel VendorName Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) EndSection Section Screen Identifier Screen Device MotherboardVideo Monitor HDMI2 DefaultDepth24 SubSection Display Viewport0 0 Depth 24 Modes 1920x1080 1920x1080 Virtual 3840 1080 EndSubSection EndSection I got the identifiers from the xrandr info, so looking at yours, you'd probably have DisplayPort-0, HDMI-0 and DVI-0 where I have HDMI1 and HDMI2 Nice things was no Xinerama which seems to be the preferred way! -Original Message- From: Andre Naujoks [mailto:nauts...@gmail.com] Sent: Tuesday, 2 September 2014 5:18 PM To: David Palacio; awesome@naquadah.org Subject: Re: Windows opening on wrong screen On 02.09.2014 03:23, David Palacio wrote: El Lun 01 Sep 2014 11:15:36 Andre Naujoks escribió: Hi. I am just giving awesome a try and like it so far. I am on a debian sid with awesome version 3.4.15-1+b1. It has one quirk, where I think it is a bug. When I open a window (say a terminal with Mod4 + Return, but the application does not matter.), the window should apear on the current active screen. This works for two of my three screens, but not for the third. The same happens when I open a window via the right-mouse-click menu from the desktop, or when I use the top left button to bring up the menu. - I select the screen by either moving the mouse into it, or Mod4+Ctrl+j/k. - I start an application on my right-most screen and the window opens on my primary/center screen. I attached a screenshot of my layout, so you get an idea of what I am talking about. (the black stripes above the left and right screen are unused, i.e. the monitors end where the menu-bar is) As mentioned it works for the left and the center screen, but not for the right one. Am I doing something wrong or is this a bug? I am not familiar enough with lua or window managers at all to try my hand at this, but I can test and try patches. Regards Andre Hi Andre, As you mention three screens I suspect you may be using two separated GPUs at the same time in the same X screen. That is not well supported in Awesome 3.4. I used to use three screens on a PC with a NVidia and integrated Intel GPUs and ran into many problems with it. To improve my setup I made some modifications to Awesome. You can check and compile it at: https://github.com/dpalacio/awesome-randr-zaphod It works in Zaphod mode and with video drivers that support RandR extension. It does not support Xinerama. Hi David, Hm. I am not using two GPUs. Just one Radeon HD 6870 with four outputs, of which three are used. My other E-Mail in reply to Elv1313 contains my xorg.conf and an xrandr output. Maybe there is something borked there, but I didn't have such problems before. Regards Andre -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org. -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
RE: can't get to run skype
Hi Yuri, I also found issues with Skype not logging in - I updated to the latest and it has worked cleanly since. It seems that your version is the latest, so only think I can suggest is removing it (possibly installing an older one) and then re-installing. Regards Dave _ From: Yuri Kanivetsky [mailto:yuri.kanivet...@gmail.com] Sent: Sunday, 10 August 2014 6:42 AM To: awesome@naquadah.org Subject: can't get to run skype Hi, I've run awesome for the first time now. And the problem is that I can't get to run skype. I enter password, press Enter, it shows contact list for a second and then disappears. If run from terminal, it crashes with: Aborted (core dumped). I'm running ubuntu 13.10, skype 4.3.0.37-1 and awesome 3.4.15-1. Any thoughts? Regards, Yuri
RE: movetoscreen - still not having much luck...
Studied awful.client.lua...
--- Move a client to a screen. Default is next screen, cycling.
-- @param c The client to move.
-- @param s The screen number, default to current + 1.
function client.movetoscreen(c, s)
screen = screen or require(awful.screen)
local sel = c or capi.client.focus
if sel then
local sc = capi.screen.count()
if not s then
s = sel.screen + 1
end
if s sc then s = 1 elseif s 1 then s = sc end
sel.screen = s
screen.focus(s)
end
end
Tried to do the same to see what was happening...
awful.key({ modkey, }, o,
function (c)
local iScreen = c.screen + 1
if iScreen screen.count() then iScreen = 1 end
c.screen = iScreen
awful.screen.focus(iScreen)
local sNum = string.format(-= %d, %d, %d =-,
c.screen, iScreen, screen.count())
naughty.notify({ text = sNum })
end),
Client still wouldn't change screens!
Notify from screen 1 was -= 1, 2, 2 =-
Notify from screen 2 was -= 2, 1, 2 =-
What I did see was that the mouse focus actually worked as expected
(moved to the other screen)
One Confused Dave
awesome v3.4.11 (Pickapart)
• Build: Apr 2 2012 18:39:18 for x86_64 by gcc version 4.6.3 (buildd@crested)
• D-Bus support: ✔
-Original Message-
From: David Sorkovsky [mailto:davidsorkov...@hotmail.com]
Sent: Friday, 21 February 2014 7:02 PM
To: awesome@naquadah.org
Cc: 'Maxim Bulatov'
Subject: RE: movetoscreen
G'Day Maxim all,
Dual monitors both working well with Awesome - like the independence, but
sometimes I use the RHS for my laptop and want to move apps to the LHS at that
time.
Wondering if there is something I needed to setup in Awesome?
xrandr on LHS...
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
VGA1 disconnected (normal left inverted right x axis y axis)
HDMI1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 531mm
x 299mm
1920x1080 60.0*+
1680x1050 60.0
1600x900 60.0
1280x1024 75.0 60.0
1280x960 60.0
1280x800 59.8
1152x864 75.0
1280x720 60.0
1024x768 75.1 60.0
1024x576 60.0
832x62474.6
800x60075.0 60.3
640x48075.0 60.0
720x40070.1
DP1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
Xrandr on RHS...
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
VGA1 disconnected (normal left inverted right x axis y axis)
HDMI1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 531mm
x 299mm
1920x1080 60.0*+
1680x1050 60.0
1600x900 60.0
1280x1024 75.0 60.0
1280x960 60.0
1280x800 59.8
1152x864 75.0
1280x720 60.0
1024x768 75.1 60.0
1024x576 60.0
832x62474.6
800x60075.0 60.3
640x48075.0 60.0
720x40070.1
DP1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
Xorg.conf...
# Manually adjusted/combined from the below...
# X.org Configured
# nvidia-xconfig: X configuration file generated by nvidia-xconfig #
nvidia-xconfig: version 304.116
(buildmeister@swio-display-x86-rhel47-01) Mon Oct 28 21:46:08 PDT 2013
Section ServerLayout
Identifier Layout
Screen 0 Screen0 0 0
Screen 1 Screen2 RightOf Screen0
InputDeviceMouse0 CorePointer
InputDeviceKeyboard0 CoreKeyboard
EndSection
Section Files
# ModulePath /usr/lib/xorg/modules
# FontPath /usr/share/fonts/X11/misc
# FontPath /usr/share/fonts/X11/cyrillic
# FontPath /usr/share/fonts/X11/100dpi/:unscaled
# FontPath /usr/share/fonts/X11/75dpi/:unscaled
# FontPath /usr/share/fonts/X11/Type1
# FontPath /usr/share/fonts/X11/100dpi
# FontPath /usr/share/fonts/X11/75dpi
# FontPath /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType
# FontPath built-ins
EndSection
Section Module
# Load dbe
# Load dri2
# Load record
# Load extmod
# Load dri
# Load glx
EndSection
Section InputDevice
Identifier Keyboard0
Driver kbd
EndSection
Section InputDevice
Identifier Mouse0
Driver mouse
Option Protocol auto
RE: movetoscreen - still not having much luck...
Tried it - Just added Option Xinerama 1 to my layout - Solved I can work with that! Thanks Uki Regards Dave -Original Message- From: Uli Schlachter [mailto:psyc...@znc.in] Sent: Sunday, 23 February 2014 9:00 PM To: awesome@naquadah.org Subject: Re: movetoscreen - still not having much luck... Hi, On 23.02.2014 09:13, David Sorkovsky wrote: [...] Dual monitors both working well with Awesome - like the independence, but sometimes I use the RHS for my laptop and want to move apps to the LHS at that time. Wondering if there is something I needed to setup in Awesome? xrandr on LHS... Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 VGA1 disconnected (normal left inverted right x axis y axis) HDMI1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 531mm x 299mm 1920x1080 60.0*+ 1680x1050 60.0 1600x900 60.0 1280x1024 75.0 60.0 1280x960 60.0 1280x800 59.8 1152x864 75.0 1280x720 60.0 1024x768 75.1 60.0 1024x576 60.0 832x62474.6 800x60075.0 60.3 640x48075.0 60.0 720x40070.1 DP1 disconnected (normal left inverted right x axis y axis) HDMI2 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) Xrandr on RHS... Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 VGA1 disconnected (normal left inverted right x axis y axis) HDMI1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 531mm x 299mm 1920x1080 60.0*+ 1680x1050 60.0 1600x900 60.0 1280x1024 75.0 60.0 1280x960 60.0 1280x800 59.8 1152x864 75.0 1280x720 60.0 1024x768 75.1 60.0 1024x576 60.0 832x62474.6 800x60075.0 60.3 640x48075.0 60.0 720x40070.1 DP1 disconnected (normal left inverted right x axis y axis) HDMI2 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) Welcome to 1987. You have two different protocol screens. They are completely independent. They only share the keyboard and the mouse. That's it. This does especially mean that you cannot move windows between screens. (This is a limitation of X11!) People were unhappy and Xinerama was invented and included in X11R6v4.0. This makes multiple screens look to the X11 protocol like a single, big one. Since from the protocol's point of view there is now just a single screen, windows can now move around freely. (At least I think that this is what's going on, since you are giving us two times the same xrandr output and claim that it is for the different screens...) Xorg.conf... # Manually adjusted/combined from the below... # X.org Configured # nvidia-xconfig: X configuration file generated by nvidia-xconfig # nvidia-xconfig: version 304.116 (buildmeister@swio-display-x86-rhel47-01) Mon Oct 28 21:46:08 PDT 2013 Section ServerLayout Identifier Layout Screen 0 Screen0 0 0 Screen 1 Screen2 RightOf Screen0 Yeah, zaphod mode, not Xinerama. InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection [...] Cheers, Uli -- alanc I think someone had a Xprint version of glxgears at one point, but benchmarking how many GL pages you can print per second was deemed too silly to merge -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org. -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
RE: movetoscreen
MonitorMonitor0
SubSection Display
Viewport 0 0
Depth 1
EndSubSection
SubSection Display
Viewport 0 0
Depth 4
EndSubSection
SubSection Display
Viewport 0 0
Depth 8
EndSubSection
SubSection Display
Viewport 0 0
Depth 15
EndSubSection
SubSection Display
Viewport 0 0
Depth 16
EndSubSection
SubSection Display
Viewport 0 0
Depth 24
# Modes 1920x1080
EndSubSection
EndSection
Section Screen
Identifier Screen2
Device Card2
MonitorMonitor2
SubSection Display
Viewport 0 0
Depth 1
EndSubSection
SubSection Display
Viewport 0 0
Depth 4
EndSubSection
SubSection Display
Viewport 0 0
Depth 8
EndSubSection
SubSection Display
Viewport 0 0
Depth 15
EndSubSection
SubSection Display
Viewport 0 0
Depth 16
EndSubSection
SubSection Display
Viewport 0 0
Depth 24
# Modes 1920x1080
EndSubSection
EndSection
-Original Message-
From: Maxim Bulatov [mailto:dvenum...@gmail.com]
Sent: Friday, 21 February 2014 1:05 PM
To: David Sorkovsky
Subject: Re: movetoscreen
I had same problem with separated screen. I could not move mouse between
screens. Solution was easier to reconfigure xorg. Now, I have one big
virtual screen from two videocards in system and two screen on the awesome
wm level.
Show your xrandr output and xorg config options and describe your hardware
environment.
On Thu, Feb 20, 2014 at 10:00:54PM +1100, David Sorkovsky wrote:
I'm not having much luck with...
awful.key({ modkey, }, o, awful.client.movetoscreen
),
awful.key({ modkey, Shift }, F1, function (c)
awful.client.movetoscreen(c, 1) end),
awful.key({ modkey, Shift }, F2, function (c)
awful.client.movetoscreen(c, 2) end),
All that happens on any keypress is that the mouse jumps to the top
left corner of the current window
Regards Dave
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
movetoscreen
I'm not having much luck with...
awful.key({ modkey, }, o, awful.client.movetoscreen
),
awful.key({ modkey, Shift }, F1, function (c)
awful.client.movetoscreen(c, 1) end),
awful.key({ modkey, Shift }, F2, function (c)
awful.client.movetoscreen(c, 2) end),
All that happens on any keypress is that the mouse jumps to the top left
corner of the current window
Regards Dave
RE: remmina in awesone - Different behaviour for RDP of Windows XP and Windows 7
Thanks! I hadn't tried that - Now I have - It worked! To get it to happen automagically I added this in the signals... -- Automatically float certain windows if c.name == david2 then awful.client.fullscreen.set(c, true) end Then I realised it was my own fault as I had actually caused it myself when I'd done this some time back... -- Adjust the geometry settings so windows do not cover the tray if not (c.name == david or c.name == Guake!) then local geometry = c:geometry() if geometry.y mywibox[c.screen]:geometry().y + mywibox[c.screen]:geometry().height then geometry.y = mywibox[c.screen]:geometry().y + mywibox[c.screen]:geometry().height + c.border_width c:geometry(geometry) end end Doh! Added or c.name == david2 and it gave me what I'd expected. Thanks for the reply as it got me back on track! PS: Must investigate if fullscreen is a better choice or if the geometry idea was a good one - comments welcome! Thanks again! -Original Message- From: m...@enric.me [mailto:m...@enric.me] Sent: Wednesday, 13 February 2013 3:33 AM To: davidsorkov...@hotmail.com Subject: Re: remmina in awesone - Different behaviour for RDP of Windows XP and Windows 7 Hey David, Have you tried mod4 + f? It's the default keybinding for fullscreen. You can also setup a rule for that. Not posting to the list because i'm on my phone, and it doesn't support mailing lists. Cheers --- Original message --- From: David Sorkovsky davidsorkov...@hotmail.com To: Sent: 11.2.'13, 12:02 Hi All, I've been using an Windows XP Virtual Machine for quite a while now. I run it headless and access it through RDP using remmina, running in Awesome - All great - Especially that when I put remmina into full screen mode as it uses the entire display, completely covering the tray. Then I just use Mod 4 # to change to another Awesome pane/desktop/? and so on. Now for the strange/interesting part. I just setup a Windows 7 VM in Virtualbox but this time, running headless and using remmina to RDP in, fullscreen mode does NOT cover the entire screen, but leaves the tray (only uses the viewport?) Anyone know where I should start to look to adjust the Windows 7 VM to use the full screen rather than just the viewport? Virtualbox, virtualbox client extensions, remmina, awesome, X, other??? Thanks in advance Dave -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
remmina in awesone - Different behaviour for RDP of Windows XP and Windows 7
Hi All, I’ve been using an Windows XP Virtual Machine for quite a while now. I run it headless and access it through RDP using remmina, running in Awesome – All great – Especially that when I put remmina into “full screen mode” as it uses the entire display, completely covering the tray. Then I just use Mod 4 # to change to another Awesome pane/desktop/? and so on. Now for the strange/interesting part… I just setup a Windows 7 VM in Virtualbox but this time, running headless and using remmina to RDP in, fullscreen mode does NOT cover the entire screen, but leaves the tray (only uses the viewport?) Anyone know where I should start to look to adjust the Windows 7 VM to use the full screen rather than just the viewport? Virtualbox, virtualbox client extensions, remmina, awesome, X, other??? Thanks in advance Dave
Skype / Tray Status Icon
Hi All, A quick question - Yesterday I had an icon in my tray for Skype [ie: minimized], now today it has gone (but the main process is definitely running) - Anyone seen this or have any suggestions on what I do to get it back? PS: Using Ubuntu Server [12.04.1] with awesome from the ubuntu repository [3.4.11] PPS: Only change I can think of was to apply the latest updates that (from memory) were man firefox PPPS: I also run remmina guake ane their icons appear Regards, Dave -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
RE: [ANNOUNCE] awesome 3.5-rc1 released (was: [ANNOUNCE] awesome 3.4-rc1 released)
Thanks for you constant effort - it is greatly appreciated! Regards, David -Original Message- From: Uli Schlachter [mailto:psyc...@znc.in] Sent: Sunday, 25 November 2012 1:48 AM To: awesome-devel list; awesome Subject: [ANNOUNCE] awesome 3.5-rc1 released (was: [ANNOUNCE] awesome 3.4-rc1 released) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi everyone, On 11.09.2009 14:05, Julien Danjou wrote: With a good month late, here comes 3.4-rc1. With a good two years late, here comes 3.5-rc1. There's an amazing number of changes, but many are internals ones, so you won't notice them.[...] There's an astonishing number of changes. Also, we did some changes to make awesome future-proof. With lua 5.2, module() was deprecated in lua. Awesome no longer uses this function. However, this has user-visible effects. You now need to explicitly assign modules to global variables: local awful = require(awful) Some things from the default rc.lua have been moved into awful to ease the configuration file management. The default rc.lua is 110 lines lighter now. The rc.lua is 50 lines longer now. 40 lines of that is due to a titlebar rewrite. Instead of forcing some kind of titlebars on the user, titlebars are now configured similar to wiboxes. The new widget layout system is also in place. Everyone will hate me for replacing the widget system again, but I do like the result. Due to this, everything works differently now. On the plus side, you won't need to use mywidget.widget ever again. :-) There's obviously a number of changes all over the place. I don't have the list in mind of course, so feel free to dig into the changelog. [...] The same applies to this release, too! Again, there is a wiki page for documenting some changes that affect configurations. Feel free to update it with any kind of information which you would have hoped to find here, but had to figure out the hard way (= asking me). http://awesome.naquadah.org/wiki/Awesome_3.4_to_3.5 As always, we all here at breaking-your-config-WMs would like to thank all contributors. Without your bug reports, patches, ideas and good questions, this window manager would suck a lot more than it already does. One thing I want to highlight: A total of 77 different people wrote patches for this release! Have fun! Uli awesome version 3.5-rc1 has been released. It is available from: tar.xz: http://awesome.naquadah.org/download/awesome-3.5-rc1.tar.xz md5: 42b76ed6a60ca376e1e0afb859986645 sha1: 2ab103a0a9675468f1dafc35e3df756e3d31b20b tar.bz2: http://awesome.naquadah.org/download/awesome-3.5-rc1.tar.bz2 md5: 1be1cb43adbc7242a6c53d3cc01a62bd sha1: 8c9b558cfa9293453fb1befda9ac06b365e15df2 number of changes - - 820 number of commiters - --- 77 shortlog - Uli Schlachter (444): wibox: Set a proper back pixel Set a wibox' bit gravity to NorthWest. wibox: make sure no garbage is painted to the screen wibox: check if a wibox' window exists before modifying it Wibox: Check if a window exists before changing it Fix a invalid pointer crash bug image: Use imlib2's image cache Make it easier to change the default layout Implement the GetCapabilities call in naughty Handle synthetic UnmapNotify events Revert Handle synthetic UnmapNotify events Handle synthetic UnmapNotify events *correctly* client_focus_update(): Balance the lua stack property.c: Don't leave stuff on the lua stack Check for UNMAPPED instead of UNVIEWABLE Use WM_STATE_NORMAL as default awesome.spawn(): Return the PID Update API docs for recent change to spawn Check for xwininfo before using it awful.menu.clients: Raise the newly focused client Tasklist: Add some missing parentheses Remove _NET_WM_DESKTOP when client got no tags Handle _NET_WM_DESKTOP more intelligently Remove invalid variable usage Update the tasklist when a client's icon changes xwindow_set_state(): Use uint32_t instead of long Reorder some code for fullscreening windows Tasklist: Listen to the correct signals Add systray windows to the save-set Don't reparent systray windows on exit Add all managed client windows to the safe set Don't manually unban all windows on exit Handle errors in the config better Read a textbox' text correctly textbox: Throw a lua error on invalid markup Naughty: Catch invalid markup in notifications Clear a draw_text_context_t during wipe() Move wibox_systray_kickout() up Kick out the systray when wiping a wibox Add a comment to XCB_NONE for sibling Avoid some flickering when a new window opens Split up screen_scan() Screen: Only use Xrandr if it provides data Ignore size hints on fullscreen windows Minor cleanup Fix a minor ICCCM incompatibility Fix some
RE: [ANNOUNCE] awesome 3.5-rc1 released (was: [ANNOUNCE] awesome 3.4-rc1 released)
Thanks for you constant effort - it is greatly appreciated! Regards, David -Original Message- From: Uli Schlachter [mailto:psyc...@znc.in] Sent: Sunday, 25 November 2012 1:48 AM To: awesome-devel list; awesome Subject: [ANNOUNCE] awesome 3.5-rc1 released (was: [ANNOUNCE] awesome 3.4-rc1 released) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi everyone, On 11.09.2009 14:05, Julien Danjou wrote: With a good month late, here comes 3.4-rc1. With a good two years late, here comes 3.5-rc1. There's an amazing number of changes, but many are internals ones, so you won't notice them.[...] There's an astonishing number of changes. Also, we did some changes to make awesome future-proof. With lua 5.2, module() was deprecated in lua. Awesome no longer uses this function. However, this has user-visible effects. You now need to explicitly assign modules to global variables: local awful = require(awful) Some things from the default rc.lua have been moved into awful to ease the configuration file management. The default rc.lua is 110 lines lighter now. The rc.lua is 50 lines longer now. 40 lines of that is due to a titlebar rewrite. Instead of forcing some kind of titlebars on the user, titlebars are now configured similar to wiboxes. The new widget layout system is also in place. Everyone will hate me for replacing the widget system again, but I do like the result. Due to this, everything works differently now. On the plus side, you won't need to use mywidget.widget ever again. :-) There's obviously a number of changes all over the place. I don't have the list in mind of course, so feel free to dig into the changelog. [...] The same applies to this release, too! Again, there is a wiki page for documenting some changes that affect configurations. Feel free to update it with any kind of information which you would have hoped to find here, but had to figure out the hard way (= asking me). http://awesome.naquadah.org/wiki/Awesome_3.4_to_3.5 As always, we all here at breaking-your-config-WMs would like to thank all contributors. Without your bug reports, patches, ideas and good questions, this window manager would suck a lot more than it already does. One thing I want to highlight: A total of 77 different people wrote patches for this release! Have fun! Uli awesome version 3.5-rc1 has been released. It is available from: tar.xz: http://awesome.naquadah.org/download/awesome-3.5-rc1.tar.xz md5: 42b76ed6a60ca376e1e0afb859986645 sha1: 2ab103a0a9675468f1dafc35e3df756e3d31b20b tar.bz2: http://awesome.naquadah.org/download/awesome-3.5-rc1.tar.bz2 md5: 1be1cb43adbc7242a6c53d3cc01a62bd sha1: 8c9b558cfa9293453fb1befda9ac06b365e15df2 number of changes - - 820 number of commiters - --- 77 shortlog - Uli Schlachter (444): wibox: Set a proper back pixel Set a wibox' bit gravity to NorthWest. wibox: make sure no garbage is painted to the screen wibox: check if a wibox' window exists before modifying it Wibox: Check if a window exists before changing it Fix a invalid pointer crash bug image: Use imlib2's image cache Make it easier to change the default layout Implement the GetCapabilities call in naughty Handle synthetic UnmapNotify events Revert Handle synthetic UnmapNotify events Handle synthetic UnmapNotify events *correctly* client_focus_update(): Balance the lua stack property.c: Don't leave stuff on the lua stack Check for UNMAPPED instead of UNVIEWABLE Use WM_STATE_NORMAL as default awesome.spawn(): Return the PID Update API docs for recent change to spawn Check for xwininfo before using it awful.menu.clients: Raise the newly focused client Tasklist: Add some missing parentheses Remove _NET_WM_DESKTOP when client got no tags Handle _NET_WM_DESKTOP more intelligently Remove invalid variable usage Update the tasklist when a client's icon changes xwindow_set_state(): Use uint32_t instead of long Reorder some code for fullscreening windows Tasklist: Listen to the correct signals Add systray windows to the save-set Don't reparent systray windows on exit Add all managed client windows to the safe set Don't manually unban all windows on exit Handle errors in the config better Read a textbox' text correctly textbox: Throw a lua error on invalid markup Naughty: Catch invalid markup in notifications Clear a draw_text_context_t during wipe() Move wibox_systray_kickout() up Kick out the systray when wiping a wibox Add a comment to XCB_NONE for sibling Avoid some flickering when a new window opens Split up screen_scan() Screen: Only use Xrandr if it provides data Ignore size hints on fullscreen windows Minor cleanup Fix a minor ICCCM incompatibility Fix some
RE: What should titlebars be like? (was: Release next major version - how bad could it be?)
The contents for me would be... High Priority: Name Close, Medium Priority: Maximize Minimize, Low Priority: Icon. Indication of mode of the window would probably be nice as well (Medium). While mouse click on the window with a key press can achieve the same purpose, clicking on the titlebar to drag a floating window is my most common action. Regards Dave David Sorkovsky +61 468 478 438 Date: Sun, 21 Oct 2012 20:47:16 +0200 From: psyc...@znc.in To: awesome@naquadah.org Subject: What should titlebars be like? (was: Release next major version - how bad could it be?) On 14.10.2012 16:12, Alexander Yakushev wrote: [...] In order to start writing real titlebar widgets first we should decide what for people want titlebars in first place. Minimize/maximize/close buttons? Moving/resizing windows by titlebar? Something else, more tiling related? This is a question to those who want titlebars in Awesome. Ping? No one wants titlebars? Or do you just want empty titlebars? That'd be easy to implement... Uli -- my $key = \x49\x03\x93\x08\x19\x94\x96\x94\x28\x93\x83\x04\x68\x28\xa8\xf5. \x0a\xb9\x94\x02\x45\x81\x93\x1f\xbc\xd7\xf3\xad\x93\xf5\x32\x93; my $cipher = Crypt::Rijndael-new( $key, Crypt::Rijndael::MODE_ECB() ); my $plain = $ciper-decrypt($daten); -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
RE: Any key binding to collapse the a menu?
Awesome Bryan - Thanks!
I've updated my rc.lua with it just so that I can simply press escape to
close the menu! Cursor keys work as well, but the escape key was the one I
really wanted ;-)
One minor change though - It worked better for me without the following
line...
mylauncher:buttons(),
Cheers,
Dave
-Original Message-
From: Bryan Gardiner [mailto:b...@khumba.net]
Sent: Sunday, 29 July 2012 5:44 AM
To: awesome@naquadah.org
Subject: Re: Any key binding to collapse the a menu?
On Sat, 28 Jul 2012 18:53:24 +0100
Javier Garcia tirengar...@gmail.com wrote:
Hi,
as you know by default there is a menu on the upper left corner that
show the apps.
Is there any key binding to collapse that menu after open it with the
mouser?
Javi
Hi Javier,
I'm looking at my Awesome 3.4.9 files, so forgive me if there are any
differences to your version.
There are three ways to open the app menu: clicking on the launcher in the
top-left, right-clicking on the desktop, or Mod+w. By default
Mod+w allows keys to be used to navigate the menu, whereas the other
two don't. But we can change this!
Right-clicking on the desktop is easy to change. Search for
root.buttons(awful.util.table.join(
awful.button({ }, 1, function () mymainmenu:toggle() end),
in your rc.lua and change toggle() to toggle({ keygrabber = true }). To
make the launcher grab keys as well, we can change this:
mylauncher = awful.widget.launcher({ image =
image(beautiful.awesome_icon),
menu = mymainmenu })
to this:
mylauncher = awful.widget.launcher({ image =
image(beautiful.awesome_icon),
command = })
mylauncher:buttons(awful.util.table.join(
mylauncher:buttons(),
awful.button({ }, 1, function ()
mymainmenu:toggle({ keygrabber = true })
end)))
Then, right-arrow can be used to open submenus and applications, and left
can go back and close.
Cheers,
Bryan
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
RE: change gnome-sound-applet icon in awesome
Try changing
This...
volumecfg.mixercommand( sset .. volumecfg.channel ..
toggle)
To this...
volumecfg.mixercommand( sset .. volumecfg.channel .. toggle)
PS: Here's my version which has 4 different icons depending on the level,
click toggles mute, wheel up/down over icon changes volume tool tip gives
actual value...
-- Volume widget
myvolume = {}
myvolume.cardid = 0
myvolume.channel = Headphone -- edit as appropriate [often Master]
myvolume.widget = widget({ type = imagebox, name = myvolume.widget })
myvolume.tooltip = awful.tooltip({ objects = { myvolume.widget },})
myvolume.mixercommand = function (command)
local fd =
io.popen(amixer -c .. myvolume.cardid .. .. command)
local status =
fd:read(*all)
fd:close()
local volume =
string.match(status, (%d?%d?%d)%%)
status =
string.match(status, %[(o[^%]]*)%])
if
string.find(status, on, 1, true) then
if
tonumber(volume) 50 then
myvolume.widget.image = image(awful.util.getdir(config) ..
/icons/audio-volume-low.png)
elseif
tonumber(volume) 100 then
myvolume.widget.image = image(awful.util.getdir(config) ..
/icons/audio-volume-medium.png)
else
myvolume.widget.image = image(awful.util.getdir(config) ..
/icons/audio-volume-high.png)
end
else
myvolume.widget.image = image(awful.util.getdir(config) ..
/icons/audio-volume-muted.png)
end
myvolume.tooltip:set_text(volume .. %)
end
myvolume.update = function () myvolume.mixercommand(sget ..
myvolume.channel) end
myvolume.up = function () myvolume.mixercommand(sset .. myvolume.channel
.. 1%+) end
myvolume.down = function () myvolume.mixercommand(sset ..
myvolume.channel .. 1%-) end
myvolume.toggle = function () myvolume.mixercommand(sset ..
myvolume.channel .. toggle) end
myvolume.widget:buttons({
button({ },
4, function () myvolume.up() end),
button({ },
5, function () myvolume.down() end),
button({ },
1, function () myvolume.toggle() end)
})
myvolume.update()
David Sorkovsky
+61 468 478 438
-Original Message-
From: pyLemon [mailto:leeway1...@gmail.com]
Sent: Tuesday, 17 July 2012 11:21 PM
To: Abhijeet R
Cc: awesome@naquadah.org; David Gomes
Subject: Re: change gnome-sound-applet icon in awesome
thanks for your quick reply Abhijeet, and thanks David Gomes. I have google
that page. haha, And I have seen someone has successful changed that icon.
but I don't know how..
this is my volume applet config
-- Volume widget
volumecfg = {}
volumecfg.cardid = 0
volumecfg.channel = Master
volumecfg.widget = widget({ type = textbox, name = volumecfg.widget,
align = right })
volumecfg_t = awful.tooltip({ objects = { volumecfg.widget },})
volumecfg_t:set_text(Volume)
-- command must start with a space!
volumecfg.mixercommand = function (command)
local fd = io.popen(amixer -c .. volumecfg.cardid .. command)
local status = fd:read(*all)
fd:close()
local volume = string.match(status, (%d?%d?%d)%%)
volume = string.format(span color='#1793d1'%3d/span,
volume)
status = string.match(status, %[(o[^%]]*)%])
if string.find(status, on, 1, true) then
volume = volume .. span color='#1793d1'%/span
else
volume = volume .. span color='#ff5656'M/span
end
volumecfg.widget.text = volume
end
volumecfg.update = function ()
volumecfg.mixercommand( sget .. volumecfg.channel) end
volumecfg.up = function ()
volumecfg.mixercommand( sset .. volumecfg.channel .. 2%+) end
volumecfg.down = function ()
volumecfg.mixercommand( sset .. volumecfg.channel .. 2%-) end
volumecfg.toggle = function ()
volumecfg.mixercommand( sset .. volumecfg.channel ..
toggle)
end
volumecfg.widget:buttons({
button({ }, 4, function () volumecfg.up() end),
button({ }, 5, function () volumecfg.down() end),
button({ }, 1, function () volumecfg.toggle() end)
})
volumecfg.update()
---EOF
the problem is , when I click the widget
RE: Installing awesome from git under Ubuntu precise?
So: But how can I use my new installation? I could specify the path to the new awesome in the xsessions file to start it, but I assume that awesome-client will then be the one installed system wide? If you want to switch between different versions, you could simply place links in the default directory... To use V1, insert links to the V1 directory. To use V2, replace V1 links with V2 links. Script the swapping of the links so you have a quick easy changeover -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
RE: Restore the Ctrl-Alt-Enter behaviour when using rdesktop
Same as Will, I use Remina with little to no problem ;-) Regards Dave David Sorkovsky home: +61 2 9945 3800 office: +61 2 9491 5255 mobile: +61 409 162 963 Date: Tue, 29 May 2012 09:26:51 -0500 Subject: Re: Restore the Ctrl-Alt-Enter behaviour when using rdesktop From: willru...@gmail.com To: awesome@naquadah.org I use remmina for remote desktop, as well as vnc when i have to, and I don't have the issues with Mod key switching, it works just fine. On Tue, May 29, 2012 at 9:22 AM, quanta quanta.li...@gmail.com wrote: Sorry for my subject. I though of 'Enter' but I manually type 'Del' (due to its popularity) The problem is MOD4 + 1-9 doesn't work in `rdesktop -f -K -u user ip`. It shows the Start dialog in Windows instead of switch to corresponding tag in Awesome. On 05/29/2012 08:12 PM, Gregor Zattler wrote: Hi quanta, * quanta quanta.li...@gmail.com [29. May. 2012]: Thanks for your info. I should read the man page first. But unfortanately, it doesn't work. Have you tested this option? Yes, last line of my posting. I do not know how Ctrl-Alt-Del behaves in rdesktop, as I said I use the awesome key bindings, e.g. MOD4 + 1 to switch to tag 1 while rdesktop is on tag 6. HTH, Gregor On 05/29/2012 03:30 PM, Gregor Zattler wrote: Hi quanta, awesome-users, * quanta quanta.li...@gmail.com [29. May. 2012]: I usually remote desktop to a Windows at full screen mode with `rdesktop -f`. To switch back to the normal screen, just press Ctrl-Alt-Enter After using Awesome WM, Ctrl-Alt-Enter doesn't work any more, the screen blink in a second and go back, so I must disconnect the session to go back to Linux. From the rdesktop man page: -K Do not override window manager key bindings. By default rdesktop attempts to grab all keyboard input when it is in focus. This allows to use the awesome key bindings to go to different tags, minimize the window etc. Any one get this problem? Me. Solved it with this switch. -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
RE: Who is interested in
Being on this mailing list, I see awesome ideas being discussed and awesome help going out from some truely awesome people, but as with any community, there are always those who disparage, berate, belittle, etc. IMHO the Awesome Window Manager [AwesomeWM ;-)] would be much more awesome if there was more documentation, it was more user friendly, it was easier to find, etc, etc. This is best achieved by growing the community, which is best done through positive interaction. As such, I'd like to encourage everyone to remember to see the positives in everthing and everyone and to offer positive suggestions and encouragement. As the saying goes - If you don't have anything nice to say, don't say anything at all. Kind regards Dave
RE: Awesome - The name!
Hi Alexander, While I understand your comment, I must say that there is a lot more out there than your (a) (b) and (no disrespect intended) the awesome wiki is not so awesome :-( I have spent MANY hours searching for other snippets of information and they are what allowed me to get through the initial getting started barrier. I'm sure that many people try Awesome but end up stumbling and move on - their loss, but our loss as well as we lose some potentially good contributors! Anyway - It was just throwing out my 2c to see what people thought PS: I don't think that adding WM to the official name and not actually changing the code would be a pretty reasonable idea. Regards David -Original Message- From: Alexander Yakushev [mailto:yakushev.a...@gmail.com] Sent: Wednesday, 7 March 2012 4:40 PM To: awesome@naquadah.org Subject: Re: Awesome - The name! Hello, David, I understand what you are talking about. I also have a frustration googling awesome. But the thing is there is no much data on awesome around the web except: a) awesome wiki b) this mailgroup So changing the name so the googling of a dozen of pages becomes easier seems too radical to me. This issue was to be thought in the first place, not after five years passed. Regards, Alexander -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org. -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
RE: awesome session via VNC and mod4 key
G'Day Alexey, I also use VNC - possibly not in the same way but I hope my comment helps... Using Awesome, Remmina as my RDP client and a number of VirtualBox VMs running headless. Remmina is setup to show the taskbar icon which gives a nice shortcut menu to my VMs [I have a tweak in my LUA to kill Remina on the window activation - just kills the window but leaves the icon ;-) ] When an RDP session starts they are in fullscreen and usually do not capture the mod-4 + # combination, allowing me to open several sessions on different tabs and easily flick between them. However (and this is the bit that I expect may help you), sometimes the mod-4 + # combination does not seem to work - For me, Right-Control + F tells Remmina to show it's menu which has a handy keyboard capture icon. Clearing the capture icon has always resolved the key capturing for me and then I return to full-screen Regards Dave David Sorkovsky home: +61 2 9945 3800 office: +61 2 9491 5255 mobile: +61 409 162 963 Date: Tue, 6 Mar 2012 20:34:47 +0200 From: ale...@alexey-kv.info To: awesome@naquadah.org Subject: awesome session via VNC and mod4 key Hello, I'm using awesome via VNC recently. I've a problem with mod4 binding while I'm using vncviewer under other awesome session - I don't know how I can bypass mod4 key to the vncviewer client (mod4 is handled by awesome session where vncviewer is running). Does somebody know how I can do that? Thanks -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Awesome - The name!
While I'm sure everyone on this list will agree, Awesome is AWESOME! My only complaint is the name... Googling awesome finds way to much and mostly unrelated! Googling awesome window manager helps, but could be better... Googling AwesomeWM helps a lot, but but it still misses those results that don't contain the somewhat common addtion of WM that gets added by those in the know... Not sure if there is a better place to post this, but gaspI'd like to suggest a minor change to the name/gasp. I'm sure there are plenty of options, but I'd like to start the ball rolling by suggesting AwesomeWM as the name. Nothing dramatic, just something to make it easier to colate all the awesome information on the internet - who knows if I used awesome in that sentence as the name or as an adjective? PS: If this suggestion is better palced elsewher, I'm happy to hear! Regards Dave David Sorkovsky home: +61 2 9945 3800 office: +61 2 9491 5255 mobile: +61 409 162 963
RE: awesome in Linux Action Show S04E20
I agree - thanks for sharing the video link - was good to see! 100% agree that awesome is a perfect low memory, powerful GUI for a server and the customization is lovely - could have a few better getting started guides/tutorials, but once you take the lid off, it isn't that hard! I have even just setup Ubuntu Server with Awesome on a BeagleBoard xM [ARM] - Especially sweet given that limited RAM! Regards, Dave -Original Message- From: Satisficer [mailto:satisfi...@insideppf.com] Sent: Tuesday, 31 January 2012 7:04 AM To: awesome@naquadah.org Subject: Re: awesome in Linux Action Show S04E20 On 2012-01-30, Julien Danjou jul...@danjou.info wrote: On Mon, Jan 30 2012, Piotr Ozarowski wrote: FYI: http://www.jupiterbroadcasting.com/16411/awesome-window-manager-las-= s20e04/ It starts at 0:50:00, and it's very fun. :) I thought I had defeated the urge to tinker with my setup, but after watching this I'll spend the next 2 days screwing around with widgets. Thanks for the link! -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org. -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Stop new windows covering the wibox [floating layout]
I'm thought there was a question about this a short while ago and I had the
same desire - Here's what I did to fulfil my needs...
Find the following section...
-- Signals
-- Signal function to execute when a new client appears.
client.add_signal(manage, function (c, startup)
Skip down a bit further to...
-- Put windows in a smart way, only if they does not set an initial
position.
if not c.size_hints.user_position and not
c.size_hints.program_position then
awful.placement.no_overlap(c)
awful.placement.no_offscreen(c)
end
Add the following lines after that...
if not (c.name == david or c.name == Guake!) then --
applications you do NOT want to affect
--naughty.notify({ text=c.name })
local geometry = c:geometry()
if geometry.y mywibox[c.screen]:geometry().y +
mywibox[c.screen]:geometry().height then
geometry.y = mywibox[c.screen]:geometry().y +
mywibox[c.screen]:geometry().height + c.border_width
c:geometry(geometry)
end
end
Note 1: Assumes top - change the .y .height to .x .width for left or
change the logic for bottom or right
Note 2: Name of the wibox array is mywibox - change to suit yours ;-)
Regards
Dave
