Not a tmux issue, happens with and without, and also nothing to scrollback. It just gives a single screen of garbage as an "error message".

#rustc blows up completely when replacing a source file under ~/.cargo/registry/src with random data. It really should do better. This is not appropriate way to signal memory corruption, shouldn’t memory safety take care of this? :-) #rust #rustlang

@hjvt https://github.com/rust-vmm/vm-memory/issues/289

@hjvt I found proper memory mapping primitives from vm-memory, they are just under "xen" feature flag, e.g. https://docs.rs/vm-memory/latest/vm_memory/mmap/struct.MmapRange.html.

I don't get the reason for "xen-only" but the API is reasonable and quick skim to source seems to give same impression.

So I see where that leads me. If possible I'd prefer vm-memory most only because of its volume. I.e. most likely to stay alive and maintained.

This is how I integrate rusty tags in my .zprofile:

# rusty-tags
[ `command -v rustc` ] && RUST_SRC_PATH=$(rustc --print sysroot)/lib/rustlib/src/rust/library/
[ -d $RUST_SRC_PATH ] && export RUST_SRC_PATH

I still prefer #ctags over LSP.

#rust #rustlang

A great mental model for #git reflog:

1. Git tree represents commit history.
2. Reflog represents the linear history of Git events, i.e. changes to 1.

#linux #kernel

Another often ignored #git #hack is using either -Xtheirs or -Xours when picking/applying/rebasing commits.

Often it is easier to be brutal and then review carefully and add possible missing bits.

#linux #kernel

Reflog be cleaned by git reflog expire --expire=all.

I get a feeling from my feed lately that not that many kernel dev’s are too familiar with git reflog, which is essential tool for solving exactly the situations of e.g.

1. Being in-between git am.
2. Being in-between git rebase.
3. Being in-between git cherry-pick.

Ignoring git merge because I’ve never used it in my career for any possible kernel dev task ;-)

It is really worth of the effort learn this subcommand properly. You won’t regret the investment.

Reflog a local cache and/or timeline of commit ID change’s at the tip. It is not stored to history and is completely ignorant, orthogonal and disjoint from whatever state the Git tree might be in.

#git #linux #kernel

@ljs My estimate all kernel maintainers in Finland in any area would take about a single store bus to fill in. Not sure if @jani agrees with my estimate but this has been impression at least in conferences :-)

@hjvt Any input is welcome most welcome because memory management (in the sense of mapping it) is not the strong point of Rust's stdlib.

I just do bunch of test programs and that will hopefully converge to choice ;-)

Way test these is that I git grep just our call sites in Enarx and then make lowest-common denominator hello world out of it...

Thank you!

Listing monospace fonts with #fontconfig:

❯ fc-list :mono : family | sort -u
Andale Mono
BlexMono Nerd Font
BlexMono Nerd Font,BlexMono Nerd Font ExtraLight
BlexMono Nerd Font,BlexMono Nerd Font Light
BlexMono Nerd Font,BlexMono Nerd Font Medium
BlexMono Nerd Font,BlexMono Nerd Font SemiBold
BlexMono Nerd Font,BlexMono Nerd Font Text
BlexMono Nerd Font,BlexMono Nerd Font Thin
BlexMono Nerd Font Mono
BlexMono Nerd Font Mono,BlexMono Nerd Font Mono ExtraLight
BlexMono Nerd Font Mono,BlexMono Nerd Font Mono Light
BlexMono Nerd Font Mono,BlexMono Nerd Font Mono Medium
BlexMono Nerd Font Mono,BlexMono Nerd Font Mono SemiBold
BlexMono Nerd Font Mono,BlexMono Nerd Font Mono Text
BlexMono Nerd Font Mono,BlexMono Nerd Font Mono Thin
Courier New
Liberation Mono
MesloLGLDZ Nerd Font
MesloLGLDZ Nerd Font Mono
MesloLGL Nerd Font
MesloLGL Nerd Font Mono
MesloLGMDZ Nerd Font
MesloLGMDZ Nerd Font Mono
MesloLGM Nerd Font
MesloLGM Nerd Font Mono
MesloLGSDZ Nerd Font
MesloLGSDZ Nerd Font Mono
MesloLGS Nerd Font
MesloLGS Nerd Font Mono
Nimbus Mono PS
Noto Color Emoji
Source Code Pro
Source Code Pro,Source Code Pro Black
Source Code Pro,Source Code Pro ExtraLight
Source Code Pro,Source Code Pro Light
Source Code Pro,Source Code Pro Medium
Source Code Pro,Source Code Pro Semibold

Had to trial and error for a while so consider no to myself ;-)

@TehPenguin In the backend it JVM does provide safe, concurrent and secure ecosystem and huge track record to back it up. I don't see any actual business reason to switch.

It neither has not made waves yet in the kernel, and it is not likely it will before GCCRS is in par with LLVM. Not saying that it never will but zero defconfigs is not a strong standing point.

The business interesting use I've seen has been WASM so far.

Sixel test. It is funny how much sixels have late years go appreciation when they were invented by DEC already in 1987, when they introduced VT-320 series of dummy terminals ;-)

@TehPenguin i also ignore all meme pic's, sorry ;-) i don't care about em.

@mhd Rust seems to have found its place as defacto for wasm, which I think appropriate use for it too.

I.e. security barrier involved with direct user input.

@mhd Its ideas became big through Objective-C kind of and influenced quite many languages over the years. World would not be the same without Smalltalk even tho it itself was not great success.

Java on the other hand is the most field-tested industry strength language in the backend. And its JIT is heavily optimized by the engineers of the CPU companies involved. It is not that great in the client and but there's no server workload in existence that would not have gone though the "Java exercise".

That said my fav desktop application Bitwig Studio is made with Java ;-) https://www.bitwig.com/

@TudbuT @orizuru Thanks for the qualitative opinion that I will ignore without reading it properly :-)

@elrohir All my password in Firefox sync are duplicates as browser sync works me only as a cache ;-)

@elrohir did not know this but neither big surprises here :-)

I have two-folded approach:

1. My main secret/password vault is https://www.passwordstore.org/.
2. I use sync features as password caches and empty them annually. So I have password “in rotation” in the browser.