[$] Highlights from systemd v258: part two
Systemd\
v258 was released on September 17 after more than nine months
of development. LWN has already covered some of the
features and changes being readied for v258 before it was final. Now
that the release is out, it is time to look at more of what came in
v258, including a sandbox shell, new boot options, service-level disk
quotas, and enhancements to systemd-resolved. ⌘ Read more

I’ve got a prototype of my hardcopy simulator going. I’m typing on the keyboard and the “display” goes to the printer:

https://movq.de/v/56feb53912/s.png

https://movq.de/v/235c1eabac/MVI_8810.MOV.mp4

The biiiiiiiiiig problem is that the print head and plastic cover make it impossible to see what’s currently being printed, because this is not a typewriter. This means: In order to see what I just entered, I have to feed the paper back and forth and back and forth … it’s not ideal.

I got that idea of moving back/forth from Drew DeVault, who – as it turned out – did something similar a few years back. (I tried hard to read as little as possible of his blog post, because figuring things out myself is more fun. But that could mean I missed a great idea here or there.)

But hey, at least this is running on my Pentium 133 on SuSE Linux 6.4, printer connected with a parallel cable. 😍

(Also, yes, you can see the printouts of earlier tests and, yes, I used ed(1) wrong at one point. 🤪 And ls insisted on using colors …)

Something happened with the frame rate of terminal emulators lately. It looks like there’s a trend to run at a high framerate now? I’m not sure exactly. This can be seen in VTE-based terminals like my xiate or XTerm on Wayland. foot and st, on the other hand, are fine.

My shell prompt and cursor look like this:

$ █

When I keep Enter pressed, I expect to see several lines like so:

$
$
$
$
$
$
$ █

With the affected terminal emulators, the lines actually show up in the following sequence. First, we have the original line:

$ █

Pressing Enter yields this as the next frame:

$
█

And then eventually this:

$
$ █

In other words, you can see the cursor jumping around very quickly, all the time.

Another example: Vim actually shows which key you just pressed in the bottom right corner. Keeping j pressed to scroll through a file means I get to see a j flashing rapidly now.

(I have no idea yet, why exactly XTerm in X11 is fine but flickering in Wayland.)

The WM_CLASS Property is used on X11 to assign rules to certain windows, e.g. “this is a GIMP window, it should appear on workspace number 16.” It consists of two fields, name and class.

Wayland (or rather, the XDG shell protocol – core Wayland knows nothing about this) only has a single field called app_id.

When you run X11 programs under Wayland, you use XWayland, which is baked into most compositors. Then you have to deal with all three fields.

Some compositors map name to app_id, others map class to app_id, and even others directly expose the original name and class.

Apparently, there is no consensus.

Just discovered how easy it is to recall my last arg in shell and my brain went 🤯 How come I’ve never learned about this before!? I wonder how many other QOL shortcuts I’m missing on 🥲

@kat@yarn.girlonthemoon.xyz @movq@www.uninformativ.de @prologic@twtxt.net Yeah, I’m also having them in my repertoire for ages, so I’m used to the weird command line options. From today’s perspective, they’re not consistent with the rest of the typical shell utilities, that’s for sure.

Regarding find | grep foo, I recommend find -name '*foo*', prologic. Also, I regularly use -type d and -type f to find directories or files.

@kat@yarn.girlonthemoon.xyz @prologic@twtxt.net Given that all these programs are super old (tar is from the late 1970ies), while trying to retain backwards-compatibilty, I’m not surprised that the UI isn’t too great. 🤔

find has quite a few pitfalls, that is very true. At work, we don’t even use it anymore in more complex scenarios but write Python scripts instead. find can be fast and efficient, but fewer and fewer people lack the knowledge to use it … The same goes for Shell scripting in general, actually.

VPS troubles and the weekend
This weekend I went to the cottage with P on Friday. I hoped I would
have a nice weekend reading in front of the wood stove, but I had also
planned to spend at least a few hours trying to configure Maddy as the
new mail server for hack.org et al.

Then the web server I moved to the new VPS died. Again. I connected to
the VNC console and, like before, the Linux kernel couldn’t find its
root disk. A simple:

# mount /dev/vda2 /sysroot; exit

in the emergency shell solved thi … ⌘ Read more

@movq@www.uninformativ.de Agreed, finding the right motivation can be tricky. You sometimes have to torture yourself in order to later then realize, yeah, that was actually totally worth it. It’s often hard.

I think if you find a project or goal in general that these kids want to achieve, that is the best and maybe only choice with a good chance of positive outcome. I don’t know, like building a price scraper, a weather station or whatever. Yeah, these are already too advanced if they never programmed, but you get the idea. If they have something they want to build for themselves for their private life, that can be a great motivator I’ve experienced. Or you could assign ‘em the task to build their own twtxt client if they don’t have any own suitable ideas. :-)

Showing them that you do a lot of your daily work in the shell can maybe also help to get them interested in text-based boring stuff. Or at least break the ice. Lead by example. The more I think about it, the more I believe this to be very important. That’s how I still learn and improve from my favorite workmate today in general. Which I’m very thankful of.

Can you automate the drawing with a script? On X11, you can:

#!/bin/sh

# Position the pointer at the center of the dot, then run this script.

sleep 1

start=$(xdotool getmouselocation --shell)
eval $start

r=400
steps=100
down=0

for step in $(seq $((steps + 1)) )
do
    # pi = 4 * atan(1)
    new_x=$(printf '%s + %s * c(%s / %s * 2 * (4 * a(1)))\n' $X $r $step $steps | bc -l)
    new_y=$(printf '%s + %s * s(%s / %s * 2 * (4 * a(1)))\n' $Y $r $step $steps | bc -l)

    xte "mousemove ${new_x%%.*} ${new_y%%.*}"
    if ! (( down ))
    then
        xte 'mousedown 1'
        down=1
    fi
done

xte 'mouseup 1'
xte "mousemove $X $Y"

Image

Interestingly, you can abuse the scoring system (not manually, only with a script). Since the mouse jumps to the locations along the circle, you can just use very few steps and still get a great score because every step you make is very accurate – but the result looks funny:

Image

🥴

DietPi April 2025 Update (Version 9.12)
The April 18th update of DietPi v9.12 introduces new software options including the fish shell and Amiberry v7/Amiberry-Lite, while also expanding compatibility and resolving various issues. This release focuses on improving usability, editor flexibility, and hardware support across platforms.   DietPi: DietPi is a lightweight, Debian-based operating system optimized for single-board computers and embedded systems. […] ⌘ Read more

Even though I really do like the shell, I always use Dolphin to mount my digicam SD card and copy the photos onto my computer. I finally added a context menu item in Dolphin to create a forest stroll directory with the current date in order to save some typing:

Image

The following goes in ~/.local/share/kservices5/ServiceMenus/galmkdir.desktop:

[Desktop Entry]
Type=Service
X-KDE-ServiceTypes=KonqPopupMenu/Plugin,inode/directory
Actions=Waldspaziergang;

[Desktop Action Waldspaziergang]
Name=Heutigen Waldspaziergang anlegen…
Icon=folder-green
Exec=~/src/gelbariab/galmkdir "%f"

In order to update the KDE desktop cache and make this action menu item available in Dolphin, I ran:

kbuildsycoca5

The referenced galmkdir script looks like that:

#!/bin/sh
set -e

current_dir="$1"
if [ -z "$current_dir" ]; then
    echo "Usage: $0 DIRECTORY" >&2
    exit 1
fi

dir="$(kdialog \
    --geometry 350x50 \
    --title "Heutigen Waldspaziergang anlegen" \
    --inputbox "Neues Verzeichnis in „$current_dir“ anlegen:" \
    "waldspaziergang-$(date +%Y-%m-%d)")"
mkdir "$current_dir/$dir"
dolphin "$current_dir/$dir"

This solution is far from perfect, though. Ideally, I’d love to have it in the “Create New” menu instead of the “Actions” menu. But that doesn’t really work. I cannot define a default directory name, not to mention even a dynamic one with the current date. (I would have to update the .desktop file every day or so.) I also failed to create an empty directory. I somehow managed to create a directory with some other templates in it for some reason I do not really understand.

Let’s see how that works out in the next days. If I like it, I might define a few more default directory names.

Just keeping this shell alive, and sending an useful twtxt in the process. :-P

@lyse@lyse.isobeef.org I’m open to other suggestions 🤣 But hopefully both adding the additional prompt, not allowing it to enter shell history and removing from my shell history prevents me from doing such silly things in haste by pressing ^R and using fuzzy search which if you type fast you sometimes get wrong 😑

Then I cleaned up my shell history of all of the invocations I ever made of dkv rm ... to make sure I never ever have this so easily accessible in my shell history (^R):

$ awk '
  /^#/ { ts = $0; next }
  /^dkv rm/ { next }
  { if (ts) print ts; ts=""; print }
' ~/.bash_history > ~/.bash_history.tmp && mv ~/.bash_history.tmp ~/.bash_history && history -r

So I re-write this shell alias that I used all the time alias dkv="docker rm" to be a much safer shell function:

dkv() {
  if [[ "$1" == "rm" && -n "$2" ]]; then
    read -r -p "Are you sure you want to delete volume '$2'? [Y/n] " confirm
    confirm=${confirm:-Y}
    if [[ "$confirm" =~ ^[Yy]$ ]]; then
      # Disable history
      set +o history

      # Delete the volume
      docker volume rm "$2"

      # Re-enable history
      set -o history
    else
      echo "Aborted."
    fi
  else
    docker volume "$@"
  fi
}

@movq@www.uninformativ.de Where can I join your club? Although, most software I use is decentish in that regard.

I just noted today that JetBrains improv^Wcompletely fucked up their new commit dialog. There’s no diff anymore where I would also be able to select which changes to stage. I guess from now on I’m going to exclusively commit from only the shell. No bloody git integration anymore. >:-( This is so useless now, unbelievable.

從 Shell 到 Go：腳本編寫的優雅進化
你有沒有想過，寫腳本這件事，可能不再需要依賴 Unix Shell 了？別誤會，Shell 確實是個 “魔法工具”，能用一行命令完成許多複雜任務。但如果你是 Go 語言的愛好者，或者正在尋找一種更現代化、更高效的腳本編寫方式，那麼今天這篇文章絕對會讓你眼前一亮！我們將深入探討如何用 Go 語言結合script包，輕鬆實現原本需要 Shell 才能完成的任務。不僅代碼更優雅，還能跨平臺運行，甚至 ⌘ Read more

@lyse@lyse.isobeef.org Doing the devil’s work:

https://movq.de/v/b895c14411/los86-shell-cursor-history.mp4

Better than nothing. 😅

I’ve never liked the behavior of OpenBSD’s shell where it just scrolls horizontally:

https://movq.de/v/1371f7efbc/vid-1741714971.mp4

But now I’m this close to implementing the same thing in my own shell – because it’s probably much, much easier than multiline stuff. 😅

@movq@www.uninformativ.de @prologic@twtxt.net @bmallred@staystrong.run @andros@twtxt.andros.dev Thank you all! I don’t have emacs installed, so I’ll try lagrange and see. According to my shell history, I must have played around with amfora ages ago.

@kat@yarn.girlonthemoon.xyz To improve you shell programming skills, I highly recommend to check out shellcheck: https://github.com/koalaman/shellcheck It points out common errors and gives some suggestions on how to improve the code. Some details in shell scripting are very tricky to get right at first. Even after decades of shell programming, I run into “corner cases” every now and then.

E.g. in getlyr’s line 7 it warns:

echo -e $(gum style --italic --foreground "#f4b8e4" "'$artist', '$song'")
        ^-- SC2046: Quote this to prevent word splitting.

For more information:
  https://www.shellcheck.net/wiki/SC2046 -- Quote this to prevent word splitt...

Most likely not all that problematic in this application, but it’s good to know about this underlying concept. Word splitting is basically splitting tokens on whitespace, this can lead to interesting consequences as illustrated by this little code:

$ echo $(echo "Hello   World")
Hello World

$ echo "$(echo "Hello   World")" 
Hello   World

In the first case the shells sees two whitespace-separated tokens or arguments for the echo command. This basically becomes echo Hello World. So, echo joins them by a single space. In the second one it sees one argument for the echo command, so echo simply echos this single argument that contains three spaces.

It needs to be said: Retrocomputing and old systems like DOS or OS/2 are fun and all, but a UNIX shell and its userland tools are the most powerful things I’ve ever seen. You can pry that from my cold dead hands. 😅

fullmetalScience submits CCS proposal for ‘NoShore’ project
fullmetalScience1 has submitted their first CCS proposal2 looking to complete work on NoShore, a project dedicated to on-the-go offline payments:

TL;DR The document proposes a shell-based environment that users can run to enable offline payments with supporting merchants, whereas the actual signing device will be developed separately in an upcoming iteration.

”`
Total funding: 45 XMR.

ETA: Read more”`

Compact RISC-V Linux Development Device with USB Form Factor Powered by Rockchip RV1103
The Luckfox Pico WebBee RV1103 is a Linux micro development board powered by the Rockchip RV1103 chip, offering a compact platform for diverse development projects. Encased in an ABS protective shell, it supports applications such as lightweight web servers, USB script tools, and smart home devices. Similar to the Luckfox Pico Mini, this device features […] ⌘ Read more

@codebuzz@www.codebuzz.nl I have some shell scripts that handle some of the log formatting details, but I mostly write my mesages by hand. Lately I’ve been browsing twtxt.net since they aggregate most of the known network. I have a couple of demo aggregators sitting around, but I’m in the middle of some infra rebuilds so a lot of my services are offline rn. They’re both built on a simple social graph analysis that extracts urls for your direct follows the follows listed on each of those feeds (friend-of-a-friend replication). certain formatting operations are awkward with my setup, so I may write an app of some kind in the future. likely gemini-based, but I have a number of projects ahead of that one in the queue.

@prologic@twtxt.net I think printf is a more portable option than echo -e for interpreting \t as tab. E.g. printf ‘%s\t%s\t%s’ “$url” “$time” “$text”. In general I always prefer printf over echo for anything non-trivial in unix shell scripts. See last paragraph of https://en.wikipedia.org/wiki/Echo_(command)#History

@sorenpeter@darch.dk oh, I thought we were settled on TABs for a while now, weren’t we? 🤔 The new website mentions TABs too. The command echo -e (on any shell?) will use \t for them.

Diving into mblaze, I think I’ve nearly* reached peek email geek.

Just a bunch of shell commands I can pipe together to search, list, view and reply to email (after syncing it to a local Maildir).

EXAMPLES at https://git.vuxu.org/mblaze/tree/README

So far I’m using most of the tools directly from the command line, but I might take inspiration from https://sr.ht/~rakoo/omail/ to make my workflow a bit more efficient.

*To get any closer, I think I’d have to hand-craft my own SMTP client or something.

So I whipped up a quick shell script to demonstrate what I mean by the increase in feed size on average as well as the expected increase in storage and retrieval requirements.

$ ./compare.sh
Original file size: 28145 bytes
Modified file size: 70672 bytes
Percentage increase in file size: 151.10%
...

@prologic@twtxt.net Thanks for writing that up!

I hope it can remain a living document (or sequence of draft revisions) for a good long time while we figure out how this stuff works in practice.

I am not sure how I feel about all this being done at once, vs. letting conventions arise.

For example, even today I could reply to twt abc1234 with “(#abc1234) Edit: …” and I think all you humans would understand it as an edit to (#abc1234). Maybe eventually it would become a common enough convention that clients would start to support it explicitly.

Similarly we could just start using 11-digit hashes. We should iron out whether it’s sha256 or whatever but there’s no need get all the other stuff right at the same time.

I have similar thoughts about how some users could try out location-based replies in a backward-compatible way (append the replyto: stuff after the legacy (#hash) style).

However I recognize that I’m not the one implementing this stuff, and it’s less work to just have everything determined up front.

Misc comments (I haven’t read the whole thing):

• Did you mean to make hashes hexadecimal? You lose 11 bits that way compared to base32. I’d suggest gaining 11 bits with base64 instead.

• “Clients MUST preserve the original hash” — do you mean they MUST preserve the original twt?

• Thanks for phrasing the bit about deletions so neutrally.

• I don’t like the MUST in “Clients MUST follow the chain of reply-to references…”. If someone writes a client as a 40-line shell script that requires the user to piece together the threading themselves, IMO we shouldn’t declare the client non-conforming just because they didn’t get to all the bells and whistles.

• Similarly I don’t like the MUST for user agents. For one thing, you might want to fetch a feed without revealing your identty. Also, it raises the bar for a minimal implementation (I’m again thinking again of the 40-line shell script).

• For “who follows” lists: why must the long, random tokens be only valid for a limited time? Do you have a scenario in mind where they could leak?

• Why can’t feeds be served over HTTP/1.0? Again, thinking about simple software. I recently tried implementing HTTP/1.1 and it wasn’t too bad, but 1.0 would have been slightly simpler.

• Why get into the nitty-gritty about caching headers? This seems like generic advice for HTTP servers and clients.

• I’m a little sad about other protocols being not recommended.

• I don’t know how I feel about including markdown. I don’t mind too much that yarn users emit twts full of markdown, but I’m more of a plain text kind of person. Also it adds to the length. I wonder if putting a separate document would make more sense; that would also help with the length.

LOl 😂 Not only have a tried to write up a full Twtxt v2 specification, I’ve also written a Bash shell script that implements the new spec 😅

Go 語言實現 systemctl 管理系統服務
在 Linux 系統中，systemd 已然成爲主流的初始化系統和服務管理器，而 systemctl 命令則是我們與之交互的橋樑。對於 Go 開發者而言，直接使用 Shell 調用 systemctl 固然可行，但難免顯得不夠優雅，並且需要編寫額外的代碼來解析命令輸出。爲解決這一問題，taigrr/systemctl 庫應運而生。它爲 Go 開發者提供了符合習慣用法的 systemctl  綁定， ⌘ Read more

@quark@ferengi.one @movq@www.uninformativ.de A general workaround in these cases is to wrap the command in a shell script and reference said script instead.

@movq@www.uninformativ.de I don’t know if I’d want to discard the twts. I think what I’m looking for is a command “jenny -g https://host.org/twtxt.txt” to fetch just that one feed, even if it’s not in my follow list. I could wrap that in a shell script so that when I see a twt in reply to a feed I don’t follow, I can just tap a key and the feed will get added to my maildir. I guess the script would look for a mention at the start of a selected twt and call jenny -g on the feed.

I love shell scripts because they’re so pragmatic and often allow me to get jobs done really quickly.

But sadly they’re full of pitfalls. Pitfalls everywhere you look.

Today, a coworker – who’s highly skilled, not a newbie by any means – ran into this:

$ bash -c 'set -u; foo=bar; if [[ "$foo" -eq "bar" ]]; then echo it matches; fi'
bash: line 1: bar: unbound variable

Why’s that happening? I know the answer. Do you? 😂

Stuff like that made me stop using shell scripts at work, unless they’re just 4 or 5 lines of absolutely trivial code. It’s now Python instead, even though the code is often much longer and clunkier, but at least people will understand it more easily and not trip over it when they make a tiny change.

go 語言調用 shell 命令有這麼兩種方式，都用過了？
阻塞方式 (需要執行結果) 主要用於執行shell命令，並且返回shell的標準輸出適用於執行普通非阻塞 shell 命令，且需要 shell 標準輸出的//阻塞式的執行外部shell命令的函數,等待執行完畢並返回標準輸出func execshell(s string) (string, error){    //函數返回一個Cmd，用於使用給出的參數執行name指定的程序    cmd := ⌘ Read more

Ukraine war: Two killed as Russia continues to pummel south and east
Shelling in city of Kostiantyivka At least two civilians were killed and eight others were wounded in the Zaporizhzhia and Kherson provinces on Sunday as Russian shelling and rocket strikes continued to pummel Ukraine’s south and east. A woman was wounded and a railway station turned into a smoldering ruin amid heavy shelling in the eastern city of Kostiantynivka, … ⌘ Read more

Starting a campain to make myself remember the difference between single and double quotes in shell.

Since I have these simple, yet effective bash shell commands, which allow me to edit notes, plans, todos and statuses from the terminal, I feel liberated from overly complex software - everything is just text files and applications which come preinstalled on every Linux system.

Anyone else keeping personal .log files updated through basic shell commands?

Also - the last thing I needed is sorted, how to get vs code to pick up the default.nix shell environment, there is a really nice addon for vs code that picks up what is in that file, and then set up the environment based on that, meaning I can now open the source, configure, compile and debug with vscode, this was the last piece that was missing. I will write a blog post on my website that explain what I learned, and how I fixed all these things, maybe it’ll help someone else to try NixOS for some development.

I was able to fix this now, by making a ‘default.nix’ file, and then you can open a shell that has all the stuff needed by simply typing ‘nix-shell’ in the root git directory. Pretty nice, I’m starting to enjoy this OS more and more.

Also, got almost everything I use up and running on NixOS, last thing I need now is a way to develop directly on my source, I think I need to set up one of those development shell files for it, so that I then can work from vscode or kdevelop. Cmake is currently happy, and I tried to install everything on my system, but the ‘nix build’ works fine - but that pulls from remote repo, I want to compile the local edited source as I work on it.

Git security vulnerabilities announced
Upgrade your local installation of Git, especially when cloning with –recurse-submodules from untrusted repositories, or if you use git shell interactive mode. ⌘ Read more

Git security vulnerabilities announced
Upgrade your local installation of Git, especially when cloning with `–recurse-submodules` from untrusted repositories, or if you use `git shell` interactive mode. ⌘ Read more

I did a take home software engineering test for a company recently, unfortunately I was really sick (have finally recovered) at the time 😢 I was also at the same time interviewing for an SRE position (as well as Software Engineering).

Got the results of my take-home today and whilst there was some good feedback, man the criticisms of my work were harsh. I’m strictly not allowed to share the work I did for this take-home test, and I really can only agree with the “no unit tests” piece of the feedback, I could have done better there, but I was time pressured, sick and ran out of steam. I was using a lot of libraires to do the work so in the end found it difficult to actually think about a proper set of “Unit Tests”. I did write one (in shell) but I guess it wasn’t seen?

The other points were on my report and future work. Not detailed enough I guess? Hmmm 🤔

Am I really this bad? Does my code suck? 🤔 Have I completely lost touch with software engineering? 🤦‍♂️

a zero dependency shell script that makes it really simple to manage your text notes [[https://github.com/nickjj/notes]] #links

@adi@f.adi.onl Ugh sorry for not replying. If the file list is dynamic, usually you use something like autoconf to generate the Makefile. I’ve also used wildcards in the past and that works okay. You should be able to use shell commands to populate the file list.

a simple Makefile for forwarding internet to your local machine:

SSH_HOST=https://xuu.me
PRIV_KEY=~/.ssh/id_ed25519
forward:
	LOCAL_PORT=$(HOST_PORT); sh -c "$(shell http --form POST $(SSH_HOST) pub=@$(PRIV_KEY).pub | grep ^ssh | head -1 | awk '{ print "ssh -T -p " $$4 " " $$5 " -R " $$7 " -i $(PRIV_KEY)"  }')"

Now i have one more project that i started on Saturday (24 July): gros - os on rust (it has simple shell already and calc and i have to do a lot more). Also sources are already published

My blog system now has tagging (all pure POSIX shell of course)
This isn’t live on the old blog system’s Github, but partially inspired by by Based Cooking’s tag system which is based on blogit, I’ve added in the feature to tag articles.

I’ve been wanting to write more articles and informational pages on my website, but doing that with no organization is somewhat … ⌘ Read more

@movq@www.uninformativ.de “Random thought: Would be great if you could do for i in ...; do something "$i" & done ; wait in a Shell script, but with the Shell only spawning one process per CPU.” -> Interesting which annoyances stay in the back of the head – I’d never articulated this, but it’s absolutely true that this would be great.

I have been using Unix for 25+ years and I just learned about the status character in shells (often ^T). Huh.

Tutorial - Write a Shell in C • Stephen Brennan

cc @adi@twtxt.net

@prologic@twtxt.net rc, the Plan 9 shell.

@prologic@twtxt.net to answer some of your previous questions, i’m using txtnish for my timeline and user controls, and plain twtxt for posting. the alternative to that would be setting up a bunch of shell aliases or small scripts. or making my own client in Go. There’s a thought… ;)

@prologic@twtxt.net (#https://twtxt.net/search?tag=tsvhqdq OK. Im upgrading my tools. twtxt works pretty well inside an Emacs shell window…

es is an extensible shell derived from Plan9’s rc. It’s also placed in the #publicdomain https://github.com/wryun/es-shell #links #plan9 #github

On Kickstarter: SSHatellite A public-access shell server in space. https://www.kickstarter.com/projects/sshatellite/sshatellite

On Kickstarter: SSHatellite A public-access shell server in space. https://www.kickstarter.com/projects/sshatellite/sshatellite

Posted to Entropy Arbitrage: Small-D date Night https://john.colagioia.net/blog/2020/03/18/date.html #techtips #programming #shell #date #gnu #linux #calendar

@mdosch@mdosch.de Apple refuses to ship GPLv3 software. bash has security bugs that Apple doesn’t want to backport. So they’ve switched default shells again, this time to zsh. (bash and the previous default, tcsh, still ship with the OS.)

@adiabetic@www.frogorbits.com What is Catalina? A new shell?

Just installed Catalina (my recommendation: don’t.). zsh is a fine shell…for downloading and installing other shells.

Finally wrote a small shell script to make posting easier though. Now I can push from pretty much anywhere that has my SSH key.

Interestingly enough, Visual Studio Code keeps running bash as its preferred shell, even though it isn’t the login shell anymore.

@kas@enotty.dk now that I understand fish enough to port over the contents of my .bashrc and .bash_profile, I’m starting to get used to it. How’s having different shell preferences for login/interactive treating you?

today was the day of the triennual trying of the fish shell only to go back to bash within an hour or two

More Than Just Fingering Your Robot Girlfriend: Pandora In The Crimson Shell - YouTube https://www.youtube.com/watch?v=hbCrpeA4HfI

Ghost in the Shell: The Major’s Body (1) - WWAC https://womenwriteaboutcomics.com/2014/07/ghost-in-the-shell-the-majors-body-1/

Almost all the content I post to social media is posted by a small shell script that simultaneously posts to several services or through IFTTT duplicating those posts to services for which I lack an API key. When facebook broke automated posting, it meant my account went dark. I didn’t notice.

Band name of the day: night shells

The Inferno Shell http://doc.cat-v.org/inferno/4th_edition/inferno_shell

Bad idea of the day: inform7 repl as command shell

Insufficiently known POSIX shell features - apenwarr https://apenwarr.ca/log/20110228

GitHub - flipcoder/textbeat: text music sequencer and midi shell with vim playback https://github.com/flipcoder/textbeat

Bad idea of the day: Scroll back through GUI input events & application states like you scroll back through shell history; inject conditionals and loops; use speculative execution of applications to show projected state from these changes.

The cyberpunk aesthetic, moreso than mere future noir, is the future as seen through the eyes of Sir Clive Sinclair: sleek but broken, and dominated by posturing. It’s a beveled black hermetically-sealed shell cracked open to fix manufacturing & design flaws, alligator-clipped wire spilling out, but no fix will prevent it from frying your brain if you look at it funny.

the political spectrum is a horseshoe crab: ancient, ugly, full of blue blood that contains poorly-understood enzymes that might cure some kinds of cancer, and frequently leaving its molted shells along the north atlantic shoreline of north america

@kas@enotty.dk Switching shells is the reason that I started deploying scripts in /usr/local/bin rather than defining aliases. :D Tested #bash #ksh #fish and #zsh and the latter it is now for years already.

GitHub - geophile/osh: Osh (Object SHell) is a command-line and API toolkit combining cluster access, database access, and data slicing and dicing. Sort of like awk and cssh morsels wrapped up in a Python crust. https://github.com/geophile/osh

SDF? Syrian Democratic Forces? Free shell accounts? Louisville International Airport?

SDF? Syrian Democratic Forces? Free shell accounts? Louisville International Airport?

Shell Scripts Matter https://dev.to/thiht/shell-scripts-matter

One thing i really miss in posix shell is local. It’s so easy to pollute your namespace. Current solution is to use more pipes and subshells.

One thing i really miss in posix shell is local. It’s so easy to pollute your namespace. Current solution is to use more pipes and subshells.

@david And there are no problems with shell quoting! And especially with history expansion when using an exclamation mark.

@david And there are no problems with shell quoting! And especially with history expansion when using an exclamation mark.

Apparently this thing — by which I mean “my shell” — has trouble with exclamation marks inside double quotes. Phooey.

Search linux bash history
Have you ever executed something on the linux shell and didn’t remember later how it was done? Well if you remember just part of it you can search for it:      history | grep -i “” ⌘ Read more