new pidgin chat-windows
Hello!
I want to open my chat-windows as slaves. I add this code to rc.lua
{ rule = { class = Pidgin, role = buddy_list },
properties = { tag = tags[1][4]} },
{ rule = { class = Pidgin, role = conversation },
properties = { tag = tags[1][4]}, callback = awful.client.setslave },
If I open window by double click it opens fine- after contact list. But
if window opens by getting new message (I have such settings) it opens
before contact list.
Is there any way to let chat-windows self-open as slaves?
Regards, Dennis.
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
change gnome-sound-applet icon in awesome
hi: I use the gnome-sound-applet to control sound in my awesome settings, and it has a full black icon. However, my top panel is also black, so I can't see the icon. Is it possible to change the icon? Thanks! best regards, pylemon -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: change gnome-sound-applet icon in awesome
I've had the same problem: http://askubuntu.com/questions/105614/change-gnome-sound-applet-icon I couldn't really get an answer, not sure if it's possible. I just ended up using a textbox to display my sound, but I'd love to find a way around this too. On Tue, Jul 17, 2012 at 8:37 AM, pyLemon leeway1...@gmail.com wrote: hi: I use the gnome-sound-applet to control sound in my awesome settings, and it has a full black icon. However, my top panel is also black, so I can't see the icon. Is it possible to change the icon? Thanks! best regards, pylemon -- To unsubscribe, send mail to awesome-unsubscribe@naquadah.**orgawesome-unsubscr...@naquadah.org .
Re: change gnome-sound-applet icon in awesome
Well, I actually don't have a solution but you can use vicious to
create a widget like this.
-- {{{ Volume level
volicon = widget({ type = imagebox })
volicon.image = image(awful.util.getdir(config) .. /icons/vol.png)
volwidget = widget({ type = textbox })
vicious.cache(vicious.widgets.volume)
-- Register widgets
vicious.register(volwidget, vicious.widgets.volume, $1%, 2, Master)
-- Register buttons
volwidget:buttons(awful.util.table.join(
awful.button({ }, 1, function () exec(gnome-alsamixer) end),
awful.button({ }, 4, function () exec(amixer -q set Master 2dB+,
false) vicious.force({volwidget}) end),
awful.button({ }, 5, function () exec(amixer -q set Master 2dB-,
false) vicious.force({volwidget}) end)
))
In the above configuration, scrolling on the textwidget changes the
sound too. Also, clicking on it opens gnome-alsamixer.
On Tue 17 Jul 2012 02:52:42 PM IST, David Gomes wrote:
I've had the same problem:
http://askubuntu.com/questions/105614/change-gnome-sound-applet-icon
I couldn't really get an answer, not sure if it's possible. I just
ended up using a textbox to display my sound, but I'd love to find a
way around this too.
On Tue, Jul 17, 2012 at 8:37 AM, pyLemon leeway1...@gmail.com
mailto:leeway1...@gmail.com wrote:
hi:
I use the gnome-sound-applet to control sound in my awesome
settings, and it has a full black icon. However, my top panel is
also black, so I can't see the icon.
Is it possible to change the icon? Thanks!
best regards,
pylemon
--
To unsubscribe, send mail to awesome-unsubscribe@naquadah.__org
mailto:awesome-unsubscr...@naquadah.org.
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
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 and it execute
volumecfg.toggle() , the computer gets mute, and I can't get it unmute
unless I use the gnome-sound-applet or something like that.. what do
you think about that problem?
pylemon
于Tue 17 Jul 2012 05:36:36 PM CST,Abhijeet R写到:
Well, I actually don't have a solution but you can use vicious to
create a widget like this.
-- {{{ Volume level
volicon = widget({ type = imagebox })
volicon.image = image(awful.util.getdir(config) .. /icons/vol.png)
volwidget = widget({ type = textbox })
vicious.cache(vicious.widgets.volume)
-- Register widgets
vicious.register(volwidget, vicious.widgets.volume, $1%, 2, Master)
-- Register buttons
volwidget:buttons(awful.util.table.join(
awful.button({ }, 1, function () exec(gnome-alsamixer) end),
awful.button({ }, 4, function () exec(amixer -q set Master 2dB+,
false) vicious.force({volwidget}) end),
awful.button({ }, 5, function () exec(amixer -q set Master 2dB-,
false) vicious.force({volwidget}) end)
))
In the above configuration, scrolling on the textwidget changes the
sound too. Also, clicking on it opens gnome-alsamixer.
On Tue 17 Jul 2012 02:52:42 PM IST, David Gomes wrote:
I've had the same problem:
http://askubuntu.com/questions/105614/change-gnome-sound-applet-icon
I couldn't really get an answer, not sure if it's possible. I just
ended up using a textbox to display my sound, but I'd love to find a
way around this too.
On Tue, Jul 17, 2012 at 8:37 AM, pyLemon leeway1...@gmail.com
mailto:leeway1...@gmail.com wrote:
hi:
I use the gnome-sound-applet to control sound in my awesome
settings, and it has a full black icon. However, my top panel is
also black, so I can't see the icon.
Is it possible to change the icon? Thanks!
best regards,
pylemon
--
To unsubscribe, send mail to awesome-unsubscribe@naquadah.__org
mailto:awesome-unsubscr...@naquadah.org.
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: change gnome-sound-applet icon in awesome
❦ 17 juillet 2012 09:37 CEST, pyLemon leeway1...@gmail.com : I use the gnome-sound-applet to control sound in my awesome settings, and it has a full black icon. However, my top panel is also black, so I can't see the icon. Is it possible to change the icon? Thanks! While I think you should use a widget for this, you can fix the icon color of most gnome applets with the following snippet: #v+ -- The systray is a bit complex. We need to configure it to display -- the right colors. Here is a link with more background about this: -- http://thread.gmane.org/gmane.comp.window-managers.awesome/9028 xprop = assert(io.popen(xprop -root _NET_SUPPORTING_WM_CHECK)) wid = xprop:read():match(^_NET_SUPPORTING_WM_CHECK.WINDOW.: window id # (0x[%S]+)$) xprop:close() if wid then wid = tonumber(wid) + 1 os.execute(xprop -id .. wid .. -format _NET_SYSTEM_TRAY_COLORS 32c .. -set _NET_SYSTEM_TRAY_COLORS .. 65535,65535,65535,65535,8670,8670,65535,32385,0,8670,65535,8670) end #v- You need to restart the applet after that due to a bug in GTK. More information here: http://thread.gmane.org/gmane.comp.window-managers.awesome/9028 https://bugzilla.gnome.org/show_bug.cgi?id=679592 https://bugzilla.gnome.org/show_bug.cgi?id=679591 Once the last bug has been solved, I'll propose a patch for awesome systray implementation. -- printk(KERN_ERR msp3400: chip reset failed, penguin on i2c bus?\n); 2.2.16 /usr/src/linux/drivers/char/msp3400.c -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: change gnome-sound-applet icon in awesome
On Tue, 17 Jul 2012 15:37:02 +0800 pyLemon leeway1...@gmail.com wrote: hi: I use the gnome-sound-applet to control sound in my awesome settings, and it has a full black icon. However, my top panel is also black, so I can't see the icon. Is it possible to change the icon? Thanks! best regards, pylemon You might also be able to get around this by switching to an icon theme that's meant for dark backgrounds, such as Faenza-Dark. Here's how to create the .gtkrc files that override the default gtk-icon-theme-name: http://awesome.naquadah.org/wiki/Customizing_GTK_Apps Cheers, Bryan -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: [ANNOUNCE] awesome 3.4.13 released
Julien Danjou wrote: Hey folks, A new awesome arrives! This is mainly to fix a regression introduced while fixing FS#1011 in v3.4.12. Happy hacking, Great, thanks! And I can confirm that this release doess fix FS#1011. Thanks again. Jerome -- mailto:jeber...@free.fr http://jeberger.free.fr Jabber: jeber...@jabber.fr signature.asc Description: OpenPGP digital signature
Re: Tag Switching Mildly Broken in 3.4.12
Jérôme M. Berger wrote: Jérôme M. Berger wrote: Leo L. Schwab wrote: I just installed Awesome 3.4.12 from Debian unstable, and noted an unfortunate change in behavior. In 3.4.11, when you changed tags, the window that was focused was, in general, the window with that tag that last had focus. That is, I could switch away from a shell window in tag 1 to tag 4, fiddle with the Web browser there, then switch back to tag 1, and the shell window I was using would get the focus again. Now, whenever I change tags, none of the windows has focus, and I have to wave my mouse around to focus one of them (even if the mouse is already over the window). This new behavior doesn't appear to be mentioned in the changelog. Is this an intended change? Is there a way to work around it in rc.lua? Any update about this? For those who don't follow Flyspray, this was entered as FS#1011 (1) and fixed in the latest release (3.4.13). Jerome (1) https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1011 -- mailto:jeber...@free.fr http://jeberger.free.fr Jabber: jeber...@jabber.fr signature.asc Description: OpenPGP digital signature
Re: change gnome-sound-applet icon in awesome
❦ 17 juillet 2012 18:07 CEST, Bryan Gardiner b...@khumba.net : I use the gnome-sound-applet to control sound in my awesome settings, and it has a full black icon. However, my top panel is also black, so I can't see the icon. Is it possible to change the icon? Thanks! best regards, pylemon You might also be able to get around this by switching to an icon theme that's meant for dark backgrounds, such as Faenza-Dark. Here's how to create the .gtkrc files that override the default gtk-icon-theme-name: http://awesome.naquadah.org/wiki/Customizing_GTK_Apps Unfortunately, applets using those symbolic icons are specifically requesting them. I did not check for the volume applet, but I got the problem with the bluetooth applet. You have something like this: icon_enabled = g_themed_icon_new_with_default_fallbacks (ACTIVE_ICON_NAME-symbolic); This result that an icon ending by -symbolic will be favored over all other icons. Only if such an icon is not found, it will try without the -symbolic suffix (and again, if not found, it will remove one suffix). However, I don't remember whay I have tested exactly. Maybe something like this would work (with `yourtheme` being a theme without symbolic icons): #v+ gtk-icon-theme-name=yourtheme gtk-fallback-icon-theme=yourtheme #v- Another solution would be to uninstall those icons. -- printk(KERN_WARNING Multi-volume CD somehow got mounted.\n); 2.2.16 /usr/src/linux/fs/isofs/inode.c -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: change gnome-sound-applet icon in awesome
于Wed 18 Jul 2012 12:45:41 AM CST,Vincent Bernat写到: ❦ 17 juillet 2012 18:07 CEST, Bryan Gardiner b...@khumba.net : I use the gnome-sound-applet to control sound in my awesome settings, and it has a full black icon. However, my top panel is also black, so I can't see the icon. Is it possible to change the icon? Thanks! best regards, pylemon You might also be able to get around this by switching to an icon theme that's meant for dark backgrounds, such as Faenza-Dark. Here's how to create the .gtkrc files that override the default gtk-icon-theme-name: http://awesome.naquadah.org/wiki/Customizing_GTK_Apps Unfortunately, applets using those symbolic icons are specifically requesting them. I did not check for the volume applet, but I got the problem with the bluetooth applet. You have something like this: icon_enabled = g_themed_icon_new_with_default_fallbacks (ACTIVE_ICON_NAME-symbolic); This result that an icon ending by -symbolic will be favored over all other icons. Only if such an icon is not found, it will try without the -symbolic suffix (and again, if not found, it will remove one suffix). However, I don't remember whay I have tested exactly. Maybe something like this would work (with `yourtheme` being a theme without symbolic icons): #v+ gtk-icon-theme-name=yourtheme gtk-fallback-icon-theme=yourtheme #v- Another solution would be to uninstall those icons. thanks vincent, your solution is awesome, and I have successfully changed my icon white now. thank you very much! and thanks bryan, thank you for your help. this group is so nice. I love awesome. : ) -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: consolekit is not active after running startx.
Anybody know the solution?? 2012/7/16 Leiking jinleileik...@gmail.com: waiting expert to solve it ... 2012/7/16 Leiking jinleileik...@gmail.com: I tryed this. Althoght the seat is active, but awesome seems not work well. meta + 1 2 3 is not responding -_-. 2012/7/15 Renato Botelho rbga...@gmail.com: On Sat, Jul 14, 2012 at 5:22 AM, Leiking jinleileik...@gmail.com wrote: ➜ ~ git:(master) ✗ cat .xinitrc #!/bin/sh #export XMODIFIERS=@im=ibus #export GTK_IM_MODULE=ibus #export QT_IM_MODULE=xim xrdb ~/.Xresources export XMODIFIERS=@im=fcitx export GTK_IM_MODULE=fcitx # 或者是xim，取决于你是否编译了对应的输入法模块 export QT_IM_MODULE=fcitx # 或者是xim，取决于你是否编译了对应的输入法模块 #eval `dbus-launch --sh-syntax --exit-with-session` #xrandr --output LVDS1 --primary #xrandr --output VGA1 --mode 1280x1024 --right-of LVDS1 xrandr --output LVDS1 --primary --mode 1366x768 --output VGA1 --mode 1280x1024 --right-of LVDS1 #exec ck-launch-session dbus-launch --sh-syntax --exit-with-session awesome ~/.awesome_stdout 2 ~/.awesome_stderr exec ck-launch-session awesome ~/.awesome_stdout 2 ~/.awesome_stderr #exec awesome ~/.awesome_stdout 2 ~/.awesome_stderr ➜ ~ git:(master) ✗ ck-list-sessions Session5: unix-user = '1000' realname = '(null)' seat = 'Seat5' session-type = '' active = FALSE x11-display = ':0' x11-display-device = '/dev/tty8' display-device = '/dev/tty1' remote-host-name = '' is-local = FALSE on-since = '2012-07-14T08:11:52.554923Z' login-session-id = '' Session1: unix-user = '1000' realname = '(null)' seat = 'Seat1' session-type = '' active = FALSE x11-display = '' x11-display-device = '' display-device = '/dev/tty1' remote-host-name = '' is-local = TRUE on-since = '2012-07-14T07:56:10.440619Z' login-session-id = '' idle-since-hint = '2012-07-14T08:12:17.578563Z' I had this same issue after move to fedora 17. The workaround i found was to run (if you are on tty1): # startx -- vt01 There is a proposed patch on redhat's bugzilla to make startx adding the vtNN automatically. Regards -- Renato Botelho -- 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: consolekit is not active after running startx.
I finally solved. I donot config my kernel well... Updated the wiki: https://awesome.naquadah.org/wiki/Autostart_with_consolekit Thanks all!! Specially thanks to @Vincent Bernat 2012/7/18 Leiking jinleileik...@gmail.com: Anybody know the solution?? 2012/7/16 Leiking jinleileik...@gmail.com: waiting expert to solve it ... 2012/7/16 Leiking jinleileik...@gmail.com: I tryed this. Althoght the seat is active, but awesome seems not work well. meta + 1 2 3 is not responding -_-. 2012/7/15 Renato Botelho rbga...@gmail.com: On Sat, Jul 14, 2012 at 5:22 AM, Leiking jinleileik...@gmail.com wrote: ➜ ~ git:(master) ✗ cat .xinitrc #!/bin/sh #export XMODIFIERS=@im=ibus #export GTK_IM_MODULE=ibus #export QT_IM_MODULE=xim xrdb ~/.Xresources export XMODIFIERS=@im=fcitx export GTK_IM_MODULE=fcitx # 或者是xim，取决于你是否编译了对应的输入法模块 export QT_IM_MODULE=fcitx # 或者是xim，取决于你是否编译了对应的输入法模块 #eval `dbus-launch --sh-syntax --exit-with-session` #xrandr --output LVDS1 --primary #xrandr --output VGA1 --mode 1280x1024 --right-of LVDS1 xrandr --output LVDS1 --primary --mode 1366x768 --output VGA1 --mode 1280x1024 --right-of LVDS1 #exec ck-launch-session dbus-launch --sh-syntax --exit-with-session awesome ~/.awesome_stdout 2 ~/.awesome_stderr exec ck-launch-session awesome ~/.awesome_stdout 2 ~/.awesome_stderr #exec awesome ~/.awesome_stdout 2 ~/.awesome_stderr ➜ ~ git:(master) ✗ ck-list-sessions Session5: unix-user = '1000' realname = '(null)' seat = 'Seat5' session-type = '' active = FALSE x11-display = ':0' x11-display-device = '/dev/tty8' display-device = '/dev/tty1' remote-host-name = '' is-local = FALSE on-since = '2012-07-14T08:11:52.554923Z' login-session-id = '' Session1: unix-user = '1000' realname = '(null)' seat = 'Seat1' session-type = '' active = FALSE x11-display = '' x11-display-device = '' display-device = '/dev/tty1' remote-host-name = '' is-local = TRUE on-since = '2012-07-14T07:56:10.440619Z' login-session-id = '' idle-since-hint = '2012-07-14T08:12:17.578563Z' I had this same issue after move to fedora 17. The workaround i found was to run (if you are on tty1): # startx -- vt01 There is a proposed patch on redhat's bugzilla to make startx adding the vtNN automatically. Regards -- Renato Botelho -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
[awesome bugs] #1022 - Moving terminal windows around usually makes them narrower
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Julien Danjou (jd) Attached to Project - awesome Summary - Moving terminal windows around usually makes them narrower Task Type - Bug Report Category - awful Status - New Assigned To - Operating System - All Severity - Low Priority - Normal Reported Version - 3.4.13 Due in Version - Undecided Due Date - Undecided Details - Copy of http://bugs.debian.org/cgi-bin/bugreport.cgi?archive=yesbug=681770 I use awesome in the stock configuration. When opening a terminal window, then move it around (Mod4 + Button1), the window typically gets narrower at a rate of around 10-15 columns per second until the mouse button is being released. This happens for roxterm and gnome-terminal in any case, but does not seem to affect xterm and konsole. It happens most of the time, and resizing the window first reduces the chances of this automatic resizing by awesome. This is annoying, but not a showstopper. More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1022 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. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
[awesome bugs] #1022 - Moving terminal windows around usually makes them narrower
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1022 - Moving terminal windows around usually makes them narrower User who did this - Uli Schlachter (psychon) -- Anyone can reproduce? (Other questions I better mail to the debian BTS) -- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1022#comment3123 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. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
[awesome bugs] #1022 - Moving terminal windows around usually makes them narrower
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1022 - Moving terminal windows around usually makes them narrower User who did this - David Ewing (ewingd) -- I have been having an issue with terminal windows resizing during movement as well. I am see it with gnome-terminal and the window gets shorter during movement until it reaches as height of 3 lines. It only seems to happen once when the terminal is initially opened on a tag set to the floating layout. It also seems to stop after resizing the window. I am seeing this on Debian Wheezy. $ awesome --version awesome debian/3.4.12-2 (Starlight) • Build: Jun 13 2012 11:30:57 for x86_64 by gcc version 4.7.0 (@zelenka) • D-Bus support: ✔ -- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1022#comment3124 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. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
Re: [ANNOUNCE] awesome 3.4.13 released
Julien Danjou wrote: Hey folks, A new awesome arrives! This is mainly to fix a regression introduced while fixing FS#1011 in v3.4.12. Happy hacking, Great, thanks! And I can confirm that this release doess fix FS#1011. Thanks again. Jerome -- mailto:jeber...@free.fr http://jeberger.free.fr Jabber: jeber...@jabber.fr signature.asc Description: OpenPGP digital signature
[awesome bugs] #1022 - Moving terminal windows around usually makes them narrower
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1022 - Moving terminal windows around usually makes them narrower User who did this - Uli Schlachter (psychon) -- Ok, first observation: The alternative systems thinks I want to use roxterm instead of urxvt just because I installed it. Meh. Doesn't happen on git/master (suddenly I care a lot less) and on 3.4, it happens somewhere in the middle of nowhere. I added some print() calls to awful.mouse. It calls c:geometry() with the old width and height, so nothing should get changed here. So I guess that the C code now screws up somewhere while it tries to apply size hints to this unchanged size. Also, checking with xwininfo/xprop, it looks like the current size of the window doesn't respect its size hints, although it should. So at this point, I'd have to add printf()s to the source code and since I can't compile 3.4, I'm giving up here. Also, no idea what xterm does differently (perhaps its initial size respects its size hints?). -- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1022#comment3125 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. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
