Re: updated wiki page xrandr screen table

[Andre Klärner]

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: updated wiki page xrandr screen table

[Uli Schlachter]

Hi again,

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


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 

> 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")

Uli
-- 
Bruce Schneier can read and understand Perl programs.

-- 
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.

Re: Some questions from an awesome beginner

[Marshall Mason]

Hi Eugen,
>From your work flow, it sounds like awesome is perfect for you. The
arrangement of the windows you described sounds ideal for tiling. Find a
tiling scheme that works for you, and just let awesome do the arranging for
you. Never move or resize windows ever again. It's hard to tell from your
description which layout would be best. Play with them, and see what you
like.

Awesome does have minimize functionality. The default key binding is Mod4-n
to minimize and Mod4-Ctrl-n to unminimize. It's certainly possible to use
tags instead of minimizing, but not necessary.

Tags in awesome, like its predecessor dwm, are a very flexible and powerful
way to use multiple desktops. To truly leverage its power, use tags
heavily. Since it's so flexible, how you use them depends on your
preferences. Some people like to have all instances of any given
application in each tag. You can easily configure awesome to always open an
application in a specific tag.

The way I like to use it is to use a tag for each project I'm working on.
All the relevant browsers, editors, and terminals are in their project's
tag. I use minimize whenever I want to hide an application relevant to a
specific project. I used to minimize often for windows that belonged to
different project. Now that I use tags heavily, I rarely need to minimize.

Your Thunderbird window sounds like its of more general interest, something
you want quick access to wherever you are. You could assign it its own tag,
and then just go to that tag whenever you want to see it. But then
everything else you're doing wouldn't be visible. If it's something you
refer to a lot when you're in your other applications, this is an ideal
case for tagging an application with multiple tags. If you hit
Mod4-Shift-Control-#, it will add that tag to the application. So if it's
in tag 1, and you hit Mod4-Shift-Control-2, it will be visible in both tags
1 and 2. Then you can minimize it when you don't need it. It's also
possible to view multiple tags at once, but hitting Mod4-Control-#. So,
another approach is to have Thunderbird in its own tag, and then when
you're in another tag and want to see Thunderbird, you just view both tags.
It all depends on what feels the most intuitive to you.

dwm has a tag 0, which represents all tags. I found this incredibly useful.
Awesome isn't configured with it by default, but it was trivial for me to
add it. That's where awesome really shines. You can literally add entirely
new features with a few lines of Lua code.

Marshall


On Wed, Oct 30, 2013 at 9:47 AM, 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)?  What do you put precisely in your tags and more
> importantly how do you use them?
>
> Note that permitting to have an app in several tags cannot be considered a
> reason to use tags.
>
>
> --
> Eugen
>
> --
> To unsubscribe, send mail to 
> awesome-unsubscribe@naquadah.**org
> .
>

Re: How to change naughty notification object text

[Tomás Solar Castro]

someone?


On Wed, Oct 23, 2013 at 7:07 AM, Maxim Bulatov  wrote:

> Hello,
> I'm using calendar2 widget (
> http://awesome.naquadah.org/wiki/Calendar_widget) long time and I need
> change it to 3.5 version.
> I understood all changes for all my configurations file except one. It can
> change month in notification
> when you scroll mouse.
> 3.4 source:
> calendar = { month, year, naughty.notify({..}) }
> calendar[3].box.widgets[2].text = 'new text'
>
> I don't know where is :set_text() now. I read naughty source, but I
> confused in terms and classes: layer, wibox, widget, margin and
> other. And I can not find widget in pairs cycle -- it is not table now.
>
> For long time I have commented line, but there is new task now where I
> need similar actions.
> I can recreate widget after naughty.destroy(), but it blinking.
>
> --
> dvenum
> dvenum...@gmail.com
>
> --
> To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
>



-- 
Tomás Solar Castro
GNU+Linux Registered User #383588
¡Sé Libre! http://www.FSFLA.org
http://identi.ca/tsolar

Re: Some questions from an awesome beginner

[Andre Klärner]

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

[Andre Klärner]

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

[Andre Klärner]

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

Re: Some questions from an awesome beginner

[Gabe Martin]

^ exactly. you can configure awesome to automatically assign an application
to a specific tag whenever it's launched. if your work flow is typically
less structured than that, you can also use them similar to workspaces,
just tossing up whatever things you happen to want on a screen together in
one place or in the same layout and then switching over to a new one when
you need more space. you could even do something like creating groups of
tags, assigning Mod4+# to switch to that tag number in whatever group of
tags you're currently using, assigning applications to be auto-assigned to
to that tag number in whatever group you're using or in a specific group,
and then switch between groups with a different key binding, in effect
giving yourself multiple workspaces each with their own set of tags. the
idea is for the system to be as flexible as possible so that you can
configure it to work exactly how you feel most comfortable.

Re: updated wiki page xrandr screen table

[Uli Schlachter]

Hi,

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

No idea if this feature is documented anywhere, but I think I just found a
volunteer to mention this in the wiki.

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.

Cheers,
Uli
-- 
Bruce Schneier can read and understand Perl programs.

-- 
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.

Re: Some questions from an awesome beginner

[zhtlancer]

Well, for me, the most benefit would be that I'll always know exactly where
an specific application should be, and I can switch to it immediately just
by switch tags. For a canonical WM, you may need to use alt-tab and stare
to find where one application is...


On Wed, Oct 30, 2013 at 12:47 PM, Eugen Dedu <
eugen.d...@pu-pm.univ-fcomte.fr> 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)?  What do you put precisely in your tags and more
> importantly how do you use them?
>
> Note that permitting to have an app in several tags cannot be considered a
> reason to use tags.
>
>
> --
> Eugen
>
> --
> To unsubscribe, send mail to 
> awesome-unsubscribe@naquadah.**org
> .
>



-- 
---
Thanks, and best regards!

Zhang Tao
Dept. Of Computer Science
Peking University
China

Re: Some questions from an awesome beginner

[Eugen Dedu]

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)?  What do you put precisely in your tags and more 
importantly how do you use them?


Note that permitting to have an app in several tags cannot be considered 
a reason to use tags.


--
Eugen

--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.

Re: Some questions from an awesome beginner

[zhtlancer]

Which distribution are you using, Ubuntu, Arch? Or more specifically, which
initscript system are you using, systemd, upstart?
For systemd users, this should be a trivial problem and you can check how
to handle pm event by checking man logind.conf.


On Wed, Oct 30, 2013 at 11:27 AM, Eugen Dedu <
eugen.d...@pu-pm.univ-fcomte.fr> wrote:

> On 29/10/13 19:42, Paweł Rumian wrote:
>
>> >>>suspend2ram when closing the lid (see below for others)?
>>>


 Use/configure acpid

>>>
> I suppose that many people there use a laptop which suspends when the lid
> closes.  I looked on Internet for maybe one hour without finding how to do
> it.  
> http://awesome.naquadah.org/**wiki/PowerManagementdoes
>  not help either.
>
> With gnome 2 closing the lid made suspend.  With gnome 3 it worked too,
> but after upgrading to recent gnome 3 it just blanks the screen.  Note that
> pm-suspend (as root) does work.
>
> Can someone share with me his solution to make suspend on lid closing?
>
> --
> Eugen
>
>
> --
> To unsubscribe, send mail to 
> awesome-unsubscribe@naquadah.**org
> .
>



-- 
---
Thanks, and best regards!

Zhang Tao
Dept. Of Computer Science
Peking University
China

Re: Some questions from an awesome beginner

[Eugen Dedu]

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...


--
Eugen

--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.

Re: Some questions from an awesome beginner

[Gerald Klein]

Tags in the awesome sense are basically 2 things, one you see them and can
use them as something similar to workspaces, 2 you can assign a tag to an
app for a "tag/workspace" it is not currently on and it will appear there
also, the fun thing about this is, that the app is not a seperate instance
but the same instance of that application which means that if it is a doc
then edits are in both places, if it is an app "Music Player" (dumb
example) it is in both places. This is great for having a reference
document that you need to use with other documents and you may have to edit
also, and you can have it on as many tags as you need.


On Wed, Oct 30, 2013 at 10:43 AM, Eugen Dedu <
eugen.d...@pu-pm.univ-fcomte.fr> wrote:

> First, thank to all who answered.  Next, see below...
>
> On 29/10/13 20:14, Andre Klärner wrote:
>
>> 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.
>>
>
> gnome-sound-applet does not exist anymore.  Using amixer sset (it is
> beautiful to use the notification for that cf. https://github.com/kiike/**
> scripts/blob/master/volume.sh)
> has a bug where it does not unmute, see https://bugs.launchpad.net/**
> ubuntu/+source/pulseaudio/+**bug/878986
> .
>
> (Until now, I spent ~10 hours with awesome and has not finished yet!)
>
>  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.
>>
>
> I do not really understand how to use tags.  My work flow involves the use
> of emacs, always open at left, with agenda and various "post-it" notes
> (random thoughts), thunderbird at the left half of the screen (minimised
> except when reading e-mail), firefox at the right half, and two terminals
> at bottom left and right, always opened.  All these apps do not change
> position.  From terminals I start applications (pdf viewer etc.) which
> float anywhere on the screen.
>
> When I have not done with an application (read half of a pdf doc for ex.)
> and have to swith to other things, I minimise it.  Thus, I have it always
> in the eyes, as if it were in the TODO list.
>
> I have never more than ~10 windows opened, since it becomes too complex to
> manage for me; I prefer working on 1-3 things at a time.
>
> So what the tags can improve in this work flow?  (The only thing I see to
> optimise is that often I open/minimise thunderbird to check messages or
> start an e-mail.)
>
>  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.
>>
>
> Have not yet found a solution for that.
>
> --
> Eugen
>
> --
> To unsubscribe, send mail to 
> awesome-unsubscribe@naquadah.**org
> .
>



-- 

Gerald Klein DBA

contac...@geraldklein.com

www.geraldklein.com 

geraldklein.wordpress.com

j...@zognet.com

708-599-0352


Arch Awesome, Ranger & Vim the coding triple threat.

Linux registered user #548580

Brought to you by the Amish Mafia

Re: Some questions from an awesome beginner

[Gabe Martin]

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.

Re: Some questions from an awesome beginner

[Eugen Dedu]

First, thank to all who answered.  Next, see below...

On 29/10/13 20:14, Andre Klärner wrote:

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.


gnome-sound-applet does not exist anymore.  Using amixer sset (it is 
beautiful to use the notification for that cf. 
https://github.com/kiike/scripts/blob/master/volume.sh) has a bug where 
it does not unmute, see 
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/878986.


(Until now, I spent ~10 hours with awesome and has not finished yet!)


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.


I do not really understand how to use tags.  My work flow involves the 
use of emacs, always open at left, with agenda and various "post-it" 
notes (random thoughts), thunderbird at the left half of the screen 
(minimised except when reading e-mail), firefox at the right half, and 
two terminals at bottom left and right, always opened.  All these apps 
do not change position.  From terminals I start applications (pdf viewer 
etc.) which float anywhere on the screen.


When I have not done with an application (read half of a pdf doc for 
ex.) and have to swith to other things, I minimise it.  Thus, I have it 
always in the eyes, as if it were in the TODO list.


I have never more than ~10 windows opened, since it becomes too complex 
to manage for me; I prefer working on 1-3 things at a time.


So what the tags can improve in this work flow?  (The only thing I see 
to optimise is that often I open/minimise thunderbird to check messages 
or start an e-mail.)



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.


Have not yet found a solution for that.

--
Eugen

--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.

Re: Some questions from an awesome beginner

[Paweł Rumian]

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

--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.

Re: Some questions from an awesome beginner

[Eugen Dedu]

On 29/10/13 19:42, Paweł Rumian wrote:

>>>suspend2ram when closing the lid (see below for others)?



Use/configure acpid


I suppose that many people there use a laptop which suspends when the 
lid closes.  I looked on Internet for maybe one hour without finding how 
to do it.  http://awesome.naquadah.org/wiki/PowerManagement does not 
help either.


With gnome 2 closing the lid made suspend.  With gnome 3 it worked too, 
but after upgrading to recent gnome 3 it just blanks the screen.  Note 
that pm-suspend (as root) does work.


Can someone share with me his solution to make suspend on lid closing?

--
Eugen

--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.

Re: Order of apps in statusbar

[Eugen Dedu]

On 29/10/13 18:05, Eugen Dedu wrote:

Hi again,

I notice that as apps are executed, their "icon" in the statusbar are
added at left.  For ex., the statusbar has "a", "b" and "c".  When I
start d, the statusbar becomes d, a, b, c.  I would like to become a, b,
c, d.  How to achieve that?

And why is the default right-to-left instead of the classical
left-to-right?


I found how to do it; I uncommented out:
awful.client.setslave(c)

--
Eugen

--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.

Re: Bugs when titlebar is on

[Eugen Dedu]

On 29/10/13 17:55, Eugen Dedu wrote:

Hi again,

I turned on titlebars by modifying:
 local titlebars_enabled = false
to this:
 local titlebars_enabled = true

Is this the right thing?


Anyone confirming that this is the right thing to do to enable titlebars?

I also noticed an issue with default rc.lua (titlebars disabled) when 
using emacs: when I start several emacs frames (ctrl-x-5-2), I simply 
cannot close them: crtl-x-5-0 shows an error in its statusbar and does 
not close window/frame.  Isn't this reproducible to you?!



With this, I experience two bugs which do not appear otherwise.

1. Opening a gnome-terminal by right-clicking in a gnome-terminal shows
a termianl with 3 lines only.


Reported at 
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1191&project=1&order=id&sort=desc.



2. Each time I restart awesome, windows are moved down a bit, I suppose
the height of the titlebar, as if awesome would retain the window
position without titlebar, and use it to position the window *with*
titlebar.


Reported at 
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1192.


--
Eugen

--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.