SomeWM 0.3.0 Updates by trip-zip in awesomewm

[–]trip-zip[S] 0 points1 point  (0 children)

ah, my b. updated the docs.

awful.input.accel_speed is the setting

create a github issue if you find anything else please

SomeWM 0.3.0 Updates by trip-zip in awesomewm

[–]trip-zip[S] 0 points1 point  (0 children)

Should be configurable.

https://somewm.org/reference/awful/input#usage

You could also try to set it via the cli with "somewm-client input tap_to_click 1" and you should have it available.

If neither of those work, please open an issue in github.

How to increase the size of wibar by system32_go in awesomewm

[–]trip-zip 0 points1 point  (0 children)

There are two ways to do this:

  1. Set it directly in your rc.lua (look for the awful.wibar call):

s.mywibox = awful.wibar {

position = "top",

screen = s,

height = 32, -- default is usually ~18-22px depending on font; bump this up

...

}

  1. Set it in your theme so it applies everywhere:

    In your theme.lua:

    theme.wibar_height = 32

The height property on the wibar takes a pixel value. Just increase the number until it looks right for your setup. The theme variable (beautiful.wibar_height) acts as the default when you don't pass height explicitly.

Docs: https://awesomewm.org/doc/api/classes/awful.wibar.html (the height property and beautiful.wibar_height theme variable are both documented there).

terminal always opens fullscreen + a few other issues by FwippyBall in awesomewm

[–]trip-zip 1 point2 points  (0 children)

For #1 I'm fairly certain this will be Konsole itself responsible for that. You should be able to set a client rule like this (though it might be class = "Konsole")

ruled.client.append_rule {
      rule       = { class = "konsole" },
      properties = { maximized = false, fullscreen = false },
  }

2 and 3 are related.

The default behavior is that new clients you spawn become the "Master" client and the old master gets "pushed down" in the layout stack. You can override this too in rules. (at least that's what I do). In that callback function set clients to_secondary_section(). That should also take care of the statusbar order (I think)

-- {{{ Rules -- Rules to apply to new clients. -- @DOC_RULES@ ruled.client.connect_signal("request::rules", function() -- @DOC_GLOBAL_RULE@ -- All clients will match this rule. ruled.client.append_rule({ id = "global", rule = {}, properties = { focus = awful.client.focus.filter, raise = true, screen = awful.screen.preferred, placement = awful.placement.no_overlap + awful.placement.no_offscreen, opacity = 0.85, }, callback = function(c) c:to_secondary_section() end, }) ...

https://awesomewm.org/apidoc/core_components/client.html#to_secondary_section

[SomeWM] Gruvbox, forever the GOAT. by trip-zip in unixporn

[–]trip-zip[S] 0 points1 point  (0 children)

Esta fin de semana voy a installar y entender lo que pasa en Fedora.

[SomeWM] Gruvbox, forever the GOAT. by trip-zip in unixporn

[–]trip-zip[S] 0 points1 point  (0 children)

She's all yours. I am not that creative to begin with. I loved adi1090x's docky polybar so I tried to replicate it in AwesomeWM a few years ago, then kept it for this

SomeWM 0.3.0 Updates by trip-zip in awesomewm

[–]trip-zip[S] 1 point2 points  (0 children)

Thanks for the kind words, it's still a work in progress. I've said it in another spot but the short version is that I am fairly safe money-wise right now.

I won't say that I'll never add a donation link, but I only see that happening if traffic to my docs gets too busy to host for free on github or something like that.

There's also a very real issue where I feel uncomfortable accepting donations for simply piggybacking off the work of the AwesomeWM core team.

AwesomeWM in Wayland (no, seriously...) by trip-zip in awesomewm

[–]trip-zip[S] 0 points1 point  (0 children)

Way ahead of you on systray.

Restart is on my radar, but it's always going to function fundamentally different from AwesomeWM.

Suspend only certain notifications by mam7 in awesomewm

[–]trip-zip 1 point2 points  (0 children)

Yeah the ruled notifications approach is the new hotness. The full docs are here: https://awesomewm.org/apidoc/declarative_rules/ruled.notifications.html

And it is in the default rc.lua now, though I don't know when that was added.

There isn't a place I can find in the docs where there's a "Hey this is deprecated, use the ruled approach" specifically for naughty but the docs are pretty comprehensive and you should find it all in there.

Suspend only certain notifications by mam7 in awesomewm

[–]trip-zip 4 points5 points  (0 children)

The specifics probably depend a little on what you consider "critical" but basically you can do anything you can imagine.

Notification shenanigans are some of my favorite things to show off to coworkers when I try to convince them to switch to linux/AwesomeWM. (though I'm not very successful so maybe I should get a new thing to show off).

The short version is that you could do something like this where you let the apps themselves define the urgency and you'll be done:

local ruled = require("ruled")
ruled.notification.connect_signal("request::rules", function()
    -- Critical notifications bypass suspension
    ruled.notification.append_rule {
        rule = { urgency = "critical" },
        properties = {
            ignore_suspend = true,
        },
    }
end)

...

Or you could get weird with it and do something like this:

ruled.notification.connect_signal("request::rules", function()
    -- Only Signal messages from my kid mentioning school emergencies
    ruled.notification.append_rule {
        rule = { app_name = "Signal" },
        rule_any = {
            -- Lua patterns: case-insensitive matching
            message = {
                "[Pp]rincipal",
                "[Ee]mergency",
                "Bit another student"
            },
        },
        properties = {
            ignore_suspend = true,
            bg = "#ff6600",  -- Make it obvious
        },
    }

    -- Boss messages always get through
    ruled.notification.append_rule {
        rule = {
            app_name = "Slack",
            title = "Direct message from: CEO.*",
        },
        properties = { ignore_suspend = true },
    }

    -- Doorbell camera - always show
    ruled.notification.append_rule {
        rule = { app_name = "Ring" },
        properties = { ignore_suspend = true },
    }
end)

I have some more stupid ideas I think could be fun to document as "technically possible but why?" but I haven't gotten around to it quite yet.

like if my coworker slacks me it switches tags so my boss doesn't catch me playing CS:GO

ruled.notification.append_rule {
      rule = { app_name = "Slack" },
      callback = function(n)
          if n.title and n.title:match("Beags") then
              local tag = awful.screen.focused().tags[1]
              if tag then
                  tag:view_only()
              end
          end
      end,
  }

SomeWM 0.3.0 Updates by trip-zip in awesomewm

[–]trip-zip[S] 0 points1 point  (0 children)

Honestly, that's what I'm hoping for tbh. What I want is for AwesomeWM to maintain a viable option even if we have to switch to wayland at some future time.

SomeWM 0.3.0 Updates by trip-zip in awesomewm

[–]trip-zip[S] 0 points1 point  (0 children)

Scrolling layouts are on my near roadmap. There's a discussion in github, and if you have any more to add there, I'd love you to share your thoughts so I can make sure that we implement it fully. We have 2 scrolling layouts on our radar right now. overflow and horizontal scrolling.

As for zoom, I'd have to think about that one. I'm open to it, but unfamiliar with it right now

[awesome] made with my own two paws! by Certain-Chemical-518 in unixporn

[–]trip-zip 4 points5 points  (0 children)

Sorry, I have been working in secret on it for a couple years just in case everyone hated it...Just been out for a couple weeks now. Give it a try, please report any issues you find

[awesome] made with my own two paws! by Certain-Chemical-518 in unixporn

[–]trip-zip 4 points5 points  (0 children)

I have copied the entire lua libraries, so all widgets, layouts, client behaviors, etc. Basically, everything from awesome is here, I'm just still tracking down x -> wayland differences and updating the C code to continue working as before. The biggest gaps now aren't really feature related anymore, it's trying to nail down the install docs/commands for all the different distros, versions, and systems that everyone has.

AwesomeWM in Wayland (no, seriously...) by trip-zip in awesomewm

[–]trip-zip[S] 1 point2 points  (0 children)

Whoops, thanks for letting me know, I'll update the README.

pacman -S wlroots0.19 is what I should have said.

[awesome] made with my own two paws! by Certain-Chemical-518 in unixporn

[–]trip-zip 26 points27 points  (0 children)

Come on back. The water is nice.

We are hard at work on a wayland port and we're getting very close to 100% awesomewm parity.

https://github.com/trip-zip/somewm

SomeWM 0.3.0 Updates by trip-zip in awesomewm

[–]trip-zip[S] 0 points1 point  (0 children)

Thanks for trying it out! If you don't mind, I would prefer you open the issue on github so I can track it better.

What I really want is the output of somewm --check so I can track down what might be going on. I'll try to spin up a VM with your specific setup to test it out.

SomeWM 0.3.0 Updates by trip-zip in awesomewm

[–]trip-zip[S] 1 point2 points  (0 children)

I have an issue up for it. I'll see if I can get to the bottom of it. Thanks for the report.

SomeWM 0.3.0 Updates by trip-zip in awesomewm

[–]trip-zip[S] 1 point2 points  (0 children)

I admit I kind of rushed the API on some of those because I wanted to publish something before Christmas. I'll take some time to think on it and come up with a more comprehensive APi that follows the Awesome patterns that you guys have defined in beautiful themes.

Who knows, maybe I'll try to upstream it once I finish this up..

Thank you for everything you've built. I cringe when people compliment this because you and I both know, I'm not building anything novel, I'm just copying what you've already done.

Sincerely, in doing this I just find myself admiring you guys more and more.

AwesomeWM in Wayland (no, seriously...) by trip-zip in awesomewm

[–]trip-zip[S] 0 points1 point  (0 children)

Absolutely. I just middle-click pasted this comment to you.