Posts

How to use i_c_fn_head for vscode.

 To activate extension: make /path/to/Your/Project/dir/i_c_fn_head.opts & write down.. //run Rust// or.. //run D// or.. //run C// or.. //run CPP// ========= i've been tested it for Rust & D.. for C & CPP, i'll test later. F12 works, but i'd like to make it more flexible. https://github.com/SarK0Y/i_c_fn_head Paradigm:   https://alg0z.blogspot.com/2026/03/update-icfnhead.html
Post a Comment
Read more

i_c_fn_head :)

Image
 Rust-analyzer looks & feels like damn utter overkill, so i've made more simple alternative... https://github.com/SarK0Y/i_c_fn_head/releases https://github.com/SarK0Y/i_c_fn_head
Post a Comment
Read more

GUI..

Image
 
Post a Comment
Read more

Typst

 https://github.com/typst/typst
Post a Comment
Read more

Go scripting.

  As suggested in the   HN thread , by replacing   //   with   /**/ , we can dodge the formatting problem! So, in my scripts going forward, I will be using: /*usr/local/go/bin/go run "$0" "$@"; exit; */ package main import "fmt" func main () { fmt.Println( "Hello world" ) } Note here the semicolon on  exit; , it will not work without it. https://lorentz.app/blog-item.html?id=go-shebang  
Post a Comment
Read more

Git stories

Image
More proper way been to use scripts a la this . script can be used for automatic saving.. bash> watch -n 210 /path/to/GitIt.sh  
Post a Comment
Read more

i'm not a beta tester :)

 LSP is great thing.. until completely doesn't: i vigorously ditched LSP thanks to its flood of issues which render IDE completely useless in no time + LSP literally bombards user w/ ridiculously annoying warnings. in short, i barely have a Time for my own projects to waste it for things like that :)
Post a Comment
Read more