Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Music <- + Memory usage | Battery fallback=weather #220

Closed
end-4 opened this issue Jan 31, 2024 · 11 comments
Closed

[Feature] Music <- + Memory usage | Battery fallback=weather #220

end-4 opened this issue Jan 31, 2024 · 11 comments

Comments

@end-4
Copy link
Owner

end-4 commented Jan 31, 2024

What would you like to be added?

How will it help

  • Makes left side of bar not too empty
@clsty
Copy link
Collaborator

clsty commented Jan 31, 2024

My personal suggestion:
If ~/.cache/ags/user/barcmd.sh exists, then execute it and show its output every $(cat ~/.cache/ags/user/barcmd-period.txt) (default 5000) miliseconds.

By supporting this, user will be able to custom this area.

And it could be even more powerful:

  • If ~/.cache/ags/user/barcmd-leftclick.sh exists, then execute it when leftclick on it.
  • If ~/.cache/ags/user/barcmd-rightclick.sh exists, then execute it when rightclick on it.
  • ...

@end-4
Copy link
Owner Author

end-4 commented Jan 31, 2024

Thanks for the suggestion
Fine I guess, though I don't really care about that. The point of using ags is to not use polling shell scripts.

@end-4
Copy link
Owner Author

end-4 commented Jan 31, 2024

the way i'll be implementing polls but doesn't need a script, just a command

@clsty
Copy link
Collaborator

clsty commented Feb 2, 2024

About city for weather, as mentioned before, curl ipinfo.io returns a false city as for my test.
I suggest that we could read an environment variable such as $AGS_WEATHER_CITY to override.

@end-4
Copy link
Owner Author

end-4 commented Feb 17, 2024

i forgot to close this

@end-4 end-4 closed this as completed Feb 17, 2024
@clsty
Copy link
Collaborator

clsty commented Feb 17, 2024

My personal suggestion: If ~/.cache/ags/user/barcmd.sh exists, then execute it and show its output every $(cat ~/.cache/ags/user/barcmd-period.txt) (default 5000) miliseconds.

By supporting this, user will be able to custom this area.

And it could be even more powerful:

* If `~/.cache/ags/user/barcmd-leftclick.sh` exists, then execute it when leftclick on it.

* If `~/.cache/ags/user/barcmd-rightclick.sh` exists, then execute it when rightclick on it.

* ...

@end-4 However I still want this one because I'm familiar with bash scripting lol

I will not submit such code to this repo of course, but I want to use it in my own version of config, and I can add document to the wiki on how to do it (or maybe you could add this document).

@end-4
Copy link
Owner Author

end-4 commented Feb 17, 2024

oops then

end-4 added a commit that referenced this issue Feb 27, 2024
end-4 added a commit that referenced this issue Feb 27, 2024
end-4 added a commit that referenced this issue Feb 27, 2024
@end-4
Copy link
Owner Author

end-4 commented Feb 27, 2024

@clsty try it
if you're happy close the issue
and it would be nice if you can add docs too

@clsty
Copy link
Collaborator

clsty commented Feb 27, 2024

Very nice. Would you please allow customed polling period (and default 5000 ms when not customed)?
I suggest to read it from ${GLib.get_home_dir()}/.cache/ags/user/scripts/custom-module-period.txt when it exists, and use 5000 when it does not exists.

@end-4
Copy link
Owner Author

end-4 commented Feb 27, 2024

done

@clsty
Copy link
Collaborator

clsty commented Feb 27, 2024

Thank you very much. I have documented them.

@clsty clsty closed this as completed Feb 27, 2024
end-4 added a commit to Soliprem/dots-hyprland that referenced this issue May 24, 2024
end-4 added a commit to Soliprem/dots-hyprland that referenced this issue May 24, 2024
end-4 added a commit to Soliprem/dots-hyprland that referenced this issue May 24, 2024
end-4 added a commit to Soliprem/dots-hyprland that referenced this issue May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants