Andy @ Andy @programming.dev

Posts

0

Comments

198

Joined

2 yr. ago

The main site isn't made with Statamic?

Anyway the docs pages fail in certain parts, too, anyway:

I love Arch but you may also be interested to try Siduction for similar benefits with less change from what you know (it's still Debian).

FWIW Statamic (like many sites) fails my basic "is everything on the main site legible for dark-mode preferring users?" test:

Yeah, since broot is a full featured file navigator and operator, you can get anywhere once it's launched. I have alt+up bound to go up a directory, but there are other ways to get around as well.

Broot supports fish out of the box, and you can use its default fish launcher function to change your folder (alt+enter quits broot then performs a cd) or insert a path (the broot command pp quits broot then prints the path, like fzf).

I never learned fish scripting, but if anyone here has they may try to port my Zsh functions, especially to get path completion for partially typed paths. If you're doing that and have questions about the broot config side of the equation, I'm happy to try to help.

FWIW broot is a great fuzzy finding file tree tool that can be used similarly (much better for the task IMO), with a little configuration.

That looks cool, thanks!

You might like to use aconfmgr to track and prune your system state.

Konsole is excellent. Wezterm is even better, and can pretty much do everything, everywhere.

There's no need to bother with the others if you like either of these.

I don't know what the install process is like for them, but FYI Siduction offers one image that is minimal but with X11, and one minimal without it.

• Siduction
• openSUSE

It's unmatched for some of the things it does and sites it supports, but I think it's a nightmare for any distro or package maintainer. It wants to manage its own installation and updates, at the user level, pulling in who knows what code or binaries.

I think that makes it mechanically hard to handle, verify, or trust.

There are many advantages relative to bash, especially much better array handling, and comprehensive globbing and expansion expressions. You can reduce your reliance on external tools, which may have multiple alternative implementations (a source of unpredictability).

Some defenses are written up at

https://www.arp242.net/why-zsh.html

(not my post)

For me, fish's differences from older shells count against it without offering any compelling benefits.

Newer shells like nushell and oils/ysh are exciting and have a lot going on, but are not mature or familiar.

For Alpine Linux:

• support a different process supervisor
  • dinit, or
  • s6 with some high level sugar
• add something like the AUR

For Arch, you may like a project called aconfmgr.

For Arch Linux:

• support a different process supervisor
  • dinit, or
  • s6 with some high level sugar
• don't use Bash anywhere
  • port down to POSIX, and
  • port up to Zsh
  • port minimal launchers to execline
• replace PKGBUILD format, maybe with
  • nearly identical but Zsh
  • NestedText containing Zsh snippets
    • use this to render Zsh based on templates
      • my favorite template engine: wheezy.template
• build packages with more optimizations, like the CachyOS repos
• include or endorse something like aconfmgr
• port conf files to NestedText

A good live recovery distro that can mount bcachefs is one thing I've been waiting for before using that filesystem for a new install.

That this will have Arch tools (including arch-chroot, probably) makes this even better.

Thanks. I know that's the case for Nim's flexibility, but I didn't think it applied to the pipe operator stuff like in Roc. I'll do some reading tonight to confirm.

That’s true, but if the transformations have more than one argument, they go after the name

Yup, I understand. That's why I've not put them in the concatenative section.

Also, there are more languages with this feature, for example D, VimScript or Koka.

Thanks, maybe I'll add them to the sidebar! I hadn't heard of Koka.

If you have a suggested heading/description to replace "partially concatenative" I'm interested. Function chaining? And I'm not sure but maybe execline is actually concatenative and needs to be moved out of that section.

Exactly. That's the second link under "Wikipedia Topics" in the sidebar.

I may be expressing it poorly and inaccurately, but what I mean is that in Nim you can re-order arguments and functions to start with some data followed by a series of transformations. The following two lines are equivalent:

 nim

    
parse_int(read_line(stdin))
stdin.read_line().parse_int()

  

Roc offers a similar flow with their |> operator. Here's a snippet from one of my Advent of Code 2022 solutions:

 roc

    
partOne =
    "input.txt"
    |> getData
    |> Task.await \data ->
        data
        |> getRangePairs
        |> List.keepIf pairHasStrictSubset
        |> List.len
        |> Num.toStr
        |> Stdout.line