Tomas Tamadamas tamadamas

Basic LazyVim Setup with Ruby/Rails

A very basic setup for ruby/rails development using LazyVim

Prerequisites

First, you'll of course need neovim. I personally just use the stable release over nightly just because I dislike when things randomly break, and I have to stop working to deal with it. But do whatever you like.

Probably a good idea to start it and run :checkhealth to make sure everything works before proceeding.

Birthday Callouts in Daily Notes

Description

Automatically insert birthday callouts for people's birthdays in your daily notes:

Edited 19/09/2022: Changed the alias part to use the updated structure (removed values)

File name must be in yyyy-MM-dd format, for example 2022-02-23
Uncomment last line dv.paragraph(mdv); if you like to see the result inside a collapse ad-note
You could copy the table and delete the dataview to maintain the work today table, and the links inside the table will update, but the table will remain for future review.
To exclude a folder modifly dailynotes in:

const created_dv_rows = dv.pages('-"dailynotes"')
...

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

Python

Lists

[1, 2, 3, 4, 5]

Power operator (2^5)

2 ** 5

Square root (power operator trick)

9 ** 0.5

Learn Go in ~5mins

This is inspired by A half-hour to learn Rust and Zig in 30 minutes.

Basics

Your first Go program as a classical "Hello World" is pretty simple:

First we create a workspace for our project:

Brew Bundle Brewfile Tips

Copyright & License

Unless otherwise noted (either in this file or in a file's copyright section) the contents of this gist are Copyright ©️2020 by Christopher Allen, and are shared under spdx:Creative Commons Attribution Share Alike 4.0 International (CC-BY-SA-4.) open-source license.

Sponsor

If you more tips and advice like these, you can become a monthly patron on my GitHub Sponsor Page for as little as $5 a month; and your contributions will be multipled, as GitHub is matching the first $5,000! This gist is all about Homebrew, so if you like it you can support it by donating to them or becoming one of their Github Sponsors.

React context vs Redux in 2020

The [React docs][condoc] give some example use cases for context:

Context is designed to share data that can be considered “global” for a tree of React components, such as the current authenticated user, theme, or preferred language.

The common property of these use cases is that data like the current theme doesn't change often and needs to be shared deep down the component tree, which would be cumbersome with "[prop drilling][drill]". Something else that needs to be shared everywhere is the application state when using a "single source of truth" pattern, so it would follow that the context API would help with that as well, but there's a catch: components that use context will rerender every time that the provided value changes, so sharing the whole application state through context would cause excessive render lifecycles.

	declare module "obsidian" {
	interface App {
	isMobile: boolean;
	}
	}

	// Call this method inside your plugin's `onLoad` function
	function monkeyPatchConsole(plugin: Plugin) {
	if (!plugin.app.isMobile) {
	return;

	use std::{
	fs::File,
	io::{Read, Write},
	time::Instant,
	};
	use tokio::task::{self, JoinHandle};

	async fn compute() {
	let handles: Vec<JoinHandle<_>> = (0..1000)
	.map(\|_\| {