Warning: Support for display of Git notes has been dropped by GitHub: https://github.com/blog/707-git-notes-display
git notes add
git notes add -m "my note"
Warning: Support for display of Git notes has been dropped by GitHub: https://github.com/blog/707-git-notes-display
git notes add
git notes add -m "my note"
| function apt-history() { | |
| local install_date login_user command type changed usage | |
| usage="apt-history - Displays content from /var/log/apt/history* in a table format (similar to yum history)" | |
| if [ $# -gt 0 ] && [[ "$1" == "-h" ]] ; then | |
| echo "$usage" | |
| return 0 | |
| elif [ $# -gt 0 ] ; then | |
| echo "This function does not accept options" | |
| return 1 |
Disclaimer: ChatGPT generated document.
When working with command-line programs, one of the first concepts you encounter is the idea of passing inputs directly to a program at launch. These inputs control behavior, configure execution, or provide data. While many developers casually refer to all such inputs as “flags,” the reality is more nuanced.
This article provides a clear, structured understanding of what these inputs are actually called, how they are categorized, and why the distinctions matter—especially for developers building robust CLI tools.
| { | |
| "title": "Takeout API", | |
| "discoveryVersion": "v1", | |
| "ownerName": "Google", | |
| "version_module": true, | |
| "resources": { | |
| "exports": { | |
| "methods": { | |
| "get": { | |
| "flatPath": "v2/{service}/exports/{exportId}", |
| <?php | |
| function randomPassword( $len = 8, $ucfirst = false, $spchar = false ){ | |
| /* Programmed by Christian Haensel | |
| * christian@chftp.com | |
| * http://www.chftp.com | |
| * | |
| * Exclusively published on weberdev.com. | |
| * If you like my scripts, please let me know or link to me. | |
| * You may copy, redistribute, change and alter my scripts as | |
| * long as this information remains intact. |
| #!/bin/bash | |
| # | |
| # Get basic info about audio / video file (MP4, MP3, WAV, WEBM, ...) by ffprobe | |
| # - Usually you should have ffmpeg on your system, including ffprobe | |
| # - ffprobe gives you MUCH MUCH (MUCH) information | |
| # - this little helper script reduces ffprobe's info hell to typical core information | |
| # - use this script as a template for personal information interests | |
| # - don't get mislead by "-v error" - it means "don't get verbose WITHOUT errors" | |
| # - information is given as JSON for readability & easy automated consumptione |
| #!/usr/bin/env bash | |
| # https://gist.github.com/BobbyRyterski/7a511b96ece47655b17d | |
| # based on http://stackoverflow.com/q/14471692 | |
| readonly BASE62=($(echo {0..9} {a..z} {A..Z})) | |
| base62_encode() { | |
| local out= | |
| for i in $(bc <<< "obase=62; $1"); do |
| MsgBox "here i am again ..." |
| ' | |
| ' function getMacAddressForIpRange | |
| ' | |
| ' Returns the MAC address of the current computer for a given internet (IP) connection, i.e. that of the network adapter with which an IP address out of a given range of IP addresses is connected. The restriction to an IP address range avoids to wrongly retrieve virtual adapters like VirtualBox. Note that technically only the first matching MAC address is returned, assuming that only one connection to the same net exists per machine. | |
| ' | |
| ' !! May not work in virtual machines. | |
| ' | |
| ' @license GPL 2 (http://www.gnu.org/licenses/gpl.html) | |
| ' @author hh.lohmann <hh.lohmann@yahoo.de> | |
| ' @version 2014-02-26 10:15 |