mmissoldtw←
HashtagsPublic conversations
PUBLIC CONVERSATIONS

#bash

Read the latest public tweets for a hashtag.

19 tweets on this page for “#bash”

0x99M avatar
0x99M@0x99M·32m

Stop retyping the long path to get back where you were. cd - takes you to the folder you were just in and prints it. Run it again to flip back. The - is OLDPWD: bash updates it each time cd succeeds. ~- is that folder in any command: cp notes.txt ~- #linux #bash

Post attachment
さんまファンクラブ会長 avatar
さんまファンクラブ会長@kaicho_subsub·1h

会長は【HO1 LEADER】 入隊前にあなたの適性をチェックしてみましょう。 #あなたにピッタリの役割を診断します! #trpg #bash #kuizy @bashfirejapanより kuizy.net/analysis/10582/0

ののの🌸 avatar
ののの🌸@zmzmpnt_2·1h

のは【HO2 ACE】 入隊前にあなたの適性をチェックしてみましょう。 #あなたにピッタリの役割を診断します! #trpg #bash #kuizy @ bashfirejapanより ほに珍し kuizy.net/analysis/10582/1

たかだ avatar
たかだ@helle_borus·1h

たかだは【HO4 HOPE】 入隊前にあなたの適性をチェックしてみましょう。 #あなたにピッタリの役割を診断します! #trpg #bash #kuizy @bashfirejapanより kuizy.net/analysis/10582/3 新人引くの珍しい!

おうどん avatar
おうどん@yn_elcielo·2h

Bashのパイプラインは、通常、最後のコマンドの終了状態が全体の結果になる。前段が失敗しても、最後が成功すれば成功扱い。途中の失敗も検知したいなら set -o pipefail。失敗したコマンドのうち右端の終了状態が返る。後ろの係が笑顔でも、厨房の鍋は見ておきたい🍲 #bash

Zion Patricks avatar
Zion Patricks@ZionPatricks·17h

Blind session hijacking requires a little terminal magic. 🪄 Natas19 looked identical to 18, but with zero access to backend source code. All I had was a weird PHPSESSID cookie. Here is how I broke it down using bash. 🧵👇 #bash #linux #offsec #ctf #websecurity

Post attachmentPost attachmentPost attachment
rono mondal avatar
rono mondal@Rono4321Rono·Nov 17

A Bash build can fail while its log pipeline succeeds. Illustrative check: false | tee build.log returns 0 if tee succeeds. Enable set -o pipefail, repeat, then inspect $? immediately: the pipeline returns 1. Make CI check that status. #bash #cicd

Creature Workshop avatar
Creature Workshop@creature_ws·Nov 17

I'm building out a standard library for the development lifecycle in #bash to demonstrate that keeping your code readable and organized is actually important for agentic-coding. One of my favorite parts of it is the #graphql module, which is built on top of the library's HTTP module. I import and use it in my #linear and #gitlab modules for a two-way ticket-sync system the library also handles. All of that's written in bash, and that's just the tip of the iceberg. I didn't even get to the #posix desugaring or the self-sharding, language-agnostic coverage and testing module. And you know what? I'd rather read the bash it's all written in than most #ai-generated #python. I'm not afraid to share my code either. Here's a function from the GraphQL module if you're curious. It's got its bash-related quirks, but otherwise? It reads like a pretty standard web call: - build the request body - make the request (in GraphQL's case it's always POST) - read the result - return it What about you? Can you still read your agent code? Do you think that readability's still important when agents can read the code for you?

Post attachment
Show more tweets