Re: local rc.lua not used

[Alexis BRENON]

The error message seems quite clear :

error loading module 'bashets' from file
'/usr/share/awesome/lib/bashets.lua':
/usr/share/awesome/lib/bashets.lua:1: unexpected symbol near '<

There is no error in your config file, but in the module you load. At the
first sight, I would say that you're not using the right Lua interpreter
(lua5.1 vs lua5.3) or something like this.

Kind,
Alexis.

Le ven. 2 sept. 2016 à 06:16, Ubuntu Linux  a écrit :

> I'm running awesome v3.4.15 on Linux ubuntu-TLS 4.4.0-36-generic (Xenial)
> I created the file
> -rw-r--r-- 1 chris chris 16819 Aug 26 21:54
> /home/chris/.config/awesome/rc.lua
> But the file is not loaded.
> awesome -k returns clean.
> Awesome starts with /etc/xdg/awesome/rc.lua and the awesome -> edit config
> menu will load this same file.
>
> The only errors I found were:
> [quote]
> chris@ubuntu-TLS:~$ cat  ~/.xsession-errors
> openConnection: connect: No such file or directory
> cannot connect to brltty at :0
> error loading module 'bashets' from file
> '/usr/share/awesome/lib/bashets.lua':
> /usr/share/awesome/lib/bashets.lua:1: unexpected symbol near '<'
> Failed to connect to session manager: Failed to connect to the session
> manager: SESSION_MANAGER environment variable not defined
>
> (xfce4-terminal:3256): Gdk-CRITICAL **: IA__gdk_window_get_window_type:
> assertion 'GDK_IS_WINDOW (window)' failed
> [/quote]
> Where else can I look for errors in the setup?
>
> Thank you,
> LinuxLover
>

Re: Awesome Configuration Improvement (Issue #442)

[Alexis BRENON]

Hi,

I don't have the time to read all the discussion on the issue #442 this
week-end, but maybe you can be interested in the way I have built my
rc.lua: many pure config files (just some assignments) and a call to
builder/backends to handle API changes and logic.
https://github.com/AlexisBRENON/awesome-configuration/blob/master/README.md#the-architecture
I'm very interested in taking part in the development to fix this issue!

Kind regards,
Alexis.

Le mer. 13 juil. 2016 22:17, Maxwell Anselm  a
écrit :

> I've been using Awesome as my go-to windows manager for a while now and
>> for various reasons have been playing around with it a lot more recently.
>> Browsing the github repo I came across issue #442 (
>> https://github.com/awesomeWM/awesome/issues/442) which discuss changing
>> the way rc.lua is constructed so as to make things more modular and move
>> the hardcoded logic somewhere more suitable (for example a new config
>> module).
>>
>> This struck me as something I might be interested in working on in my
>> free time this summer. It has been a few months since anyone posted on the
>> thread so I thought I would send an email here to see if anybody was
>> currently working on anything like this or had further thoughts as to how
>> this could be implemented.
>>
>
> I originally proposed these changes and I while I would still love to see
> them integrated, I just haven't had the time. Please feel free to take a
> crack at it.
>
> Because the potential changes are so sweeping, I think a good way to chip
> away at it would be to slim down rc.lua bit-by-bit. For example, take
> something like global/client key bindings and modify the Lua API so that
> they can be defined more simply and in a modular way.
>

Re: keybinding to switch to specific layout?

[Alexis BRENON]

Hi,

This seems to be a cool feature! I would probably do it the same way you
explain it (with table).
I'm waiting for your implementation!

Kind regards,
Alexis.

Le ven. 10 juin 2016 21:24, Jeroen Budts  a écrit :

> Hi all,
>
> After using the default (?) maximize keybinding for a while I would
> rather prefer it that modkey+m would simpley switch to the maximized
> layout to immediately maximize all clients and avoid some weird
> behaviour I sometimes see with maximized clients (they are sometimes
> behind other clients right after maximizing). I guess this should be
> doable using awful.layout.set('awful.layout.suit.max').
> However when pressing modkey+m again, I'd like to switch back to the
> previous layout for the tag, similar to the regular modkey+m keybinding.
> I'm not entirely sure how to do this. I could store the layout for the
> current tag in a table right before switching to the max layout and
> lookup the previous layout in the table when restoring from it.
> Has anyone done something like this already? Maybe it's just a crazy
> idea...
>
> Kind regards,
> Jeroen
>
> --
> website: http://budts.be/ - twitter: @teranex
> ___
> Registered Linux User #482240 - GetFirefox.com - ubuntu.com
>
>
>

Re: Stack-like behavior for restoring minimized windows

[Alexis BRENON @Awesome]

Hi Bill,

You probably have to do this manually, looking up a table each time you
minimize/unminimize a window. This way you can track which window was
minimized last and restore it.

Kind regards,
Alexis

Le dim. 5 juin 2016 à 19:57, Vitorio Miguel  a
écrit :

> would be interesting! it would be one of those things that show attention
> to details.
>
> 2016-05-17 10:53 GMT-03:00 Bill Sun :
>
>> Hi all,
>>
>> Currently there's a keyboard shortcut in my config so that I can use
>> keyboard to restore minimized windows. It reads:
>> awful.key({ modkey, }, "d", function (c) c.minimized = not
>> c.minimized   end),
>>
>> It works. Recently I noticed that when I have multiple minimized
>> windows, awesome always first restore the window that is created first.
>>
>> For me, it would be better if the un-minimizer has a stack-like
>> behavior: that is, restore first the window that is minimized last.
>>
>>
>> Any suggestions? Thanks.
>>
>> --
>> To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
>>
>
>

Re: Focus loss when switching between tags on multiple monitors

[Alexis BRENON]

Hi Viacheslav,

You probably have to restore focus, look at the
awful.client.focus.history.get function.
Another idea is to loop over the screens beginning with the current one
(with the focus or mouse) plus one and to finish with the current one:
awful.tag.gettags((current_screen + screen) % screen.count)[i]

Kind regards,
Alexis

Le ven. 19 févr. 2016 à 18:23, Viacheslav Mikerov 
a écrit :

> I am using two monitors and I wish to switch tags on both monitors, so I
> am using this for the tag switching function:
>
>for screen = 1, screen.count() do
> local tag = awful.tag.gettags(screen)[i]
> if tag then
>awful.tag.viewonly(tag)
> end
> end
>
> The problem is that all the time when I switch between tags, I lose window
> focus if it was on the first screen.
>
> How can I fix that?
>
> Best Regards,
> Viacheslav
>

Naughty notifications with buttons

[Alexis BRENON]

Hi guys,

I'm using blueman to transfer file between my laptop and my phone. But
blueman display many notifications with buttons:
To accept pairing
To accept incoming file
These notifications are displayed with naughty, but I can't click on the
buttons... Is there a way to fix this problem?

Kind regards, Alexis.

Re: Naughty notifications with buttons

[Alexis BRENON]

Ok, thanks for the answer. I stop using Naughty of I stop using blueman ;-)

Cheers,
Alexis

Le mar. 19 janv. 2016 20:12, Uli Schlachter <psyc...@znc.in> a écrit :

> Hi,
>
> Am 19.01.2016 um 11:00 schrieb Alexis BRENON:
> > Hi guys,
> >
> > I'm using blueman to transfer file between my laptop and my phone. But
> > blueman display many notifications with buttons:
> > To accept pairing
> > To accept incoming file
> > These notifications are displayed with naughty, but I can't click on the
> > buttons... Is there a way to fix this problem?
> >
> > Kind regards, Alexis.
>
> Awesome from Git has support for notification actions.
>
> Awesome 3.5 correctly signals that it doesn't support actions and so it's
> a bug
> in blueman that it tries to use them anyway. You could stop using naughty
> and
> instead use some other notification implementation that does support
> actions.
>
> Cheers,
> Uli
> --
> “I’m Olaf and I like warm hugs.”
>

Re: duplicate action from key bind

[Alexis BRENON]

Hi William,

First thing you can try is to see if the key is not sent twice. You can use
xev for this. In my case, the XF86IncreaseBrightness key code was always
sent twice (I haven't found why)...

I didn't read your configuration yet.

Regards,
Alexis.

Le mar. 22 sept. 2015 à 22:32, William Hatch  a
écrit :

> Hello,
>
> I've recently added some bindings that run their function twice when the
> keybinding is pressed.  My normal bindings use Mod4, occasionally with
> control or alt.  My new bindings that are having trouble are with Mod2
> (which is not numlock in my setup, and doesn't lock).  Any action I've
> tried for such key bindings executes twice.  I'm using awesome version
> 3.5.6 and my configuration file is here:
> https://github.com/willghatch/dotfileswgh/blob/master/config/awesome/rc.lua
>
> If anyone has run into this before, or can point me in the right direction
> to fix it, I'll appreciate it.
>
> Thanks,
> William
>

Re: Awesome in Awesome

[Alexis BRENON]

Is there any icon in the VB tray indicating that mouse is captured by VB?
For example, using Xephyr, if you press Ctrl+Shift, mouse is grab by
Xephyr, and you're not allowed to move the mouse outside the Xephyr's
window. I believe to remember that VB guest additions allow to move the
mouse from guest to host without hitting the host key (the special key
which disable the keyboard grabbing).. Maybe you have to disable this
feature (if it exists).

Kind,
Alexis

Le jeu. 3 sept. 2015 à 20:26, Marc Petit-Huguenin 
a écrit :

> On 09/03/2015 11:54 AM, Greg Meyer wrote:
> > This is interesting. I've had similar problems with VMs other similar
> > software before. I'm not sure what the solution would be, unfortunately,
> > but I would be interested to hear if you find one.
> >
> > My best guess would be this: VirtualBox grabs the mouse when you're in
> the
> > VM and releases it when you press the host key.
>
> According to the icon indicator at the bottom of VB, the keyboard is still
> captured by VB, although the VB window is moving.  That's why I suspect
> that the problem is AWM somehow intercepting the event, although it should
> not.
>
> > Is there any chance that
> > your host key has been mapped to mod4?
>
> No, it is a different key (Alt during my tests).
>
> >
> > Best,
>
> Thanks.
>
> >
> >
> > Greg Meyer
> >
> > gmmeyer.com
> >
> > @GMMeyer 
> >
> > 862 684 9101
> >
> > gregory.matthew.me...@gmail.com
> >
> > On Thu, Sep 3, 2015 at 12:02 PM, Marc Petit-Huguenin <
> > m...@petit-huguenin.org> wrote:
> >
> >> I am using a guest Linux instance with Awesome in Virtualbox.  This
> >> Virtualbox guest is itself running in a Linux host that is also using
> >> Awesome.
> >>
> >> The Mod4 key works fine with key sequences in the guest - i..e. when
> >> pressing Mod4+Enter, it opens a new terminal in the guest, not in the
> >> host.  This is when using Mod4+Mouse that things start to break: When I
> try
> >> to move a Window in the Guest, it is the VirtualBox window that moves.
> >>
> >> So my questions are:
> >>
> >> - Is there a possibility to fix this by configuration?
> >>
> >> - If not, where should I look to fix that?  Would it be in the Awesome
> >> running on the host, the Awesome running on the guest, VirtualBox or X?.
> >>
> >> Thanks.
> >>
> >>
> >>
> >> --
> >> To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
> >>
> >
>
>
>
> --
> To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
>

Re: Lua versus any other programming language

[Alexis BRENON]

@Sam :
Personnaly, I never tried to embed Python, but I know some projects who do
it : XBMC, Blender
I don't know a lot different programming language, but as far as I know Lua
is easy but not widely known. Nevertheless, I agree, it's syntax is pretty
nice (even if it could be improved).

I don't know Guile or Lisp (I only tried Scheme and OCaml), but I'm not
sure that they would allow the same things as easily as in Lua.

@Oon-Ee :
I don't think that mixing two DE/WM is a good idea. I give a look to i3
doc, the main config file doesn't seems to be written in Python, it should
be a quite 'expert' functionnality. Nevertheless, I LOVE AwesomeWM, I don't
want to change (for the moment).

@cedlemo :
I know that you can implement a kind of OO programming in Lua (
http://www.lua.org/pil/16.html), but it's not straight-forward. Why does a
'class' keyword not exist ?

I'm quite new to Ruby, and I don't know it well. If you say that it's not
very lightweight, it's probably not the best choice for Awesome.

@everyone:
Thanks, for your first answers. Hope we will have more opinions !

Alexis

Le sam. 1 août 2015 à 10:47, cedlemo cedl...@gmx.com a écrit :

  Not designed for OO programming

 Yes it is ! I thought that too at first when I didn't really know lua. The
 OO in Lua is not based on Class but on Prototype with the table. You should
 get
 a copy of Programming in Lua from Roberto Ierusalimschy it is really
 worth it.


  Does anyone would be interested in using Python (or another one : Ruby,
 ???) instead ?

 For Ruby that I really like (I contribute to ruby-gnome and ruby-opengl
 bindings) I think that
 lua is by far a best choice if you want to embed an interpreter in your
 application and want it to be ligthweigth.

 Some of the ruby dev work on mruby a lightweight alternative to ruby
 http://www.mruby.org/


 Regards

 https://github.com/cedlemo


 On 31/07/2015 22:56, Alexis BRENON wrote:

 Hi everyone,

 Perhaps the question was already asked million times, and probably it's a
 very good subject for trolls, but I'm asking myself a question.

 Why Lua has been chosen to be the language for AwesomeWM configuration ?

 I'm currently building a kind of framework for Awesome confg (
 https://github.com/AlexisBRENON/awesome-configuration) and to do so, I
 learned many aspects of Lua. I even use it for Hackaton, to see if I know
 it well. But the more I learn, the more I see it's defaults...
 Just to cite a few that piss me off :

- No distinction between list/table and hash/dict
- Too few standard functions for table manipulation (the length
operator on a table used as a dictionnary, always returns 0... No table
concatenation)
- No multithreading/multi-CPU support (only coroutines)
- Not designed for OO programming

 As far as I know, Python could have been a good choice.

 TL;DR :
 Why AwesomeWM uses Lua as configuration language ?
 Does anyone would be interested in using Python (or another one : Ruby,
 ???) instead ?
 Does an attempt to build an Awesome API in another language has been
 already started ?

 I would be happy to hear/read the position of the first creator of Awesome.

 Kind regards,
 Alexis

Lua versus any other programming language

[Alexis BRENON]

Hi everyone,

Perhaps the question was already asked million times, and probably it's a
very good subject for trolls, but I'm asking myself a question.

Why Lua has been chosen to be the language for AwesomeWM configuration ?

I'm currently building a kind of framework for Awesome confg (
https://github.com/AlexisBRENON/awesome-configuration) and to do so, I
learned many aspects of Lua. I even use it for Hackaton, to see if I know
it well. But the more I learn, the more I see it's defaults...
Just to cite a few that piss me off :

   - No distinction between list/table and hash/dict
   - Too few standard functions for table manipulation (the length operator
   on a table used as a dictionnary, always returns 0... No table
   concatenation)
   - No multithreading/multi-CPU support (only coroutines)
   - Not designed for OO programming

As far as I know, Python could have been a good choice.

TL;DR :
Why AwesomeWM uses Lua as configuration language ?
Does anyone would be interested in using Python (or another one : Ruby,
???) instead ?
Does an attempt to build an Awesome API in another language has been
already started ?

I would be happy to hear/read the position of the first creator of Awesome.

Kind regards,
Alexis

Re: Howto apply certain rules only at startup

[Alexis BRENON]

Hi Johannes,

First of all, I don't know if you did a copy paste, but at the end of your
config file you'd better write :
   run_once(firefox)
   awful.rules.rules = rules_ALWAYS

Nevertheless, I don't know if you can change rules on the fly... Reading
the code quicly, it seems possible.
Let us know about the last line of your rc.lua, we will see deeper after.

Kind regards,
Alexis

Le jeu. 11 juin 2015 à 16:22, Johannes Sauer joh.sa...@googlemail.com a
écrit :

 Hi,

 what I want to do is automatically start application on a certain tag.
 However when I later start another instance of the application I want it to
 appear on the tag I am at that moment.
 I tried to do something like this in rc.lua:

rules_always  = {
-- All clients will match this rule.
{ rule = { },
  properties = { border_width = beautiful.border_width,
 border_color = beautiful.border_normal,
 focus = true,
 keys = clientkeys,
 buttons = clientbuttons } },

-- Set Thunderbird to always map on tags number 3 of screen 1.
{ rule = { class = Thunderbird },
  properties = { tag = tags[1][3] } },
}

rules_startup = {
-- Set Firefox to always map on tags number 3 of screen 1.
{ rule = { class = Firefox },
  properties = { tag = tags[1][2] } },
}

awful.rules.rules = awful.util.table.join(rules_always, rules_startup)

 then at the end of rc.lua:

run_once(firefox)

awful.rules.rules = rules_startup

 However the effect is that still all rules will be applied, i.e. every new
 instance of firefox will appear on tag 2.

 What am I doing wrong?

 Best,
 Johannes

 PS: My awesome version is 3.4.11, don't think it's relevant for this
 question.

Re: Naughty Notifications on multiple monitors

[Alexis BRENON]

Instead of hidding the error just replace line 600 from:
local id = naughty.notify(args).id
to
naughty.notify(args)

You don't need the id any more if you don't use it. This way, no more error.

Le ven. 5 juin 2015 à 14:57, Abraham Baker z1693...@students.niu.edu a
écrit :

 Hi,

 My goal is to get every notification to show up on all monitors.  This
 isn't critical; it just makes switching between standing/sitting easier.

 I don't use often-updating notifications, so I (for now) don't care about
 the notification id's.  So, I'm thinking Elv1313's solution + hiding the
 naughty.lua:600 error would be enough.

 The relevant part of my rc.lua:

 -- Standard awesome library
 local gears = require(gears)
 local awful = require(awful)
 awful.rules = require(awful.rules)
 require(awful.autofocus)
 -- Widget and layout library
 local wibox = require(wibox)
 -- Theme handling library
 local beautiful = require(beautiful)
 -- Notification library

 local naughty = require(naughty)
 naughty.notify_ = naughty.notify
 naughty.notify = function (args,...)
for i = 1, screen.count() do
args.screen = i
naughty.notify_(args,...)
end
 end
 local menubar = require(menubar)
 local revelation=require(revelation)
 -- {{{ Error handling
 -- Check if awesome encountered an error during startup and fell back to
 -- another config (This code will only ever execute for the fallback
 config)
 if awesome.startup_errors then
 naughty.notify({ preset = naughty.config.presets.critical,
  title = Oops, there were errors during startup!,
  text = awesome.startup_errors })
 end

 -- Handle runtime errors after startup
 do
 local in_error = false
 awesome.connect_signal(debug::error, function (err)
 -- Make sure we don't go into an endless error loop
 if in_error then return end
 in_error = true

 naughty.notify({ preset = naughty.config.presets.critical,
  title = Oops, an error happened!,
  text = err })
 in_error = false
 end)
 end
 -- }}}


 The relevant part of naughty.lua (the only part changed from default):
 local id = naughty.notify(args).id
 return u, id
 --local notifs = naughty.notify(args)
 --local id = {}
 --for notif in ipairs(notifs) do
 --  id:insert(notif.id)
 --end

 Thanks,
 Abe

 On Fri, Jun 5, 2015 at 2:22 AM, Alexis BRENON brenon.ale...@gmail.com
 wrote:

 Hi Abraham,

 I'm sorry, I don't understand what and when did commented out ?
 Can you please post your config file on pastebin (http://pastebin.com/)
 or something like that (github?).

 To fix the error about 'insert' method, you can replace the line :
 notifications:insert(i, naughty.notify_(args,...))
 by
 table.insert(notifications, i, naughty.notify)

 Maybe you will have also to cheat a little bit if i doesn't start to 1...

 Maybe I can explain you a little deeper what are the goals, this way you
 will be able to debug yourself.

 So, you want to have your notifications displayed on many screens (the
 exact number is not important).
 To do so, you have to redefine the classic naughty.notify function, to
 call the initial naughty.notify function with the screen arg which loop
 over all your screen. This is what is done by the code sent by Elv1313.

 Nevertheless, the initial notify function returns a table representing
 the notification, containing for example an ID (the id field). If you don't
 need it, so fine, stick to the Elv1313 solution and remove any
 naughty.notify(...).id code in your config.
 But this ID can be useful if you need to replace a notification instead
 of adding a new one (this can be the case if you use notification to
 display volume changement, backlight modification, battery alert, whatever).
 To handle this, your new notify function must return the created
 notifications, or at least their ID.
 This is what my code intend to do. For each call to the initial notify
 function, I put the resulting table in a 'result' table, indexed by the
 index of the screen on which the notification is displayed. Up to ypu after
 to use it the right way.

 The last chunk of code I sent you, handle the case where you want to use
 the replaces_id argument of notify. As, in your case, you will have not
 only one, but many notifications to replace (one on each screen), you will
 pass the replaces_id argument as a table. This is not handled by the
 initial notify function, so for the actual call you use the value at the
 index representing your screen, as we do for the 'screen' arg.

 I hope the reasonning is clear.

 Alexis

 Le ven. 5 juin 2015 à 05:13, Abraham Baker z1693...@students.niu.edu a
 écrit :

 Hi,

 When I commented out 600 and 601 of naughty.lua *before* changing
 rc.lua, I got:
 naughty.lua:604: bad arg #1 to 'ipairs' (table expected, got nil)
 on both screens.

 Then, when I added the updated naughy.notify function to rc.lua, I got:
 rc.lua:22 attempt to call

Re: Naughty Notifications on multiple monitors

[Alexis BRENON]

Hum, well, you will have to update a little bit your config!

First, the default naughty.notify function returns a table representing the
notification, but your new notify function doesn't, so update it :

naughty.notify_ = naughty.notify
naughty.notify = function (args,...)
  notifications = {}
   for i = 1, screen.count() do
   args.screen = i
   notifications:insert(i, naughty.notify_(args,...))
   end
   return notifications
end

Then line 600 you update to something like :
local notifs = naughty.notify(args)
local id = {}
for notif in ipairs(notifs) do
  id:insert(notif.id)
end

Nevertheless, I think that you use the id value to replace the
notification, do you ? In this case, you will have to update again your
custom notification to handle the case if args.id is a table (instead of a
number) :

naughty.notify = function (args,...)
   notifications = {}
   naughty_args = args
   for i = 1, screen.count() do
   if args.replaces_id and type(args.replaces_id) == table then
  naughty_args.replaces_id = args.replaces_id[i]
   end
   naughty_args.screen = i
   notifications:insert(i, naughty.notify_(args,...))
   end
   return notifications
end

Or something like that.

Cheers,
Alexis

Le mer. 3 juin 2015 à 22:30, Abraham Baker z1693...@students.niu.edu a
écrit :

 That actually works, but also generates an error (in the form of a
 critical notification on both screens) at the same time:
 /usr/share/awesome/lib/naughty.lua:600: attempt to index a nil value

 For context, line 600 is:
 local id = naughty.notify(args).id

 Looks like this is close to working right! Thanks!

 On Wed, Jun 3, 2015 at 2:24 PM, Elv1313 . elv1...@gmail.com wrote:

 This should help:

 local naughty = require('naughty')
 naughty.notify_ = naughty.notify
 naughty.notify = function (args,...)
for i = 1, screen.count() do
args.screen = i
naughty.notify_(args,...)
end
 end

 On 3 June 2015 at 10:42, Abraham Baker z1693...@students.niu.edu wrote:
  I tried adding that code right after the local naughty =
 require(naughty)
  that was already there, but it didn't work and actually stopped any
  notifications from showing on any monitor.
 
  I doubt it was the cause, but some other functions in my rc.lua also use
  local i as a counter;  these shouldn't interfere with each other as
 long as
  they are inside their own functions, right?
 
  Thanks,
  Abe
 
  On Wed, Jun 3, 2015 at 8:20 AM, Alexis BRENON brenon.ale...@gmail.com
  wrote:
 
  Hi Abraham,
 
  you have to call the anughty.notift() function twice, once for each
  screen.
  Maybe you can define a function which do it for you :
 
  local naughty = require('naughty')
  naughty.notify = function (args)
  local i = 1
  while i = screen.count() do
  args.screen = i
  naughty.notify(args)
  end
  end
 
  Or something like that
 
  Regards,
  Alexis
 
  Le mer. 3 juin 2015 à 15:13, Abraham Baker z1693...@students.niu.edu
 a
  écrit :
 
  Hi,
 
  I have a standing/sitting monitor arrangement on my desk that makes it
  hard to see notifications on the upper monitor while sitting and vice
 versa.
  I've been trying to change the default naughty config so notifications
  appear on both monitors at once, but so far I'm only able to just
 change
  which monitor it shows up on (not both).
 
  Is there an easy way to have notifications shown on all monitors?
 
  Thanks,
  Abe Baker
 
 

Re: advices for widget

[Alexis BRENON]

Hi Mickael,

For battery state and volume control, I use Vicious library (
https://awesome.naquadah.org/wiki/Vicious)
I use it also for clock but I implemented calendar manually, based on the
work of Vincent Bernat (
https://github.com/AlexisBRENON/awesome-configuration/blob/master/backend/datetime/calendar.lua
).

For wifi and more generally network controller, I never found anything as
good as NetworkManager with nm-applet. I tried all in this list
https://wiki.archlinux.org/index.php/List_of_applications/Internet#Network_managers
.

I didn't use any easy drive mounter, as I don't have many external drives
or USB key. Only one good rule in /etc/fstab a folder named /mnt/external,
and I only have to type mount /etc/external to mount my USB drive when
needed.

Hope my experience can help.

Kind regards,
Alexis

Le mar. 2 juin 2015 à 17:05, mickael foucaux mickael.fouc...@gmail.com a
écrit :

 Hi folks!

 I'm happy with new laptop running an Ubuntu 14.01 / Awesome 3.5.6.

 Now I'm looking for few useful / essentials widget as:
 - battery state
 - volume control
 - wifi controller
 - clock / calendar
 - easy drive mounter

 Ok I saw few of them in
 https://awesome.naquadah.org/wiki/User_Contributed_Widgets . However as I
 know not all of them are compatible with awesome 3.5.6, I would like some
 feedback and advice before to try randomly widgets.

 cheers,

 Mickael

Re: Naughty Notifications on multiple monitors

[Alexis BRENON]

Hi Abraham,

you have to call the anughty.notift() function twice, once for each screen.
Maybe you can define a function which do it for you :

local naughty = require('naughty')
naughty.notify = function (args)
local i = 1
while i = screen.count() do
args.screen = i
naughty.notify(args)
end
end

Or something like that

Regards,
Alexis

Le mer. 3 juin 2015 à 15:13, Abraham Baker z1693...@students.niu.edu a
écrit :

 Hi,

 I have a standing/sitting monitor arrangement on my desk that makes it
 hard to see notifications on the upper monitor while sitting and vice
 versa.  I've been trying to change the default naughty config so
 notifications appear on both monitors at once, but so far I'm only able to
 just change which monitor it shows up on (not both).

 Is there an easy way to have notifications shown on all monitors?

 Thanks,
 Abe Baker

Re: Combination row+column layout?

[Alexis BRENON]

Hi Thomas,

Thanks for support :-)
i'll try to improve it, maybe next week, I'm quite busy for the moment. In
the whole things that can be done, I will try :

   - Different layouts for north-west/north-east/SW/SE master window
   - Choose between column is full height or row is full width
   - Let the user change the master size

I'll let you know when it's done.

Kind regards,
Alexis

Le jeu. 28 mai 2015 à 11:16, Thomas Jost schno...@schnouki.net a écrit :

 Le 27 mai 2015 à 14:21 CEST, Alexis BRENON brenon.ale...@gmail.com a
 écrit :
  No feedback... So sad... I will try to improve it, and open a pull
 request.
 
  Le lun. 25 mai 2015 à 17:17, Alexis BRENON brenon.ale...@gmail.com a
  écrit :
 
  Hi Rena,
 
  Joined is a draft patch to add a corner layout. Of course, you have to
  add it in your rc.lua file!
  You can also find it on my github account :
  https://github.com/AlexisBRENON/awesome/tree/feature/corner_layout
  I compiled it without any problem and it works quite well. I've got some
  weird behaviour, but I tried it with small screen resolution, with
 terminal
  which honour size hints (round height and width to match a full number
 of
  columns and rows), and so, sometimes there is gap between windows.
  I hope that you can understand my new file : lib/awful/layout/suit/
  corner.lua.in, and that you will be able to change it to meet the best
 as
  it can you need.
 
  Kind regards,
  Alexis

 Hi Alexis,

 For what it's worth, I like this layout a lot. There's still room for
 improvement, but it's definitely interesting, and it would be great if
 you could get this merged in awesome.

 For those who want to know what it looks like, here's a simple
 screenshot:
 https://dl.dropboxusercontent.com/u/597621/Screenshots/2015-05-28_01.png

 Cheers,
 --
 Thomas/Schnouki

Re: Combination row+column layout?

[Alexis BRENON]

Hi Rena,

Joined is a draft patch to add a corner layout. Of course, you have to
add it in your rc.lua file!
You can also find it on my github account :
https://github.com/AlexisBRENON/awesome/tree/feature/corner_layout
I compiled it without any problem and it works quite well. I've got some
weird behaviour, but I tried it with small screen resolution, with terminal
which honour size hints (round height and width to match a full number of
columns and rows), and so, sometimes there is gap between windows.
I hope that you can understand my new file : lib/awful/layout/suit/
corner.lua.in, and that you will be able to change it to meet the best as
it can you need.

Kind regards,
Alexis

Le lun. 25 mai 2015 à 10:20, Alexis BRENON brenon.ale...@gmail.com a
écrit :

 Hi Rena,

 I don't use spiral or dwindle layout, so I don't exactly know how they
 behave. Nevertheless, I think that they are the nearest to what you try to
 achieve.

 I never implement a new layout, so I can't really help you for the moment.
 I suggest you to copy one of spiral or dwindle and try to modify it. I will
 try this also. I will tell you if I manage anything.

 Kind regards,
 Alexis.

 Le ven. 22 mai 2015 à 23:40, Rena hyperhac...@gmail.com a écrit :

 On Fri, May 22, 2015 at 3:16 AM, Alexis BRENON brenon.ale...@gmail.com
 wrote:
  Hi Rena,
 
  It seems quite similar to spiral or zig-zag layouts, doesn't ? Dis you
 try
  them ? Maybe you can create a new layout based on these which better
 fits
  your needs.
 
  Kind regards,
  Alexis
 
  Le ven. 22 mai 2015 à 02:49, Rena hyperhac...@gmail.com a écrit :
 
  How can I achieve a layout like this? http://i.imgur.com/lNF0fpw.png
 
  --
  Sent from my Game Boy.
 
  --
  To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.

 Those layouts appear to divide the screen area repeatedly in half?
 It's not quite what I'm after. Perhaps if I could adjust them a bit.
 The spiral, dwindle, and fair layouts don't seem to let me resize any
 windows and ignore the nmaster/ncols settings; not sure if that's a
 bug?

 I think my first image wasn't clear, maybe an animation will help:
 http://i.imgur.com/JVnsfkX.gifv

 Basically with most layouts there's one row or column for master
 windows and N for non-master windows (where N is adjustable). What
 I'm looking for is the non-master windows to be in both rows *and*
 columns, with the master window(s) in a corner.

 I might have a go at implementing it myself, but I'm not really sure
 where to begin there.

 --
 Sent from my Game Boy.


diff --git a/lib/awful/layout/init.lua.in b/lib/awful/layout/init.lua.in
index 875e851..c2f82cd 100755
--- a/lib/awful/layout/init.lua.in
+++ b/lib/awful/layout/init.lua.in
@@ -31,6 +31,7 @@ layout.suit = require(awful.layout.suit)
 -- The default list of layouts
 layout.layouts = {
 layout.suit.floating,
+layout.suit.corner,
 layout.suit.tile,
 layout.suit.tile.left,
 layout.suit.tile.bottom,
diff --git a/lib/awful/layout/suit/corner.lua.in b/lib/awful/layout/suit/corner.lua.in
new file mode 100644
index 000..7c8757d
--- /dev/null
+++ b/lib/awful/layout/suit/corner.lua.in
@@ -0,0 +1,90 @@
+---
+-- @author Uli Schlachter lt;psyc...@znc.ingt;
+-- @copyright 2009 Uli Schlachter
+-- @copyright 2008 Julien Danjou
+-- @release @AWESOME_VERSION@
+---
+
+-- Grab environment we need
+local ipairs = ipairs
+local math = math
+
+-- awful.layout.suit.corner
+local corner = {}
+
+local function do_corner(p)
+local wa = p.workarea
+local cls = p.clients
+
+local master_width = 1
+local master_height = 1
+if #cls  1 then
+master_width = 0.75
+if #cls  2 then
+master_height = 0.75
+end
+end
+local column = {}
+local row = {}
+
+column.x = wa.x + (master_width * wa.width)
+column.width = wa.width - (master_width * wa.width)
+column.height = wa.height
+column.number_win = math.ceil((#cls - 1)/2)
+column.win_height = column.height/column.number_win
+column.win_idx = 0
+
+row.y = wa.y + (master_height * wa.height)
+row.width = wa.width - column.width
+row.height = wa.height - (master_height * wa.height)
+row.number_win = (#cls - 1) - column.number_win
+row.win_width = row.width/row.number_win
+row.win_idx = 0
+
+for i, c in ipairs(cls) do
+local g = nil
+-- Handle master window
+if i == 1 then
+g = {
+x = wa.x,
+y = wa.y,
+width = (master_width * wa.width) - (2 * c.border_width),
+height = (master_height * wa.height) - (2 * c.border_width)
+}
+-- handle windows in column
+elseif i % 2 == 0 then
+g = {
+x = column.x,
+y = wa.y + (column.win_idx * column.win_height

Re: Change tags on the non-focused screen

[Alexis BRENON]

I don't think that a twin view of a window is possible with Awesome. You
probably have to look with Xorg, but I even think that it's not possible at
all.

As you have only 2 screens, you have 3 choices:
  - First, use a binding which switch the tag of the not focused screen
  - Second, use a different modifier key for each screen
  - Lastly, use the key grabber.

Some users notified me that Hi guys is a gender-neutral introduction. So
I'm sorry for my mis-translation, and you can stick on it !

Kind Regards,
Alexis

Le mer. 22 avr. 2015 à 11:09, vandr0iy email.quella...@gmail.com a écrit :

  First of all, thank you for your reply.

 For my questions, in the second one I was basically asking how to show a
 window in one of the tags of one screen, and in one of the tags of the
 other. Like, I want it on the 1st tag on my main screen, and on the 3rd
 tag on my secondary one; wondered if it were possible. For my last
 question: this means that, if I wanted to
 change tags on the unfocused screen, I'd have 2 choices: to use a new
 modifier key for every screen, due to
 the fact that the 2 keys shortcut is not possible, or to launch a
 dedicated application which grabs a
 combination of keys and then does what I need?

 Finally, I'd like you to specify how should I address you, and if that
 noun/pronoun/whatever complies with
 the English semantics, I shall use it.


 Vandr0iy



 On 04/22/2015 07:34 AM, Alexis BRENON wrote:

 Hi Vandr0iy,

 First of all, before I try to answer you, PLEASE, don't start your mail
 with : Hi guys. I'm quite sure that there is some women which use Awesome
 and that can help you,  so use a more neutral way. Thanks.

 For your questions everything you ask seems possible.
 I don't know if you use shifty to manage your tags, but it has some
 functions to move them between screens, so this doesn't seems difficult.
 For the second one, I don't really understand what you want. Let me know
 if I'm wrong but you would like that if you send the tag 1 from screen 1 to
 screen 2 it automatically becomes tag 3 on this new screen? I think that
 it's not handle by Awesome or shifty, but you can (quite) easily handle
 this in your callback for tag's screen switching.
 For the last one, you can't have a 2 keys shortcut in Awesome. I think you
 have to use a key binding to launch the key grabber, and then press keys
 for screen and tag selection. I never used key grabber so I can't help you
 more for the moment.

 I hope it helps you! I don't have the Awesome API documentation with me,
 so I can't be more precise. Ask me if you need more details, I'll try to
 guide you in the right direction.

 Kind regards,
 Alexis.

 Le mar. 21 avr. 2015 à 16:57, vandr0iy email.quella...@gmail.com a
 écrit :

 Hi guys!

 I got a two-screen setup, and I made them work using xrandr (sometimes
 arandr, but since it is just a GUI, I
  do not think it really matters).

 Is there an optimal way to manage them? In particular, I look for:
 1. a shortcut to throw a tag from one screen to another (the whole tag,
 not just a client)
 2. a way toassign to a client one tag from one screen, and one from
 another (say, client C has tag 1 from
  screen 1 and tag 3 from screen 2)
 3. a way to change tags on the screen 1 while focusing screen 0, and/or
 vice versa; would be also nice to have
  a way to do it with even more than one screen (like, pressing mod4
 + F1 + 3 shows the 3 tag from 1 screen)

 Thank you very much in advance for your help

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

Re: Change tags on the non-focused screen

[Alexis BRENON]

Hi Vandr0iy,

First of all, before I try to answer you, PLEASE, don't start your mail
with : Hi guys. I'm quite sure that there is some women which use Awesome
and that can help you,  so use a more neutral way. Thanks.

For your questions everything you ask seems possible.
I don't know if you use shifty to manage your tags, but it has some
functions to move them between screens, so this doesn't seems difficult.
For the second one, I don't really understand what you want. Let me know if
I'm wrong but you would like that if you send the tag 1 from screen 1 to
screen 2 it automatically becomes tag 3 on this new screen? I think that
it's not handle by Awesome or shifty, but you can (quite) easily handle
this in your callback for tag's screen switching.
For the last one, you can't have a 2 keys shortcut in Awesome. I think you
have to use a key binding to launch the key grabber, and then press keys
for screen and tag selection. I never used key grabber so I can't help you
more for the moment.

I hope it helps you! I don't have the Awesome API documentation with me, so
I can't be more precise. Ask me if you need more details, I'll try to guide
you in the right direction.

Kind regards,
Alexis.

Le mar. 21 avr. 2015 à 16:57, vandr0iy email.quella...@gmail.com a écrit :

 Hi guys!

 I got a two-screen setup, and I made them work using xrandr (sometimes
 arandr, but since it is just a GUI, I
  do not think it really matters).

 Is there an optimal way to manage them? In particular, I look for:
 1. a shortcut to throw a tag from one screen to another (the whole tag,
 not just a client)
 2. a way toassign to a client one tag from one screen, and one from
 another (say, client C has tag 1 from
  screen 1 and tag 3 from screen 2)
 3. a way to change tags on the screen 1 while focusing screen 0, and/or
 vice versa; would be also nice to have
  a way to do it with even more than one screen (like, pressing mod4
 + F1 + 3 shows the 3 tag from 1 screen)

 Thank you very much in advance for your help

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

Systray doesn't seems to be present...

[Alexis BRENON]

Hi all,

I say it now, it's a quite difficult problem, because there is many source
code to handle !

I'm working on a kind of framework to easily change awesome configuration ;
my future goal is to build a GUI tool to build the awesome configuration.

In the whole, my framework is in a good state, as it allows me to build my
current configuration with it ! But I have a problem with the systray... It
seems that all works well, I have no particular message in my log, as seen
in the pastebin (http://pastebin.com/qwGLLcyj). This must not tell you
anything without the code, I have no other way than guiding you to my
Github (
https://github.com/AlexisBRENON/awesome-configuration/tree/separated_config
).

So, to quickly explain, I build the systray (
https://github.com/AlexisBRENON/awesome-configuration/blob/separated_config/builder/widgets/99-core/systray.lua)
and I add it to the wibox (
https://github.com/AlexisBRENON/awesome-configuration/blob/separated_config/builder/widgets/init.lua#L64
).

I run Awesome in Xephyr or in live, but in both, systray doesn't seem to be
present, the nm-applet or blueman-applet doesn't appear anywhere...

If anyone has an idea to debug this, to make an empty systray visible or
whatever, thanks !

Ask more info if needed, it will be a very pleasure for me to explain you
more my framework ! Any idea to improve it will be appreciated too !

Best regards,
Alexis BRENON

Re: Clear naughty notifications

[Alexis BRENON]

Hi,

You can save the IDs of all notifications, then call naughty.destroy(id) on
each one.

Regards,
Alexis

Le dim. 8 mars 2015 à 20:40, zhtlancer zhtlan...@gmail.com a écrit :

 Hi all,

 I'm using naughty to get notifications from my firewall activities, but
 it's kind of annoying that when a naughty notification comes out, I have to
 use my mouse to clear it (I'm not setting the time-out limit as I don't
 want to miss any warnings when AFK). So is there any API to clear all the
 naughty notifications thus we can bind it to a hot key?

 Thanks!

Re: Systray doesn't clean before icon update

[Alexis Brenon]

Hi LLoyd, thank you to answer. It's not the same screenshot twice actually,
there is a small difference in the icon on left most side in the top-right
corner. But I reframe the images to highlight the error.

So as I said, after a fresh awesome start the nm-applet icon looks clear :
http://www.hostingpics.net/viewer.php?id=411045unnamed.jpg

But after a deconnection  reconnection, icons stacked and are weird...
http://www.hostingpics.net/viewer.php?id=959344unnamed1.jpg

Any idea how can I fix this ? Thanks.
Alexis

Le Tue Feb 17 2015 at 23:59:07, Namikaze Minato lloydsen...@gmail.com a
écrit :

 You sent the same screenshot twice, the shooting star didn't move...

 LLoyd  sorry for the stupid joke, but I had to make it ^^' 

 On 17 February 2015 at 21:18, Alexis Brenon brenon.ale...@gmail.com
 wrote:
 
  Hi all,
 
  I use transparancy on my wibox and on my sytray as you can see on the
 screenshots. I also use nm-applet to display the network status in the
 systray. But I encounter a small issue with the icons drawn in the systray.
 When icon updates, the previous one is not erase. So with a fresh start of
 awesome, the icon looks beautiful and clear as shown in the first
 screenshot, but after, when wireless disconnect, then try reconnect, all
 the icons stack on each other and so the result is weird, and I can't see
 the difference between Wifi connected and Wifi disconnected...
 
  Is there anybody which already encounter this problem and managed to
 solve it ? Else, any idea where I can investigate ?
 
  Thanks,
  Alexis
 
 

Re: Change wibox.widget.textbox() depends on the tag

[Alexis Brenon]

tag1.connect_signal(property::selected, function(_)
mytextbox:set_text(Good) end)
tag2.connect_signal(property::selected, function(_)
mytextbox:set_text(Bad) end)

Le Wed Jan 28 2015 at 16:59:04, mongoose pythonpr...@gmail.com a écrit :


 Forgot to add in examples text values.
 Text in the widget to be on first tag Good, and on the second tag Bad.
 For exmaple ofcourse




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

Re: Interactive shell in textbox.

[Alexis Brenon]

Hi,

What do you mean by interactive shell ? Where does the output will be
displayed ?
Maybe take a look a the quake-like terminal :
http://awesome.naquadah.org/wiki/Drop-down_terminal

Regards,
Alex (too)

Le Wed Jan 28 2015 at 16:19:43, alex fisher alexfishersm...@gmail.com a
écrit :

 Hi, just started with Awesome 3.4.13-1 ( in Debian ), and Lua. I've put a
 text widget text box on my system-bar next to 'mytextclock'. How can I run
 an interactive shell (bash) in this textbox? I would like to keep the shell
 one line in height. Any thoughts appreciated - thanks, Alex.

Re: awesome does not start after login

[Alexis Brenon]

Hi,

Is there any error reported in your .xsession-error. As awesome even start
on the fallback config, I think it's a more serious error than a
configuration one. Probably missing some dependancies. I don't know
OpenSuse, and it's package management...

For the compilation, it's right that the file is called libcairo0.so. To
better manage libraries update, many libs are called libfoo.x.y.z.so and
then the system does some symbolic name libfoo.x.so and libfoo.so to the
first file. Without the compilation output, it's hard to guess if it fails
because it's not the right version of cairo, or if it doesn't find the
cairo lib at all.

We need more info to help you...

Regards,
Alexis

Le Mon Jan 26 2015 at 18:11:13, vandr0iy email.quella...@gmail.com a
écrit :

 Hi, guys! I decided to try awesome on openSUSE, so I installed it from
 the official repositories.
 It worked flawlessly, but, there's the only issue, - it's a really old
 version, something like 3.4.15. So, I uninstalled it, grabbed a .rpm for
 an older version of opensuse (why in the world there's a later version
 of awesome for an older openSUSE??? ) and installed it instead;
 according to zypper it was ok, like, an upgrade.
 After this operation there were no way awesome would start. I usually
 run it from lightDM, but it would give me a black screen and return to
 login. Is there a way to repair it? I tried to cleanse it in every way,
 by renaming my ~/.config/awesome folder, but there is still nothing to do.

 What could I do to remedy?

 P.S. I also tried to compile it from sources, but it gives me errors by
 saying that several dependencies are missing. The issue consists in the
 fact that I already have those dependencies, but under another name
 (like, cairo-libcairo0, or things like that). Is there a way to make it
 compile w/out errors?

 Thank you very much for your help.

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

Re: new version of awesome and old version of a peace of code

[Alexis Brenon]

Hi Mohsen,

Your error about comma is because your awful.key() call is the last
argument to another function call (probably awful.util.table.join), and so
the comma is forbidden !
Two things seem possible :

   - Your last update also update the scrot util which change its options.
   Is your command scrot -e '...' works if you launch it from a terminal
   - The Print is never recognized. Try to do a naughty.notify in your
   callback function to be sure it is called. Check with xev that your key
   press is actually mapped to Print.

Regards,
Alexis

Le Thu Jan 22 2015 at 11:30:17, Mohsen Pahlevanzadeh 
moh...@pahlevanzadeh.org a écrit :

  Dear All,

 I migrated 3.5.x (32bit) to 64bit,  I don't remember version of my
 awesome, My screenshot was working fine But doesn't work with new version:
 my new version of awesome is 3.5.5-1
 I put such as past into rc.lua:

 awful.key({ }, Print, function () awful.util.spawn(scrot -e 'mv $f
 ~/screenshots/ 2/dev/null' ) end),

 When i eliminate last comma i don't get any error , but my screenhsot
 doesn't work and when i put last comma , i get the following error:
 unexcpected symbol near ','

 At two state i have problem,

 Do you have any solution?

 --Regards
 Mohsen

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

Re: Xorg and my laptop

[Alexis Brenon]

Hi,

Of course, I send you the link for the latest default awesomerc.lua wich
only work for awesome 3.5 !
I agree with you, the Awesome API doc is sometime incomplete or cryptic,
but I remember that someone start to fix this (see the mailing list
archives).

So, sorry, I don't really understand your message but, does all work well,
or have you got any error again ?

Just some advice for your code :

   - replace *kbdcfg.widget.text = t *with* kbdcfg.widget:set_markup(t)*
   - replace your function in awful.key and awful.button :
*function () kbdcfg.switch() end* become *kbdcfg.switch*
   No more needed as your function doesn't require any arguments. it
   increases the readability.

Regards,
Alexis

Le Thu Dec 04 2014 at 20:41:58, Mohsen Pahlevanzadeh 
moh...@pahlevanzadeh.org a écrit :

  Oh by the way, i find api ref now.


 On 12/02/2014 11:37 AM, Alexis Brenon wrote:

 Hi Mohsen,

 The { Mod1 }, Shift_R stand for the Alt modifier plus the Shift key, but
 the right one, not the left one.
 To make sure that the right keys are detected, you can use the xev program
 (see the ArchLinux wiki page
 https://wiki.archlinux.org/index.php/extra_keyboard_keys#In_Xorgfor a
 quick guide). You can also add a notification in your switch function to
 see if it is called :

 kbdcfg.switch = function ()
 naughty.notify({text = Keyboard layout switch})
 kbdcfg.current = kbdcfg.current % #(kbdcfg.layout) + 1
 local t =   .. kbdcfg.layout[kbdcfg.current] ..  
 kbdcfg.widget.text = t
 os.execute( kbdcfg.cmd .. t )
 end

  Just a question : after defining your awful.key (your key binding, which
 is, moreover, defined twice), did you add it to root.keys ?
 https://github.com/awesomeWM/awesome/blob/master/awesomerc.lua.in#L347

  Regards,
 Alexis

 Le Mon Dec 01 2014 at 20:43:52, Mohsen Pahlevanzadeh 
 moh...@pahlevanzadeh.org a écrit :


 On 12/01/2014 11:49 AM, Alexis Brenon wrote:

 Hi Mohsen,

 Frome here, I don't see any particular error in your code or anything.
 But maybe you can start by remove some useless parts which can interact
 with others or whatever.

  Firstly, in your xorg.conf file, remove the line :
   Option XkbOptions  grp:shifts_toggle

  I commented at  xorg.

  This line, allow you to switch layouts with the shift keys, but without
 any interaction with Awesome (so your widget will not be updated), it's not
 what you want, but it can interfere.

  Then, as you define your layout in the xorg.conf file, you don't need
 to use
   setxkbmap us,fa
 in your xinit.rc file. When X starts, it reads the xorg.conf file and so
 this line is useless.

   I remove it from ~/.xinitrc


  Finally, you say that you can't change to persian language, but I see 3
 layouts in your kbdcfg.layouts. Can you change between us and fa, but not
 to Persian, or you can't change at all. In both cases, try to execute
 manually the commands in your terminal, maybe setxkbmap will report you an
 error (missing the -layout option, unrecognized layout name, etc.).

  Just to finnish ; it's now recommended to not use the xorg.conf file,
 but the xorg.conf.d/ folder with one file for each device.

  Hopping that it will help you.

  Regards,
 Alexis

 Le Mon Dec 01 2014 at 03:21:46, Mohsen Pahlevanzadeh 
 moh...@pahlevanzadeh.org a écrit :

  Dear all,

 I migrate to awesome, But may be awesome depend on X, At first i
 provided xorg.conf with:
 Xorg -configure

 Then i changed InputClass such as :
 ///

Section InputClass
Identifier  keyboard0
Driver  evdev
#MatchIsKeyboard on
Option XkbModelevdev
# Switch between layouts by pressing both shift keys
Option XkbLayout   us,fa
Option XkbOptions  grp:shifts_toggle
EndSection

 

 Then :
  cp /etc/xdg/awesome/rc.lua ~/.config/awesome/
 Add the following change to it:
 //
 -- Keyboard map indicator and changer
 kbdcfg = {}
 kbdcfg.cmd = setxkbmap
 kbdcfg.layout = { us, fa, Persian }

   I change abobe line to :

 kbdcfg.layout = { us, fa}

   kbdcfg.current = 1  -- us is our default layout


 kbdcfg.widget = widget({ type = textbox, align = right })
 kbdcfg.widget.text =   .. kbdcfg.layout[kbdcfg.current] ..  
 kbdcfg.switch = function ()
kbdcfg.current = kbdcfg.current % #(kbdcfg.layout) + 1
local t =   .. kbdcfg.layout[kbdcfg.current] ..  
kbdcfg.widget.text = t
os.execute( kbdcfg.cmd .. t )
 end
-- Alt + Right Shift switches the current keyboard layout
 awful.key({ Mod1 }, Shift_R, function () kbdcfg.switch()
 end),
 -- Mouse bindings
 kbdcfg.widget:buttons(awful.util.table.join(
 awful.button({ }, 1, function () kbdcfg.switch() end)
 ))
  -- end by me
 
 Also i add the folloiwoing section to layout

Re: Xorg and my laptop

[Alexis Brenon]

Hi Mohsen,

The { Mod1 }, Shift_R stand for the Alt modifier plus the Shift key, but
the right one, not the left one.
To make sure that the right keys are detected, you can use the xev program
(see the ArchLinux wiki page
https://wiki.archlinux.org/index.php/extra_keyboard_keys#In_Xorgfor a
quick guide). You can also add a notification in your switch function to
see if it is called :

kbdcfg.switch = function ()
naughty.notify({text = Keyboard layout switch})
kbdcfg.current = kbdcfg.current % #(kbdcfg.layout) + 1
local t =   .. kbdcfg.layout[kbdcfg.current] ..  
kbdcfg.widget.text = t
os.execute( kbdcfg.cmd .. t )
end

Just a question : after defining your awful.key (your key binding, which
is, moreover, defined twice), did you add it to root.keys ?
https://github.com/awesomeWM/awesome/blob/master/awesomerc.lua.in#L347

Regards,
Alexis

Le Mon Dec 01 2014 at 20:43:52, Mohsen Pahlevanzadeh 
moh...@pahlevanzadeh.org a écrit :


 On 12/01/2014 11:49 AM, Alexis Brenon wrote:

 Hi Mohsen,

 Frome here, I don't see any particular error in your code or anything. But
 maybe you can start by remove some useless parts which can interact with
 others or whatever.

  Firstly, in your xorg.conf file, remove the line :
   Option XkbOptions  grp:shifts_toggle

 I commented at  xorg.

  This line, allow you to switch layouts with the shift keys, but without
 any interaction with Awesome (so your widget will not be updated), it's not
 what you want, but it can interfere.

  Then, as you define your layout in the xorg.conf file, you don't need to
 use
   setxkbmap us,fa
 in your xinit.rc file. When X starts, it reads the xorg.conf file and so
 this line is useless.

  I remove it from ~/.xinitrc


  Finally, you say that you can't change to persian language, but I see 3
 layouts in your kbdcfg.layouts. Can you change between us and fa, but not
 to Persian, or you can't change at all. In both cases, try to execute
 manually the commands in your terminal, maybe setxkbmap will report you an
 error (missing the -layout option, unrecognized layout name, etc.).

  Just to finnish ; it's now recommended to not use the xorg.conf file,
 but the xorg.conf.d/ folder with one file for each device.

  Hopping that it will help you.

  Regards,
 Alexis

 Le Mon Dec 01 2014 at 03:21:46, Mohsen Pahlevanzadeh 
 moh...@pahlevanzadeh.org a écrit :

  Dear all,

 I migrate to awesome, But may be awesome depend on X, At first i provided
 xorg.conf with:
 Xorg -configure

 Then i changed InputClass such as :
 ///

Section InputClass
Identifier  keyboard0
Driver  evdev
#MatchIsKeyboard on
Option XkbModelevdev
# Switch between layouts by pressing both shift keys
Option XkbLayout   us,fa
Option XkbOptions  grp:shifts_toggle
EndSection

 

 Then :
  cp /etc/xdg/awesome/rc.lua ~/.config/awesome/
 Add the following change to it:
 //
 -- Keyboard map indicator and changer
 kbdcfg = {}
 kbdcfg.cmd = setxkbmap
 kbdcfg.layout = { us, fa, Persian }

  I change abobe line to :

 kbdcfg.layout = { us, fa}

   kbdcfg.current = 1  -- us is our default layout


 kbdcfg.widget = widget({ type = textbox, align = right })
 kbdcfg.widget.text =   .. kbdcfg.layout[kbdcfg.current] ..  
 kbdcfg.switch = function ()
kbdcfg.current = kbdcfg.current % #(kbdcfg.layout) + 1
local t =   .. kbdcfg.layout[kbdcfg.current] ..  
kbdcfg.widget.text = t
os.execute( kbdcfg.cmd .. t )
 end
-- Alt + Right Shift switches the current keyboard layout
 awful.key({ Mod1 }, Shift_R, function () kbdcfg.switch() end),
 -- Mouse bindings
 kbdcfg.widget:buttons(awful.util.table.join(
 awful.button({ }, 1, function () kbdcfg.switch() end)
 ))
  -- end by me
 
 Also i add the folloiwoing section to layout:
 /
 right_layout:add(kbdcfg.widget)
 //

 Then i create a ~.xinitrc and pu into it:
 //
 #!/bin/sh
 setxkbmap us,fa
 ///

 Also i put into the following code in rc.lua:
 
 awful.key({ Mod1 }, Shift_R, function () kbdcfg.switch() end),
 //

   I have to learn lua, But i don't know above line (define hot key,)
 What's key binding for changing layout?
 mod+shift+R?
 How can i find out which hotkey active is?

 --Regard

 Mohsen

   But i can't change my keyboard language to persian language, how can i do 
 it?
 Where's my problem?
 Please give me a link from key codes

 --Regards
 Mohsen




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

Re: Awesome as a wayland compositor

[Alexis Brenon]

Maybe, feel free to contribute : https://github.com/awesomeWM/awesome

Le Mon Dec 01 2014 at 23:30:20, MohsenPahlevanzadeh 
moh...@pahlevanzadeh.org a écrit :

 Gnome 3.14 has been ported to wayland, but i don't know why awesome still
 X11 stay.



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

Re: Awesome as a wayland compositor

[Alexis Brenon]

Hi blastmaster,

I don't know Wayland at all (just by name). I'm more and more common with
X11 since time I use it, and thanks to this very good website : Xplain -
Explaining X11 for the rest of us http://magcius.github.io/xplain/article/
Maybe you can start with this !

It's obvious that porting Awesome to wayland is not a so easy job !! But
maybe it can be feasible, if a motivated team is build.

Regards,
Alexis


Le Tue Dec 02 2014 at 10:38:37, Sebastian Oeste blastmas...@tuxcode.org a
écrit :

 Alexis Brenon wrote:
  Maybe, feel free to contribute : https://github.com/awesomeWM/awesome
 
  Le Mon Dec 01 2014 at 23:30:20, MohsenPahlevanzadeh 
  moh...@pahlevanzadeh.org a écrit :
 
   Gnome 3.14 has been ported to wayland, but i don't know why awesome
 still
   X11 stay.

 I'am neither a X11 nor a Wayland expert, but i would think to port
 awesome to wayland it is necessary to port all the xcb stuff in awesome
 to wayland.

 When grepping over the C source the following files seems to be affeced.

 $ ack --cc -lc 'xcb'

 event.h:4
 systray.c:44
 color.c:3
 property.c:65
 mousegrabber.h:2
 color.h:3
 common/xcursor.c:5
 common/atoms.h:3
 common/atoms.c:6
 common/xcursor.h:6
 common/xutil.h:11
 common/xembed.h:28
 common/xutil.c:20
 common/xembed.c:19
 keygrabber.h:3
 objects/client.c:74
 objects/drawin.c:13
 objects/drawin.h:1
 objects/button.h:3
 objects/client.h:12
 objects/window.h:4
 objects/window.c:12
 objects/screen.c:46
 objects/key.h:2
 objects/drawable.c:5
 objects/drawable.h:1
 systray.h:6
 root.c:50
 awesome.c:82
 luaa.c:9
 keyresolv.h:5
 selection.c:21
 spawn.c:1
 mouse.h:4
 keyresolv.c:13
 event.c:78
 mouse.c:11
 ewmh.c:68
 mousegrabber.c:8
 draw.h:11
 keygrabber.c:6
 xwindow.c:72
 ewmh.h:8
 xwindow.h:22
 globalconf.h:18
 draw.c:28
 property.h:4
 stack.c:6

 So thats not a trivial change. I'am really interessted in the wayland -
 x11 thing. But still have a lack of knowledge.

 If someone has more detailed ideas about the topic, or a good starting
 point please let me know.

 best regards,
 blastmaster

Re: Xorg and my laptop

[Alexis Brenon]

Hi Mohsen,

Frome here, I don't see any particular error in your code or anything. But
maybe you can start by remove some useless parts which can interact with
others or whatever.

Firstly, in your xorg.conf file, remove the line :
  Option XkbOptions  grp:shifts_toggle
This line, allow you to switch layouts with the shift keys, but without any
interaction with Awesome (so your widget will not be updated), it's not
what you want, but it can interfere.

Then, as you define your layout in the xorg.conf file, you don't need to
use
  setxkbmap us,fa
in your xinit.rc file. When X starts, it reads the xorg.conf file and so
this line is useless.

Finally, you say that you can't change to persian language, but I see 3
layouts in your kbdcfg.layouts. Can you change between us and fa, but not
to Persian, or you can't change at all. In both cases, try to execute
manually the commands in your terminal, maybe setxkbmap will report you an
error (missing the -layout option, unrecognized layout name, etc.).

Just to finnish ; it's now recommended to not use the xorg.conf file, but
the xorg.conf.d/ folder with one file for each device.

Hopping that it will help you.

Regards,
Alexis

Le Mon Dec 01 2014 at 03:21:46, Mohsen Pahlevanzadeh 
moh...@pahlevanzadeh.org a écrit :

  Dear all,

 I migrate to awesome, But may be awesome depend on X, At first i provided
 xorg.conf with:
 Xorg -configure

 Then i changed InputClass such as :
 ///

Section InputClass
Identifier  keyboard0
Driver  evdev
#MatchIsKeyboard on
Option XkbModelevdev
# Switch between layouts by pressing both shift keys
Option XkbLayout   us,fa
Option XkbOptions  grp:shifts_toggle
EndSection

 

 Then :
  cp /etc/xdg/awesome/rc.lua ~/.config/awesome/
 Add the following change to it:
 //
 -- Keyboard map indicator and changer
 kbdcfg = {}
 kbdcfg.cmd = setxkbmap
 kbdcfg.layout = { us, fa, Persian }
 kbdcfg.current = 1  -- us is our default layout
 kbdcfg.widget = widget({ type = textbox, align = right })
 kbdcfg.widget.text =   .. kbdcfg.layout[kbdcfg.current] ..  
 kbdcfg.switch = function ()
kbdcfg.current = kbdcfg.current % #(kbdcfg.layout) + 1
local t =   .. kbdcfg.layout[kbdcfg.current] ..  
kbdcfg.widget.text = t
os.execute( kbdcfg.cmd .. t )
 end
-- Alt + Right Shift switches the current keyboard layout
 awful.key({ Mod1 }, Shift_R, function () kbdcfg.switch() end),
 -- Mouse bindings
 kbdcfg.widget:buttons(awful.util.table.join(
 awful.button({ }, 1, function () kbdcfg.switch() end)
 ))
  -- end by me
 
 Also i add the folloiwoing section to layout:
 /
 right_layout:add(kbdcfg.widget)
 //

 Then i create a ~.xinitrc and pu into it:
 //
 #!/bin/sh
 setxkbmap us,fa
 ///

 Also i put into the following code in rc.lua:
 
 awful.key({ Mod1 }, Shift_R, function () kbdcfg.switch() end),
 //

 But i can't change my keyboard language to persian language, how can i do it?
 Where's my problem?
 Please give me a link from key codes

 --Regards
 Mohsen




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

Keyboard keys not recognized after AwesomeWM binding

[Alexis Brenon]

Hi dear Awesome users,

I bought a new laptop recently (Dell Inspiron 14-7437, on the French Dell
site), and I tried it on Ubuntu where all worked well. So I decided to
install ArchLinux with AwesomeWM. Most of devices work well (touchpad,
touchscreen, keyboard backlight, etc...), but I'm issuing some problems
with the keyboard.

While no binding is assigned to the combination : Meta + Shift + F1, xev
output what expected as you can see here : http://pastebin.com/nKd5ezhP

But as soon as I add a binding to this combination in my Awesome
configuration :

awful.key({modkey, Shift}, F1, volume.toggle)

The xev output changes -- http://pastebin.com/H9NEA9aA -- and so the
callback assigned to the binding isn't executed...

This weird behaviour happens with other keys like F1, F2, F3, Print Screen,
or Up/Down arrow keys, but not on others like F11, F12 or Left/Right
arrows...

I don't know from where it can come from... If anyone can help me to
investigate this, it would be very welcome !! Thanks.


Regards,
Alexis BRENON

Re: Force mouse to follow opened window but only when in same screen

[Alexis Brenon]

Hi Abhijeet,

Maybe adding in the condition someting like :
 if mouse.object_under_pointer() ~= c and mouse.screen = c.screen then
...
end

This way, your mouse will move to the focused window only if they are on
the same screen.

Best regards,
Alexis BRENON



Le Fri Nov 21 2014 at 09:00:14, Abhijeet Rastogi abhijeet.1...@gmail.com
a écrit :

 Hi everyone,,

 Right now, I've this small snipped in my rc.lua that makes the mouse
 focus to the center of newly opened window.

 client.connect_signal(focus, function(c)
 if mouse.object_under_pointer() ~= c then
 local geometry = c:geometry()
 local x = geometry.x + geometry.width/2
 local y = geometry.y + geometry.height/2
 mouse.coords({x = x, y = y}, true)
 end
 end)

 The problem with this is that, it also focuses to a window if it's in
 a separate screen. I only want it to happen for current screen. How
 do I make this possible?

 I tried to add c:isvisible() as one more condition but for some
 reason it isn't working. I'm dealing with IceadTea java windows so
 support for it is already messy. Could that be the reason?

 --
 Cheers,
 Abhijeet Rastogi (shadyabhi)

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

Re: awful.util.spawn creates a process with PPID=1. Any way to create a child of awesome process?

[Alexis Brenon]

Just an idea... Why do you not implement the whole yes-no box in lua in
awesome config file ?
Maybe it will solve the freeze problem and let you use clients and other
awesome stuff more easily.

Alexis.
Le 10 oct. 2014 10:34, Dmitry Grigoriev m...@dimgel.ru a écrit :

  On 10/10/2014 11:57 AM, Uli Schlachter wrote:

 How about io.popen()? I don't have Xdialog, but hopefully this represents
 its behavior:

  return io.popen((exit 1)  echo yes):read(*a)

  return io.popen((exit 0)  echo yes):read(*a)
 yes

 This assumes that Xdialog creates an override_redirect window. While
 Xdialog is running, awesome will freeze and stop doing anything until
 Xdialog exits. This is also what would happen with your posix.wait().

 Ah, I see... That freezing looks like bad idea. :) So perhaps I should
 code whole logic block into script like in this example
 http://awesome.naquadah.org/wiki/ShutdownDialog and let awesome
 continue working on its own after spawning that script. And later - e.g. if
 my dialog is about manipulating some client or other awesome object - use
 awesome-client to interact back, keeping track of manipulated object by
 storing it temporarily into some table and passing its key in command line
 arg.

 Thanks!

 --
 Best regards,
 Dmitry Grigoriev

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

Re: Library to configure Awesome from a file

[Alexis Brenon]

Hello Andrew,

It is a very interesting project. I started a mail thread
http://www.mail-archive.com/awesome@naquadah.org/msg07563.html few days
ago to know if some people are interested in an awesomeWM GUI configuration
builder, and so I'm very interested by your project.

I will have a look to it as soon as I will have the time.

Regards,
Alexis


2014-06-30 21:28 GMT+02:00 Andrew Phillips the...@gmail.com:

 Hello,

 I've written a library to read a JSON file describing your Awesome
 configuration with the goal of having the same configuration file work
 in both Awesome 3.4.x and 3.5.x, but not limiting the flexibility of
 awesome.  My long term intent is to make this library extensible so
 that the configuration could be edited with a GUI and be utilized by
 other extensions to Awesome.

 The code, instructions and example configuration are available here:
 https://github.com/theasp/awesome-config

 I am interested in any comments you wish to provide.

 --
 Andrew Phillips the...@gmail.com

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

GUI configuration

[Alexis Brenon]

Hello folks !

I've got an idea. What about an AwesomeWM configuration generator. A small
soft which allow new users to easily discover all (or at least many)
options that awesome offer.

In my head, the most important feature is to generate readable file with
comments which allow anyone to learn awesome API reading the generated file.

Is there an app that already exists for this ? Is anybody interested in
this kind of soft ? Is anybody interested to take part in the dev process ?

Bye,
Have a good day !

Alexis BRENON

Re: GUI configuration

[Alexis Brenon]

Hi Eugene,

Thanks for the answer. I never used Qt Designer so I don't very know what
it looks like. But I imagine that you can define your tags (with shifty or
not), define your common widgets (with common callbacks and format (for
example for clock, volume, battery), or custom (if you have particular
need) and place them as you want.

I don't know if it's very clear. Maybe some sketchup and/or use case will
help to identify features.

Best,
Alexis


2014-06-21 15:26 GMT+02:00 Evgeny Pakhomov p1hi...@gmail.com:

 Hi Alexis,

 I think it's an interesting idea, at least from the development challenge
 perspective.

 But how do you see it? Will it be something like Qt Designer, so a user
 will be available to define new widgets, configure and add them to his
 desktops? Or something that will change only the existing layout?

 Regards,
 Eugene


 On Sat, Jun 21, 2014 at 3:20 PM, Alexis Brenon brenon.ale...@gmail.com
 wrote:

 Hello folks !

 I've got an idea. What about an AwesomeWM configuration generator. A
 small soft which allow new users to easily discover all (or at least many)
 options that awesome offer.

 In my head, the most important feature is to generate readable file with
 comments which allow anyone to learn awesome API reading the generated file.

 Is there an app that already exists for this ? Is anybody interested in
 this kind of soft ? Is anybody interested to take part in the dev process ?

 Bye,
 Have a good day !

 Alexis BRENON

Re: GUI configuration

[Alexis Brenon]

Yes, something like this, but without the UI design part (that seems to be
quite difficult to make), because as I remember, in awesome, wiboxes can
only be on top, left, right, bottom, not anywhere on screen.

I will do some sketches this evening.

Best,
Alexis


2014-06-21 15:47 GMT+02:00 Evgeny Pakhomov p1hi...@gmail.com:

 You can see how Qt Designer handles signals and slots (it's how Qt
 implemented callbacks) at this video:
 http://www.youtube.com/watch?v=BYohbT6oUDM#t=350

 Yes, some sketch or use case will surely help.

 Regards,
 Eugene


 On Sat, Jun 21, 2014 at 8:36 PM, Alexis Brenon brenon.ale...@gmail.com
 wrote:

 Hi Eugene,

 Thanks for the answer. I never used Qt Designer so I don't very know what
 it looks like. But I imagine that you can define your tags (with shifty or
 not), define your common widgets (with common callbacks and format (for
 example for clock, volume, battery), or custom (if you have particular
 need) and place them as you want.

 I don't know if it's very clear. Maybe some sketchup and/or use case will
 help to identify features.

 Best,
 Alexis


 2014-06-21 15:26 GMT+02:00 Evgeny Pakhomov p1hi...@gmail.com:

 Hi Alexis,

 I think it's an interesting idea, at least from the development
 challenge perspective.

 But how do you see it? Will it be something like Qt Designer, so a user
 will be available to define new widgets, configure and add them to his
 desktops? Or something that will change only the existing layout?

 Regards,
 Eugene


 On Sat, Jun 21, 2014 at 3:20 PM, Alexis Brenon brenon.ale...@gmail.com
 wrote:

 Hello folks !

 I've got an idea. What about an AwesomeWM configuration generator. A
 small soft which allow new users to easily discover all (or at least many)
 options that awesome offer.

 In my head, the most important feature is to generate readable file
 with comments which allow anyone to learn awesome API reading the generated
 file.

 Is there an app that already exists for this ? Is anybody interested in
 this kind of soft ? Is anybody interested to take part in the dev process ?

 Bye,
 Have a good day !

 Alexis BRENON

Re: GUI configuration

[Alexis Brenon]

Yes, now that you say this, it's quite like other WM panel.
For the New widget window, you have the choice between common widgets, like
clock that only need a few arguments (format, color, battery ID, etc...) or
custom widgets that you can create from base widgets with custom callbacks
that you have to write.

Mohan :
It is what I propose but with a full app which allow you to change only one
option without the need of running through the whole script, and more user
friendly.

Good night,
Alexis.
Le 21 juin 2014 22:13, Evgeny Pakhomov p1hi...@gmail.com a écrit :

 Ah, I see now. At the beginning I was thinking about something like
 Drag-n-drop Lua with Awesome bindings.

 So, you want to see something that most major WM have. The only thing that
 I don't quite understand on your picture is the New Widget dialog. How
 will this work? As far as I can see you will still need to write some Lua
 code in order to create a meaningful widget, simple UI elements won't do
 the trick here.
 If I recall correctly in Gnome you can't create a new item for your panel
 from GUI, you have to write some actual code and then somehow register it
 (or a binary compiled from this code) the the Gnome UI Settings knows about
 it.
 Maybe something similar can be done in Awesome.

 - Eugene


 On Sun, Jun 22, 2014 at 2:43 AM, Alexis Brenon brenon.ale...@gmail.com
 wrote:

 Good evening !

 These are my first sketches, very simple, with many flaws... But to have
 an idea. Not really graphic. Much more like menu-config of linux kernel but
 with Qt or GTK, or whatever.

 Best,
 Alexis


 2014-06-21 16:30 GMT+02:00 Mohan Sundaram mohan@gmail.com:

 It would be good to have a bash driven script where one can choose
 widgets with their order, menu entries with order, keyboard/ mouse
 shortcuts, theme or background colour, fonts etc. It should produce rc.lua
 and a back up of the last good rc.lua.

 Regards
 Mohan Sundaram
 Mobile mail, please pardon autocomplete /autoreplace typos
 On Jun 21, 2014 7:40 PM, Alexis Brenon brenon.ale...@gmail.com
 wrote:

 Yes, something like this, but without the UI design part (that seems to
 be quite difficult to make), because as I remember, in awesome, wiboxes can
 only be on top, left, right, bottom, not anywhere on screen.

 I will do some sketches this evening.

 Best,
 Alexis


 2014-06-21 15:47 GMT+02:00 Evgeny Pakhomov p1hi...@gmail.com:

 You can see how Qt Designer handles signals and slots (it's how Qt
 implemented callbacks) at this video:
 http://www.youtube.com/watch?v=BYohbT6oUDM#t=350

 Yes, some sketch or use case will surely help.

 Regards,
 Eugene


 On Sat, Jun 21, 2014 at 8:36 PM, Alexis Brenon 
 brenon.ale...@gmail.com wrote:

 Hi Eugene,

 Thanks for the answer. I never used Qt Designer so I don't very know
 what it looks like. But I imagine that you can define your tags (with
 shifty or not), define your common widgets (with common callbacks and
 format (for example for clock, volume, battery), or custom (if you have
 particular need) and place them as you want.

 I don't know if it's very clear. Maybe some sketchup and/or use case
 will help to identify features.

 Best,
 Alexis


 2014-06-21 15:26 GMT+02:00 Evgeny Pakhomov p1hi...@gmail.com:

 Hi Alexis,

 I think it's an interesting idea, at least from the development
 challenge perspective.

 But how do you see it? Will it be something like Qt Designer, so a
 user will be available to define new widgets, configure and add them to 
 his
 desktops? Or something that will change only the existing layout?

 Regards,
 Eugene


 On Sat, Jun 21, 2014 at 3:20 PM, Alexis Brenon 
 brenon.ale...@gmail.com wrote:

 Hello folks !

 I've got an idea. What about an AwesomeWM configuration generator.
 A small soft which allow new users to easily discover all (or at least
 many) options that awesome offer.

 In my head, the most important feature is to generate readable file
 with comments which allow anyone to learn awesome API reading the 
 generated
 file.

 Is there an app that already exists for this ? Is anybody
 interested in this kind of soft ? Is anybody interested to take part 
 in the
 dev process ?

 Bye,
 Have a good day !

 Alexis BRENON

Re: taglist square resize : TODO or deprecated feature

[Alexis Brenon]

Radical seems to be a very complete set of extensions ! I will have a look.
Thanks.


2014-06-10 16:34 GMT+02:00 Elv1313 . elv1...@gmail.com:

 Yes, there is:


 https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1230project=1order=idsort=desc

 you can also watch the Radical (and use) repository implementation if
 you wish. That way to can report issues on github and be part of the
 development process.

 Emmanuel
 On 10 June 2014 08:57, Alexis Brenon brenon.ale...@gmail.com wrote:
  Hi, thanks for the answer.
 
  Is there a thread/discussion on the taglist successor somewhere ? I would
  like to see the progress.
 
  Thanks.
 
 
  2014-06-06 18:57 GMT+02:00 Elv1313 . elv1...@gmail.com:
 
  Hi,
 
  It is possible with some hacks, see https://github.com/Elv13/blind
  (read the code about how to use a function instead of an image file to
  be able to stretch it) . But really the taglist is pseudo deprecated
  by now. What will replace it is still debated, but I personally have
  my own, more flexible and extensible alternative here (
  https://github.com/Elv13/radical/tree/master/impl/taglist ). It is not
  really documented, but there is an usage example in my awesome config.
  It works fine and support themes, there is currently 6 of them, basic
  look like the current taglist while arrow_prefix is the one used in
  this screenshot (
 
 https://raw.githubusercontent.com/Elv13/radical/master/screenshot/all.png
  ).
 
  On 6 June 2014 02:56, Alexis Brenon brenon.ale...@gmail.com wrote:
   Hi all,
  
   In the taglist widget, I would like to have the image (square_[un]sel)
   to be
   stretched horizontally to fit the tag image. I thought that
   taglist_square_resize option was here for this purpose but it didn't
   seems
   to work...
  
   After a quick look in the source code, it seems that this option is
 only
   read in the awful.widget.taglist.taglist_label() function but is value
   isn't
   relayed to any tag creation function.
  
   I would like to know if it's a normal behaviour (perhaps I missed
   another
   place where the option is read), or if it's a bug, in which case, if
   there
   anybody who already try to fix it or have I to do it myself ?
  
   Thanks.
   Alexis BRENON
 
 

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

Re: taglist square resize : TODO or deprecated feature

[Alexis Brenon]

Hi, thanks for the answer.

Is there a thread/discussion on the taglist successor somewhere ? I would
like to see the progress.

Thanks.


2014-06-06 18:57 GMT+02:00 Elv1313 . elv1...@gmail.com:

 Hi,

 It is possible with some hacks, see https://github.com/Elv13/blind
 (read the code about how to use a function instead of an image file to
 be able to stretch it) . But really the taglist is pseudo deprecated
 by now. What will replace it is still debated, but I personally have
 my own, more flexible and extensible alternative here (
 https://github.com/Elv13/radical/tree/master/impl/taglist ). It is not
 really documented, but there is an usage example in my awesome config.
 It works fine and support themes, there is currently 6 of them, basic
 look like the current taglist while arrow_prefix is the one used in
 this screenshot (
 https://raw.githubusercontent.com/Elv13/radical/master/screenshot/all.png
 ).

 On 6 June 2014 02:56, Alexis Brenon brenon.ale...@gmail.com wrote:
  Hi all,
 
  In the taglist widget, I would like to have the image (square_[un]sel)
 to be
  stretched horizontally to fit the tag image. I thought that
  taglist_square_resize option was here for this purpose but it didn't
 seems
  to work...
 
  After a quick look in the source code, it seems that this option is only
  read in the awful.widget.taglist.taglist_label() function but is value
 isn't
  relayed to any tag creation function.
 
  I would like to know if it's a normal behaviour (perhaps I missed another
  place where the option is read), or if it's a bug, in which case, if
 there
  anybody who already try to fix it or have I to do it myself ?
 
  Thanks.
  Alexis BRENON

taglist square resize : TODO or deprecated feature

[Alexis Brenon]

Hi all,

In the taglist widget, I would like to have the image (square_[un]sel) to
be stretched horizontally to fit the tag image. I thought that
taglist_square_resize option was here for this purpose but it didn't seems
to work...

After a quick look in the source code, it seems that this option is only
read in the awful.widget.taglist.taglist_label()
https://github.com/awesomeWM/awesome/blob/master/lib/awful/widget/taglist.lua.in#L28
function but is value isn't relayed to any tag creation function.

I would like to know if it's a normal behaviour (perhaps I missed another
place where the option is read), or if it's a bug, in which case, if
there anybody who already try to fix it or have I to do it myself ?

Thanks.
Alexis BRENON