endeavouros-team / endeavouros-i3wm-setup Goto Github PK

To get chips' temperature in script, "sensors -u $chip |" command is used as main way to achieve the function.
the output is seems lilke due to this loop, which seems like read temp1_input as default temp indicator.
while () {
if (/^\s+temp1_input:\s+[+]([-]\d+.\d)/) {
$temperature = $1;
last;
}
}
close(SENSORS);

here is my "sensors -u $chip" output in shell:

iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:
temp1_input: 43.000

temp1_input is allocated to the virtual device.

I'm not familiar with programming, just could read basic bash or python script, it seems like I need some help from advanced programmers.
so, Is there any way to mk temp indicator as default expected functions?Thanks

i did a raw install
and idk how to resize the windows

i tried many keybindings

Reason: feh is called in config but not installed as package

at least geometry is now configured differently.

there is https://raw.githubusercontent.com/cytopia/i3blocks-modules/master/modules/battery

Could you upload or provide source for default font used for this config, please? It was patched Noto Sans I think. Mine was overwritten by another one.

Description

Hi. Monitor brightness control keys (XF86MonBrightnessUp & XF86MonBrightnessDown) might not work out of the box on some systems.

Issue

In i3 config xbacklight is used to control brightness.
But xbacklight only works with Intel drivers (see: https://wiki.archlinux.org/title/backlight).

Steps to reproduce

• CPU: AMD Ryzen 7 PRO 5850U with Radeon Graphics

Command:

xbacklight -get

will return No outputs have backlight property.

Possible fix

1. Install acpilight that is backward-compatibile with xbacklight - so there would be no need to change i3 config.
2. Add current user to the video group (as mentioned in: https://gitlab.com/wavexx/acpilight/-/issues/16) to allow user to update brightness.

No guide for managing startup applications. How on earth is Skype able to launch at login if there isn't a tool for this? A Google search yielded no helpful information on this topic.

Hi!
I've been using Linuxmint 20.3 since 2021 and I've decided to switch to EndeavourOS some weeks ago.
When I have installed EndeavourOS, I've choosen to install the official i3 flavour and after install, I booted to i3 and the icons in the menus were normal. After I have extracted my old ~, which it had a LOT OF fonts in ~/.fonts and ~/.local/share/fonts, they were not as they were before

e.g the powermenu

the battery mode menu

fc-list
fc-list.txt

fc-list | awk -F ":" '{ print $2 }' | uniq
fc-list2.txt

this is probably my fault with all these fonts i have on my ~ 😅

This happen after I update 09/12/2022.

I am on i3wm, endeavourOS.

I also check the config for i3, nothing looked change/different.

This is the best default configuration I ever used and, thank you for your work, it helped me a lot to build my own configuration and learn about Linux.

Hello how can I install endeavouros-i3wm-setup in my arch base

I believe there are missing packages in https://raw.githubusercontent.com/endeavouros-team/EndeavourOS-packages-lists/master/i3

• upower - required by battery.sh script and probably reason of #16
• nano-syntax-highlighting

HI, I want to open this issue to give attention to the picom exec command that you can find on the i3 config file
I know that it is disabled by default but the command
exec --no-startup-id picom -b
doesn't work when I apply the changes ( actually does with a reboot )
but if I do:
exec_always --no-startup-id picom -b
will work perfectly after only a reload of i3wm I think this change could make the default experience better

Cheers,
Al6263 ( EOS user )

When I run:

sudo pacman -S --needed - < i3

, I get

Total nedlastingsstørrelse:     0,07 MiB
Total installasjonsstørrelse:   0,10 MiB

:: Fortsett installasjonen? [J/n] j
:: Laster ned pakker...
 endeavouros-skel-default-1.0-3-any                         15,3 KiB  47,8 KiB/s 00:00 [--------------------------------------------------] 100%
 eos-lightdm-slick-theme-2.0-1-any                          13,5 KiB  39,6 KiB/s 00:00 [--------------------------------------------------] 100%
 endeavouros-skel-i3wm-3.0-9-any                            41,0 KiB   113 KiB/s 00:00 [--------------------------------------------------] 100%
 Totalt (3/3)                                               69,8 KiB   167 KiB/s 00:00 [--------------------------------------------------] 100%
(3/3) kontrollerer nøkler i nøkkelringen                                               [--------------------------------------------------] 100%
(3/3) kontrollerer pakkeintegritet                                                     [--------------------------------------------------] 100%
(3/3) laster pakkefiler                                                                [--------------------------------------------------] 100%
(3/3) finner filkollisjoner                                                            [--------------------------------------------------] 100%
feil: kunne ikke utføre transaksjon (motstridende filer)
eos-lightdm-slick-theme: /etc/lightdm/slick-greeter.conf finnes i filsystemet
Feil oppstod, ingen pakker ble oppgradert.

Where the instalation gets the default keyboard configuration?

edit: all i can found online are paliative solutions regarding calls of setxkbdmap in i3 config but I want to change the original configuration

current i3 configuration
https://github.com/Arrow-x/dotfiles/tree/main/i3

For me, the play pause function with playerctl wasn't working. I fixed it by changing
bindsym XF86AudioPlay exec --no-startup-id playerctl play
to
bindsym XF86AudioPlay exec --no-startup-id playerctl play-pause
And commenting out the same function for pause.

Additional proposed change:

# automatic focus of new window if it is opened in a workspace other than the current:

Since I need the terminal in i3wm to have a transparent background, I made some configurations.

• Install the compositor picom

sudo pacman -S picom

• Configure i3wm to start picom

# Start picom in the i3wm configuration file
exec_always --no-startup-id picom -b

nano-syntax-highlighting is referenced in .nanorc, but is not installed

if i have endeavouros-gemini installed with kde , is it safe to use i3wm script to install or should i do it manually ?

Experiencing an issue where the labels (fontawesome glyphs) are overlapping with the values they represent.

Temporarily I've resolved the issue by adding spaces (3 to be accurate) at the end of each label in i3blocks.conf, and that seems to work but I don't know if it's the best solution for everyone, or if there's a more universal option, and so haven't submitted a PR. I can do so if you'd like

This commit for example:

06f0d4e

The configs are deleted from the repo and then uploaded again completely. This makes it more difficult to compare changes, instead of just committing the changes so that the config can have a proper git history.

Battery Charge is not being displayed in status bar, running the battery.sh also gives following errors

Use of uninitialized value $bat_state in pattern match (m//) at .config/i3/scripts/battery.sh line 46.
Use of uninitialized value $bat_state in concatenation (.) or string at .config/i3/scripts/battery.sh line 47.

After switching back to this version https://github.com/endeavouros-team/endeavouros-i3wm-setup/blob/3c7ced74922a4116bbec21a44d20687c0abefdb3/.config/i3/scripts/battery.sh it works again

I was recently doing some digging to configure myself a combination lock and suspend on top of the base EndevourOS i3 and I had some thoughts for discussion.

• It appears the blur-lock implementation is a verbatim copy of this repo, and it does not appear that any credit is given to the author(s). While their script is extremely useful, it is not complicated, but nevertheless it seems right to credit them given that it's a direct copy. Also, their code has no license, which could be a problem.
• There is an umerged PR on said code that offers a very nice suggestion (adding -z to the scrot call to ensure no beep). On my system the beep is horrible and jolting, and I think this flag should definitely be added to our version.
• How do people feel about a lock+suspend entry in the menu, or replacing the command for the "suspend" with lock+suspend commands (my preference and current config)? Personally, I think this is much more useful and desirable than a plain suspend, and I believe most desktop environments also lean this way (calling it suspend and doing a lock+suspend). It also keeps from having a lock but no sleep/dark case, which I have had multiple times, and is quite frustrating and possibly bad for your screen.

Hello. Keyboard backlight is not working out of the box.
I modified Giorgos Keramidas's script (https://keramida.wordpress.com/2013/03/28/controlling-the-keyboard-backlight-from-cli/) to handle a stepwise increase/decrease of the backlight.

Here the code:

#!/bin/sh
 
# backlight_get
#       Print current keyboard brightness from UPower to stdout.
backlight_get()
{
    dbus-send --type=method_call --print-reply=literal --system         \
        --dest='org.freedesktop.UPower'                                 \
        '/org/freedesktop/UPower/KbdBacklight'                          \
        'org.freedesktop.UPower.KbdBacklight.GetBrightness'             \
        | awk '{print $2}'
}
 
# backlight_get_max
#       Print the maximum keyboard brightness from UPower to stdout.
backlight_get_max()
{
    dbus-send --type=method_call --print-reply=literal --system       \
        --dest='org.freedesktop.UPower'                               \
        '/org/freedesktop/UPower/KbdBacklight'                        \
        'org.freedesktop.UPower.KbdBacklight.GetMaxBrightness'        \
        | awk '{print $2}'
}
 
# backlight_set NUMBER
#       Set the current backlight brighness to NUMBER, through UPower
backlight_set()
{
    value="$1"
    if test -z "${value}" ; then
        echo "Invalid backlight value ${value}"
    fi
 
    dbus-send --type=method_call --print-reply=literal --system       \
        --dest='org.freedesktop.UPower'                               \
        '/org/freedesktop/UPower/KbdBacklight'                        \
        'org.freedesktop.UPower.KbdBacklight.SetBrightness'           \
        "int32:${value}}"
}
 
# backlight_change [ UP | DOWN | NUMBER ]
#       Change the current backlight value upwards or downwards, or
#       set it to a specific numeric value.
backlight_change()
{
    change="$1"
    if test -z "${change}" ; then
        echo "Invalid backlight change ${change}."                    \
            "Should be 'up' or 'down'." >&2
        return 1
    fi
 
    case ${change} in
    # AMST - manage increase and decrease
    [+-][1234567890]|[[+-][[1234567890][[1234567890]|[[+-][[1234567890][[1234567890][[1234567890])
        current=$( backlight_get )
        max=$( backlight_get_max )
        value=$( expr $((change)) + 0 )
        current_and_value=$( expr ${current} + ${value})
        if test ${current_and_value} -lt 0 ; then
            current_and_value=0
        elif test ${current_and_value} -gt ${max} ; then
            current_and_value=${max}
        fi
        backlight_set "${current_and_value}"
        notify-send -t 800 "Keyboard brightness set to ${current_and_value}"
        ;;

    # AMST - manage max 3 digits input instead of only 2
    # [1234567890]|[[1234567890][[1234567890])
    [1234567890]|[[1234567890][[1234567890]|[[1234567890][[1234567890][[1234567890])
        current=$( backlight_get )
        max=$( backlight_get_max )
        value=$( expr ${change} + 0 )
        if test ${value} -lt 0 || test ${value} -gt ${max} ; then
            echo "Invalid backlight value ${value}."                  \
                "Should be a number between 0 .. ${max}" >&2
            return 1
        else
            backlight_set "${value}"
            notify-send -t 800 "Keyboard brightness set to ${value}"
        fi
        ;;
 
    [uU][pP])
        current=$( backlight_get )
        max=$( backlight_get_max )
        if test "${current}" -lt "${max}" ; then
            value=$(( ${current} + 1 ))
            backlight_set "${value}"
            notify-send -t 800 "Keyboard brightness set to ${value}"
        fi
        ;;
 
    [dD][oO][wW][nN])
        current=$( backlight_get )
        if test "${current}" -gt 0 ; then
            value=$(( ${current}  - 1 ))
            backlight_set "${value}"
            notify-send -t 800 "Keyboard brightness set to ${value}"
        fi
        ;;
 
    *)
        echo "Invalid backlight change ${change}." >&2
        echo "Should be 'up' or 'down' or a number between"           \
            "1 .. $( backlight_get_max )" >&2
        return 1
        ;;
    esac
}
 
if test $# -eq 0 ; then
    current_brightness=$( backlight_get )
    notify-send -t 800 "Keyboard brightness is ${current_brightness}"
else
    # Handle multiple backlight changes, e.g.:
    #   backlight.sh up up down down up
    for change in "$@" ; do
        backlight_change "${change}"
    done
fi

and here the config edited

# increase/decrease keyboard brightness
bindsym XF86KbdBrightnessUp exec backlight +25
bindsym XF86KbdBrightnessDown exec backlight down -25