I’m also on Mastodon as https://hachyderm.io/@BoydStephenSmithJr .

  • 0 Posts
  • 14 Comments
Joined 2 years ago
cake
Cake day: October 2nd, 2023

help-circle

  • bss03@infosec.pubtocats@lemmy.worldHappy Stomp
    link
    fedilink
    English
    arrow-up
    15
    ·
    edit-2
    2 months ago

    “there can be only one” is a common saying from the Highlander series of movies and TV shows, which refers to an in-universe event where “immortals” (they can be killed by decapitation) feel compelled to “the gathering” and slay each other until the last one receives “the gift”.

    The series is named “Highlander” because the protagonist in the first movie, Connor MacLeod, is an immortal from the highlands of Scotland and often called “the highlander” by immortals, since he may be living under a different name (because even in fiction paperwork is a bitch).

    Outside of the series, “highlander” variants of various games exist which impose a limit of a single instance of a card/token/spell/action where the standard rules have a higher limit or no limit.













  • I primarily operate in strict standard compliance mode where I write against the shell specifications in the lastest Single Unix Specification and do not use a she-bang line since including one results in unspecified, implementation-defined behavior. Generally people seem to find this weird and annoying.

    Sometimes I embrace using bash as a scripting language, and use one of the env-based she-bangs. In that case, I go whole-hog on bashisns. While I use zsh as my interactive shell, even I’m not mad enough to try to use it for scripts that need to run in more than one context (like other personal accounts/machines, even).

    In ALL cases, use shellcheck and at least understand the diagnostics reported, even if you opt not to fix them. (I generally modify the script until I get a clean shellcheck run, but that can be quite involved… lists of files are pretty hard to deal with safely, actually.)