Skip to content

Instantly share code, notes, and snippets.

View Applicafroguy's full-sized avatar
🏠
Working from home

Sivuyile Magutywa Applicafroguy

🏠
Working from home
View GitHub Profile
@Applicafroguy
Applicafroguy / clean-up-arch-linux.md
Created March 20, 2023 13:03 — forked from rumansaleem/clean-up-arch-linux.md
Instructions to clean up Arch Linux (Manjaro)

Contents

  • Clean pkg cache
  • Remove unused packages (orphans)
  • Clean cache in /home
  • remove old config files
  • Find and Remove
    • duplicates
    • empty files
    • empty directories
  • broken symlinks
@Applicafroguy
Applicafroguy / clean-up-arch-linux.md
Created March 20, 2023 13:03 — forked from rumansaleem/clean-up-arch-linux.md
Instructions to clean up Arch Linux (Manjaro)

Contents

  • Clean pkg cache
  • Remove unused packages (orphans)
  • Clean cache in /home
  • remove old config files
  • Find and Remove
    • duplicates
    • empty files
    • empty directories
  • broken symlinks
@Applicafroguy
Applicafroguy / README.md
Created April 22, 2016 00:55 — forked from jxson/README.md
README.md template

Synopsis

At the top of the file there should be a short introduction and/ or overview that explains what the project is. This description should match descriptions added for package managers (Gemspec, package.json, etc.)

Code Example

Show what the library does as concisely as possible, developers should be able to figure out how your project solves their problem by looking at the code example. Make sure the API you are showing off is obvious, and that your code is short and concise.

Motivation