I want a Nightfox badly but I’ve seen nothing but bad reviews (example video review) of the Hako switches, in particular the Trues that are the only remaining available choice.

You said you love it, so I wonder what switches you have and what your preferences are? Have you tried Zealios?

because that’s what the developer uses?

I mean, I do too, but people do actually take this kind of thing seriously. I’ve had several people say they wouldn’t use ripgrep because the command was too long to type, but upon hearing that the actual command was rg, were much more satisfied. Maybe I missed their facetiousness, but they didn’t appear to be joking…

For those of us with RSI, these little savings add up, and can make for a pretty big difference in comfort while typing.

My thoughts exactly. I have often wasted time trying to optimize something which took so little time to begin with, even if I reduced the time to nothing it would have no significant impact on overall performance. And the less-obvious trap is optimizations like this add additional complexity which leads to more time spent down the road.

All right, buddy. Cool.

Did I say it a “life saver”? Nope. Did I say it could save you a lot time? Yup. If cd'ing into directories doesn’t waste your time, cool. Move along, read the next blog post on the list.

I’m sorry about your roadmap estimations. Sounds like you’ve got a lot on your chest there.

the parent tool is probably overkill but a simple zsh function to jump to marked projects with tab completion is pretty awesome to have.

alias j="jump "
export MARKPATH=$HOME/.marks
function jump {
cd -P "$MARKPATH/$1" 2>/dev/null || echo "No such mark: $1"
}

function mark {
echo "mark name_of_mark"
mkdir -p "$MARKPATH"; ln -s "$(pwd)" "$MARKPATH/$1"
}

function unmark {
rm -i "$MARKPATH/$1"
}

#if you need it on another os.
#function marks {
#ls -l "$MARKPATH" | sed 's/  / /g' | cut -d' ' -f9- | sed 's/ -/\t-/g' && echo
#}

# fix for the above function for osx.
function marks {
\ls -l "$MARKPATH" | tail -n +2 | sed 's/  / /g' | cut -d' ' -f9- | awk -F ' -> ' '{printf "%-10s -> %s\n", $1, $2}'
}

function _completemarks {
reply=($(ls $MARKPATH))
}

compctl -K _completemarks jump
compctl -K _completemarks unmark

I mean… it’s a web browser running in a web browser. We’re in, “Yo dawg, I heard you like Chrome tabs, so I put a Chrome tab in your Chrome tab so you can consume memory while you consume memory.”

It doesn’t help that it claims that it is fast without any evidence towards that claim.

Would I be able to use wireguard with something like Mullvad?

Because the “Oil Shell” is a new unix shell being built. Read the homepage.

I second the Kakoune recommendation. It lacks plugins but is very promising. I missed CtrlP for example when I tried it.

Vis is another option that I’ve been eyeing, along side Edit.

Have you tried spacemacs out? it’s really a much better at customizing the editor than vim but still has a very well done version of vim emulation. I consider myself to be a power user of vim and spacemacs is very compelling if you don’t want the hacky feel. magit is a phenomenal package(shows just what a decent programming language inside the editor gets you) and changes the way I look at version control.

I tried Kakoune for a week around New Year’s. And it was surprising how deep I got into it. In the end, though, I found myself deeply incompatible with it.

• In spite of being modal, Kakoune’s shortcuts started to feel like Emacs. Default chords like alt-C would require pressing three keys at once.

• Kakoune’s scripting language started to feel just as hacky as Vim, albeit in different ways. More minimal, but a lot more nested-string escaping. If I was willing to put up with chords, why not just use Emacs and get a real language to script my editor with?

• Critical keyboard shortcuts had no equivalent. { and } for navigating by paragraph. , was impossible to make work as I expected. X for deleting a character backwards. You can’t just hit w to skip ahead one word and then hit i to start typing. You have to hit w, then ; to reset the selection before you can start inserting. Just felt weird.

• Kakoune has no window management. Instead you’re supposed to just use tmux. That felt nice and orthogonal in theory. In the spirit of Unix. But in practice it turned out to be not so nice. For example, I could open multiple windows in tmux panes, but Kakoune would always be in the directory I first started it in, rather than the directory I opened the current window at. There was no sequence of autocommands and scripting that would allow windows to have their own directories like Vim has. I think the same idea may apply to Rob Pike’s criticism of the proliferation of commandline flags in Unix: it’s easy to criticize Unix on principle, but when you get into the details it is perhaps not so bad.

Perhaps I was just too programmed by Vim. I don’t know. Interesting, mind-broadening experience for sure. The lesson I was left with was something fundamental about software: we still don’t know how to unbundle the timeless essence of a piece of software (in the case of Kakoune, the object-verb grammar and multiple cursors) from the slow accretion of more arbitrary design choices like how you navigate by paragraph or the implementation of f and ;. Back in the git history of Kakoune is a sweet spot with a more compatible and elegant text editor. It may have missed some features, but it didn’t have conflicting features to a human being on Earth used to Vim.

I had this exact same experience. Initially I went to emacs (and I still love bits of emacs - org-mode is outstanding) but for day to day editing I’ve transitioned to Visual Studio Code.

It’s very featureful and its extension language is Javascript, which I’m finding much easier to wrap my head around.

I love kakoune too, I think it’s heading in a very interesting direction. The always-on “visual mode” is great, and the use of standard UNIX tools to extend the editor makes a lot of sense. I implemented a simple “netrw”-style extension with little effort and calls to ls.

One thing that bothers me though is the lack of a simple C key to replace until the end of the line, as in Vim. I use this very often, and maybe I just missed something, but it’s just not that quick and easy in kakoune, it would require a custom mapping or something, I believe.

I doubt anyone here on lobsters does but I know for a fact that a lot of people still do.

I have been using 1Password since 2009 and am very happy with it. I have tried LastPass on some occasions, but it always looked flakey. Also, at the time it seemed to lack separation between the browser extension and actual password storage, which 1Password does have [1].

Of course, 1Password is not really an option if you use Linux.

[1] https://support.1password.com/mini-extension-security/

I personally use enpass

iPhone - iOS 10 supports 3rd party apps supplying call blacklists and the API is write-only, so apps can only inject numbers that should be blocked, they can’t see any calls you’ve made. It’s just like their API for 3rd party ad blockers, which just supply Safari with a big list of regexes, they don’t actually see URLs you load.

One such app (can’t vouch for it): https://itunes.apple.com/us/app/truecaller-spam-identification-block/id448142450?mt=8

I think I read that T-Mobile offers something along those lines. Not sure how it works or whether it is effective.

voicemail? how often do scammers leave messages? for that matter, i’ve noticed comcast likes to call me every week but never leaves a message, so I know it’s some crap promotion and not anything important.

When you think about it it’s so ridiculous that this isn’t trivial on all smartphones.