WordPress has two similar translation functions __() and _x(). The function _x() does the same thing as the function __() except the _x() function allows you to define a context for the translation (with the $context parameter). This is helpful when you have a string that could be two different words. For example there are two words that are spelled “tear” each with a separate meaning (and separate pronunciation). By including the context you could use both of these words and have them correctly translated based on their $context value.
I wanted to run the latest development version of Neovim (0.4.0) to use some of the latest features (e.g. the floating window). Unfortunately, my attempts to install it were failing. These are my notes on the problem and how I fixed it.
When using Vim sometimes I want to duplicate a file, however the default file explorer in Vim (netrw) does not handle this well. This is a Vim mapping I created to make duplicating a file easier.
When making a HubSpot API call to update a date picker field, I’m getting a response with “response code 400”, “error INVALID_DATE”, and the message includes “not midnight!”. This is why I’m getting this error and how I fixed this call.
Using Screenflow 6 with my Scarlet Solo USB connection, I end up with a recording only on the left channel. I want my recording to be on both channels (in stereo). This is how I do that.
I spend a lot of my time communicating in Bitbucket (and in GitHub) and I’ve come to love writing in markdown. Unfortunately, I’ve noticed Bitbucket changed their editing experience to use a WYSIWYG (What You See Is What You Get) editor instead of my beloved markdown area. This is the setting I changed to turn it back to a markdown field.
When using Vim you can find your <Leader> by using echo for the value of “mapleader”, however there are some edge cases that make this less than ideal. If “mapleader” is undefined an error is thrown instead of showing the default <Leader>. If “mapleader” is not a visible character (e.g. <Space> or <Tab>), you can not see the value. I use the following command to display <Leader> while working around these edge cases.
By default all of the WordPress database tables will start with the prefix “wp_” (e.g. wp_users, wp_posts, etc.). Because this is the default value, you’ll often hear the tables referred to (and written about) using the “wp_” prefix. Let’s look at how and why this prefix is modified.
A list of the database tables (and the columns in those tables) used by a default WordPress installation. This is the companion blog post to my talk, “Introduction to the WordPress Database”.
In the WordPress database table “wp_term_taxonomy”, each row almost always has the same value for the two columns ‘term_taxonomy_id’ and ‘term_id’. What is the difference between these two columns?