dotfiles VS notes

You can set this up with even less customization. Here's my snippet for doing so [0]. In this way, the default rule for all containers that are part of compose projects gets assigned a subdomain (service.compose-stack.lvh.me).

However, even with my tweaks, the overall solution is still limited. Because it's not on "localhost", the browser considers it an "insecure context" unless you also set up local HTTPS.

[0] https://github.com/CGamesPlay/dotfiles/blob/13659d19ca899cea...

I’ve started using Remote OSS [0] with some custom scripts to install and run the remote code host. Works great on remote servers and even with devcontainers on remote hosts. You can use a script like the one here to handle automatically installing and setting up the tunnel [1]. I’m working on a PR that adds a way to automatically run custom scripts to set up the tunnels as well [1].

[0] https://open-vsx.org/extension/xaberus/remote-oss

[1] https://github.com/CGamesPlay/dotfiles/blob/master/files/.lo...

[2] https://github.com/xaberus/vscode-remote-oss/pull/9

I built a "Control-P" feature for fish that would also be a good trigger for this tool. Basically, you activate the shortcut to run the program, then it will change the directory based on the selection, but restore your original command line after. So you can be halfway through a command before realizing you are in the wrong place. Also, can cd with one fewer keystroke. My version is at [0], but obviously modifiable for other tools like this one.

[0] https://github.com/CGamesPlay/dotfiles/blob/master/files/.co...

FWIW, I still use regular vim with ale [0] and it does everything I want. It formats files with Black and isort, shows ruff and pyright errors, supports jumping to definitions, and has variable information available on hover. I have collected my config over the past several years, but I pretty rarely encounter errors with it.

[0]: https://github.com/dense-analysis/ale [1] https://github.com/CGamesPlay/dotfiles/blob/master/files/.co...

I think the first example should have been done with direnv rather than having a manual step, but I supposed to each their own. The other examples are all pretty neat.

I recently set up fasd, which I recommend, but I tied it together with fzf, which makes it really nice.

fasd: https://github.com/clvv/fasd

tie it with fzf: https://github.com/CGamesPlay/dotfiles/blob/master/files/.co...

I've documented some really cool things that vifm can do: https://github.com/sitaramc/notes/blob/master/vifm.mkd

So I wrote https://github.com/sitaramc/notes/blob/master/dac -- 30 lines of shell plus maybe another 30 or 40 of comments, and it does everything I want in a dotfile manager.

All this is painlessly taken care of by https://github.com/sitaramc/notes/blob/master/dac (documentation: https://github.com/sitaramc/notes/blob/master/dac.mkd)

If you have fzf installed, grab https://github.com/sitaramc/notes/blob/master/try, and run try dust. Then start typing -t jpg (for example). Then backspace over the jpg and change it to png. Or use some other options.

I hesitate to nominate any of them because (a) there are dozens or even hundreds of them and (b) I don't like any of them; I wrote my own because I needed a "hold" feature that no one had (i.e., when propagating changes to the repo, I want to hold back some parts of the change; https://github.com/sitaramc/notes/blob/master/dac.mkd explains better if you're interested

For those of you who are curious, https://github.com/sitaramc/notes/blob/master/vifm.mkd is my part "review" and part "tips and tricks" on vifm.

Most of my tools are in bash or perl, most of them less than 100 lines of code, (most of them are less than 200 even with comments). https://github.com/sitaramc/notes has all of them (terrible name for a repo full of tools I know; sorry!)

Absolutely vifm. My notes+tips/tricks on this at https://github.com/sitaramc/notes/blob/master/vifm.mkd

https://github.com/sitaramc/notes/blob/master/dac.mkd for documentation, https://github.com/sitaramc/notes/blob/master/dac.mkd for code, if you're interested.

if you're a vim user, you can't go wrong with vifm. My take on vifm is here: https://github.com/sitaramc/notes/blob/master/vifm.mkd -- can't hurt to give it a read (it's a wee bit outdated but not much; probably only the last section needs to be updated)