TIL

Have you ever wanted to take a JavaScript array of strings and turn them into a sentence? Here’s how you do that. const toLearn = [ 'object-oriented programming', 'frontend engineering', 'testing', ] const sentence = new Intl.ListFormat().format(toLearn) > "object-oriented programming, frontend engineering, and testing" ListFormat takes options. This has cross-browser support! The days of building a ’to sentence’ function in JavaScript are over.

When viewing a Figma design file, you can zoom in/out with CMD and up/down on a trackpad or magic mouse. Scroll left or right with one-finger swipe left or right. Zoom and scroll; along with adding comments and copying CSS, that’s most of what I do in Figma. I’m sure that these commands are useful in many other settings, but I find them especially valuable in a Figma file, which can feel otherwise challenging for me to navigate.

You’ve been iterating on your Tmux configuration file, and now you want to your configs in action without closing the program. But how? Here’s the command to source an updated tmux.conf: $ tmux source-file tmux.conf

Last week we encountered a breaking change in our Tmux configuration, and briefly lost the ability to scroll with the mouse. It became an opportunity to re-learn Tmux’s copy mode, and liberate ourselves from the mouse a little more. Enter copy mode with <prefix> [. From here, you can navigate with standard Vim commands. ctrl-u moves you a half-page up, perfect for wading through test failure backtraces.

Let’s say you have a string evaluated into a HTML template that contains newlines, like "getting\n\things\ndone" and you want those newlines to be reflected in the presentation. Like this: getting things done We can solve this with the following CSS on the string’s containing element: white-space: pre-wrap; With pre-wrap, “[s]equences of white space are preserved. Lines are broken at newline characters, at [breaks] and as necessary to fill line boxes.” white-space docs

The local environment is a great place to iterate on a CircleCI configuration. You’ll catch errors faster than pushing to CI, and help drive a fast, iterative configuration process. Install the CircleCI CLI via Homebrew (or any package manager of your choice): $ brew install circleci Then, in the same directory as your .circleci/config.yml, run: $ circleci config validate # Config file at .circleci/config.yml is valid

When I upgrade ASDF, I sometimes get an error like this when I try to run a command: /Users/jakeworth/.asdf/shims/jq: line 3: /usr/local/Cellar/asdf/0.9.0/libexec/bin/asdf: No such file or directory The issue is that I’ve upgraded ADSF to v0.10.2, but the jq shim doesn’t know that and can’t find it in a directory called “0.9.0”. This issue persists even after running asdf reshim. My solution is to force ASDF to rebuild shims directory by renaming it. A rename lets me get back to where I am now, in case I need to. ...

I use Vim’s spell feature when writing blog posts. Very often, the first suggestion it makes is the one that I choose. Consider a word like ‘Rubysit.’ My dictionary contains the word ‘Rubyist’ (naturally) and that’s what Vim spell is going to suggest to me first. For transposition errors like this I’d like to skip the word picker when possible. To automatically choose the first suggestion, in normal mode put your cursor over the word and type 1z=.

Do you use bookmarks in Chrome, and also take a lot of browser screenshots? If so, read on. I don’t like including my Chrome bookmarks in browser screenshots; they are irrelevant and personal. Today I learned that the CMD + SHIFT + B hotkey toggles hiding/showing the Chrome browser bookmarks bar. My workflow is toggle off the bookmarks, take a clean browser screenshot with CMD + SHIFT + 4, SPACE, ENTER, and then toggle them back on.

Something I took for granted at Hashrocket was the file that configures Exhuberant Ctags. Without configuration, recursive tag generation will tag many things and cause problems. overindex badly. Here’s how you configure Ctags to ignore things: /ctags.cnf (on MSDOS, MSWindows only) /etc/ctags.conf /usr/local/etc/ctags.conf $HOME/.ctags $HOME/ctags.cnf (on MSDOS, MSWindows only) .ctags ctags.cnf (on MSDOS, MSWindows only) If any of these configuration files exist, each will be expected to contain a set of default options which are read in the order listed when ctags starts, but before the CTAGS environment variable is read or any command line options are read. This makes it possible to set up site-wide, personal or project-level defaults. Here’s the head of my root .ctags, which even this far in is excluding a lot: ...