You are not logged in.
I'm curious about this:
--!Table of layouts to cover with awful.layout.inc, order matters.
awful.layout.layouts = {
awful.layout.suit.tile,
-- awful.layout.suit.floating,
-- awful.layout.suit.tile.left,
-- awful.layout.suit.tile.bottom,
-- awful.layout.suit.tile.top,
-- awful.layout.suit.fair,
-- awful.layout.suit.fair.horizontal,
-- awful.layout.suit.spiral,
-- awful.layout.suit.spiral.dwindle,
-- awful.layout.suit.max,
-- awful.layout.suit.max.fullscreen,
-- awful.layout.suit.magnifier,
-- awful.layout.suit.corner.nw,
-- awful.layout.suit.corner.ne,
-- awful.layout.suit.corner.sw,
-- awful.layout.suit.corner.se,
}
-- }}}
Why are you only using one layout?
You must unlearn what you have learned.
-- yoda
Online
To make it easier for me to transition to awesome from openbox. In tile mode, modkey-m takes a window out of tiling so it's essentially floating maximized. So witching to floating mode doesn't seem that useful to me. And for a complete tiling n00b, removing options to begin with simplifies the learning curve.
The layouts are there, just enable them and have at it. modkey+Space to cycle through the layouts, and I'd enable the layout-switcher widget in rc.lua, too.
roy@TyrellCorp:~$ apt-cache policy awesome
awesome:
Installed: 4.3-4
Candidate: 4.3-4
Version table:
*** 4.3-4 500
500 https://deb.debian.org/debian buster/main amd64 Packages
100 /var/lib/dpkg/status
roy@TyrellCorp:~$
Stretch is 4.0 but jessie is 3.4-15, so good heads up that my rc.lua might not work there.
Last edited by hhh (2019-04-28 05:23:18)
No, he can't sleep on the floor. What do you think I'm yelling for?!!!
Offline
^ Jessie? how does that relate to the next release??? :confused:
the gaps around the terminals will close and all screen real estate will be utilized.
sorry to be nitpicking, but that's not strictly true: it will put empty space around the text inside the terminal. the terminal however cannot utilize this empty space.
that said it definitely looks better and sometimes also helps with moving windows around (you can be sure that 50% height is exactly 50% height, and not 50% minus a few pixels).
Last edited by ohnonot (2019-04-27 07:09:44)
Offline
^ Jessie? how does that relate to the next release??? :confused:
Users need to keep in mind that lua (and therefore awesome) is not always backwards compatible
Just erring on the side of caution. I originally mentioned jessie as a marginal case, anyway.
No, he can't sleep on the floor. What do you think I'm yelling for?!!!
Offline
PackRat wrote:Users need to keep in mind that lua (and therefore awesome) is not always backwards compatible
Just erring on the side of caution. I originally mentioned jessie as a marginal case, anyway.
lua code is also not necessarily compatible from one rc.lua to another even though the versions of awesome/lua are the same. I'm finding that out right now trying to port some keybindings for window movement over from the ArchLabs config to my own config. Can't bring the bindings and helper function over directly; going to need to translate some additional lua to get them working.
Curse you for getting me started on this 8o
You must unlearn what you have learned.
-- yoda
Online
Nice writeup and I may give Awesome a whirl one of these days. How lightweight can you go with a WM?
Real Men Use Linux
Offline
How lightweight can you go with a WM?
In general? Pretty low, but you start to lose basic features. Scroll down for a comparison - window manager comparison
Awesome is similar to openbox, i3, and fluxbox once you start running some widgets with it.
17.9 MiB + 3.8 MiB = 21.7 MiB awesome
Last edited by PackRat (2019-04-27 22:45:08)
You must unlearn what you have learned.
-- yoda
Online
DeepDayze wrote:How lightweight can you go with a WM?
In general? Pretty low, but you start to lose basic features. Scroll down for a comparison - window manager comparison
Awesome is similar to openbox, i3, and fluxbox once you start running some widgets with it.
17.9 MiB + 3.8 MiB = 21.7 MiB awesome
Cool, and from the screenshot that Triple H posted it looks close to openbox with the background and the layout. Can Tint2 be used with Awesome?
Real Men Use Linux
Offline
Can Tint2 be used with Awesome?
Not very well (if at all); that may have changed, I haven't tried tint2 with awesome in about a year. Awesome is not fully EWMH compliant. What were you needing from tint2? The default configuration for awesome includes a panel (wibar) that includes tag list, iconbar, systemtray and clock. Better aesthetics with tint2, but there are enough 3rd party widgets available to replicate tint2 and conky functionality on the wibar.
xfce-panel works better, and no problems with polybar.
Last edited by PackRat (2019-04-28 02:31:34)
You must unlearn what you have learned.
-- yoda
Online
Can Tint2 be used with Awesome?
Not very well (if at all); that may have changed, I haven't tried tint2 with awesome in about a year. Awesome is not fully EWMH compliant. What were you needing from tint2? The default configuration for awesome includes a panel (wibar) that includes tag list, iconbar, systemtray and clock. Better aesthetics with tint2, but there are enough 3rd party widgets available to replicate tint2 and conky functionality on the wibar.
xfce-panel works better, and no problems with polybar.
OK great tip and I'll give the wibar a spin and see how closely I can replicate in wibar as in Tint2/xfce-panel. For tint2 be using the default BL config and will it work?
Real Men Use Linux
Offline
PackRat wrote:Can Tint2 be used with Awesome?
Not very well (if at all); that may have changed, I haven't tried tint2 with awesome in about a year. Awesome is not fully EWMH compliant. What were you needing from tint2? The default configuration for awesome includes a panel (wibar) that includes tag list, iconbar, systemtray and clock. Better aesthetics with tint2, but there are enough 3rd party widgets available to replicate tint2 and conky functionality on the wibar.
xfce-panel works better, and no problems with polybar.
OK great tip and I'll give the wibar a spin and see how closely I can replicate in wibar as in Tint2/xfce-panel. For tint2 be using the default BL config and will it work?
You posted before I could edit - From the Arch Forum - you get the idea about using 3rd part panels with tint2, hasn't changed much since that thread.
It will take some scripting, but I think the default BL tint2 layout can be replicated in the awesome wibar. I know the launchers can be created as widgets, and the system tray and clock are available OOTB. I've don't recall seeing the tasklist widget laid out in multi-desk pager mode. That would need some scripting.
You must unlearn what you have learned.
-- yoda
Online
DeepDayze wrote:PackRat wrote:Not very well (if at all); that may have changed, I haven't tried tint2 with awesome in about a year. Awesome is not fully EWMH compliant. What were you needing from tint2? The default configuration for awesome includes a panel (wibar) that includes tag list, iconbar, systemtray and clock. Better aesthetics with tint2, but there are enough 3rd party widgets available to replicate tint2 and conky functionality on the wibar.
xfce-panel works better, and no problems with polybar.
OK great tip and I'll give the wibar a spin and see how closely I can replicate in wibar as in Tint2/xfce-panel. For tint2 be using the default BL config and will it work?
You posted before I could edit - From the Arch Forum - you get the idea about using 3rd part panels with tint2, hasn't changed much since that thread.
It will take some scripting, but I think the default BL tint2 layout can be replicated in the awesome wibar. I know the launchers can be created as widgets, and the system tray and clock are available OOTB. I've don't recall seeing the tasklist widget laid out in multi-desk pager mode. That would need some scripting.
Guess I was too fast posting
Got a lot to learn about scripting to be able to replicate the BL setup in wibar. Awesome looks nice and I plan to spend some time playing with it with a VM install of BL.
Real Men Use Linux
Offline
Curse you for getting me started on this 8o
It's a curse I'll just have to bear. I'm loving this awesome session.
re: RAM, the awesome config in this guide uses most of the same daemons and programs as BL Openbox (power manager, network manager, pnmixer, compton, gnome-daemon gets started, polkit gets started...) so the result is almost identical RAM usage. About ~280M during desktop idle once thunar has been opened, which starts tumblerd and more gvfs processes like Trash. That's on the 64bit version with 3G of RAM installed.
No, he can't sleep on the floor. What do you think I'm yelling for?!!!
Offline
As PackRat said, tint2 with awesome sucks. The placement is all wonky,for one thing.
xfce4-panel works great, though...
https://wiki.archlinux.org/index.php/aw … th_awesome
So if you're using this tutorial and you've installed xfce4-panel, you can add that to your autorun.sh and then comment out the following block in rc.lua that starts around line #230, thusly...
--[[
-- Create the wibox
s.mywibox = awful.wibar({ position = "top", screen = s })
--!Panel widgets
-- Add widgets to the wibox
s.mywibox:setup {
layout = wibox.layout.align.horizontal,
{ -- Left widgets
layout = wibox.layout.fixed.horizontal,
--! mylauncher,
s.mytaglist,
s.mypromptbox,
},
s.mytasklist, -- Middle widget
{ -- Right widgets
layout = wibox.layout.fixed.horizontal,
--! mykeyboardlayout,
wibox.widget.systray(),
mytextclock,
--! s.mylayoutbox,
},
}
--]]
end)
-- }}}
And at line #202...[code] -- Each screen has its own tag table.
--! awful.tag({ "1", "2", "3", "4", "5" }, s, awful.layout.layouts[1])
awful.tag({ "1", "2" }, s, awful.layout.layouts[1])[/code]
-- {{{ Mouse bindings
And pic or it didn't happen...
Last edited by hhh (2019-04-28 08:13:23)
No, he can't sleep on the floor. What do you think I'm yelling for?!!!
Offline
^ looks good; if you open some windows can you control them (focus, minimize etc ...) from the xfce4-panel window buttons? I can in Void and ArchLabs. I suspect Debian Stable will be as functional.
If a user really needs the bells and whistles, awesome can be used as the window manager in xfce4 desktop (not the subject for a beginner's tutorial though):
You must unlearn what you have learned.
-- yoda
Online
^Yes, the taksbar icons work as expected (-edit- Wrong. Clicking a running app's panel icon isn't minimizing, but right-click and choose the menu item does. Clicking the icon restores it as expected). It takes a few seconds to open, and Conky is causing problems, it's appearing above opened windows. If I restart conky everything behaves normally.
How do I add a sleep time to the autorun? 'run (sleep 20 && bl-conky-session)' doesn't work.
No, he can't sleep on the floor. What do you think I'm yelling for?!!!
Offline
I think you need to specify the time units -
sleep 2s && conky-script <-- that "s" for seconds is required, I believe.
For conky, you can also use the -p flag in your script/command.
For that conky clock, you may just want to go with "own_window = false" and let it draw directly to the desktop.
You must unlearn what you have learned.
-- yoda
Online
^ looks good; if you open some windows can you control them (focus, minimize etc ...) from the xfce4-panel window buttons? I can in Void and ArchLabs. I suspect Debian Stable will be as functional.
If a user really needs the bells and whistles, awesome can be used as the window manager in xfce4 desktop (not the subject for a beginner's tutorial though):
https://cdn.scrot.moe/images/2019/03/01/2019-03-01-04-51-03.th.png
https://cdn.scrot.moe/images/2019/03/01/2019-03-01-04-52-00.th.png
Lovely. What's the code to keep the window-list in the panel @ ~200px like you have it? Is it possible to just display icons with no title text?
Also, I can't get window active-border-highlight colors to work, the option in theme.lua isn't working, either.
No, he can't sleep on the floor. What do you think I'm yelling for?!!!
Offline
Lovely. What's the code to keep the window-list in the panel @ ~200px like you have it? Is it possible to just display icons with no title text?
That's xfce4-panel; so unchecking the "show labels" for the window button item will show icons only. The button width is in the gtk theme isn't it? User should be able to use tint2 instead if desired.
You must unlearn what you have learned.
-- yoda
Online
Also, I can't get window active-border-highlight colors to work, the option in theme.lua isn't working, either.
What code are you using?
Something like this not working?
theme.border_focus = "#478061"
I think the theme is read top down; you have that line later in the theme.lua messing you up?
You must unlearn what you have learned.
-- yoda
Online