sts10

A curated list of command-line utilities written in Rust

Note: I have moved this list to a proper repository. I'll leave this gist up, but it won't be updated. To submit an idea, open a PR on the repo.

Note that I have not tried all of these personally, and cannot and do not vouch for all of the tools listed here. In most cases, the descriptions here are copied directly from their code repos. Some may have been abandoned. Investigate before installing/using.

The ones I use regularly include: bat, dust, fd, fend, hyperfine, miniserve, ripgrep, just, cargo-audit and cargo-wipe.

• atuin: "Magical shell history"
• bandwhich: Terminal bandwidth utilization tool

robinp

Lots of goodies like <githubstatus> pinging.
https://github.com/input-output-hk/iohk-ops/blob/bc8195de286d8b9b55b06f2046ab5412307a51b6/modules/hydra-master-common.nix

Declarative jobset bootstrapping:
https://github.com/shlevy/declarative-hydra-example

Declarative jobset with Git PR evals:
https://github.com/cleverca22/hydra-configs/tree/master/toxvpn

Other notes:

eyecatchup

git commit stats

Commands to get commit statistics for a Git repository from the command line -
using git log, git shortlog and friends.

---

travisbhartwell

NOTE: a more up-to-date version of this can be found on my blog

nix-shell and Shebang Lines

A few days ago, version 1.9 of the Nix package manager was released. From the release notes:

nix-shell can now be used as a #!-interpreter. This allows you to write scripts that dynamically fetch their own dependencies.

geoffjay

"$schema" = "https://starship.rs/config-schema.json"

# colorscheme
#
# #2E3440
# #3B4252
# #434C5E
# #4C566A
# #D8DEE9
# #E5E9F0

lheckemann

Expression for a buildEnv-based declarative user environment

This is one way of managing your user profile declaratively.

Alternatives include:

• an attrset-based nix-env-based environment, installed using nix-env -ir rather than nix-env --set. LnL has an overlay which shows a way of doing this.
• home-manager, which provides NixOS-like config for your $HOME

Note that this is incompatible with regular imperative use of nix-env, e.g. nix-env -iA nixpkgs.hello. It has the advantage of allowing the installation of multiple outputs of the same package much better than nix-env's builtin profile builder does.

borispoehland

import * as S from '@effect/schema/Schema'
import { Context, Effect } from 'effect'

export interface IFetcher {
  fetch: typeof fetch
}

export const TFetcher = Context.Tag<IFetcher>('IFetcher')

class FreshFetcher implements IFetcher {

tazjin

Nix builder for Kubernetes

Table of Contents

• Nix builder for Kubernetes
  • Overview
  • Why?
• How?

evelant

import {
    Span as SentrySpan,
    SpanStatusType,
    getActiveSpan,
    getActiveTransaction,
    getCurrentHub,
    startSpanManual,
    startTransaction,
} from "@sentry/core"
import type * as Sentry from "@sentry/types"

robertjpayne

#import <Foundation/Foundation.h>
#import "RCTBridgeModule.h"

#define RCT_EXTERN_MODULE(objc_name, objc_supername) \
  RCT_EXTERN_REMAP_MODULE(objc_name, objc_name, objc_supername)

#define RCT_EXTERN_REMAP_MODULE(js_name, objc_name, objc_supername) \
  objc_name : objc_supername \
  @end \
  @interface objc_name (RCTExternModule) <RCTBridgeModule> \