Test speaker on Linux

-
speaker-test -t wav -c 6
Total page views:

Comments

Post a Comment

Popular posts from this blog

Useful aliases

-
alias ll="ls -lah" alias branch="git branch" alias checkout="git checkout" commit() { echo "Enter commit message (Ctrl+D to finish):" msg=$(cat) git commit -m "$msg" } add() { # Ensure git repo git rev-parse --is-inside-work-tree >/dev/null 2>&1 || return 0 # Colors GREEN="\e[32m" RED="\e[31m" YELLOW="\e[33m" CYAN="\e[36m" BOLD="\e[1m" RESET="\e[0m" local current_branch remote_branch behind local files file answer local added_files=() local skipped_files=() local temp_ignored_files=() local existing_temp_ignored=() current_branch=$(git branch --show-current) # ---------- STEP 0: Check existing temp-ignore files ---------- mapfile -t existing_temp_ignored /dev/null 2>&1 || { echo -e "${RED}Fetch failed.${RESET}" return 1 } behind=$(git rev-list --count HEAD.."$remote_branch" ...
Read more

Create rish shortcut on Home Screen

-
Install  Shizuku  from GitHub (not playstore vesion) Install Termux (Terminal emulator with packages) from F-Droid Install Termux:Widget (Launch Termux commands from the homescreen) from F-Droid  Make sure your Shizuku can be run on boot using Wireless ADB (look up for it) In Shizuku, click "Use Shizuku in terminal apps" Click "Export files" Export anywhere, like in Download/rish  Run Termux Type "termux-setup-storage" Copy both files exported from Shizuku mkdir ~/rish  cp ~/storage/shared/Download/rish/* ~/rish  Edit rish as instruction on Shizuku nano ~/rish/rish Press CTRL + \  Type PKG Press Enter Type com.termux Press Ctrl + O Press Enter Press Ctrl + X Change rish permission chmod +x ~/rish/rish Create shortcuts folder mkdir ~/.shortcuts Create your shortcut file in  .shortcuts folder Example:  To archive and unarchive Macrodroid nano ~/.shortcuts/archive_macrodorid.sh ~/rish/rish -c 'pm archive --user 0 com.arlosoft.macrodroid' Sa...
Read more

Check Change Files in Git

-
You can compare only the files that differ between your current local branch and another branch on the remote using Git. Here are the most common and useful ways, from simplest to more detailed. 1. List only the changed files (most common) git fetch origin git diff --name-only origin/other-branch If you want to be explicit about your current branch: git diff --name-only origin/other-branch..HEAD ➡️ Shows only file paths that are different. 2. List changed files with change type (added / modified / deleted) git diff --name-status origin/other-branch..HEAD Example output: M src/app.js A src/new-file.ts D src/old-file.css 3. Compare against the common ancestor (recommended for PR-style comparison) This avoids noise from changes made in the target branch after you branched. git diff --name-only origin/other-branch...HEAD ... (three dots) means: changes on your branch since it diverged from the other branch This is usually what you want when prepari...
Read more