[Source code](https://gist.github.com/sebastiancarlos/2f822a1d1f8e7aad816baded6eb437a4)
```
#!/usr/bin/env bash
# diffc - diff commands
# - allows to call as: diffc 'command one' 'command two'
# instead of: diff <(command one) <(command two)
# (Just to save typing a few characters. Lol I'm a lazy programmer)
function diffc () {
if [[ "$#" != "2" ]]; then
echo "diffc requires two arguments"
return 1
fi
local command=$(printf 'diff <( %s ) <( %s )' "$1" "$2")
echo $command
eval $command
}
# diffh - diff history
# - make a diff of the output of the last two commands in the shell history
function diffh () {
# first one is 2nd to last. second is last
# remove preceeding spaces
local first=$(fc -ln -2 -2)
local second=$(fc -ln -1 -1)
# print and run diff
local command=$(printf 'diff <( %s ) <( %s )' "${first}" "${second}")
echo $command
eval $command
local error_code=$?
# replace this 'diffh' entry in history with the command
history -s "$(echo $command)"
return $error_code
}
```
Among the 15~ million lines of codes in the GCC source code, there is a single CSS line.
Who dares to call CSS bloat now? More like GSS eh.
```
$ cloc gcc-13.2.0
github.com/AlDanial/cloc v 1.98 T=113.87 s (1029.7 files/s, 143776.9 lines/s)
---------------------------------------------------------------------------------------
Language files blank comment code
---------------------------------------------------------------------------------------
C++ 31144 610803 701522 2961450
C 50773 410175 635758 2033424
PO File 44 332336 443572 916826
Ada 6610 290082 396614 831278
Go 5347 102068 191016 769730
...
Brainf*** 1 3 4 10
Lisp 1 4 12 7
DOS Batch 2 0 0 4
CSS 1 0 0 1
---------------------------------------------------------------------------------------
SUM: 117256 2322548 2988111 11061312
---------------------------------------------------------------------------------------
```
Source code: https://gist.github.com/sebastiancarlos/1a5b04099b750f5a15c77c8cb4f03fc8
```
### Sample output:
#
# CREATE_HOME no
# CREATE_MAIL_SPOOL no
# LOG_INIT yes
# USERGROUPS_ENAB yes
# HOME /home
# MAIL_DIR /var/spool/mail
# MAIL_FILE N/A
# SHELL /bin/bash
# SKEL /etc/skel
# EXPIRE N/A
# GROUP 984 (users)
# INACTIVE -1
# PASS_MAX_DAYS 99999
# PASS_MIN_DAYS 0
# PASS_WARN_AGE 7
# UMASK 077
# -------------------------------------------------------------------------------------
# CREATE_HOME: Create a home directory if it does not exist.
# CREATE_MAIL_SPOOL: Create a mailbox file for the user.
# LOG_INIT: Add the user to the lastlog and faillog databases.
# USERGROUPS_ENAB: If set to yes, useradd will create a group with the name of the
# user, and userdel will remove the user's group if it contains no
# more members.
# HOME: The user's name will be affixed to form the new home.
# MAIL_DIR: The mail spool file will be created using this value.
# MAIL_FILE: Same, but relative to the user's home directory.
# SHELL: The user's login shell.
# SKEL: The skeleton directory, which contains files and directories to
# be copied into the user's home directory.
# EXPIRE: The date on which the user account will be disabled, if any.
# GROUP: If USERGROUPS_ENAB is set to no, or if the flag -N/--no-user-group
# is passed, this will be the new user's group.
# INACTIVE: The number of days after a password has expired in which the
# password is still be accepted. -1 disables the inactive period.
# PASS_MAX_DAYS: The number of days a password may be used. If is older, a password
# change will be forced.
# PASS_MIN_DAYS: The minimum number of days allowed between password changes. Any
# attempt sooner will be rejected.
# PASS_WARN_AGE: Warn user N days befere password expiration.
# UMASK: The file mode creation mask is initialized to this value.
```
Thanks! I guess yas-bdsm is more of a minimal, “bring your own compiler” project. You end up with a folder for your dotfiles, and it’s up to you to decide how to put stuff there.
I thought about it but there are two complications here: The code is recursive, and it calls an external shell script. I’m sure there are ways to do that in awk, but I’m not too much of an awk guru, so I decided to leave my awking to self-contained smaller scripts. Also, considering I need to spawn subprocesses anyway for this, Bash wouldn’t be a bad choice since it’s built for that.
Almost every program that we run has access to the environment, so nothing stops them from curling our credentials to some nefarious server.
Why don't we put credentials in files and then pass them to the programs that need them? Maybe coupled with some mechanism that prevents executables from reading any random file except those approved.
just trying to get a good mental model of when it’s reasonable to use tools like awk instead of simpler unix tools. also further confirming that sed is almost never the best tool except for substitutions.
It’s also traditional to eat raw meat, but we discovered fire at some point.