There are two ways to measure memory usage in Linux:

• Available memory is being used for something, but is readily available. Linux does this to run programs more efficiently if RAM is not being used.
• Free memory is not being used for anything. You could call it wasted RAM. It is almost always very low and lower than available memory.

[linuxatemyram.com](https://www.linuxatemyr

I looked in the documentation. it doesn't work. ive looked online. all search results are either about awesome 3.5, or windows 10. how do i change the 24 hour clock into a 12 hour one

info: awesome v4.3 (Too long)
• Compiled against Lua 5.3.3 (running with Lua 5.3)
• D-Bus support: ✔
• execinfo support: ✔
• xcb-randr version: 1.6
• LGI version: 0.9.2

Distribution (run cat /etc/os-release):
Pop!_OS 20.04

**Related Application and/or Pa

Hi, first of all, many thanks for this awesome project! Now onto my issue/question:

I find it confusing that when I'm pressing Super+Left/Right (and the minimap is active) I cannot use other hotkeys, like for instance Shift+Super+Left/Right to change monitor. Is this intended or undesired?

Many thanks!

Describe the bug
When restoring a full-screened view, the decorations are not reset.

To Reproduce
Steps to reproduce the behavior:

1. Enable grid and wm-actions plugins
2. Full screen view with wm-actions plugin
3. Restore view with grid plugin

Expected behavior
The decoration is reset when a full-screened view is no longer full screen.

Wayfire version
0.6.0

Unfortunately, I lost my setup some days ago... and I have no copy of that. So, I decided to redo it, but I'm struggling following the spare guides. I'm trying to reproduce my sticky workspaces setup (three monitors) with no success at all.

The bare template config is:

{
    context.AddBar();
    context.AddFocusIndicator();
    var actionM

I ran out of time to implement this today and don't really need it for anything I'm personally working towards yet. We should probably implement parent events though to better support this protocol.

Much like moveToPercentOfScreen, it would be handy if there were a Window.percentOfScreen() getter.

I want to use this to so I can throw a window to the next screen, but maintain its relative position/sizing.