https://github.com/microeinstein/plain-scripts

Curated collection of scripts I have written or discovered in the last few years.
https://github.com/microeinstein/plain-scripts

bash bashrc desktop education http-handlers javascript kde latex linux lua partitioning pipewire prompt proot-distro python tweaks unix virtual-machine x11

Last synced: about 5 hours ago
JSON representation

Curated collection of scripts I have written or discovered in the last few years.

• Host: GitHub
• URL: https://github.com/microeinstein/plain-scripts
• Owner: Microeinstein
• License: mit
• Created: 2023-10-31T16:00:26.000Z (about 1 year ago)
• Default Branch: trunk
• Last Pushed: 2024-08-02T19:57:41.000Z (4 months ago)
• Last Synced: 2024-08-02T22:46:54.684Z (4 months ago)
• Topics: bash, bashrc, desktop, education, http-handlers, javascript, kde, latex, linux, lua, partitioning, pipewire, prompt, proot-distro, python, tweaks, unix, virtual-machine, x11
• Language: Shell
• Homepage:
• Size: 252 KB
• Stars: 3
• Watchers: 2
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: COPYING
  • Code of conduct: CODE_OF_CONDUCT.md

Awesome Lists containing this project

README

        
# Plain scripts

Curated collection of scripts I have written or [discovered](/unix/x64v-check.awk) (rare) in the last few years, most of which are independent standalone programs (no build config, separate files... — hence the "plain"). The monorepo strategy was chosen for this reason, and to avoid maintaining scattered gists and snippets across the web.

## Content

General notes:

- quality, code style and localization will vary significantly from file to file

- system dependencies are not always checked

- most installable scripts will point to `~/.local/scripts` for convention

- some configurations are stored inside the scripts themselves

- some scripts don't even have usage info

For more information, see the README for each respective directory and the source of each script; not all files are documented.

## Download

It's advisable to clone the repository to `~/.local/scripts` (or other locations, and making a symlink right after); I chose it to avoid littering my home or other places intended for different purposes.

### Cloning specific scripts

With the following snippet, it's possible to avoid cloning the entire repository while also keeping your local files synchronized through `git pull`:

```bash

git clone --depth 1 [--branch bb] --no-checkout url

cd repo

for p in "${repo_paths[@]}":

  git sparse-checkout set  "$p"

  git checkout [bb]

```

## Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

## License

[MIT](COPYING)