nq VS notes

If you want something quick and janky, I suggest nq. It's stupidly simple and lightweight; it just requires that everyone is running as the same user. And only lets exactly one job of any kind run in a given queue. There's basically zero configuration; just nq , and it'll either start running , or will wait its turn.

For your ad-hoc uses, I would introduce nq. It's an extremely lightweight queuing system, which gives you two things with minimal overhead:

I'm already aware of alternatives which I will consider (at, nq, snooze, but I still want an accurate lightweight CLI stopwatch/timer app and the script otherwise works well--this is more of an exercise on understanding background processes and could be handy in other scripts. Or if the attempt is considdered hacky and ill-advised, I'm curious of an alternative implementation. I just feel nothing is more simple than a very lightweight C-based timer app that exits 0 after specified time has elapsed and don't want to run a cron job or even a while sleep 1 loop for a reminder (sleep isn't even a builtin...).

Interesting project. Unfortunate that its name conflicts with one of nq’s executables (https://github.com/leahneukirchen/nq), but I’m not sure anything can be done about it.

nq

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)