Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Suggestions for Command-outputs and a little issue with WCM

Abierto
  • ¿Algo no está bien?
#261 1 comentario 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
cpp, shell
Área
desktop, tooling

Línea de trabajo

Comienza reproduciendo el comportamiento de WCM al editar las secciones Dock, Panel o Background, e inspecciona cómo se gestiona la configuración de command-output. El bug reportado se consideraría resuelto si las entradas existentes de command-output, incluidos los ejemplos personalizados y la entrada sensors, permanecen intactas; las click-action suggestions requerirían una decisión de alcance independiente.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug enhancement

Hello, I want to touch some questions about the command-outputs, first I want to share these 3 that I have created:

For those who don't get the sound widget working:

# Volume Level using Pamixer
command_output_2 = pamixer --get-volume-human
command_output_tooltip_2 = printf 'Volume Level'
command_output_period_2 = 5
command_output_icon_2 = speaker
command_output_icon_size_2 = 16

For those who use Connman instead of Network Manager I think you will appreciate it, as the Network Widget is only useful for NM. The | grep -v -E '^ Tethering|^ Type' filter in tooltip is for avoid showing tethering parameters and type of connection (because it already prints the name of the device).

# Connection status using Connman and iwconfig
command_output_3 = connmanctl state | grep 'State =' | awk -F'= ' '{print $2}' | sed -e 's/online/ON/' -e 's/offline/OFF/'
command_output_tooltip_3 = connmanctl technologies | grep -v -E '^  Tethering|^  Type' | sed 's|/net/connman/technology/||g'; iwconfig | grep -E 'ESSID|Signal level'
command_output_period_3 = 10
command_output_icon_3 = atmosphere
command_output_icon_size_3 = 16

wttr.in - this shows current weather of your location based on IP, + 3 cities (edit them) and the phase of the moon:

# WTTR.in
command_output_4 = curl -s http://wttr.in/?format=1
command_output_tooltip_4 = curl -s http://wttr.in/?format=4; curl -s 'wttr.in/{Asuncion,Copenhagen,Berlin}?format=4'; printf 'Moon phase: ' & curl -s http://wttr.in/?format=%m
command_output_period_4 = 3600
command_output_icon_4 =

I also have enabled the sensors command-output that comes in the example.
Screenshot_2024-06-09-16 05 30

Having said this:

  1. I want to report a bug with WCM: when I edit any settings in the Dock, Panel or Background section, the command-output I set (the ones above) are deleted from the configuration, except the sensors one, so I always have to have a backup...

  2. I want to offer suggestions, the command-output have a lot of potential, it would be great to add custom actions, either with:
    Left click - right click - middle click - scroll up - scroll down
    So you could do something like the custom/modules of Waybar, in fact, I remember that someone had already tried it some time ago: https://github.com/WayfireWM/wf-shell/pull/86#issue-831108873 but apparently it was not followed up...

If it could be achieved, I could, for example:

  1. In the pamixer widget, left click to open Pavucontrol, right click to mute, scroll up/down to increase/decrease volume.
  2. connman widget, open connman-gtk by left click.
  3. wttr widget, show terminal with weather forecast in my area by left click or show Berlin forecast for example by right click.

Of course, I want to thank @ammen99 for his work and @NamorNiradnug for his great contributions, just what was needed to not depend on Waybar anymore :D

Lenguaje dominante
C++
Estrellas
179
Forks
56
Merge medio
6 d 34 min
PR fusionados (30 d)
3

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de WayfireWM/wf-shell

Todos los issues de WayfireWM/wf-shell

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.