Re: Changing dpi settings
Hi Paul, On Tue 18.11.2014 16:55:33, Paul Jolly wrote: > My switch in ~/.Xresources is essentially: > > Xft.dpi:196 -> ! Xft.dpi:196 > URxvt*font: xft:DejaVuSansMono:medium:size=7:antialias=false -> URxvt*font: > xft:DejaVuSansMono:medium:size=8:antialias=false > > This is accompanied by a couple of changes to my Awesome config. > > An Awesome restart (unsurprisingly) doesn't pick up the .Xresources > changes. > > Any thoughts on how best to achieve this? xrdb -remove && xrdb -merge ~/.Xresources While I was tinkering with my .Xresources the xrdb -merge got essential to me.. You definately need the -remove beforehand, as you do not replace Xft.dpi with a new setting, but comment it out. This way it won't override the existing value (you can test it with -query). Regards, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: How to place widgets on desktop itself?
Hi Dmitry, On Thu 09.10.2014 11:00:24, Dmitry Grigoriev wrote: > I'm a newbie in Awesome, have a few questions and will ask each one > separately. > > Wiki says that I can place widgets on status bar and title bar. Never > mentioned how to place them on desktop: like application icons or > gkrellm-like graphical system monitors (ideally - with semi-transparent > background). I believe it's possible because someone has already done it: > http://awesome.naquadah.org/w/images/Screenshot-nac-theme.png So, how can I > do it? This is actually not awesome itself, but conky. The configs for this theme are under https://awesome.naquadah.org/wiki/Nice_and_Clean_Theme I found it by simply googling the file name and found http://pastebin.com/kACECZHb Have fun, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: my alt-tab
Hi Joren, On Sun 28.09.2014 15:23:22, Joren Heit wrote: > On Sun, Sep 28, 2014 at 12:51 PM, Andre Klärner wrote: > > Who, if not you, is the best person to describe this? Please go ahead, a > > wiki is there to be edited by everyone! > > > Yeah you're right, so I followed your advice and added the entry: > https://awesome.naquadah.org/wiki/Familiar_Alt_Tab > > I hope it's complete enough :-) Looks really nice, I am quite near to installing it for my desktops! Regards, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: my alt-tab
Hi Joren, On Sun 28.09.2014 11:55:37, Joren Heit wrote: > On Sep 28, 2014 5:46 AM, "Isaac Xin Pei" wrote: > > This is nice! it would be good if we can add a wiki entry on the awesome > > website > Thanks! That would be a real honor. But I'm not going to do that myself... > that would seem a little arrogant ;-) Who, if not you, is the best person to describe this? Please go ahead, a wiki is there to be edited by everyone! Regards, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: Using 3.5 on Wheezy
Hi Mike,
you can add the repositories for jessie and experimental temporarily and
install the experimental version of awesome, which turns out to be 3.5.5. I
have been using this very exact package and it works perfectly. Just pay a bit
of attention to not upgrade your whole system and it should turn out very well.
Afterwards you can comment out the repos back again.
Regards,
Andre
On August 8, 2014 6:22:15 PM CEST, Mike wrote:
>I have Debian Wheezy system which supports 3.4 in the package
>repository. I have a configuration for 3.5 that I have been using
>perfectly happily on my previous, now broken, Ubuntu system. At first
>blush it seems I have to build 3.5 from source, but it complains that
>the lgi module is missing (a new run-time dependency).
>
>The Wheezy package is for lgi-0.6.1, which is no good for 3.5.2.
>
>Using luarocks I can install lgi 0.8, but it seems it is not
>recognised.
>The test command "lua -e 'lgi = require("lgi") ... fails to recognise
>it.
>
>One issue may come from the fact that the Wheezy install has ended up
>with both lua5.1 _and_ lua5.2. The default is to run 5.2 but as far as
>I can see install of lua-lgi is linked to 5.1.
>
>Two questions:
>
>1. Has anyone got a reasonable suggestion for what to do next?
>
>2. Is this a reasonable question for this list (or, indeed, who should
>I
>ask)?
>
>Cheers
>
>Mike S.
--
Andre Klärner
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: wierd resizing issue in my config
Hi Luke, thanks a lot. With the change from aae577c in place (removing the width-fiddeling from the focus function) it works like a treat. seems a bit to obvious for me to spot. Thanks, Andre On Sun 08.06.2014 12:48:37, luke bonham wrote: > Try with the latest commit: > > https://github.com/copycat-killer/awesome-copycats/blob/master/rc.lua.powerarrow-darker > > Il 08/06/2014 02:26, Andre Klärner ha scritto: > >Hi all, > > > >I got a minor issue in my config, but seem to be too stupid to find out why > >it is doing this. > > > >I wanted to get borderless windows if only one window is shown (like in > >max-layout or if #clients is 1). So I stole from awesome-copycats (Thanks > >by the way for the idea and implementation). > > > >But since than my terminal windows (urxvt) started behaving funny. After > >drilling down a bit I noticed that somehow the window border first gets > >added and removed a split-second later, which seems to screw up most > >ncurses apps (but not e.g. vim). > > > >Could someone please take a look at my config and tell me if I did > >something stupid (and if yes what)? > > > >My config (for awesome 3.5 on Debian) can be found at > >https://gitlab.ak-online.be/kandre/awesome/tree/master/.config/awesome > >together will all accompanying files. I assume the problematic code is > >somewhat around lines 735 til EOF. > > > >Thanks a lot in advance, keep rockin' > > > >Andre > > -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
wierd resizing issue in my config
Hi all, I got a minor issue in my config, but seem to be too stupid to find out why it is doing this. I wanted to get borderless windows if only one window is shown (like in max-layout or if #clients is 1). So I stole from awesome-copycats (Thanks by the way for the idea and implementation). But since than my terminal windows (urxvt) started behaving funny. After drilling down a bit I noticed that somehow the window border first gets added and removed a split-second later, which seems to screw up most ncurses apps (but not e.g. vim). Could someone please take a look at my config and tell me if I did something stupid (and if yes what)? My config (for awesome 3.5 on Debian) can be found at https://gitlab.ak-online.be/kandre/awesome/tree/master/.config/awesome together will all accompanying files. I assume the problematic code is somewhat around lines 735 til EOF. Thanks a lot in advance, keep rockin' Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: script to cycle through possible multi-screen configurations
On Wed 30.04.2014 04:09:50, Raphael Cervantes wrote: > On Sun, Apr 20, 2014 at 7:30 PM, Andre Klärner wrote: > > On April 20, 2014 9:16:47 PM CEST, Raphael Cervantes > > wrote: > > > I was wondering if anyone has a script that would allow a plug-and-play > > > dual monitor that Gnome offers. I can't be bothered to play with xrandr > > > commands when I'm about to give a presentation to an audience. > > > > actually there are a gazillion scripts of this kind and everyone finds its > > best fit. > > > > For me it has worked best to have my awesome configured to deal with all > > my screen setups (one up to three displays, machine-dependant tags on > > different displays) and rely on the auto detection of new displays that > > lead to an awesome restart. For special purposes I use autorandr (invoked > > manually) that tries to guess the right display arrangement from the > > connected displays, but in each case of a important presentation I try to > > check a while before the presentation how to configure e.g. the > > displayport or VGA with the optimal resolution and prepare an xrandr line > > in a shell script beforehand, so that I just need to apply this one I'm > > on. Also "xrandr --output VGA-0 --auto" works a treat if the display > > device supports DDC. > > > > Also xrandr gets a lot easier once you used it a bit, but it turns out to > > be more reliable when you finally got its syntax in your muscle memory. > > It seems that I was already on the right track. I just have a problem > dealing with projectors that have a lower screen resolution than my native > screen resolution. > > IN="LVDS1" > EXT="VGA1" > > xrandr --output $IN --auto --output $EXT --auto --same-as $IN > > However, I think this makes my computer assume that the external display is > the same resolution as my monitor, which is not the case. How do I fix this? > I haven't found the answer to my question. Well, if it doesn't assume that both are the same resolution, how should it be able to display a different count of pixels on each of them? So either use an external display capable of the resolution your internal can do, or downgrade both to a matching one. I have found 1280x720 and 1280x800 to be good candidates for current projectors, which deliver a sensible size and screen real estate tradeoff. Another solution would be panning, but this is something I personally only experienced by accident and hated it very much (scrolling within a browser - okay .. scrolling your screen within your display - not cool at all). Also another way around this is using not the same screen content on both screens.. Like displaying the presenter view on the internal display, and just the presentation output on the external display (so no need to have the same resolution on both displays) Regards, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: Running lua code from a menu
Hi William, Is your config published anywhere on the net? I would love to see that specific connect/reconnect function and see if I can extend it for gnu screen. Thanks a lot, Andre On April 24, 2014 5:04:39 PM CEST, William Tomlinson wrote: >I have something similar that looks through my list of clients >to >see if I already have a session open and switches to it. Maybe you can >adapt this to your purposes? -- Andre Klärner -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: script to cycle through possible multi-screen configurations
Hi Raphael, actually there are a gazillion scripts of this kind and everyone finds its best fit. For me it has worked best to have my awesome configured to deal with all my screen setups (one up to three displays, machine-dependant tags on different displays) and rely on the auto detection of new displays that lead to an awesome restart. For special purposes I use autorandr (invoked manually) that tries to guess the right display arrangement from the connected displays, but in each case of a important presentation I try to check a while before the presentation how to configure e.g. the displayport or VGA with the optimal resolution and prepare an xrandr line in a shell script beforehand, so that I just need to apply this one I'm on. Also "xrandr --output VGA-0 --auto" works a treat if the display device supports DDC. Also xrandr gets a lot easier once you used it a bit, but it turns out to be more reliable when you finally got its syntax in your muscle memory. Regards, Andre On April 20, 2014 9:16:47 PM CEST, Raphael Cervantes wrote: >Hi all, >I'm trying to implement the script suggested in this page >http://awesome.naquadah.org/wiki/Using_Multiple_Screens >for cycling through different multi-screen configurations. Its in the >section: Cycling through possible configurations. > >When I put it in my rc.lua file, I get the error message "attempt to >index global 'config' (a nil value). > >I was wondering if anyone has a script that would allow a plug-and-play > >dual monitor that Gnome offers. I can't be bothered to play with xrandr > >commands when I'm about to give a presentation to an audience. > >-Raphael -- Andre Klärner Telefon: 0351/79666546 Fax: 0351/79688547 Mobil: 0172/9838653 Anschrift: Prohliser Allee 43 01239 Dresden -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: overscan question
Hi David, in one way awesome might be able to help you: you can define a custom layout or modify an existing one to always place windows with in the visible part. I personally have never done this but there is plenty information out there. Also I think most TVs should be able to be reconfigured properly. Also you might have to take a look at your receiver if it is already clipping parts. Which devices do you own? Regards, Andre David Henderson wrote: >Thanks for the info Matt! Unfortunately all the inputs are routed >through >a receiver. Plus the tv is a cheap one without many settings. I've >been >looking all over for a solution to this, but haven't found anything >that >will resolve the problem yet. I was hoping awesome could provide a >solution, but it looks like that won't be the case either. Oh well, >back >to X... Thanks for the help though! > >Thanks, >Dave > > > > >On Mon, Mar 3, 2014 at 3:38 PM, Matthieu Cameirao < >matthieu.camei...@isboring.org> wrote: > >> Le Monday 03 March 2014 à 01:38:41PM, David Henderson a écrit : >> > Good afternoon everyone! I've recently built an HTPC and have it >> connected >> > to the TV via HDMI. Previously it was using a VGA cable, but since >I've >> > made the transition to the different connection the tv is >generating >> > overscan with no way of turning it off in the setup (or with xrandr >it >> > seems). My question to the mailing list is can I correct this >using >> > awesome? It appears that just changing the resolution will not >correct >> the >> > problem, but instead I will need to "add a border" around the >viewable >> area >> > of the screen. Can this be accomplished with awesome or do I need >to >> work >> > with X? >> > >> > Thanks, >> > Dave >> >> Hello >> >> I don't think this is a job for awesome (and I'm not sure it could do >> something), so you probably need to change something in your X >> configuration. >> >> But before doing anything, I had the same problem with my HTPC, >solved >> it by changing the HDMI input label name to 'PC' (in my TV settings). >> After this change the TV switched to a resolution working with the >HTPC. >> So try looking in your TV menu for this setting. My TV is a Sony, >but >> it seems that it is the same for Samsung ones. >> >> Matthieu >> >> -- >> To unsubscribe, send mail to awesome-unsubscr...@naquadah.org. >> -- Andre Klärner Telefon: 0351/79666546 Fax: 0351/79688547 Mobil: 0172/9838653 Anschrift: Prohliser Allee 43 01239 Dresden -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: updated wiki page xrandr screen table
On Thu 31.10.2013 10:39:25, Uli Schlachter wrote: > On 31.10.2013 05:46, Andre Klärner wrote: > > On Wed 30.10.2013 20:28:32, Uli Schlachter wrote: > [...] > >> Having written this mail and re-reading it before sending it, I notice > >> that you > >> mentioned awesome 3.4.15. A quick look confirms that 3.4 does not have this > >> feature. It was introduced in the following commit: > >> > >> commit 9393b2d1110b308edddf3255b5a001fe64f49478 > > > > Well, I think one should document this in the wiki. > > Documented this in git. No idea if my explanation makes much sense. > > http://git.naquadah.org/?p=awesome.git;a=commitdiff;h=29ecc6095f6f566757d17538635eb2b7674ed96f Yeah, I think it makes sense. I also documented it within the wiki page for xrandr screen table that it's not needed anymore in v3.5+. > > Well, obviously this can't be found in 3.4's code (as I checked it out via > > apt-source..). But I am still very impressed.. there should be a how-to on > > reading source code.. ;) > > No idea how such a how-to should look like. It seems like the problem here was > partly in our magic for implementing classes in lua. However, most of that is > part of lua already... I think this is mainly a problem for people like me that don't like C and alike, so I think I should simply read more C code and really try to understand it. > > Thanks a lot, I think it won't take long until I finally get around > > switching to 3.5. > > Arnau once mentioned that 3.5.1 was uploaded to debian experimental, because > it > didn't work for him. His bug report (FS#1155) was fixed with 3.5.2 and thus I > guess 3.5.2 might show up in unstable eventually... I hope so. But I think as I can live with a bug like this I'll try to convert my config during this nightshift ;). Thanks a lot for your effort! Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: updated wiki page xrandr screen table
Hi Uli,
On Wed 30.10.2013 20:28:32, Uli Schlachter wrote:
> On 30.10.2013 18:42, Andre Klärner wrote:
> > On Wed 30.10.2013 18:00:33, Uli Schlachter wrote:
> >> On 30.10.2013 03:37, Andre Klärner wrote:
> >>> as my setup at home is a bit more complex than the one on the go and at
> >>> work I had to modify the xrandr screen table function a bit. To not keep
> >>> it
> >>> just for me I updated the wiki page for it.
> >>>
> >>> https://awesome.naquadah.org/wiki/XRandR_Screen_Table
> >>>
> >>> I'd be grateful if anyone using the script might try out the updated
> >>> version and tell me if and what mistakes I made.
> >>
> >> I might be missing something, but I think that this code (copied from that
> >> wiki
> >> page):
> >>
> >> screens = xrandr_screens()
> >> client.focus.screen = screens["VGA"]
> >>
> >> is equivalent to this code:
> >>
> >> client.focus.screen = screen.VGA.index
> >
> > This doesn't work for me. I tried with v3.4.15 and it first struggeled with
> > the output name "DP-1", and on my laptop with an output named "LVDS" it
> > also returned nothing at all.
>
> For DP-1, you would need screen["DP-1"].index. In lua, foo.bar is syntactic
> sugar for foo["bar"], but the later is more generic and also works with
> non-lua-identifiers.
>
> I tested this for all my screens locally with:
>
> $ echo 'return screen.LVDS1.index' | awesome-client
>double 2
> $ echo 'return screen.VGA1.index' | awesome-client
>double 1
One more item on the "switching to 3.5" list.. You really whetted my
appetite with this one..
> Having written this mail and re-reading it before sending it, I notice that
> you
> mentioned awesome 3.4.15. A quick look confirms that 3.4 does not have this
> feature. It was introduced in the following commit:
>
> commit 9393b2d1110b308edddf3255b5a001fe64f49478
> Author: Julien Danjou
> Date: Mon Sep 21 20:35:14 2009 +0200
>
> screen: add index by output name (FS#361)
>
> Signed-off-by: Julien Danjou
Well, I think one should document this in the wiki. I think I read this bug
report way back when I first searched for this. Unfortunately I seemingly
missed the "fixed in 3.5 part".
> > I tried to find the code responsible for creating the screens array, but it
> > seems like I am not a really good C-reader. But if such a feature was
> > available it would definately ease my day.
>
> Heh. :-)
>
> Look at screen.c, function luaA_screen_module_index(). This function is called
> whenever you index the screen object. It's implementation is:
>
> /** Screen module.
> * \param L The Lua VM state.
> * \return The number of elements pushed on stack.
> * \luastack
> * \lfield number The screen number, to get a screen.
> */
> static int
> luaA_screen_module_index(lua_State *L)
> {
> const char *name;
>
> if((name = lua_tostring(L, 2)))
> foreach(screen, globalconf.screens)
> foreach(output, screen->outputs)
> if(A_STREQ(output->name, name))
> return luaA_pushscreen(L, screen);
>
> int screen = luaL_checknumber(L, 2) - 1;
> luaA_checkscreen(screen);
> return luaA_pushscreen(L, &globalconf.screens.tab[screen]);
> }
>
> So it checks all screens and for each of its output, it checks its name (a
> screen can have more than one output! A screen object tells you about its
> output
> with the "outputs" key. This is a table with the keys being the output name
> and
> the values being another table with entries "mm_width" and "mm_height")
Well, obviously this can't be found in 3.4's code (as I checked it out via
apt-source..). But I am still very impressed.. there should be a how-to on
reading source code.. ;)
Thanks a lot, I think it won't take long until I finally get around
switching to 3.5.
> Uli
> --
> Bruce Schneier can read and understand Perl programs.
and I guess also C ;)
Regards, Andre
--
Andre Klärner
smime.p7s
Description: S/MIME cryptographic signature
Re: Some questions from an awesome beginner
Hi Eugen, On Wed 30.10.2013 17:47:58, Eugen Dedu wrote: > On 30/10/13 16:49, Gabe Martin wrote: > >a tag is just a group of applications. rather than minimising and > >maximising things, you can assign applications to different tags. then, > >when you want to view those things, you can toggle the tag to be visible > >along with your current tag, and, when you're done, toggle that tag to be > >invisible again. > > So IF you put one app per tag, then minimising an app is equivalent > to disabling a tag. (Except that by default you do not see the apps > from other tags, I suppose this can be changed if needed.) > > I suppose the benefit of using tags appears when you put several > apps in one tag. I still do not see the benefit. > > I gave you my work flow. Could you give some test cases for tag > usage (or your work flow)? In your workflow I'd think you'd be best of by putting emacs, thunderbird and firefox each on one tag, and scattering your other applications (pdf, terminals...) on one tag per task. Than if you need to jump between tasks you can simply change the tag to get back to where you were, and maybe switch to a thunderbird or emacs tag intermittingly to update the todo or check the mails. Than you'd also profit most of the tiling layouts, as emacs/thunderbird/firefox are using the full screen when you only have their tag open, same with the collection of various windows on a task-tag, and when you mix the two tags they'll share the available space without you intervening. > What do you put precisely in your tags and more importantly how do you > use them? I have a tag for nearly everything. So there are tags for chrome,mutt,irssi,pidgin,games,rdp clients,ica clients etc. There are some special tags I have like the one going to a jumphost and appox 20-100 servers at work, which are not as well split up as I'd like, and some tags that contain a bunch of misc terminals which were opened over the long runtime. And than there are some tags that contain everything for a specific task, like a manpage, editor and a testing terminal, or a filebrowser with some code-editor for web-development (there for example I often mix in the web-tag for viewing the results of my code and the html-inspector). It took me a while to figure out how to run it for myself, but in the end it only has to suit me. What I love about it is that I can apply the same config on my work, my home and my laptop without ever worrying where something is. So if I want to go to my web-tag it's always just a Mod4-1 far, same with my chat at no. 9, irssi at 8, mutt at 7, etc etc.. > Note that permitting to have an app in several tags cannot be > considered a reason to use tags. Well, it is a benefit compared to what gnome does. But it depends on what you need. Like with the web-dev scheme above it wouldn't be possible to tag the chrome-window with my project on it as well to the www-tag as to the webdev-tag. Regards, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: Some questions from an awesome beginner
Hi Eugen, On Wed 30.10.2013 17:01:35, Eugen Dedu wrote: > On 30/10/13 16:33, Paweł Rumian wrote: > >2013/10/30 Eugen Dedu : > >>On 29/10/13 19:42, Paweł Rumian wrote: > >>>>>Use/configure acpid > >>Can someone share with me his solution to make suspend on lid closing? > > > >I'm not with my laptop right now, but I remember I've used this solution > >https://wiki.archlinux.org/index.php/acpid#Example_Events > > Thank you very much! I do not have /etc/acpi/handler.sh, but I > noticed /etc/acpi/lid.sh. In it, I set to true LID_SLEEP, I > restarted acpi-support and now it works!! > > However, that file was last modified in March 2012, whereas this > issue appeared on my machine about 2 weeks ago. So I assume that > the suspend has been done in a different way until 2 weeks ago. I > still wonder why it is not on by default... I'd assume that gnome itself reacted to the lid close event, and gnome itself triggered the suspend. I myself use a different approach: as I travel even at work a lot with my laptop, from one meeting room to another I never want to close the lid and notice that the laptop suspended if just about 20sec later I am going to open it again. Therefor I opted for doing it manually. The thinkpads I use have a Fn-F4 keyboard shortcut that triggers (by default in debian) the suspend. So if I want to suspend it takes me just this one combo to do so. Regards, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: updated wiki page xrandr screen table
Hi Uli, On Wed 30.10.2013 18:00:33, Uli Schlachter wrote: > On 30.10.2013 03:37, Andre Klärner wrote: > > as my setup at home is a bit more complex than the one on the go and at > > work I had to modify the xrandr screen table function a bit. To not keep it > > just for me I updated the wiki page for it. > > > > https://awesome.naquadah.org/wiki/XRandR_Screen_Table > > > > I'd be grateful if anyone using the script might try out the updated > > version and tell me if and what mistakes I made. > > I might be missing something, but I think that this code (copied from that > wiki > page): > > screens = xrandr_screens() > client.focus.screen = screens["VGA"] > > is equivalent to this code: > > client.focus.screen = screen.VGA.index This doesn't work for me. I tried with v3.4.15 and it first struggeled with the output name "DP-1", and on my laptop with an output named "LVDS" it also returned nothing at all. I tried to find the code responsible for creating the screens array, but it seems like I am not a really good C-reader. But if such a feature was available it would definately ease my day. > No idea if this feature is documented anywhere, but I think I just found a > volunteer to mention this in the wiki. If it is documented I couldn't find it. It might also be, that this has been introduced far after the wiki page was created. > > Of course, this does not work if awesome is not using RANDR for querying the > monitor configuration. Also, there doesn't seem to be a way for querying the > list of available screens. Well, I assume that this pretty obvious. I think pure Xinerama wouldn't work with this solution, but in this case the screen order is pretty static anyway. AFAIK RANDR is the only way to change the screen layout during the runtime of the xserver. Regards, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
updated wiki page xrandr screen table
Hi guys, as my setup at home is a bit more complex than the one on the go and at work I had to modify the xrandr screen table function a bit. To not keep it just for me I updated the wiki page for it. https://awesome.naquadah.org/wiki/XRandR_Screen_Table I'd be grateful if anyone using the script might try out the updated version and tell me if and what mistakes I made. Thanks a lot, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: surviving as a windows user
On Tue 29.10.2013 10:46:14, Wayne Werner wrote: > On Tue, Oct 29, 2013 at 10:36 AM, Andre Klärner wrote: > > as my post to Eugen's thread has reminded me, does anyone of you have to > > use a microsoft windows (e.g. at work)? I am stuck with it, with no way to > > get around using windows, but every day I am once again struck again by the > > stupidity of using windows.. > > > > Has anyone of you to deal with something alike and found a solution, how to > > at least get something awesome-like as a window manager? If there anything > > that can lessen the pain? ;) > > I use WinSplit Revolution and VirtuaWin. > > It gets me "close enough" to not scream in frustration. Well, I tried things like these two in the past, but they were not really what I'd expected. They are most often only half the way to like awesome works. I think awesome is simply too awesome to be mimicked.. ;) > Of course, if it's not against your corporate rules, I'd just run a linux > VM on top of Windows. Well, I did this. First with only a VM in a screen, later by using the VM with an USB-Displaylink device as graphics output. But the VM was always limited by the slow-as-hell scheduler from windows. Later I swapped the places of windows and linux, ran linux on bare metal and windows within a virtualbox, which worked perfectly until the network security decided to employ a network based security system that locked my laptop out too often, with only the IT support guys being able to unlock it. So I had to switch back to using windows physically. The main bummer with the linux-vm solution were speed (as awesome itself is really fast, but the graphics of the vm couldn't keep up) and the most annoying piece is, that there is no way to disable the Win-L hotkey, which I used too often in awesome.. And I can't to another modkey, as Ctrl is awkward and Alt already used in too many applications. > If you have a dual monitor setup like I do, then the rare occasions that > you actually *do* need something in windows, you can setup something like > tinyvnc so you really don't have to leave the comforts of home. Yeah, the displaylink setup explicitly exploited that by keeping windows in single-screen mode on the laptop and linux with awesome via displaylink on the external screen. I'd love to have something like splittable graphics cards for pci-redirection of only the external connector ;) Regards, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: surviving as a windows user
Hi Ignas, On Tue 29.10.2013 15:41:30, Ignas Anikevičius wrote: > "Andre Klärner" wrote: > > as my post to Eugen's thread has reminded me, does anyone of you have > > to use a microsoft windows (e.g. at work)? I am stuck with it, with no > > way to get around using windows, but every day I am once again struck > > again by the stupidity of using windows.. > > > > Has anyone of you to deal with something alike and found a solution, > > how to at least get something awesome-like as a window manager? If > > there anything that can lessen the pain? ;) > > I also need to use Windows from time to time and I found this DWM port to > windows, although it did not satisfactorily work for me. That was > probably because I was too lazy with diving into the source code and > configuring it. > > The link: > http://www.brain-dump.org/projects/dwm-win32/ I tried it an hour ago.. most of the hour I spent waiting for windows to boot again, as it crashed my pc.. Thanks, but I don't think it's really made for win7 (at least the last version is from 2009). Regards, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: surviving as a windows user
Hi Eugen, On Tue 29.10.2013 20:08:49, Eugen Dedu wrote: > On 29/10/13 16:36, Andre Klärner wrote: > >as my post to Eugen's thread has reminded me, does anyone of you have to > >use a microsoft windows (e.g. at work)? I am stuck with it, with no way to > >get around using windows, but every day I am once again struck again by the > >stupidity of using windows.. > > > >Has anyone of you to deal with something alike and found a solution, how to > >at least get something awesome-like as a window manager? If there anything > >that can lessen the pain? ;) > > Could http://en.wikipedia.org/wiki/Dynamic_window_manager be at help? Well, I looked at exactly this page already about two years ago. But for some reason I only looked into windawesome which didn't work for me. But bug.n sounds a bit more interesting today.. I'll try probaply now ;). Thanks, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: Some questions from an awesome beginner
On Tue 29.10.2013 19:42:59, Paweł Rumian wrote: > 2013/10/29 Eugen Dedu : > > On 29/10/13 14:31, Paweł Rumian wrote: > > Most of the tasks that you've mentioned above are perfectly doable by > simple programs that adhere to Unix philosophy (that 'do one thing > good' one). > No worries. Couldn't agree move. For me the gnome-sound-applet does the trick for controlling the master pulseaudio volume, and everything else is done using pavucontrol. > After some time icons seem to be absolutely redundant when you have > command line with tab completion just one keystroke away. > Screensaver? Take this, in 7kb there aren't many things that could > interfere with other programs > http://tools.suckless.org/slock Or back to the good old xscreensaver which has the coolest hack ever: xmatrix ;) > > I exaggerate a bit, but it is like now we cannot buy assembled computers > > anymore. One has to choose each of the pieces to have a computer. It is > > useful to have customisation, but is there a customisation ready to use, > > familiar to people coming from a desktop manager? > > For me it would be like buying an already-built LEGO model ;) > Assembling your own desktop environment can be fun... Oh, and what a fun it is. > > Well, I noticed several people are happy with that. But I am too habituated > > to have some applications at fixed size and at fixed locations, and minimise > > them when I do not need them. > > Perhaps you are among those people who would never adopt to tiling, > but honestly speaking, I doubt it. > Instead of minimizing applications, just switch to a fresh tag... Yeah, that might take a little getting used to. I also starting using mostly two or three tags like I did with workspaces under gnome. But now I always have 10-15 tags open, each with it's specific set of applications. > > Well, I still use gnome-terminal, so the settings are the same as in gnome. > > Still, in gnome there was a bell, now there is not. And "terminal bell" is > > checked on in terminal settings. > > Hmm, a bit strange... Perhaps Gnome configured sound system in some > way at start? > Do you have any sounds at all? I guess you might need to take a llok > at alsa/pulseaudio/whatever else is there... I'd guess it's some kind of xbelld thing within gnome. Regards, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: surviving as a windows user
Hi Enric, On Tue 29.10.2013 19:03:03, Enric Morales wrote: > On 29 Oct 2013 16:36, Andre Klärner wrote: > > Has anyone of you to deal with something alike and found a solution, how to > > at least get something awesome-like as a window manager? If there anything > > that can lessen the pain? ;) > > You don't state the windows version you are using but, in windows 7, > when you drag and drop windows to the edges of the screen they can split > the space effectively like the tiling feature in awesome, although the > OS won't do it for you, which sucks, but at least you don't have a > floating windows mess. Yeah, you guessed right. I think with XP I'd already given up.. > > If you drag the window to the top it maximises, and in the side edges > they take half of the screen. I know about the AeroSnap features, while I mostly use the Win-Left/Right/Up combinations. But the annoying thing is that the Alt-Tab sequence is totally unpredictable. When I minimize a window it goes to the last spot, except there are other minimized windows, than it gets (seemingly) prepended to the other minimized, but after all visible windows. And than are there windows like google hangouts chrome extension that stay no matter what always in the front of all other windows in the list. This is simply annoying as hell. So what I am missing is the kind of tagging feature wich works on curating windows to tags using rules like awesome can. > I am also stuck at windows, but I try to do as much as I can via a tmux > session over SSH, and the rest I have to manage with this > drag-to-the-edges-of-the-screen crap. Well, I am lucky enough to have mobaxterm as an at least acceptable unix-like terminal, while urxvt with screen in comparison simply kicks ass. But most of my job takes place in outlook and browser-based ticketing/alerting/cmdb windows which is window-wise just a PITA. Thanks and regards, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
surviving as a windows user
Hi guys, as my post to Eugen's thread has reminded me, does anyone of you have to use a microsoft windows (e.g. at work)? I am stuck with it, with no way to get around using windows, but every day I am once again struck again by the stupidity of using windows.. Has anyone of you to deal with something alike and found a solution, how to at least get something awesome-like as a window manager? If there anything that can lessen the pain? ;) Thanks a lot guys, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: Some questions from an awesome beginner
Hi Eugen, On Tue 29.10.2013 15:58:12, Eugen Dedu wrote: > I noticed how to add some of this *manually*. I searched for a > gnome-ish style with all this inside, so that I do not spend hours > for it. And, since it uses external programs developed > independently of awesome, I fear that I will run into trouble. But > I will try. Well, I feel like you should know, that some on this list did all this a while ago. Awesome is not like gnome or kde or xfce. It is more a unique way of approaching the desktop. Some consider it more a desktop framework than actually "just" a window manager ;). I myself had 3 attempts at switching to awesome. The first time I saw it was on a lighning talk at a university nearby, I found it fascinating and tried it back home a few days later. But I had to get stuff done and didn't have the patience to look up the keybinding everytime I wanted to do something. The second time was, when I stumbled over it in a youtube video. I still liked the concept, so I gave it a go and ran it for a few days before getting too annoyed to run back to gnome for doing my work. But this was still in the times, when gnome's latest version was 2.6 and really usable. But than a while later the first version of gnome3 came to my desktop, it slipped through in an update.. So as the first gnome3 version were quite unusable I thought back to what I might want to switch to now. And I remembered awesome and how awesome this concept was. But this time I was upset enough with gnome, so there was no way I'd ever switch back to gnome at this point in time. So I ran a "man awesome|lpr", glued that to the wall above my desk and starting using the default config. It took me maybe a week to get used to the keyboard bindings, and maybe a few months to create my own config. But now after using it for about two years I'd never go back to anything else. Gnome's gotten better by now, I can recommend it without doubts to my friends and colleagues, but I always will tell them, if they want to be really productive they should give awesome a try. > I exaggerate a bit, but it is like now we cannot buy assembled > computers anymore. One has to choose each of the pieces to have a > computer. It is useful to have customisation, but is there a > customisation ready to use, familiar to people coming from a desktop > manager? Well, actually the default config is really usable. It has many tags (like gnome), it has floating windows and sloppy focus. What it misses are things that everyone would like to customize later. I am lazy, so I am still running gnome-settings-daemon, gnome-sound-applet, nm-applet in the background, and they might not integrate perfectly, but they'll do what they are supposed to do. If you take one thing away from this really lengthy mail, than that: Keep going, adapt the config to everything you need. You will never regret putting the work into this, as the benefit to too high. Regards, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: Restore Hidden Clients
Hi Hugh, On Fri 18.10.2013 04:48:49, xiheasas wrote: > I have some problem to restore the hidden clients. Initially I have 3 > clients in a tiling manner, and I maximize one of the clients, and the > other two clients are hidden. I want to know if there is any key shortcut > to make the two unmaximized clients visiable and restore the layout as > previous? What about reversing the maximization? The default config simply negates the maximized state when pressing modkey+m. Regards, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: spawn something on a certain tag without rules
Hi Manuel, On Sat, May 11, 2013 at 02:55:59PM +0200, Manuel Kasser wrote: > > there should be ways, but nothing works without rules. > Ok, then I'll do it with a rule. Your proposals gave me the idea of > tracking the name of the client which would be sufficient. Thanks! > > But I ran into another problem: using pcmanfm the name of the window is > the name of the folder it is in, which would be completely sufficient to > be used in a rule. Unfortunately this only works for pcmanfm-clients > which aren't the first window of pcmanfm spawning, because the name is > "pcmanfm" on startup and switches to the folder's name slightly later. Did you ran a xprop on a started window? I guess it will have a class like "pcmanfm" or so, that you can use to track all windows pcmanfm creates, and a name the represents your current instance. I guess you are starting your clients via a script - and that already knows about the folder to start (as it gives it as argument to pcmanfm-client). So you should be able to extract the portion that is used in the window title and use that for your rule (coupled with class=pcmanfm). Regards, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: spawn something on a certain tag without rules
Hi Manuel, On Wed, May 08, 2013 at 07:44:27PM +0200, Manuel Kasser wrote: > Hi, > I want to start a process on a certain tag. I could do this combining > awful.util.spawn() and a rule, but in this case I need to do it entirely > without a rule. > > The exact scenario is that I have a script which changes to a certain > directory and starts a filemanager (pcmanfm) in there afterwards. This > filemanager shall come up on a certain tag (getting the correct tag is > no problem). > > But just this filemanager spawned by this script shall be started on > this one tag, other filemanager processes shall not be affected by this > (that's why I can't work with a rule, because the way of spawning is the > only differernce between certain instances). > > Any good ideas how to archieve that? I can pipe most commands to awesome > from a shellscript via "echo 'command' | awesome-client", if someone there should be ways, but nothing works without rules. But you should be able to figure out a rule that matches at exactly this time for the process you spawn (like by PID or by class and window title) and add this rule to the running awesome-instance via awesome-client. So this rule would be temporary until awesome is restarted the next time. If you check the archives of this mailing list you should find that similiar discussions were held this and last month. Regards, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: launching a program on a tag, without static rules
Hi Daniel, On Fri, Apr 26, 2013 at 04:51:26PM +, Daniel wrote: > Yeah I've begun to understand the strangely complicated nature of this. > I just want to tell a program where it should open its window(s), and > not have to find and move it afterwards. Ideally from the outside, upon > launching, but it seems hard even from inside the program. just a small question: if you don't want to use static rules, why don't you "compile" the just before launching and feed them to awesome via awesome-client? That way they don't exist in the config and you have only to maintain within your launcher the ruleset how to match your starting app. Regards, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: How to change Awesome WM's DPI from 96 to 120?
On Thu, Feb 21, 2013 at 03:42:14PM +0100, Uli Schlachter wrote: > On 20.02.2013 13:41, WANG Chao wrote: > [...] > > After some work, any X client's DPI is 120 except Awesome WM itself. > > Fonts on taglist/tasklist/wibox/naughty/... still uses DPI 96. > > How are you setting the DPI everywhere else? Shouldn't one set this via the xorg.conf? I think there was an option to set the DPI for each screen, which should be determined usually automaticaly? Regards, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: dual monitor sleep problem
Hi Vincent, On Wed, Feb 20, 2013 at 06:46:32PM +0100, Vincent Bernat wrote: > ❦ 20 février 2013 13:45 CET, Ekram : > > > Hi I have a strange problem in awesome 3.4. > > I have dual monitor but when my monitor goes to sleep mode > > sometimes one monitor never come up. > > I have the same problem on one host. I am pretty sure this has nothing > to do with awesome (this is too low level for a window > manager). However, I am able to fix the situation without logging out by > using "xrandr --output DVI-1 --off". This is odd because it turns the > output off, then on, without further interaction. Might this also work by running just "xrandr" once? If you don't change anything it still tries to refresh the table of currently connected outputs and the DDI-data. Regards, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: Autostart with dex - only execute once
Hi Rainer, On Thu, Feb 07, 2013 at 09:40:30AM +0100, Rainer M Krug wrote: > On 06/02/13 20:15, Andre Kl￤rner wrote: > > On Wed, Feb 06, 2013 at 04:09:48PM +0100, Rainer M Krug wrote: > > Maybe run dex just from the ~/.Xsession and not from the awesome-config? > > I sometimes use other WN - so it won't work for me. In addition, I prefer to > have the whole > awesome config together in one place. > > > Or put your call to dex into a script that checks the value of > > /proc/sys/kernel/random/boot_id > > against a .cache/awesome/dex-last-boot-uuid and if they match don't start > > it. > > This sounds interesting. But I have to write the value > .cache/awesome/dex-last-boot-uuid myself - > correct? I think I will try this approach. Yeah, I also thought about implementing it, but than came the time of beeing too addicted to awesome, so I resorted to using .Xsession and forgetting about all the other DEs that simply annoy me. ;) > >> Is there a way that I can make sure that nirtogen is executed after > >> gnome-settings-daemon is completely started? > > > > Well, I think there was a setting to prevent gnome-settings-daemon from > > drawing the wallpaper. > > > > Gconf-Key: /desktop/gnome/background/draw_background (accessible with > > gconf-editor) Dconf-Key: > > org.gnome.desktop.background (accessible with dconf-editor) > > > > Both are bools that you just need to toggle so gnome-settings-daemon stops > > if forever. > > OK - done and working. Perfect. > > I changed both - but I assume one is gnome3 and the other an older version - > correct? Exactly. Regards, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: Autostart with dex - only execute once
Hi Rainer,
On Wed, Feb 06, 2013 at 04:09:48PM +0100, Rainer M Krug wrote:
> I am using dex for autostart applications and I have the following in my
> rc.lua:
>
> awful.util.spawn_with_shell("gnome-settings-daemon && dex -a -e Awesome")
>
> Now I have two problems:
>
> 1) When I change the screen setup via e.g. arandr / xrandr, awesome is
> restarted and consequently
> dex is executed as well. This causes multiple instances of e.g. skype and
> other programs to run
> which are started via sutostart and dex. Is there a way that I can tell
> awesome to only execute
> dex, when it hasn't been executed before? Effectively a run-once for dex, but
> as dex is not
> running anymore (and only doing the autostart), the approaches described in
> the wiki wont work.
> Any suggestions?
Maybe run dex just from the ~/.Xsession and not from the awesome-config?
Or put your call to dex into a script that checks the value of
/proc/sys/kernel/random/boot_id against a .cache/awesome/dex-last-boot-uuid
and if they match don't start it.
>
> 2) in the autostart I have nitrogen for setting the background of my dual
> monitor setup
> independently fr each monitor. Now gnome-settings-daemon is setting the
> background as well, and
> most of the time gnome-settings-daemon has finished setting the background
> before nitrogen is
> called and everything is fine. But sometimes this is not the case, and
> gnome-settings-daemon is
> resetting the desktop. Is there a way that I can make sure that nirtogen is
> executed after
> gnome-settings-daemon is completely started?
Well, I think there was a setting to prevent gnome-settings-daemon from
drawing the wallpaper.
Gconf-Key: /desktop/gnome/background/draw_background (accessible with
gconf-editor)
Dconf-Key: org.gnome.desktop.background (accessible with dconf-editor)
Both are bools that you just need to toggle so gnome-settings-daemon stops
if forever.
Regards, Andre
--
Andre Klärner
smime.p7s
Description: S/MIME cryptographic signature
Re: Shifty and Revelation
On Thu, Jan 31, 2013 at 10:08:10AM +0100, David Soulayrol wrote: > > > I appreciate those who have helped with pull requests and such but I feel > > > shifty has been > > > obsolete for some time now. > > > > Could you lease elaborate on this? I am using shifty, but if I can achieve > > the same in similarly > > easy fashion, I would be really tempted to stick with "out of the box" > > awesome? Could you please > > give some examples? > > I'm also interested in this. What I like with Shifty is the automatic > creation and removal of tags when there are no more clients in it. Is it > possible to handle this in a simple way with a raw awesome > configuration? I'd also like to add a question: How can one achieve dynamic creation and deletion of tags? I use it e.g. to start my mutt instance. Instead of running a program I create a new tag named "mutt", which will end on the right position, and when it's created it starts my mutt-script. Thanks and regards, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: getting max window size for a shell script
Hi Vitor, On Tue, Jan 22, 2013 at 06:39:16PM -0200, Vitor Eiji Justus Sakaguti wrote: > On Tue, Jan 22, 2013 at 6:18 PM, Andre Klärner wrote: > > Did somebody already do this or has an idea how to fix the workarea > > geometry? > > You can use awesome-client to get the workarea from awesome. > See > http://awesome.naquadah.org/doc/api/modules/screen.html#screen thanks a lot, that works perfectly. But has anyone an idea why the standard way in rdesktop does not work? I saw (via xprop) that the _NET_WORKAREA property is present, but rdesktop seems not to be able to use it. Should I file a bug for rdesktop? Thanks and kind regards, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
getting max window size for a shell script
Hi Guys,
does anyone have an idea how to determine the maximum available window
size? I want to use that in a connect script that starts rdesktop sessions,
but rdesktop will either use a default screen size or can run fullscreen
(both not cool for tiling wm users).
So I looked into the rdesktop manpage which mentions the special geometry
("-g workarea") that claims to:
"the geometry will be fetched from the extended window manager hints
property _NET_WORKAREA, from the root window."
Anyway that won't work under awesome, so I thought about running rdesktop
via a wrapper that determines the correct maximum window size. (I use max
layout for rdp-sessions, so the screen-size minus the 1px borders and the
wibox on the top edge).
Did somebody already do this or has an idea how to fix the workarea
geometry?
Thanks and kind regards,
Andre
--
Andre Klärner
smime.p7s
Description: S/MIME cryptographic signature
Re: Maintain client layout on XRandR event
On Tue, Jan 22, 2013 at 06:34:41PM +0100, Marco wrote: > On 2013–01–21 Andre Klärner wrote: > > > > I don't know how other window managers deal with this issue. Do they > > > all completely lose the state and fall back to the default window > > > configuration? > > > > Well, I for my part also had the problem that the state got lost, but I was > > also annoyed by the fact, that on each boot (and my work-machine has to be > > powered on and off each day) I have to start all applications again and > > move them to the right tag, and so on. So I looked around and found rules > > and shifty. > > Rules are a very powerful tool that I appreciate since my first day > of using awesome. They are great for setting up static and > predictable applications such as web browser, IRC client, mail > reader, etc. > > However, they are only usable if the setup can be expressed as a > rule (this applied to shifty as well, since shifty is also driven by > rules). One problem you already mentioned yourself: some things are > hard or impossible to express as a rule. Well, I also thought that of most of my rules I have today (e.g. one of the first: how do I get pidgin of the rightmost screen at home, while on the primary at work) are harder to discribe at first, but once you got the first idea it takes only minutes to complete this to perfection. > Awesome allows for manual adjustment of tiling layout, window > proportions (mwfact), number of master windows, etc. If everything > could be expressed as a rule these functions would not be necessary. > Tagging clients manually would also be superfluous. Yet, there is a > reason that all these adjustments can be done manually and people > use it for good reasons. And it's exactly those settings that get > lost when awesome restarts, those settings that can't be expressed > by rules because they were set up during the work flow, like your > VLC or virtualbox setup. Well, but I (IMHO) consider the manual changes to be not valuable. I use quite often one up to ten terminals to our jump host at work, but the sizes of them always depend on what I am doing that day. If I am batch-running SLES upgrades I have no need to manuall adjust anything, but if I repair a database server I need to connect and do stuff on a small term while watching the long lines in another widescreen term. So this isn't hard-programmable, but in this case the change of mwfact is matter of seconds if I really need to restore it after an undock event. > Rules can surely reduce the mess created during a restart, but they > don't solve the foundational problem of forgetting the state. Well, someone posted a while ago the following git-repo: https://github.com/dodo/uzful/blob/master/restore.lua If I remember right it should do exactly that: remembering (some) state. Anyway I still know that there are things that annoy me: my new 27" screen at home is connected via displayport, so if I power it down the gfx card disables this screen via xrandr and let's awesome restart, while when I power it back on the same happens again.. Well, this will drive me to finally do what I wanted to do for a while: write a applet that runs the urxvt->screen->ssh path to any of my machines and let's me reconnect to them, while creating a tag for each of them in shifty.. ;) Regards, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: External monitor and wallpaper in awesome 3.5
Hi Levent, On Tue, Jan 22, 2013 at 06:25:47AM +0100, Levent S.B. wrote: > thanks for the help. I didn't realize awesome restarts automatically when > a randr-command is executed. Still, even when i add the restart command > you proposed to my randr-script, which doesn't make sense as implied in > your mail, i need to restart awesome one more time after executing > XRandR. Well, as it's only striking mod4+crtl+r, i can live with the > bug. well, it depends on what xrandr events are finally generated by the script. I noticed that if I only change the primary screen (xrandr --output DP-4 --primary) that awesome didn't restart in this case. But that is more closely written in issue #498. Maybe post your randr-script? Regards, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: Maintain client layout on XRandR event
Hi Marco, On Mon, Jan 21, 2013 at 04:26:59PM +0100, Marco wrote: > On 2013–01–21 Uli Schlachter wrote: > > > It's doable, but other stuff is more important. > > That's arguable :) I agree if you use a desktop with a static screen > setup. But if you use a laptop and reconnect your screen 4 times per > day, you will re-state you priorities. > > I don't know how other window managers deal with this issue. Do they > all completely lose the state and fall back to the default window > configuration? Well, I for my part also had the problem that the state got lost, but I was also annoyed by the fact, that on each boot (and my work-machine has to be powered on and off each day) I have to start all applications again and move them to the right tag, and so on. So I looked around and found rules and shifty. I loved the dynamic stuff of shifty, so it took me quite a while, but by now each window get's opened where it belongs, and I have only 2 corner cases: my vlc is quite movable depending on in which situation I am, and virtualbox is not always on the tag I'd like to have it on (depending on quite complex rules, that I am not able to write down - else this would have been solved by now). So I resolved all this with a config that looks at the hostname and screen.count() and depending on these it layouts my tags and defines which window to be on which screen. So if I really do this perfect I'll never have to care if it is restarting or just adjusting the screens-table. (well, my current config would break if the config wouldn't be fully evaluated again, so the tradeoff is : restarting or changing table and reloading config - I guess restarting costs less time) Regards, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: Awesome vs. LXpanel
Hi Levent, On Sun, Jan 20, 2013 at 09:49:16AM +0100, Levent S.B. wrote: > And yet another question concerning my personal awesome-lxde mix. > Since upgrading to awesome 3.5, awesome started auto-focusing on > the lxde-panel if i change to another tag. This is very inconvenient, > as the panel is killed if i hit mod4+shift+c accidentally, when aiming to > close a different window. Also, the transparent panel appears with an > annoying black line to the top. > > I already edited my rc.lua, as described in a post by Uli > (http://www.mail-archive.com/awesome@naquadah.org/msg03349.html), > to keep the panel from being focused on-click. Well, I think you should only mix both: filter also when handling the mod4-shift-c keybinding. -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: External monitor and wallpaper in awesome 3.5
On Sun, Jan 20, 2013 at 08:43:40AM +0100, Levent S.B. wrote:
> If i use smartbg-git, and i attach another monitor with an XRandR
> script, i have
> to restart awesome for smartbg-git to set the wallpaper. adding
> "/usr/bin/awesome restart"
> to my script wouldn't work, as LXDE is already running. Is there a
> way to send
> a restart command to awesome in a script, like the one that is
> invoked by "Mod4+Ctrl+r"?
> Of course this is a minor issue :)
Well, awesome should automatically restart once it receives the
randr-events that a new screen is detected or removed. But anyway:
# echo "awesome.restart()" | awesome-client
should do the trick of restarting awesome.
regards, Andre
> Am 20.01.2013 07:55, schrieb Levent S.B.:
> >Great!
> >Installed smartbg, restarted awesome, got a nice wallpaper on both
> >monitors instantly.
> >Thanks for the tip!
> >Levent
> >
> >
> >Am 19.01.2013 19:03, schrieb Prashanth:
> >>Since you're on Arch Linux already, I recommend smartbg (
> >>https://aur.archlinux.org/packages/smartbg-git/). This works
> >>perfectly for me; each monitor gets a different wallpaper.
> >>
> >>On 19/01/13 17:30, Levent S.B. wrote:
> >>>Hi there!
> >>>I"m running awesome as a window manager for LXDE on 64bit ArchLinux
> >>>and just upgraded to awesome 3.5 yesterday. I'm done with my
> >>>rc.lua workover
> >>>and everything works fine, except for one little issue:
> >>>When i attach an external monitor via XRandR, the Wallpaper, instead of
> >>>being drawn on both screens separately, gets moved to the
> >>>external Monitor,
> >>>leaving the actual LVDS display without wallpaper (save for a
> >>>piece of it's lower right corner).
> >>>I guess i have to change something in these lines of the rc.lua?
> >>>
> >>>
> >>>-- {{{ Wallpaper
> >>>if beautiful.wallpaper then
> >>>for s = 1, screen.count() do
> >>>gears.wallpaper.maximized(beautiful.wallpaper, s, true)
> >>>end
> >>>end
> >>>-- }}}
> >>>
> >>>
> >>>Can you help me out here?
> >>>
> >>>Greetings,
> >>>Levent
> >>>
> >>
> >>
> >
> >
>
>
> --
> To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
--
Andre Klärner
Telefon: 0351/79666546
Fax: 0351/79688547
Mobil: 0172/9838653
Anschrift:
Prohliser Allee 43
01239 Dresden
Diese E-Mail ist mittels S/MIME signiert worden.
Für S/MIME sind die Root-Zertifikate der CAcert.org zu installieren
(unter http://www.cacert.org/index.php?id=3 zu finden), damit mein
Zertifikat als vertrauenswürdig eingestuft wird.
CAcert.org ist eine offene Zertifizierungsstelle für SSL-Zertifikate auf
Basis eines Web-Of-Trust. Weitere Details finden Sie auf der Website.
Wenn diese E-Mail nicht als authentifiziert angezeigt wird, überprüfen
Sie bitte doppelt die Korrektheit dieser Mail.
smime.p7s
Description: S/MIME cryptographic signature
Re: zap naughty notifications
On Sat, Dec 15, 2012 at 04:43:21PM +0100, Juergen Descher wrote: > Quoting Daniel (Sat, 15 Dec 2012, 15:37:08): > > Just try with the latest awesome from git; you cannot access > > naughty.notifications from your rc.lua. It is local to the module; all you > > get > > is nil. It happened here: > Ok, didn't know. Shouldn't it be possible to patch naughty, so that you can query it for a list of active notifications? Regards, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: Program that runs of 2 monitor.
Hi Dominik, On Tue, Dec 04, 2012 at 06:09:09PM +0100, Dominik "Socek" Długajczyk wrote: > I am making a program in Qt that will manage on two screens. My program > will decide on which screen (monitor) will the window appear. How set the > awesome-shifty configur, to make my program able to do that? Well, how do you "make your program go to the other screen"? I'd would solve it by assigning a quite uniqe window class name to each of the window, like "$app-screen1" and "$app-screen2" and use shifty to put each of the window classes on it own screen.. Or is your requirement that the app will behave the same if not running under a cool window manager? Regards, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: [ANNOUNCE] awesome 3.5-rc1 released (was: [ANNOUNCE] awesome 3.4-rc1 released)
Hi guys, it's never too late to release ;) Anyway: can someone prepare a debian package? Thanks and kind regards, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: Automatic titlebars
On Wed, Nov 14, 2012 at 03:20:21AM +0100, Adrian C. wrote: > On Mon, 12 Nov 2012, Yuri D'Elia wrote: > > It would be even nicer though if floating/unfloating a window in a > > tile would also handle (hide/show) the titlebar properly > > Just update the floating toggle keybinding. But what if the client gets set to floating by a rule or by itself? Than that won't work, right? -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: Addition: Externalise part of the wibox.widgets-code
Hi Manuel,
I did something similar, I run this near the top of my rc.lua:
-- Determine hostname (stolen from https://github.com/xtaran )
local io = { popen = io.popen }
local f = io.popen("hostname")
local hostname = f:read("*all")
f:close()
hostname = string.gsub(hostname, '[\n\r]+', '')
naughty.notify ( { text = "awesome running on " .. hostname } )
if hostname == "sapdeb2" then
autorunsapdeb = true
systrayscreen = 1
else
autorunsapdeb = false
systrayscreen = math.max(screen.count(), 1)
end
which sets some variables I use to adjust awesome's behaviour according to
the machine it is running on.
I guess it might be possible to use that kind also for widgets. One of my
examples is for shifty's config:
chat = {
layout = awful.layout.suit.tile.left,
mwfact = 0.20,
exclusive = true,
position= 9,
init= true,
screen = ( autorunsapdeb and 1 or math.max(screen.count(),1) ),
},
You should be able to use a "machineA and widgetX or nil" to optionally
disable a widget.
@Anyone: please correct me if I missed something, I am still a bit noobish ;)
regards,
Andre
--
Andre Klärner
smime.p7s
Description: S/MIME cryptographic signature
Re: Invert the screen in a dual head setup
On Sat, Oct 27, 2012 at 02:49:16PM +0200, Marco wrote:
> 2012-10-26 Andre Klärner:
>
> > (pure IMHO) Well, if I remember right VidMode is as ancient as X11
> > itself. As RANDR was patched in later, and allowed to mix physical
> > outputs to one "protocol screen" there still needed to be a way to
> > calibrate each output for itself. So I guess one has to either
> > create a ICC profile that does the inversion for each monitor and
> > use some of the screen calibration utilities to load it (probaply
> > not xcalib ;) or port xcalib's invert function to a single tool
> > that runs again RANDR (maybe redshift might be a good example).
>
> I think this is overkill, since it's not essential functionality, it
> just makes reading easier. I probably wouldn't bother writing a tool
> for that.
well, just as I had some time spare I read xcalib and redshift
comparatively and found this in the redshift code:
for (int i = 0; i < state->crtc_count; i++) {
r = randr_set_temperature_for_crtc(state, i, temp, brightness, gamma);
if (r < 0) return -1;
}
So redshift iterates via randr over all CRTCs that are composing this
X11-Display and sets the temperature on it.
xcalib instead does the following:
if (!XF86VidModeSetGammaRamp (dpy, screen, ramp_size, r_ramp, g_ramp, b_ramp))
warning ("Unable to calibrate display");
So xcalib sets it's modified version of the gamma ramp to the whole
display, and the X11 server decides which CRTC it will hit.
I also saw that there are many other conditionals for FGLRX in the xcalib
source. I guess that someone using xcalib with an AMD card might experience
other behaviour. If someone here is running a amd-dualhead setup I'd like
to hear if it works on both screens.
Maybe one should file a bug agains xcalib that it doesn't work on RANDR
setups.
Regards, Andre
smime.p7s
Description: S/MIME cryptographic signature
Re: Changing window property 'instance'
On Sun, Oct 28, 2012 at 11:52:00AM +0100, Uli Schlachter wrote: > On 28.10.2012 11:14, Claudio Kozický wrote: > > On Sun, Oct 28, 2012 at 09:44:02AM +0100, Uli Schlachter wrote: > >> On 28.10.2012 09:19, Claudio Kozický wrote: > >>> I'm autorunning chromium and want the autorun window to be moved to tag > >>> 3. After the chromium window is moved to tag 3, all additionally opened > >>> chromium windows get moved to tag 3 as well (I don't want that). To > >>> solve the problem, I have to change chromium's instance after the > >>> autorun chromium gets moved to tag 3. > >> > >> So you autorun chromium and it starts up with instance "chromium-autorun", > >> right? And non-autorun chromiums have instance "chromium". At least the > >> rule > >> from your original mail suggests so. > >> > >> That means you can make a rule that just moves chromium-autorun to tag 3 > >> and > >> doesn't move other chromiums...? > > > > Yes I autorun chromium with instance set to "chromium-autorun". When I > > decide to open another chromium window on a tag different from tag 3, I > > execute "chromium" on that tag. But the problem is that when I execute > > "chromium", chromium opens a new window which inherits instance set to > > "chromium-autorun" and therefore gets moved from whatever tag I executed > > the "chromium" command to tag 3. > > Isn't it somehow possible to make chromium start a new process instead of > letting the already-running one handle the new page? :-/ I guess starting chromium with --temp-profile or another profile should do the trick, right? regards, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: Invert the screen in a dual head setup
On Fri, Oct 26, 2012 at 08:33:04PM +0200, Marco wrote: > 2012-10-26 Uli Schlachter: > > But people wanted to move windows between screens, so Xinerama is > > created. To 'old' clients, Xinerama looks like a single, big > > protocol screen. However, only parts of it are visible. You can > > ask the Xinerama extension for which parts exactly are visible. > > > > Then came RANDR. RANDR doesn't really matter to this issue at all. > > It just made dynamic configuration possible. With Xinerama, you > > had to configure the layout before starting the server. RANDR > > makes it possible to enable new screens at runtime. > > I assume that the -s setting of xcalib operates on the "protocol > screen", the I don't understand why only one screen is inverted, > since they both belong to the same protocol screen. If RANDR uses > the same screen notion as Xinerama it also should invert both, since > both appear as a single one. (pure IMHO) Well, if I remember right VidMode is as ancient as X11 itself. As RANDR was patched in later, and allowed to mix physical outputs to one "protocol screen" there still needed to be a way to calibrate each output for itself. So I guess one has to either create a ICC profile that does the inversion for each monitor and use some of the screen calibration utilities to load it (probaply not xcalib ;) or port xcalib's invert function to a single tool that runs again RANDR (maybe redshift might be a good example). > > If I understand this correctly, then I didn't even know that X11 > > can do so. I never heard about xcalib either (and I haven't ever > > built and run xcalib). > > When I heard about the possibility if inverting a screen (or a > single window) I thought of it as a useless cheap gimmick. But once > discovered I have to admit that inverting is a very handy small > tool. I have two use-cases: > > ∙ insane web designers which print white text on black background > (often combined with a very thin font) Understandable for me ;) at least the other way round. I hate websites that use plain white (#FF) as background color, as usually I work and live at night, and this ruins my concentration and visual reception quality. > ∙ reading PDFs in a dark environment. Usually I set my PDF reader to > low-contrast (dark grey on light grey) for that, but some PDFs > use white as background and then the inversion comes into play. Well, to fix this work at night problem I'd really like to recommend redshift (for linux) and f.lux (for windows and mac os). It adjusts the color temperature of all outputs to a more night fitting red. So once you got used to seeing a slight red instead of white you will be much more relaxed over the night or in dark environments. And it also just "burns" the really bright colors, and doesn't make the dark onces totally unreadable. Regards, Andre smime.p7s Description: S/MIME cryptographic signature
Re: What should titlebars be like?
Let me be the first one to say: thank you Uli, we all appreciate your hard work. Looks awesome! Uli Schlachter schrieb: >Hi, > >On 21.10.2012 20:47, Uli Schlachter wrote: >> 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... > >Since there were so many replies to my mail, I'll just reply to my own >mail: > >Done, see the attached image. > >What I didn't do: Minimize/Fullscreen buttons, resize with just the >mouse >(although that wouldn't be hard...), anything with awful.rules > >But at least the hard part is done. :-) > >Cheers, >Uli -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: What should titlebars be like? (was: Release next major version - how bad could it be?)
Hi Uli, On Sun, Oct 21, 2012 at 08:47:16PM +0200, Uli Schlachter wrote: > 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... Well, I for my part would like to see only the following in the default config: (left to right) app icon if given, windows title, minimize, maximize, and close. Everything else should be easily extendibly by the user, and if possible via rules (so like a sticky button for some window-types or a globally toggable xprop/xwininfo button). What are you guys thoughts about it? regards, Andre smime.p7s Description: S/MIME cryptographic signature
Re: Problem with dual-screen scenario, second screen does not work
Hi Raimund, On Wed, Sep 19, 2012 at 02:52:19PM +0200, Raimund Sacherer wrote: > I am trying to use awesome as my main window manager. It works on the > same hardware out of the box on Ubuntu 12.04. I recently installed a > complete new system on another partition on the same equipment with > debian wheezy. > > Now If I start in debian wheezy my X session it opens awesome mirrored on > both monitors. > > When I do an xrandr configuration to say monitor x is on the left of > monitor y it works, but awesome is only on one screen, the other does not > have the top bar and no background, it's basically black. > > I can switch the focus to the other screen with the key combination, and > the cursor moves to the second screen (I can also move the cursor with > the mouse to the second screen) but I can't create windows (e.g. terminal > with mod4+enter). Also rightclicking with the mouse does not reveil the > awesome menu. > > > I am not sure if it's X-related, awesome-related or myself-related, I > hope someone had similiar issues in the past and can tell me how to fix > this, This sounds (for me) more like a Xinerama problem. Do you use the non-Xorg.conf scheme from Debian or did you have to build your own? Which driver do you use? Have you maybe tried another one? Do you use your own .Xsession, or the standard Debian-one? Regards, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
synergys and awful.screen.focus_relative()
Hi all together, I am using synergy a lot, and noticed that when I want to switch screens with the keybinding it works perfectly in one direction, but when I want to go from my right screen to my left one I won't stay there but move to the screen left of that (and that is only available via synergy). Initially I thought this might be kind of a feature, but in the meantime I often notice, that it is simply annoying. BTW: as on the other desktop is running awesome too, might there be a way to allow switching between the synergy-connected screens as if they were running within one awesome? Thanks and regards, Andre -- Andre Klärner smime.p7s Description: S/MIME cryptographic signature
Re: Slow Gaming
Hi David, are you running the games in a window mode? If yes it might be worth trying a compositing manager, like unagi or xcompmgr. Regards, Andre Thorsten Sperber schrieb: >Am 09.08.2012 10:41, schrieb David Gomes: >> Hey there everyone, >> >> When I use gnome-shell and I just open up a game like Sauerbraten, >> Warsow or Urban Terror, I can play smoothly, at 40 or 50 FPS. >> >> However, on Awesome WM (and for the record, any tiling window manager >> like dwm, or even openbox), the games won't go past 15 FPS. They're >> really really slow and unplayable. Any idea why? >> >> I actually have an idea... Hardware acceleration (or that OpenGL >> acceleration thingie), which I think Gnome Shell has enabled, but I >> don't know how I could fix it so that games could run just fine on >> Awesome WM. >> >> Thank you. > >That doesn't really make any sense...if some application makes use of >the GPU, then other applications have less resources, not more. There >must be some other difference. Is this the same machine, with both >gnome >and awesome installed? -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: blacklisting systray icons
On Sun, Jul 29, 2012 at 08:56:52PM +0200, wojtek danilo wrote: > 2012/7/29 Andre Klärner > > I did it with a "(unset DISPLAY ; dropbox start ) &" in my ~/.Xsession. > > > > I don't know if this will also work with skype, but it might be worth > > trying. > > very nice idea! > It works perfectly with dropbox ut not with skype. > Anyway - thank you very much for solving half of my problem :D Well, than that simply means that skype can't live without X11 - well, let's give it what it want. Try to use Xvfb or Xpra. With Xvfb you start an "invisble" second X11 server on e.g. :9 and run skype on it. This means you can't interact with it directly, but it won't mess up your tray. Should-Run example:"( Xvfb :9 & export DISPLAY=:9 ; skype ) &" I have not tested this, but it might work. The alternative might be xpra, it also starts another virtual X11 server, that you can attach/detach like screen. Or another solution might be Xvnc. But I am assuming a bit that all these things might cost you more CPU-time that you are willing to spend. It is also on my mind, that I don't know exactly how the pidgin and skype instances communicate together. If they use some really odd place like X11 root window properties to exchange information this won't obviously work. But I think the best solution forever would be to disable a client like skype simply. IMHO there are many more sane protocols out there to replace it. Regards, Andre -- Andre Klärner Telefon: 0351/79666546 Fax: 0351/79688547 Mobil: 0172/9838653 smime.p7s Description: S/MIME cryptographic signature
Re: blacklisting systray icons
On Sun, Jul 29, 2012 at 06:48:03PM +0200, wojtek danilo wrote: > > 2012/7/29 Musee U > > > On Sun, Jul 29, 2012 at 9:28 AM, wojtek danilo < > > wojtek.danilo@gmail.com> wrote: > >> And is there maybe a "linux way" to block some applications from > >> displaing thie icons on systray? > > > > I haven't used Skype in a while so I can't verify this but, have you > > checked to see if either Dropbox or Skype have an option to hide their > > systray icon? > > > yes I've checked it 100 times :( You might want to try starting dropbox without a set DISPLAY. This will at least prevent it from displaying a icon as well as the notifications (that was what annoyed me until I found the matching prefence setting for this). I did it with a "(unset DISPLAY ; dropbox start ) &" in my ~/.Xsession. I don't know if this will also work with skype, but it might be worth trying. Regards, Andre -- Andre Klärner Telefon: 0351/79666546 Fax: 0351/79688547 Mobil: 0172/9838653 smime.p7s Description: S/MIME cryptographic signature
Re: Screenshots of Menus
Hi all, On Thu, Jul 19, 2012 at 06:22:38PM +0200, Michael Hauser wrote: > Vivian Brégier ejaculated: > > eval $(tr '\0' ' ' < /proc/$(pgrep awesome)/environ) scrot > > Thanks for that oneliner. > > Telneting or sshing into the box is of course the obvious option. Well, it was too obvious for me. SSHing works best, a local VT seems not to work, I can do the screenshot fine, but only get a black image. Seems like the framebuffer gets overridden with all black when I switch to another VT. But ssh and a small shellscript did its job perfectly. If anyone 'd like to reuse it, this was all: | kandre@sapdeb2(pts/8) ~ % cat bin/screenshot.sh | #!/bin/bash | cd ~/Bilder | eval $( tr '\0' '\n' < /proc/`pidof awesome`/environ | grep -e DISPLAY -e | XAUTHORITY ) | scrot Thanks to all for helping me! Regards, Andre -- Andre Klärner Telefon: 0351/79666546 Fax: 0351/79688547 Mobil: 0172/9838653 smime.p7s Description: S/MIME cryptographic signature
Screenshots of Menus
Hi alltogether, I am currently trying to debug a problem with some strange behaving GTK-menus. I wanted to take a screenshot of the phenomen but somehow awesome does not get my keypress as long as the gtk-menu is open. As this menu-problem sometimes doesn't happen for days I can't always keep a recordmydesktop session open to capture that. Does anyone of you have an idea how I could get awesome to notice the keypress or a better approach to getting this captured? Thanks, Andre -- Andre Klärner Telefon: 0351/79666546 Fax: 0351/79688547 Mobil: 0172/9838653 smime.p7s Description: S/MIME cryptographic signature
Re: desktop is common across/shared by both screens?
Hi Alexander, hi all, On Tue, Jul 03, 2012 at 09:18:59PM +0300, Alexander Yakushev wrote: > Here's the article on implementing this particular thing: > http://awesome.naquadah.org/wiki/Shared_tags Does anyone of you know, if this is compatible to shifty? I'd like to move around a few of my tags quite freely, but currently this will only work with newly created tags. Thanks, Andre -- Andre Klärner Telefon: 0351/79666546 Fax: 0351/79688547 Mobil: 0172/9838653 Anschrift: Prohliser Allee 43 01239 Dresden Diese E-Mail ist mittels S/MIME signiert worden. Für S/MIME sind die Root-Zertifikate der CAcert.org zu installieren (unter http://www.cacert.org/index.php?id=3 zu finden), damit mein Zertifikat als vertrauenswürdig eingestuft wird. CAcert.org ist eine offene Zertifizierungsstelle für SSL-Zertifikate auf Basis eines Web-Of-Trust. Weitere Details finden Sie auf der Website. Wenn diese E-Mail nicht als authentifiziert angezeigt wird, überprüfen Sie bitte doppelt die Korrektheit dieser Mail. smime.p7s Description: S/MIME cryptographic signature
shifty: re-evaluate window title
Hi Guys, could anyone of you give me a hint how to get Shifty to re-check the windows titles when they change? I got a bunch of terminals at work, all going to some gateway-hosts and from there to a really big multiverse of landscapes of servers.. ;) Now I end up with exactly one tag with all my terminals to the jumphosts and then approx 5-20 other terminals to the same set of hosts. And once the EMC-Autostart cluster stuff comes up I stop being able to navigate this.. Previously I used a set of on most days 1-4 tags where each groups a set of hosts from a landscape. So, finally my thought: couldn't I just group the terminals my the hostname each sets in the window-title? So I end up with a set of tags, one host per tag and on tag per host.. In case it helps I can post my rc.lua. Greetings and thanks a lot to all of you. Andre -- Andre Klärner Telefon: 0351/79666546 Fax: 0351/79688547 Mobil: 0172/9838653 Anschrift: Prohliser Allee 43 01239 Dresden Diese E-Mail ist mittels S/MIME signiert worden. Für S/MIME sind die Root-Zertifikate der CAcert.org zu installieren (unter http://www.cacert.org/index.php?id=3 zu finden), damit mein Zertifikat als vertrauenswürdig eingestuft wird. CAcert.org ist eine offene Zertifizierungsstelle für SSL-Zertifikate auf Basis eines Web-Of-Trust. Weitere Details finden Sie auf der Website. Wenn diese E-Mail nicht als authentifiziert angezeigt wird, überprüfen Sie bitte doppelt die Korrektheit dieser Mail. smime.p7s Description: S/MIME cryptographic signature
