home.social

#bash — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #bash, aggregated by home.social.

  1. #Linux #shell ( #bash ) question.
    How do make get such great "shell homepages" with system information when opening a #terminal ?
    Thank you!

  2. #Linux #shell ( #bash ) question.
    How do make get such great "shell homepages" with system information when opening a #terminal ?
    Thank you!

  3. Как ИИ помог автоматизировать контент с помощью Pandoc, bash и пары утилит

    Привет, на связи Влада, веб-специалист ЮMoney. Год назад я рассказывала на Хабре , как контент-менеджеру пригодятся терминал, Git и несколько десятков строк кода. С тех пор многое изменилось. В работе появился ИИ — инструмент, снизивший порог входа в автоматизацию. Не потому, что пишет код вместо нас, а потому, что ускорил создание небольших утилит под наши процессы. Расскажу, как из одного bash-скрипта вырос набор внутренних инструментов для контент-команды. Идеи пригодятся техническим писателям, контент-менеджерам и всем, кто регулярно работает с Markdown, XML и CMS.

    habr.com/ru/companies/yoomoney

    #pandoc #bash #автоматизация #markdown #регулярные_выражения #контентменеджмент #искусственный_интеллект #ai #cms

  4. Как ИИ помог автоматизировать контент с помощью Pandoc, bash и пары утилит

    Привет, на связи Влада, веб-специалист ЮMoney. Год назад я рассказывала на Хабре , как контент-менеджеру пригодятся терминал, Git и несколько десятков строк кода. С тех пор многое изменилось. В работе появился ИИ — инструмент, снизивший порог входа в автоматизацию. Не потому, что пишет код вместо нас, а потому, что ускорил создание небольших утилит под наши процессы. Расскажу, как из одного bash-скрипта вырос набор внутренних инструментов для контент-команды. Идеи пригодятся техническим писателям, контент-менеджерам и всем, кто регулярно работает с Markdown, XML и CMS.

    habr.com/ru/companies/yoomoney

    #pandoc #bash #автоматизация #markdown #регулярные_выражения #контентменеджмент #искусственный_интеллект #ai #cms

  5. Как ИИ помог автоматизировать контент с помощью Pandoc, bash и пары утилит

    Привет, на связи Влада, веб-специалист ЮMoney. Год назад я рассказывала на Хабре , как контент-менеджеру пригодятся терминал, Git и несколько десятков строк кода. С тех пор многое изменилось. В работе появился ИИ — инструмент, снизивший порог входа в автоматизацию. Не потому, что пишет код вместо нас, а потому, что ускорил создание небольших утилит под наши процессы. Расскажу, как из одного bash-скрипта вырос набор внутренних инструментов для контент-команды. Идеи пригодятся техническим писателям, контент-менеджерам и всем, кто регулярно работает с Markdown, XML и CMS.

    habr.com/ru/companies/yoomoney

    #pandoc #bash #автоматизация #markdown #регулярные_выражения #контентменеджмент #искусственный_интеллект #ai #cms

  6. kitfucoda.medium.com/orchestra

    Why do we always assume a simple shell script is enough to fix a flaky command-line tool? It starts as a quick automation experiment. But as the feature wishlist inevitably grows, so does the complexity of your code. Before you know it, you are asking a basic scripting language to handle time-sensitive guards, conditional retry loops, and external user interactions.

    That is how my humble Bash script ended up spawning subshells, tracking process IDs, and trapping SIGTERM just to handle a 2FA prompt timeout on my phone. The script spent half its lines deciding how to exit gracefully, quickly devolving into cryptic gibberish that even my LLM chatbot couldn't comprehend. That was the breaking point where I realized: I need a proper programming language.

    Rebuilding the script in Python with asyncio turned out to be an absolute breeze. Thanks to asyncio’s non-blocking event loop, managing timeouts, cleanly forwarding data to stdin during authentication, and gracefully catching shutdown signals became elegant, simple, and incredibly readable. It completely bypassed the need to fiddle with complex cross-process message passing.

    Sometimes, keeping personal scripts intentionally crude and un-tested is perfectly fine—so long as they remain structurally sound and readable. If you have been wrestling with complex, brittle process orchestration in Bash, this is your sign to let asyncio save your sanity. Read the full article for a breakdown of the code snippets!

  7. kitfucoda.medium.com/orchestra

    Why do we always assume a simple shell script is enough to fix a flaky command-line tool? It starts as a quick automation experiment. But as the feature wishlist inevitably grows, so does the complexity of your code. Before you know it, you are asking a basic scripting language to handle time-sensitive guards, conditional retry loops, and external user interactions.

    That is how my humble Bash script ended up spawning subshells, tracking process IDs, and trapping SIGTERM just to handle a 2FA prompt timeout on my phone. The script spent half its lines deciding how to exit gracefully, quickly devolving into cryptic gibberish that even my LLM chatbot couldn't comprehend. That was the breaking point where I realized: I need a proper programming language.

    Rebuilding the script in Python with asyncio turned out to be an absolute breeze. Thanks to asyncio’s non-blocking event loop, managing timeouts, cleanly forwarding data to stdin during authentication, and gracefully catching shutdown signals became elegant, simple, and incredibly readable. It completely bypassed the need to fiddle with complex cross-process message passing.

    Sometimes, keeping personal scripts intentionally crude and un-tested is perfectly fine—so long as they remain structurally sound and readable. If you have been wrestling with complex, brittle process orchestration in Bash, this is your sign to let asyncio save your sanity. Read the full article for a breakdown of the code snippets!

    #Python #AsyncIO #SoftwareDevelopment #Bash #Automation #DeveloperLife #CodingHumor #Nix

  8. kitfucoda.medium.com/orchestra

    Why do we always assume a simple shell script is enough to fix a flaky command-line tool? It starts as a quick automation experiment. But as the feature wishlist inevitably grows, so does the complexity of your code. Before you know it, you are asking a basic scripting language to handle time-sensitive guards, conditional retry loops, and external user interactions.

    That is how my humble Bash script ended up spawning subshells, tracking process IDs, and trapping SIGTERM just to handle a 2FA prompt timeout on my phone. The script spent half its lines deciding how to exit gracefully, quickly devolving into cryptic gibberish that even my LLM chatbot couldn't comprehend. That was the breaking point where I realized: I need a proper programming language.

    Rebuilding the script in Python with asyncio turned out to be an absolute breeze. Thanks to asyncio’s non-blocking event loop, managing timeouts, cleanly forwarding data to stdin during authentication, and gracefully catching shutdown signals became elegant, simple, and incredibly readable. It completely bypassed the need to fiddle with complex cross-process message passing.

    Sometimes, keeping personal scripts intentionally crude and un-tested is perfectly fine—so long as they remain structurally sound and readable. If you have been wrestling with complex, brittle process orchestration in Bash, this is your sign to let asyncio save your sanity. Read the full article for a breakdown of the code snippets!

    #Python #AsyncIO #SoftwareDevelopment #Bash #Automation #DeveloperLife #CodingHumor #Nix

  9. kitfucoda.medium.com/orchestra

    Why do we always assume a simple shell script is enough to fix a flaky command-line tool? It starts as a quick automation experiment. But as the feature wishlist inevitably grows, so does the complexity of your code. Before you know it, you are asking a basic scripting language to handle time-sensitive guards, conditional retry loops, and external user interactions.

    That is how my humble Bash script ended up spawning subshells, tracking process IDs, and trapping SIGTERM just to handle a 2FA prompt timeout on my phone. The script spent half its lines deciding how to exit gracefully, quickly devolving into cryptic gibberish that even my LLM chatbot couldn't comprehend. That was the breaking point where I realized: I need a proper programming language.

    Rebuilding the script in Python with asyncio turned out to be an absolute breeze. Thanks to asyncio’s non-blocking event loop, managing timeouts, cleanly forwarding data to stdin during authentication, and gracefully catching shutdown signals became elegant, simple, and incredibly readable. It completely bypassed the need to fiddle with complex cross-process message passing.

    Sometimes, keeping personal scripts intentionally crude and un-tested is perfectly fine—so long as they remain structurally sound and readable. If you have been wrestling with complex, brittle process orchestration in Bash, this is your sign to let asyncio save your sanity. Read the full article for a breakdown of the code snippets!

    #Python #AsyncIO #SoftwareDevelopment #Bash #Automation #DeveloperLife #CodingHumor #Nix

  10. kitfucoda.medium.com/orchestra

    Why do we always assume a simple shell script is enough to fix a flaky command-line tool? It starts as a quick automation experiment. But as the feature wishlist inevitably grows, so does the complexity of your code. Before you know it, you are asking a basic scripting language to handle time-sensitive guards, conditional retry loops, and external user interactions.

    That is how my humble Bash script ended up spawning subshells, tracking process IDs, and trapping SIGTERM just to handle a 2FA prompt timeout on my phone. The script spent half its lines deciding how to exit gracefully, quickly devolving into cryptic gibberish that even my LLM chatbot couldn't comprehend. That was the breaking point where I realized: I need a proper programming language.

    Rebuilding the script in Python with asyncio turned out to be an absolute breeze. Thanks to asyncio’s non-blocking event loop, managing timeouts, cleanly forwarding data to stdin during authentication, and gracefully catching shutdown signals became elegant, simple, and incredibly readable. It completely bypassed the need to fiddle with complex cross-process message passing.

    Sometimes, keeping personal scripts intentionally crude and un-tested is perfectly fine—so long as they remain structurally sound and readable. If you have been wrestling with complex, brittle process orchestration in Bash, this is your sign to let asyncio save your sanity. Read the full article for a breakdown of the code snippets!

    #Python #AsyncIO #SoftwareDevelopment #Bash #Automation #DeveloperLife #CodingHumor #Nix

  11. Kernel Installation Script

    📅 July 15, 2026 Given how the latest Ubuntu mainline kernels now seem to need the added step of manually running update-initramfs, here is a Bash script to simplify the process.

    Archive: ia: https://s.faithcollapsing....

    #bash #linux
    delightlylinux.wordpress.com/2

  12. Kernel Installation Script

    📅 July 15, 2026 Given how the latest Ubuntu mainline kernels now seem to need the added step of manually running update-initramfs, here is a Bash script to simplify the process.

    Archive: ia: https://s.faithcollapsing....

    #bash #linux
    delightlylinux.wordpress.com/2

  13. Since I re-image my Linux desktop so often, I have given a great deal of thought to preserving and re-creating my configurations.

    So I wrote a single bash file to rule them all, sort of.

    My script, `dot`, creates a tiny CLI Ansible installation, and interactively helps write a short Ansible playbook that defines symlinks, install scripts and Python environments.

    I download the script and run `./dot --help` to get started. Use `dot check` to review selections, and `dot apply` to ensure localhost is configured with them.

    Because it uses Ansible under the hood, it doesn't do unecessary work, it provides detailed output, and it creates a file with a full definition of the configuration in a well know standard (which can always be re-used later, even without my script.)

    If you add `dot` to your own `dotfiles` repository, and organize yours like mine (`files`, `installs` and `reqs`) then `dot` will use find your folders and offer to link your files, run your install scripts, or create your Python environments.

    codeberg.org/EdTheDev/dotfiles

    #linux #macos #bash #cli #localhost #config #ansible

  14. Since I re-image my Linux desktop so often, I have given a great deal of thought to preserving and re-creating my configurations.

    So I wrote a single bash file to rule them all, sort of.

    My script, `dot`, creates a tiny CLI Ansible installation, and interactively helps write a short Ansible playbook that defines symlinks, install scripts and Python environments.

    I download the script and run `./dot --help` to get started. Use `dot check` to review selections, and `dot apply` to ensure localhost is configured with them.

    Because it uses Ansible under the hood, it doesn't do unecessary work, it provides detailed output, and it creates a file with a full definition of the configuration in a well know standard (which can always be re-used later, even without my script.)

    If you add `dot` to your own `dotfiles` repository, and organize yours like mine (`files`, `installs` and `reqs`) then `dot` will use find your folders and offer to link your files, run your install scripts, or create your Python environments.

    codeberg.org/EdTheDev/dotfiles

    #linux #macos #bash #cli #localhost #config #ansible

  15. Since I re-image my Linux desktop so often, I have given a great deal of thought to preserving and re-creating my configurations.

    So I wrote a single bash file to rule them all, sort of.

    My script, `dot`, creates a tiny CLI Ansible installation, and interactively helps write a short Ansible playbook that defines symlinks, install scripts and Python environments.

    I download the script and run `./dot --help` to get started. Use `dot check` to review selections, and `dot apply` to ensure localhost is configured with them.

    Because it uses Ansible under the hood, it doesn't do unecessary work, it provides detailed output, and it creates a file with a full definition of the configuration in a well know standard (which can always be re-used later, even without my script.)

    If you add `dot` to your own `dotfiles` repository, and organize yours like mine (`files`, `installs` and `reqs`) then `dot` will use find your folders and offer to link your files, run your install scripts, or create your Python environments.

    codeberg.org/EdTheDev/dotfiles

    #linux #macos #bash #cli #localhost #config #ansible

  16. Since I re-image my Linux desktop so often, I have given a great deal of thought to preserving and re-creating my configurations.

    So I wrote a single bash file to rule them all, sort of.

    My script, `dot`, creates a tiny CLI Ansible installation, and interactively helps write a short Ansible playbook that defines symlinks, install scripts and Python environments.

    I download the script and run `./dot --help` to get started. Use `dot check` to review selections, and `dot apply` to ensure localhost is configured with them.

    Because it uses Ansible under the hood, it doesn't do unecessary work, it provides detailed output, and it creates a file with a full definition of the configuration in a well know standard (which can always be re-used later, even without my script.)

    If you add `dot` to your own `dotfiles` repository, and organize yours like mine (`files`, `installs` and `reqs`) then `dot` will use find your folders and offer to link your files, run your install scripts, or create your Python environments.

    codeberg.org/EdTheDev/dotfiles

    #linux #macos #bash #cli #localhost #config #ansible

  17. Since I re-image my Linux desktop so often, I have given a great deal of thought to preserving and re-creating my configurations.

    So I wrote a single bash file to rule them all, sort of.

    My script, `dot`, creates a tiny CLI Ansible installation, and interactively helps write a short Ansible playbook that defines symlinks, install scripts and Python environments.

    I download the script and run `./dot --help` to get started. Use `dot check` to review selections, and `dot apply` to ensure localhost is configured with them.

    Because it uses Ansible under the hood, it doesn't do unecessary work, it provides detailed output, and it creates a file with a full definition of the configuration in a well know standard (which can always be re-used later, even without my script.)

    If you add `dot` to your own `dotfiles` repository, and organize yours like mine (`files`, `installs` and `reqs`) then `dot` will use find your folders and offer to link your files, run your install scripts, or create your Python environments.

    codeberg.org/EdTheDev/dotfiles

    #linux #macos #bash #cli #localhost #config #ansible

  18. #Linux #Bash #ASCII Art
    Starwars IV für die Konsole (KDE)

    Man kann das mit Telnet gucken. Viele halten telnet für ein Sicherheitsrisiko und installieren das nicht.
    telnet towel.blinkenlights.nl

    Mit Netcat:
    nc towel.blinkenlights.nl 23

    oder Terminaleinstellung + Netcat
    stty -icanon && nc towel.blinkenlights.nl 23

    funktioniert das bei mir aber auch prima
    gist.github.com/dewomser/5a93d

  19. #Linux #Bash #ASCII Art
    Starwars IV für die Konsole (KDE)

    Man kann das mit Telnet gucken. Viele halten telnet für ein Sicherheitsrisiko und installieren das nicht.
    telnet towel.blinkenlights.nl

    Mit Netcat:
    nc towel.blinkenlights.nl 23

    oder Terminaleinstellung + Netcat
    stty -icanon && nc towel.blinkenlights.nl 23

    funktioniert das bei mir aber auch prima
    gist.github.com/dewomser/5a93d

  20. Tracklisten per Subsonic importieren

    Ich kann jetzt beliebige Playlisten mit meiner Musiksammlung in der Nextcloud abgleichen und daraus richtige Playlisten per Subsonic erstellen lassen. Ganz nebenbei war das eine Zeitreise in die Geschichte der Kieler Club-Kultur - aber dazu später mehr. Content Warning: Vibe Coding […]

    kaffeeringe.de/2026/07/17/next

  21. Tracklisten per Subsonic importieren

    Ich kann jetzt beliebige Playlisten mit meiner Musiksammlung in der Nextcloud abgleichen und daraus richtige Playlisten per Subsonic erstellen lassen. Ganz nebenbei war das eine Zeitreise in die Geschichte der Kieler Club-Kultur - aber dazu später mehr. Content Warning: Vibe Coding […]

    kaffeeringe.de/2026/07/17/next

  22. Tracklisten per Subsonic importieren

    Ich kann jetzt beliebige Playlisten mit meiner Musiksammlung in der Nextcloud abgleichen und daraus richtige Playlisten per Subsonic erstellen lassen. Ganz nebenbei war das eine Zeitreise in die Geschichte der Kieler Club-Kultur - aber dazu später mehr. Content Warning: Vibe Coding […]

    kaffeeringe.de/2026/07/17/next

  23. Tracklisten per Subsonic importieren

    Ich kann jetzt beliebige Playlisten mit meiner Musiksammlung in der Nextcloud abgleichen und daraus richtige Playlisten per Subsonic erstellen lassen. Ganz nebenbei war das eine Zeitreise in die Geschichte der Kieler Club-Kultur - aber dazu später mehr. Content Warning: Vibe Coding […]

    kaffeeringe.de/2026/07/17/next

  24. Tracklisten per Subsonic importieren

    Ich kann jetzt beliebige Playlisten mit meiner Musiksammlung in der Nextcloud abgleichen und daraus richtige Playlisten per Subsonic erstellen lassen. Ganz nebenbei war das eine Zeitreise in die Geschichte der Kieler Club-Kultur - aber dazu später mehr. Content Warning: Vibe Coding […]

    kaffeeringe.de/2026/07/17/next

  25. I often get frustrated when copy-pasting commands from a website into my Nushell terminal, especially with those line-escaping backslashes...

    Here is a little snippet I found to solve that issue.

    Read more on my blog: moskitohero.com/post/2026-07-1

    #nushell #bash #shell #snippet

  26. I often get frustrated when copy-pasting commands from a website into my Nushell terminal, especially with those line-escaping backslashes...

    Here is a little snippet I found to solve that issue.

    Read more on my blog: moskitohero.com/post/2026-07-1

    #nushell #bash #shell #snippet

  27. #Linux #Bash Kommando
    Wenn der Akku vom Notebook immer auf 100% lädt.
    Bei mir hats geholfen. Huawei Matebook D14 / Manjaro Linux
    gist.github.com/dewomser/4a2c6

  28. #Linux #Bash Kommando
    Wenn der Akku vom Notebook immer auf 100% lädt.
    Bei mir hats geholfen. Huawei Matebook D14 / Manjaro Linux
    gist.github.com/dewomser/4a2c6

  29. #Linux #Bash
    Gestern hab ich gezeigt wie man ein Backup von seinen Github Repositorys macht.
    Ein 1-Zeiler der funktioniert

    Heute zeige ich wie man Ein Github #Gist #Backup machen lässt mittels AI-Prompt
    Es ist eine Codekatastrophe aber funktioniert.
    gist.github.com/dewomser/9e7d2

  30. #Linux #Bash
    Gestern hab ich gezeigt wie man ein Backup von seinen Github Repositorys macht.
    Ein 1-Zeiler der funktioniert

    Heute zeige ich wie man Ein Github #Gist #Backup machen lässt mittels AI-Prompt
    Es ist eine Codekatastrophe aber funktioniert.
    gist.github.com/dewomser/9e7d2

  31. #Linux #Bash
    Gestern hab ich gezeigt wie man ein Backup von seinen Github Repositorys macht.
    Ein 1-Zeiler der funktioniert

    Heute zeige ich wie man Ein Github #Gist #Backup machen lässt mittels AI-Prompt
    Es ist eine Codekatastrophe aber funktioniert.
    gist.github.com/dewomser/9e7d2

  32. #Linux #Bash
    Gestern hab ich gezeigt wie man ein Backup von seinen Github Repositorys macht.
    Ein 1-Zeiler der funktioniert

    Heute zeige ich wie man Ein Github #Gist #Backup machen lässt mittels AI-Prompt
    Es ist eine Codekatastrophe aber funktioniert.
    gist.github.com/dewomser/9e7d2

  33. #Linux #Bash
    Gestern hab ich gezeigt wie man ein Backup von seinen Github Repositorys macht.
    Ein 1-Zeiler der funktioniert

    Heute zeige ich wie man Ein Github #Gist #Backup machen lässt mittels AI-Prompt
    Es ist eine Codekatastrophe aber funktioniert.
    gist.github.com/dewomser/9e7d2

  34. Meteorology Kwamalasemutu

    Current weather in Kwamalasemutu SR SA with mighty power of wttr.in & the grace of lolcat(6) 🏳️‍🌈 wttr curl(1) & {ba{c{k{z{fi}}}}}sh

    Background photograph is my Clouds in FL colours scene_03 composed with CIRC_POL 81A FL and UV filters chronologically stacked using a Nikon ASLR lens combo

    log

    $ curl --verbose wttr.in/kwamalasemutu|lolcat
    % Total % Received % Xferd Average Speed Time Time Time Current
    Dload Upload Total Spent Left Speed
    0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Host wttr.in:80 was resolved.

    • IPv6: (none)
    • IPv4: 5.9.243.187
    • Trying 5.9.243.187:80...
    • Connected to wttr.in (5.9.243.187) port 80
    • using HTTP/1.x> GET /kwamalasemutu HTTP/1.1> Host: wttr.in> User-Agent: curl/8.14.1> Accept: />
    • Request completely sent off< HTTP/1.1 200 OK< Access-Control-Allow-Origin: *< Cache-Control: public, max-age=600< Content-Type: text/plain; charset=utf-8< Date: Wed, 15 Jul 2026 05:12:30 GMT< Transfer-Encoding: chunked< { [1195 bytes data]1e00 8612 0 8612 m0 0 15775 u 0 --:--:-- --t:--:-- --:--:-- 15772
    • Connection #0 to host wttr.in left intact
      u

      \ / Clear
      .-. +22(17) °C
      ― ( ) ― ← 5 km/h
      `-’ 10 km
      / \ 0.0 mm

    Location: Kwamalasemutu, Coeroeni, Sipaliwini, Suriname [2.3554503,-56.787836]

    Note:

    Remember to repeat the request with an interval of 8 then 56 secs when the server sends and empty response to curl

    Watch the LOG!

    API

    wttr.in

    en.wikipedia.org/wiki/Bash_(Un

    gnu.org

    directory.fsf.org/wiki/Bash

    curl.se/

    github.com/busyloop/lolcat

    Z

    #Weather #wttr #lolcat #curl #bash #csk #ksh #zsh #sh #fish #meteorology #environment #Physics #Chemistry #Mathematics #Lineair #algebra #technology #OpenSource #programming #POSIX

  35. Meteorology Kwamalasemutu

    Current weather in Kwamalasemutu SR SA with mighty power of wttr.in & the grace of lolcat(6) 🏳️‍🌈 wttr curl(1) & {ba{c{k{z{fi}}}}}sh

    Background photograph is my Clouds in FL colours scene_03 composed with CIRC_POL 81A FL and UV filters chronologically stacked using a Nikon ASLR lens combo

    log

    $ curl --verbose wttr.in/kwamalasemutu|lolcat
    % Total % Received % Xferd Average Speed Time Time Time Current
    Dload Upload Total Spent Left Speed
    0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Host wttr.in:80 was resolved.

    • IPv6: (none)
    • IPv4: 5.9.243.187
    • Trying 5.9.243.187:80...
    • Connected to wttr.in (5.9.243.187) port 80
    • using HTTP/1.x> GET /kwamalasemutu HTTP/1.1> Host: wttr.in> User-Agent: curl/8.14.1> Accept: />
    • Request completely sent off< HTTP/1.1 200 OK< Access-Control-Allow-Origin: *< Cache-Control: public, max-age=600< Content-Type: text/plain; charset=utf-8< Date: Wed, 15 Jul 2026 05:12:30 GMT< Transfer-Encoding: chunked< { [1195 bytes data]1e00 8612 0 8612 m0 0 15775 u 0 --:--:-- --t:--:-- --:--:-- 15772
    • Connection #0 to host wttr.in left intact
      u

      \ / Clear
      .-. +22(17) °C
      ― ( ) ― ← 5 km/h
      `-’ 10 km
      / \ 0.0 mm

    Location: Kwamalasemutu, Coeroeni, Sipaliwini, Suriname [2.3554503,-56.787836]

    Note:

    Remember to repeat the request with an interval of 8 then 56 secs when the server sends and empty response to curl

    Watch the LOG!

    API

    wttr.in

    en.wikipedia.org/wiki/Bash_(Un

    gnu.org

    directory.fsf.org/wiki/Bash

    curl.se/

    github.com/busyloop/lolcat

    Z

    #Weather #wttr #lolcat #curl #bash #csk #ksh #zsh #sh #fish #meteorology #environment #Physics #Chemistry #Mathematics #Lineair #algebra #technology #OpenSource #programming #POSIX

  36. Meteorology Kwamalasemutu

    Current weather in Kwamalasemutu SR SA with mighty power of wttr.in & the grace of lolcat(6) 🏳️‍🌈 wttr curl(1) & {ba{c{k{z{fi}}}}}sh

    Background photograph is my Clouds in FL colours scene_03 composed with CIRC_POL 81A FL and UV filters chronologically stacked using a Nikon ASLR lens combo

    log

    $ curl --verbose wttr.in/kwamalasemutu|lolcat
    % Total % Received % Xferd Average Speed Time Time Time Current
    Dload Upload Total Spent Left Speed
    0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Host wttr.in:80 was resolved.

    • IPv6: (none)
    • IPv4: 5.9.243.187
    • Trying 5.9.243.187:80...
    • Connected to wttr.in (5.9.243.187) port 80
    • using HTTP/1.x> GET /kwamalasemutu HTTP/1.1> Host: wttr.in> User-Agent: curl/8.14.1> Accept: />
    • Request completely sent off< HTTP/1.1 200 OK< Access-Control-Allow-Origin: *< Cache-Control: public, max-age=600< Content-Type: text/plain; charset=utf-8< Date: Wed, 15 Jul 2026 05:12:30 GMT< Transfer-Encoding: chunked< { [1195 bytes data]1e00 8612 0 8612 m0 0 15775 u 0 --:--:-- --t:--:-- --:--:-- 15772
    • Connection #0 to host wttr.in left intact
      u

      \ / Clear
      .-. +22(17) °C
      ― ( ) ― ← 5 km/h
      `-’ 10 km
      / \ 0.0 mm

    Location: Kwamalasemutu, Coeroeni, Sipaliwini, Suriname [2.3554503,-56.787836]

    Note:

    Remember to repeat the request with an interval of 8 then 56 secs when the server sends and empty response to curl

    Watch the LOG!

    API

    wttr.in

    en.wikipedia.org/wiki/Bash_(Un

    gnu.org

    directory.fsf.org/wiki/Bash

    curl.se/

    github.com/busyloop/lolcat

    Z

    #Weather #wttr #lolcat #curl #bash #csk #ksh #zsh #sh #fish #meteorology #environment #Physics #Chemistry #Mathematics #Lineair #algebra #technology #OpenSource #programming #POSIX

  37. Meteorology Kwamalasemutu

    Current weather in Kwamalasemutu SR SA with mighty power of wttr.in & the grace of lolcat(6) 🏳️‍🌈 wttr curl(1) & {ba{c{k{z{fi}}}}}sh

    Background photograph is my Clouds in FL colours scene_03 composed with CIRC_POL 81A FL and UV filters chronologically stacked using a Nikon ASLR lens combo

    log

    $ curl --verbose wttr.in/kwamalasemutu|lolcat
    % Total % Received % Xferd Average Speed Time Time Time Current
    Dload Upload Total Spent Left Speed
    0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Host wttr.in:80 was resolved.

    • IPv6: (none)
    • IPv4: 5.9.243.187
    • Trying 5.9.243.187:80...
    • Connected to wttr.in (5.9.243.187) port 80
    • using HTTP/1.x> GET /kwamalasemutu HTTP/1.1> Host: wttr.in> User-Agent: curl/8.14.1> Accept: />
    • Request completely sent off< HTTP/1.1 200 OK< Access-Control-Allow-Origin: *< Cache-Control: public, max-age=600< Content-Type: text/plain; charset=utf-8< Date: Wed, 15 Jul 2026 05:12:30 GMT< Transfer-Encoding: chunked< { [1195 bytes data]1e00 8612 0 8612 m0 0 15775 u 0 --:--:-- --t:--:-- --:--:-- 15772
    • Connection #0 to host wttr.in left intact
      u

      \ / Clear
      .-. +22(17) °C
      ― ( ) ― ← 5 km/h
      `-’ 10 km
      / \ 0.0 mm

    Location: Kwamalasemutu, Coeroeni, Sipaliwini, Suriname [2.3554503,-56.787836]

    Note:

    Remember to repeat the request with an interval of 8 then 56 secs when the server sends and empty response to curl

    Watch the LOG!

    API

    wttr.in

    en.wikipedia.org/wiki/Bash_(Un

    gnu.org

    directory.fsf.org/wiki/Bash

    curl.se/

    github.com/busyloop/lolcat

    Z

    #Weather #wttr #lolcat #curl #bash #csk #ksh #zsh #sh #fish #meteorology #environment #Physics #Chemistry #Mathematics #Lineair #algebra #technology #OpenSource #programming #POSIX

  38. Meteorology Kwamalasemutu

    Current weather in Kwamalasemutu SR SA with mighty power of wttr.in & the grace of lolcat(6) 🏳️‍🌈 wttr curl(1) & {ba{c{k{z{fi}}}}}sh

    Background photograph is my Clouds in FL colours scene_03 composed with CIRC_POL 81A FL and UV filters chronologically stacked using a Nikon ASLR lens combo

    log

    $ curl --verbose wttr.in/kwamalasemutu|lolcat
    % Total % Received % Xferd Average Speed Time Time Time Current
    Dload Upload Total Spent Left Speed
    0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Host wttr.in:80 was resolved.

    • IPv6: (none)
    • IPv4: 5.9.243.187
    • Trying 5.9.243.187:80...
    • Connected to wttr.in (5.9.243.187) port 80
    • using HTTP/1.x> GET /kwamalasemutu HTTP/1.1> Host: wttr.in> User-Agent: curl/8.14.1> Accept: />
    • Request completely sent off< HTTP/1.1 200 OK< Access-Control-Allow-Origin: *< Cache-Control: public, max-age=600< Content-Type: text/plain; charset=utf-8< Date: Wed, 15 Jul 2026 05:12:30 GMT< Transfer-Encoding: chunked< { [1195 bytes data]1e00 8612 0 8612 m0 0 15775 u 0 --:--:-- --t:--:-- --:--:-- 15772
    • Connection #0 to host wttr.in left intact
      u

      \ / Clear
      .-. +22(17) °C
      ― ( ) ― ← 5 km/h
      `-’ 10 km
      / \ 0.0 mm

    Location: Kwamalasemutu, Coeroeni, Sipaliwini, Suriname [2.3554503,-56.787836]

    Note:

    Remember to repeat the request with an interval of 8 then 56 secs when the server sends and empty response to curl

    Watch the LOG!

    API

    wttr.in

    en.wikipedia.org/wiki/Bash_(Un

    gnu.org

    directory.fsf.org/wiki/Bash

    curl.se/

    github.com/busyloop/lolcat

    Z

    #Weather #wttr #lolcat #curl #bash #csk #ksh #zsh #sh #fish #meteorology #environment #Physics #Chemistry #Mathematics #Lineair #algebra #technology #OpenSource #programming #POSIX

  39. Was mir immer wieder bei diversen Tutorials auffällt: "In #Linux kann man Programmnamen mit Tab-Tab ergänzen" und ähnliches.
    Das ist eine unzulässige Vermischung. Die #bash ist nur eine unter vielen Shells. Sie läuft nicht nur unter Linux.
    Ein Sex-Ratgeber, der nur die Missionarsstellung behandelt, wäre genauso einseitig.
  40. Was mir immer wieder bei diversen Tutorials auffällt: "In #Linux kann man Programmnamen mit Tab-Tab ergänzen" und ähnliches.
    Das ist eine unzulässige Vermischung. Die #bash ist nur eine unter vielen Shells. Sie läuft nicht nur unter Linux.
    Ein Sex-Ratgeber, der nur die Missionarsstellung behandelt, wäre genauso einseitig.
  41. #Linux #Bash
    Eigene Github Repositorys komplett downloaden und einen Tarball draus machen. Skript ist eigentlich nur ein 1-Zeiler
    gist.github.com/dewomser/8b5e0