gamma

joined 2 years ago
MODERATOR OF
[–] gamma 4 points 1 day ago

The "$@" doesn't do that you think it does in an alias. It gets expanded on alias creation.

[–] gamma 7 points 2 days ago (2 children)

I've got optimizer tendencies, but we've also got another member who is 100% "What would my character do in this high stress situation with the knowledge they have" and I've found myself leaning that way during combat more and more.

I will still scrutinize everything outside of combat though, and I'm thankful for the IRL time pressure to get me out of that.

[–] gamma 3 points 1 month ago

Love the Towerfall OST myself, it was such a shock to hear about him.

[–] gamma 1 points 1 month ago* (last edited 1 month ago)

Rivals of Aether 2, its so good to have an indie platfighter that has Smas'hs level of polish.

The first one is still a better casual experience because of workshop and single player modes, but I'm here to shmoove in ranked.

[–] gamma 3 points 3 months ago

Basically the Matrix Spec Change Proposal system, I like it. Opens the floor to more players, gives tool authors a list of protocols they could choose to build on, and hopefully compositors will choose to adopt or adapt one of these protocols before writing their own.

[–] gamma 8 points 3 months ago (1 children)

I know that "Vanity Addresses" are a common thing for onion sites, and there are tools which generate tons of keys looking for prefixes. I haven't seen such a tool for ssh host keys though.

[–] gamma 9 points 3 months ago

I put newlines in my filenames to break both CLI tools and Windows filesystems

[–] gamma 7 points 4 months ago* (last edited 4 months ago)

Taking courses which involve subjects that you will likely never encounter in the workforce is a thing in every discipline. Most engineers don't need to manually solve differential equations in their day jobs, they just need to know that they exist and will often require numerical solutions.

Getting your hands dirty with the content provides a better understanding when dealing with higher level concepts.

[–] gamma 9 points 5 months ago

zsh-syntax-highlighting

There's also a fork called fast-syntax-highlighting, I use it.

[–] gamma 4 points 5 months ago

manually call the others

Yeah, most distros will set up source chains to make things nicer for users.

[–] gamma 1 points 5 months ago* (last edited 5 months ago)

Yeah, I'd write this as a single update script with options to update vimplugins or update pkg or update all.

I see that you want it to be a function so you can get the chdir as a side effect, but mixing that with updating doesn't make sense to me.

[–] gamma 13 points 5 months ago

When in doubt, ~/.zshrc. It's the right choice 99% of the time. Otherwise, there's a chance you fuck up scripts you've installed which assume no shell options have been changed in non-interactive contexts.

 

The document itself is paywalled like all the POSIX specifications, so here are some highlights courtesy of some comments at HackerNews, especially from a-french-anon.

 

This release of fish includes a number of improvements over fish 3.6.4, detailed below. Although work continues on the porting of fish internals to the Rust programming language, that work is not included in this release. fish 3.7.0 and any future releases in the 3.7 series remain C++ programs.

Notable improvements and fixes

  • Improvements to the history pager, including:
  • The history pager will now also attempt subsequence matches (#9476), so you can find a command line like git log 3.6.1..Integration_3.7.0 by searching for gitInt.
  • Opening the history pager will now fill the search field with a search string if you’re already in a search (#10005). This makes it nicer to search something with and then later decide to switch to the full pager.
  • Closing the history pager with enter will now copy the search text to the commandline if there was no match, so you can continue editing the command you tried to find right away (#9934).
  • Performance improvements for command completions and globbing, where supported by the operating system, especially on slow filesystems such as NFS (#9891, #9931, #10032, #10052).
  • fish can now be configured to wait a specified amount of time for a multi-key sequence to be completed, instead of waiting indefinitely. For example, this makes binding kj to switching modes in vi mode possible.
  • The timeout can be set via the new fish_sequence_key_delay_ms variable (#7401), and may be set by default in future versions.
62
submitted 1 year ago by gamma to c/linux
 

Check out the newest version of everyone's favorite^[citation needed] command line json processing tool!

Highlights include significant speed improvements (>10x on some of my workloads), new flags, new builtins, and a litany of bugfixes.

27
submitted 1 year ago* (last edited 1 year ago) by gamma to c/shell
 

I'm sure some of you have absolute monstrosities of sigils (I know I do, in my .zshrc alone). Post them without context, and try and guess what other users's lines are. If you want to provide context or guess, use the markdown editor to spoiler-tag your guesses and explanations!

11
submitted 2 years ago* (last edited 2 years ago) by gamma to c/shell
 

This came out of playing around with curl and the Lemmy API. I wanted a repeatable way to declare a bunch of shell parameters from a json object, so I wrote a jq module! Take a look at the README for examples, or once you install, run

source <( curl 'https://programming.dev/api/v3/community?id=267' | jq -r 'import "shell" as shell; .community_view | shell::param' )

Currently this project only provides a param function, and only supports Bash and Zsh. If I think of other useful helper functions, I may add them to the project.

This uses _ as a default prefix for each parameter. This is so things like {"PATH": "..."} generate typeset _PATH='...' and don't mangle your $PATH, for example. The prefix can be customized by passing in a string: param("mypfx").

Before declaring a 1.0, I'm planning on expanding shell support, and have the function determine how to output using the the $SHELL parameter:

# This does not work (yet!)
eval (curl $URL | jq -r '
  import "shell" as shell;
  "fish" as $SHELL |
  .community_view | param
')

Always up for feedback!

7
submitted 2 years ago by gamma to c/shell
 

YSH, or the shell formally known as oil, is touted as a possible upgrade path from Bash.

This is the first in a three-part series of posts re-introducing the language.

  1. Reviewing YSH
  2. Sketches of YSH Features (you are here)
  3. YSH, Narrow Waists, and Perlis-Thompson Problems (Not yet released)
5
[ysh] (1/3) Reviewing YSH (www.oilshell.org)
submitted 2 years ago* (last edited 2 years ago) by gamma to c/shell
 

YSH, or the shell formally known as oil, is touted as a possible upgrade path from Bash.

This is the first in a three-part series of posts re-introducing the language.

  1. Reviewing YSH (you are here)
  2. Sketches of YSH Features
  3. YSH, Narrow Waists, and Perlis-Thompson Problems (Not yet released)
8
submitted 2 years ago by gamma to c/shell
20
submitted 2 years ago by gamma to c/shell
 

A huge part of programming in general is learning how to troubleshoot something, not just having someone else fix it for you. One of the basic ways to do that is by tracing. Not only can this help you figure out what your script is doing and how it's doing it, but in the event that you need help from another person, posting the output can be beneficial to the person attempting to help.

(If your shell isn't listed and you know how to enable tracing, comment below and I'll add it to the table!)

Shell How to enable tracing
Bash set -x or set -o xtrace
Fish set fish_trace on
sh set -x
Zsh set -x or setopt xtrace

Also, writing scripts in an IDE that supports your language. syntax highlighting can immediately tell you that you're doing something wrong.

If an IDE isn't an option and you're using Bash or Sh, you can paste your script into https://www.shellcheck.net/

(Inspired by this post on /r/bash)

view more: next ›