xdg-go
xdg-ninja
xdg-go | xdg-ninja | |
---|---|---|
4 | 20 | |
591 | 2,184 | |
- | - | |
6.7 | 8.6 | |
13 days ago | 8 days ago | |
Go | Haskell | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
xdg-go
- $Home, Not So Sweet $Home
-
Rob Pike: “Dotfiles” being hidden is a UNIXv2 mistake (2012)
Slight correction here, XDG keys are analogous to Windows standards: https://github.com/adrg/xdg/blob/master/README.md
-
Seeking input on wallpaper utility
Annoyingly enough, while you claim to use XDG_CONFIG_HOME, you're only using $HOME/.config which is what it defaults to but not what the user might have set. Use os.Getenv("XDG_CONFIG_HOME") or similar functions to get the directory that the user have actually set to. You could also just use this package
-
Generic path to Documents folder for every user?
Perhaps use packages like https://github.com/adrg/xdg, that do the magic also for all operating systems.
xdg-ninja
-
Why not export XDG variables?
As a user, these variables make my experience simpler. I'm not going to argue that these specifications should be followed by all, because I know there are many users who are committed to dying on the hill that is their cluttered home directory. However, the existence of these variables is not a deterrent to users who do not want to use the specification, as many applications will want to use your home directory anyway. If the existence of these variables made the specification strictly followed, projects like xdg-ninja (https://github.com/b3nj5m1n/xdg-ninja) would have no reason to exist.
-
$Home, Not So Sweet $Home
Regardagin cargo (and other tools), I've had some success with following suggestions from https://github.com/b3nj5m1n/xdg-ninja
-
Weird Linux benefits, anyone with a similar experience?
It's not as bad as it used to be. And ther's even software that can help you with that: https://github.com/b3nj5m1n/xdg-ninja
-
Home directory
Check out xdg-ninja
-
Use the XDG Base Directory Specification
https://github.com/b3nj5m1n/xdg-ninja
This utility has been a lifesaver to clean up my home directory.
- xdg-ninja - A shell script which checks your $HOME for unwanted files and directories
-
Using the Same Arch Linux Installation for a Decade
Stuff like [xdg-ninja](https://github.com/b3nj5m1n/xdg-ninja) helps but... at one point my home is still a mess.
-
Will dotfiles in home directory (~) be loaded automatically
For the ones that adhere to XDG specs, there are tools that can help transition to using these XDG directories and avoid breaking programs - like XDG Ninja - but it's still a sort of manual process that doesn't cover all dotfiles and applications.
-
Dotfile Madness
There are shell scripts like xdg-ninja that can help with this:
https://github.com/b3nj5m1n/xdg-ninja
-
Clean your home folder ! discover XDG
View on GitHub
What are some alternatives?
Golang-PDF-to-Image-Converter - This project will help you to convert PDF file to IMAGE using golang.
plugin-xdg - Setup xdg environment on Linux.
zb - an opinionated repo based tool for linting, testing and building go source
HomeBrew - 🍺 The missing package manager for macOS (or Linux)
Peanut - 🐺 Deploy Databases and Services Easily for Development and Testing Pipelines.
boxxy - boxxy puts bad Linux applications in a box with only their files.
golang-tutorials - Golang Tutorials. Learn Golang from Scratch with simple examples.
vuizvui - Nix(OS) expressions used by the OpenLab and its members
go-wkhtmltopdf - Go bindings for wkhtmltopdf and high-level HTML to PDF conversion interface
config - Config files for some things.
depth - Visualize Go Dependency Trees
dotfiles - Dotfiles