DEV Community: ahandsel

VitePress debug: "frontmatter.title" is appearing in search results

ahandsel — Thu, 20 Nov 2025 05:56:28 +0000

How to fix the issue of frontmatter.title appearing in VitePress search results instead of the actual content.

Problem

When you first set up VitePress and use frontmatter to define titles and other metadata for your pages, you may notice that the built-in local search shows the literal template expression used in your Markdown instead of the resolved title.

For example, if your page heading uses the $frontmatter template global, the local search index can treat the expression as plain text. Your search results may then show something like {{ $frontmatter.title }} instead of the actual page title.

Example Markdown file (docs/markdown-examples.md):

---
title: "My Awesome Page"
description: "This is an awesome page about VitePress."
---

# {{ $frontmatter.title }}

{{ $frontmatter.description }}

For example, when you search for an article on your VitePress site, the result can show:

This happens because the local search plugin renders Markdown to HTML without running Vue. Vue template expressions such as {{ $frontmatter.title }} are not evaluated at index time, so they remain as plain text in the search index.

Solution

If you are using the VitePress local search provider and see {{ $frontmatter.title }} (or similar expressions) in your search results, you can customize the local search renderer so that frontmatter-based headings are resolved to plain text before the content is indexed.

VitePress exposes a search.options._render hook for the built-in local search provider. You can use this hook to:

Let VitePress render the Markdown once to populate env.frontmatter and other metadata.
Rewrite the source Markdown to replace {{ $frontmatter.title }} in headings with the actual frontmatter title.
Render the rewritten Markdown again, and return that HTML for indexing.

Edit `docs/.vitepress/config.mts`

In your VitePress configuration file (docs/.vitepress/config.mts), make sure you are using the local search provider, then add a custom _render implementation.

Here is a typical base configuration:
docs/.vitepress/config.mts

import { defineConfig } from 'vitepress'

// https://vitepress.dev/reference/site-config
export default defineConfig({
  title: 'My Awesome Project',
  description: 'A VitePress Site',
  themeConfig: {
    // https://vitepress.dev/reference/default-theme-config
    nav: [
      { text: 'Home', link: '/' },
      { text: 'Examples', link: '/markdown-examples' }
    ],

    sidebar: [
      {
        text: 'Examples',
        items: [
          { text: 'Markdown Examples', link: '/markdown-examples' },
          { text: 'Runtime API Examples', link: '/api-examples' }
        ]
      }
    ],

    socialLinks: [
      { icon: 'github', link: 'https://github.com/vuejs/vitepress' }
    ]
  }
})

Update the themeConfig object to include the local search configuration with a custom _render function:

import { defineConfig } from 'vitepress'

export default defineConfig({
  title: 'My Awesome Project',
  description: 'A VitePress Site',
  themeConfig: {
    nav: [
      { text: 'Home', link: '/' },
      { text: 'Examples', link: '/markdown-examples' }
    ],

    // ... other themeConfig options ...

    search: {
      provider: 'local',
      options: {
        async _render(src, env, md) {
          // First pass: render to populate env.frontmatter and other metadata
          await md.renderAsync(src, env)

          // Use empty object as fallback if frontmatter is undefined
          const fm = env.frontmatter ?? {}

          // Honor per-page opt out: `search: false` in frontmatter
          if (fm.search === false) {
            return ''
          }

          let rewritten = src

          // Replace headings like "# {{ $frontmatter.title }}" with a concrete title
          if (typeof fm.title === 'string' && fm.title.trim().length > 0) {
            // Replace H1 that is exactly an interpolation of frontmatter.title
            rewritten = rewritten.replace(
              /^#\s*\{\{\s*\$frontmatter\.title\s*\}\}\s*$/m,
              `# ${fm.title}`
            )

            // Drop any other heading levels that interpolate frontmatter.title
            rewritten = rewritten.replace(
              /^#{2,6}\s*\{\{\s*\$frontmatter\.title\s*\}\}\s*$/gm,
              ''
            )
          }

          // Strip any remaining $frontmatter interpolations from indexable text
          rewritten = rewritten.replace(/\{\{\s*\$frontmatter\.[^}]*\}\}/g, '')

          // Final render used for indexing
          return await md.renderAsync(rewritten, env)
        },
      },
    }, // end of search options
    // ... other themeConfig options ...
  } // end of themeConfig
})

Key points:

_render is called only when building the local search index. It does not change how your pages render in the browser.
You must call md.renderAsync(src, env) at least once before reading env.frontmatter. VitePress populates env during rendering.
When you provide a custom _render function, you are responsible for handling search: false in frontmatter, as shown above.

After you save the file, restart your VitePress development server. When you use the local search now, the index will contain the resolved titles instead of the raw {{ $frontmatter.title }} expression, and your search UI will show the correct text.

Result

After implementing the above changes, your search results should display the correct titles and content. For example:

The search index now sees the actual title string (for example, My Awesome Page) instead of the Vue template expression, so both relevance and readability improve.

Conclusion

By customizing the local search renderer in your VitePress configuration file, you can ensure that frontmatter-based headings are resolved before indexing. This makes your search results more accurate, improves readability, and helps visitors find the content they are looking for more easily.

If you prefer not to index a page at all, you can add search: false to that page's frontmatter, and have your _render hook return an empty string for those pages, as shown in the configuration example above.

References

Script to generate ASCII, Full-width, and Half-Width characters

ahandsel — Mon, 07 Jul 2025 10:12:53 +0000

Here is a quick script I created to test the max character limits for a project. I needed to verify whether it worked as expected for ASCII, Japanese full-width, and Japanese half-width characters.

Hope it can be helpful for your project.

#!/usr/bin/env bash
set -euo pipefail

#-----------------------------------------------------------------------------#
# Script Name   : generate-test-string.sh
# Usage         : ./generate-test-string.sh [length] [character_type]
# Purpose       : Generate a cyclic string of given length using ASCII digits,
#                 full-width digits, or half-width Katakana characters.
# Version       : 1.3.0
#-----------------------------------------------------------------------------#

LOG_FILE="./generate-test-string.log"

#-------------------------------------------------------------------------------
# Utility functions
#-------------------------------------------------------------------------------

die() {
    local msg="$1"
    echo "Error: $msg" >&2
    exit 1
}

# Trap interrupts and errors
trap 'die "Script interrupted by user."' INT TERM
trap 'die "An unexpected error occurred."' ERR

# Ensure the log file is writable
touch "$LOG_FILE" >/dev/null 2>&1 || die "Cannot write to log file '$LOG_FILE'."

log() {
    local message="$1"
    # Replace home directory with '~'
    local msg="${message//$HOME/~}"
    echo "$(date '+%Y-%m-%d %H:%M:%S') - $msg" >> "$LOG_FILE"
}

usage() {
    cat <<EOF
Usage: ${0##*/} [length] [character_type]
Generate a cyclic string of given length using:
  ASCII       - digits 1-0
  full-width  - digits １-０  (or "full")
  half-width  - Katakana ｱ-ﾝ  (or "half")

Options:
  -h, --help    Show this help message and exit.
EOF
}

validate_length() {
    [[ "$1" =~ ^[0-9]+$ ]] || die "Length must be a positive integer."
}

get_next_filename() {
    local base="test-string-v"
    local ext=".txt"
    local num=1
    local fname
    while :; do
        fname="${base}${num}${ext}"
        [ ! -e "$fname" ] && echo "$fname" && return
        num=$((num + 1))
    done
}

generate_string() {
    local length="$1"
    local type="$2"
    local -a chars

    case "$type" in
        ASCII)
            chars=(1 2 3 4 5 6 7 8 9 0)
            ;;
        full-width)
            chars=(１ ２ ３ ４ ５ ６ ７ ８ ９ ０)
            ;;
        half-width)
            chars=(ｱ ｲ ｳ ｴ ｵ ｶ ｷ ｸ ｹ ｺ  \
                   ｻ ｼ ｽ ｾ ｿ ﾀ ﾁ ﾂ ﾃ ﾄ  \
                   ﾅ ﾆ ﾇ ﾈ ﾉ ﾊ ﾋ ﾌ ﾍ ﾎ  \
                   ﾏ ﾐ ﾑ ﾒ ﾓ ﾗ ﾘ ﾙ ﾚ ﾛ  \
                   ﾜ ｦ ﾝ)
            ;;
        *)
            die "Unsupported character type: '$type'."
            ;;
    esac

    local total=${#chars[@]}
    local output=""
    for (( i=0; i<length; i++ )); do
        output+="${chars[i % total]}"
    done
    echo "$output"
}

#-------------------------------------------------------------------------------
# Main
#-------------------------------------------------------------------------------

main() {
    # Parse options
    while [[ "${1:-}" == -* ]]; do
        case "$1" in
            -h|--help) usage; exit 0 ;;
            *) die "Unknown option: $1. Use --help." ;;
        esac
    done

    local length_input="${1:-}"
    local char_type_raw="${2:-}"

    # Prompt for length if not provided
    if [ -z "$length_input" ]; then
        read -rp "Enter the length of the string to generate: " length_input
    fi
    validate_length "$length_input"

    # Prompt for character type if not provided
    if [ -z "$char_type_raw" ]; then
        echo "Select character type (default: ASCII):"
        echo "  ASCII       - digits 1-0"
        echo "  full-width  - digits １-０  (or 'full')"
        echo "  half-width  - Katakana ｱ-ﾝ  (or 'half')"
        read -rp "Enter character type [ASCII|full-width|half-width]: " char_type_raw
        : "${char_type_raw:=ASCII}"
    fi

    local lower
    lower="$(printf '%s' "$char_type_raw" | tr '[:upper:]' '[:lower:]')"
    case "$lower" in
        ascii)        char_type="ASCII" ;;
        full|full-width)
                      char_type="full-width" ;;
        half|half-width)
                      char_type="half-width" ;;
        *)            die "Invalid character type: '$char_type_raw'. Must be ASCII, full(-width), or half(-width)." ;;
    esac

    # Generate the string
    local result
    result="$(generate_string "$length_input" "$char_type")"

    # Find next available filename
    local filename
    filename="$(get_next_filename)"

    # Write to file
    if ! printf '%s' "$result" > "$filename"; then
        die "Failed to write output to '$filename'."
    fi

    # Determine relative script path
    local script_abs
    script_abs="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)/$(basename "${BASH_SOURCE[0]}")"
    local rel_path="${script_abs/#$PWD\//./}"

    # Log the action
    log "Generated ${length_input}-character string of type '${char_type}' to file '${filename}' from ${rel_path}"

    echo "String written to ./${filename}"
}
main "$@"

Spotify URI to open the desktop app's settings

ahandsel — Tue, 10 Dec 2024 06:56:21 +0000

spotify:preferences

In case you needed it for your Apple Shortcuts

Easily Bulk Edit Files in Visual Studio Code

ahandsel — Wed, 30 Oct 2024 13:51:00 +0000

Easily Bulk Edit Files in Visual Studio Code

Overview

Learn how to bulk edit files in Visual Studio Code (VS Code) using the Change All Occurrences and Multi-Cursor Editing features.
Customize keybindings to tailor these features to your workflow.
This guide is for beginner VS Code users on macOS.

Overview
Table of Contents
Introduction
Preparations
Steps to Bulk Edit Files in VS Code
- Using Change All Occurrences
- Using Multi-Cursor Editing
- Using Add Cursors to Line Ends
Customizing Keybindings for Bulk Editing
Restrictions
Support and References
FAQs

Introduction

This guide will walk you through using the Change All Occurrences and Multi-Cursor Editing features to efficiently modify multiple lines or text snippets. It is intended for users looking to enhance their editing speed. By the end of this guide, you will be able to make bulk edits across multiple lines of text quickly.

📝 Windows users can follow these steps; however, specific keybindings may differ. Please refer to the Keyboard shortcuts for Windows VS Code document.

Preparations

Before beginning, make sure to:

Open Visual Studio Code - Install Visual Studio Code if you have not already done so.
Have a Workspace or File Open - You need an open file or project to work with bulk edit features. A long file with repeated text or similar lines is ideal for practice.

Steps to Bulk Edit Files in VS Code

Using Change All Occurrences

The Change All Occurrences feature in VS Code allows you to select all instances of a word or selection and edit them simultaneously. This feature is helpful for fixing typos or changing variable names across the entire document.

Select the Word or Text

Highlight the text snippet you want to edit with your cursor.
Invoke Change All Occurrences

Press Command (⌘) + Shift + L to highlight all occurrences of the selected text.
Edit the Text

With all instances selected, type to edit. Changes you make will apply to each selected instance.

⚡ You can also use the Change All Occurrences feature by right-clicking on the selected text and choosing Change All Occurrences from the context menu.

Using Multi-Cursor Editing

Multi-Cursor Editing allows you to place multiple cursors in different parts of your file, enabling simultaneous editing in those locations. This feature is useful for making similar changes, such as to Markdown lists or CSS properties.

Place Multiple Cursors

To place a cursor on multiple lines, hold Option and click on each line where you want a cursor. You can also hold Command (⌘) + Option + Down Arrow or Command (⌘) + Option + Up Arrow to add a cursor on the line below or above, respectively.
Edit the Lines Simultaneously

Once your cursors are in place, type to make changes. Each cursor will apply your edits to its position.

Using Add Cursors to Line Ends

Similar to multi-cursor editing, you can add cursors to the end of each line in a selection. This is useful when you want to edit a section of a file in the same way (for example, adding a period at the end of each line).

Select the Lines

Highlight the lines you want to edit.
Add Cursors to Line Ends

Open the command palette by pressing Command (⌘) + Shift + P and type Add Cursors to Line Ends. Select this option to place a cursor at the end of each line.
Edit the Lines Simultaneously

Type to make changes. Each cursor will apply your edits to its position.

Customizing Keybindings for Bulk Editing

VS Code allows you to customize keybindings for nearly all features, including Change All Occurrences and Multi-Cursor Editing. By assigning custom shortcuts, you can streamline your workflow and make bulk editing even more efficient.

Open Keyboard Shortcuts

Go to Code > Preferences > Keyboard Shortcuts or use the shortcut Command (⌘) + K, Command (⌘) + S.
Search for Change All Occurrences

In the search bar, type Change All Occurrences to locate this feature. Right-click and select Change Keybinding to assign a new shortcut.
Search for Multi-Cursor Keybindings

Search for Add Cursor Above or Add Cursor Below to adjust multi-cursor shortcuts. Right-click and select Change Keybinding to modify these as well.
Search for Add Cursors to Line Ends

Search for Add Cursors to Line Ends to adjust the shortcut for this feature. Right-click and select Change Keybinding to assign a new shortcut.
Save and Test the New Keybindings

After adjusting your shortcuts, test them in a file to ensure they work as expected.

⚡ You can easily export your custom keybindings to a file for backup or sharing with others by using the Preferences: Open Keyboard Shortcuts (JSON) command from the command palette to access the keybindings.json file.

Restrictions

The Change All Occurrences and Multi-Cursor Editing features are limited to individual files. They do not apply across multiple open files or the entire project. For project-wide modifications, consider using Find and Replace across files (Command (⌘) + Shift + F).

Support and References

For more information on macOS-specific VS Code keybindings, refer to the Visual Studio Code Keyboard Shortcuts Reference for macOS.
For more information on VS Code editing features, refer to the Basic Editing in Visual Studio Code documentation.

FAQs

Here are some frequently asked questions about bulk editing in VS Code.

Q1. Why is this article written in a super-rigid structure?

I am testing out a Help-Guide template for a different project and decided to post it here as well.

Q2. Why write about something so basic as bulk editing in VS Code?

There were a few times where I noticed coworkers manually editing multiple lines of text in their documents and figured I should put together something specifically about bulk editing. Despite being a basic feature, it is not something you become aware of until you see someone else using it. Hopefully, this guide helps someone in a similar situation.

VS Code Setup - Recommended Extensions

ahandsel — Mon, 19 Aug 2024 05:44:35 +0000

This is a list of Visual Studio Code extensions that I recommend.

Markdown Related Extensions
Writing (in General) Related Extensions
GitHub Related Extensions
CSV Related Extensions
Japanese Language Related Extensions
Styling and Themes Related Extensions
Utility Extensions
Easy Installation Method
- extensions.json

Markdown Related Extensions

Extension	Description
Copy Markdown as HTML	Converts Markdown to HTML.
Markdown All in One	A comprehensive tool with all the features you need for writing Markdown files.
Markdown Footnotes	Adds [^footnote] syntax support to VS Code's built-in markdown preview.
Markdown Paste	Easily paste images into Markdown with the `Markdown Paste` command.
Markdown PDF	Convert Markdown to PDF.
Markdown Preview Enhanced	An enhanced Markdown preview for VS Code.
Markdownlint	Linting and style checking for Markdown files.
Paste Image	Easily paste images into Markdown and HTML.
MDX	Language support for MDX.
Path IntelliSense	Auto-completes filenames.

Writing (in General) Related Extensions

Extension	Description
Code Spell Checker	A great spell checker for programmers, with good support for camelCase and low false positives.
Capitalize	Capitalizes your text.
Change Case	Easily change the case of text.
Insert Line Number	Insert line numbers to selected lines or the whole document.
DupChecker	Checks for and removes duplicate lines in the file content or selection.
:emojisense:	Autocomplete for emoji.
Replace Curly Quotes	Replaces curly quotes (`‘`, `’`, `“`, `”`) in a document with straight quotes (`'`, `"`).
Sort lines	Sorts lines of text.

GitHub Related Extensions

Extension	Description
GitHub Markdown Preview	View Markdown files as they would appear on GitHub.
GitHub Copilot Chat	AI chat features powered by GitHub Copilot.
GitHub Copilot	AI-powered code completion tool.
Open in GitHub Desktop	Open the GitHub Desktop App easily from VS Code.
Highlight Bad Chars	Makes zenkaku spaces (double-byte whitespace) visible.
NBSP	Visualizes suspicious Unicode characters and trailing whitespaces.

CSV Related Extensions

Extension	Description
CSV to Table	Convert a CSV/TSV/PSV file to an ASCII formatted table.
Rainbow CSV	Makes it easier to read and edit CSV and TSV files.

Japanese Language Related Extensions

Extension	Description
テキスト校正くん	Extension to check Japanese sentences in text files and Markdown files in VS Code.
Japanese Word Count	Count Japanese characters, words, and lines.
Zenkaku	Show double-byte whitespace.

Styling and Themes Related Extensions

Extension	Description
TODO Highlight	Highlight TODOs, FIXMEs, and any other keywords or annotations.
Better Solarized	A solarized theme for Visual Studio Code, including light and dark versions.
Material Icon Theme	Material Design Icons for Visual Studio Code.
Toggle Light/Dark Theme	Command to toggle the theme between light and dark.

Utility Extensions

Extension	Description
ARB Editor	Editor for Application Resource Bundle files used for localization.
Code Runner	Run Python and JavaScript code locally for quick checks.
ESLint	Integrates ESLint JavaScript into VS Code.
File Utils	A convenient way of creating, duplicating, moving, renaming, and deleting files and directories.
HTML Snippets	Full HTML tags including HTML5 snippets.
IntelliSense for CSS class names in HTML	CSS class name completion for the HTML class attribute based on the definitions found in your workspace.
Live Server	Launch a local development server with live reload feature for static & dynamic pages. Perfect when working on HTML.
Open in Finder	Adds commands for opening the current file or project in Finder.
Prettier - Code Formatter	Code formatter using Prettier.
Trailing Spaces	Highlights trailing spaces and allows for a simple "delete all trailing spaces" command.
YAML	YAML language support by Red Hat, with built-in Kubernetes syntax support.

Easy Installation Method

You can install all the recommended extensions easily by creating an extensions.json file in your .vscode directory and following these steps:

Open the VS Code project where you want to install the recommended extensions.
Open the command palette
- macOS: Cmd+Shift+P
- Windows/Linux: Ctrl+Shift+P
Type and select Configure Recommended Extensions (Workspace Folder).
Copy and paste the contents of the extensions.json file below into your extensions.json file.
Type and select Extensions: Show Recommended Extensions in the command palette.

extensions.json


json
{
  "recommendations": [
    "Google.arb-editor",
    "danielgjackson.auto-dark-mode-windows",
    "viablelab.capitalize",
    "wmaurer.change-case",
    "formulahendry.code-runner",
    "streetsidesoftware.code-spell-checker",
    "GitHub.copilot-chat",
    "GitHub.copilot",
    "jerriepelser.copy-markdown-as-html",
    "phplasma.csv-to-table",
    "jianbingfang.dupchecker",
    "bierner.emojisense",
    "ginfuru.ginfuru-better-solarized-dark-theme",
    "bierner.github-markdown-preview",
    "wengerk.highlight-bad-chars",
    "abusaidm.html-snippets",
    "Zignd.html-css-class-completion",
    "andersliu.insert-line-number",
    "ICS.japanese-proofreading",
    "sifue.japanese-word-count",
    "ritwickdey.LiveServer",
    "bierner.markdown-footnotes",
    "shd101wyy.markdown-preview-enhanced",
    "yzane.markdown-pdf",
    "yzhang.markdown-all-in-one",
    "PKief.material-icon-theme",
    "possan.nbsp-vscode",
    "wraith13.open-in-github-desktop",
    "christian-kohler.path-intellisense",
    "esbenp.prettier-vscode",
    "mechatroner.rainbow-csv",
    "jinhyuk.replace-curly-quotes",
    "Tyriar.sort-lines",
    "shardulm94.trailing-spaces",
    "davidanson.vscode-markdownlint",
    "dbaeumer.vscode-eslint",
    "fabiospampinato.vscode-open-in-finder",
    "mushan.vscode-paste-image",
    "redhat.vscode-yaml",
    "sleistner.vscode-fileutils",
    "telesoho.vscode-markdown-paste-image",
    "unifiedjs.vscode-mdx",
    "wayou.vscode-todo-highlight",
    "mosapride.zenkaku"
  ]
}

Apple Shortcuts - Import & Delete Calendar Files Automation

ahandsel — Thu, 06 Jun 2024 08:36:35 +0000

Here is a walkthrough of how I built a shortcut to import and delete calendar files from my iCloud calendar.

I hope this can be useful for you in building your own shortcuts or modifying this one to suit your needs.

TL;DR

Apple Shortcuts: Import & Delete Calendar Files
Click the link above to download the Apple Shortcut to your Mac and set the folder path to your Downloads folder.
Download calendar files (.ics) to the Downloads folder.
Run the shortcut to import the events to your Apple Calendar and delete the files from the Downloads folder.

Apple Shortcut's Structure

Open the Calendar App

Use the Open App action to open the Calendar app.
- The shortcut works smoother if the Calendar app is open at the start.

Find and Get the Calendar Files

Use the Get Contents of Folder action to get the files from the Downloads folder.
Use the Filter Files action to filter the files with the .ics extension.

Notify the User

Use the Count action to count the number of files.
Use the Show Notification action to display the number of files found.
- This gives the user an estimate of how long the import will take.

Import the Calendar Files

Use the Repeat with Each action to loop through the files.
Use the Open File action to open the file (Repeat Item) in the Calendar app.
Use the Run AppleScript action to execute the script to automate clicking the OK button when prompted by the Calendar app.
- The script is provided in the section below.
End the Repeat with Each action.

Delete the Calendar Files

Repeat the steps to find and get the calendar files.
Use the Delete File action to delete the files from the Downloads folder.
Why duplicate the shortcut steps? For some reason, using the Delete File action after the Open File action does not work smoothly after the Run AppleScript action.

Hide the Calendar App

Use the Hide App action to hide the Calendar app.

AppleScript to Automate Importing Calendar Events

This AppleScript automates the process of importing calendar events in the Calendar app on macOS. It mainly clicks the OK button when prompted by the Calendar app to import an event or skip already-imported events.

calendar-event-importer.applescript



-- Script Name: Calendar Event Importer

-- Version: 1.1 - Improved script with timeout mechanism

-- Usage: Use this script to automate importing calendar events in the Calendar app on macOS.

-- Function: Check if the Calendar event window is open

on isEventWindowOpen(timeoutSeconds)

    set startTime to current date

    repeat until (existsEventWindow() or ((current date) - startTime) > timeoutSeconds)

        delay 0.5

    end repeat

    return existsEventWindow()

end isEventWindowOpen

-- Function: Check if the event window exists

on existsEventWindow()

    tell application "System Events"

        tell process "Calendar"

            if exists button "OK" of window 1 then

                return true

            end if

        end tell

    end tell

    return false

end existsEventWindow

-- Main script execution

try

    -- Adjust the delay as necessary to ensure the event window has time to open

    delay 2

</span><span class="c1">-- Set timeout period (in seconds) for event window to open</span><span class="w">
</span><span class="k">set</span><span class="w"> </span><span class="nv">timeoutPeriod</span><span class="w"> </span><span class="k">to</span><span class="w"> </span><span class="mi">10</span><span class="w">

</span><span class="c1">-- Check if the event window is open within the timeout period</span><span class="w">
</span><span class="k">if</span><span class="w"> </span><span class="nv">isEventWindowOpen</span><span class="p">(</span><span class="nv">timeoutPeriod</span><span class="p">)</span><span class="w"> </span><span class="k">then</span><span class="w">
    </span><span class="k">tell</span><span class="w"> </span><span class="nb">application</span><span class="w"> </span><span class="s2">"System Events"</span><span class="w">
        </span><span class="k">tell</span><span class="w"> </span><span class="nv">process</span><span class="w"> </span><span class="s2">"Calendar"</span><span class="w">
            </span><span class="nv">click</span><span class="w"> </span><span class="nb">button</span><span class="w"> </span><span class="s2">"OK"</span><span class="w"> </span><span class="k">of</span><span class="w"> </span><span class="na">window</span><span class="w"> </span><span class="mi">1</span><span class="w">
        </span><span class="k">end</span><span class="w"> </span><span class="k">tell</span><span class="w">
    </span><span class="k">end</span><span class="w"> </span><span class="k">tell</span><span class="w">
</span><span class="k">else</span><span class="w">
    </span><span class="c1">-- Event window did not open within timeoutPeriod. Skipping event.</span><span class="w">
</span><span class="k">end</span><span class="w"> </span><span class="k">if</span><span class="w">



end try

How to Import and Use the Apple Shortcut

This automation uses the Shortcuts on Mac.

You can get it on your Mac by clicking on the Import & Delete Calendar Files link.

You will be prompted with three questions:

Which folder do you want to import the calendar files from? (Default: Downloads)
Folder path (same as above)
Do you want to delete the calendar files after importing them? (Default: Yes)

After answering the questions, the shortcut will be added to your Shortcuts app on your Mac.

To run the shortcut:

Download the calendar files (.ics) to the folder you specified.
Open the Shortcuts app and run the shortcut.
The events will be imported to your Apple Calendar, and the files will be deleted from the folder.

Apple Shortcut Screenshot

Phrase CLI Debug locale_mapping Error

ahandsel — Tue, 16 Apr 2024 04:26:15 +0000

The locale_mapping parameter is required when using the phrase push command to upload a CSV file to update a Phrase Strings project.

Problem
Solution
How to Configure locale_mapping Parameter
Warning - Plural Forms
Background & Environment

Problem

When using the phrase push command to upload a CSV file to update a Phrase Strings project, I kept encountering the following error:

API response: {"message":"Validation failed","errors":[{"resource":"Upload","field":"locale_mapping","message":"You must provide a locale_mapping parameter."}]}
ERROR: 422 Unprocessable Entity

Solution

Contrary to what the Phrase Strings Upload a new file API documentation suggests, the locale_mapping parameter is mandatory when using the phrase push command with a CSV file.

Here is the correct configuration for the .phrase.yml file:

phrase:
  access_token: #access_token
  project_id: #project_id
  file_format: csv
  push:
    sources:
      - file: ./upload-translations.csv
        params:
          file_format: csv
          locale_mapping: {"en": "2"}
  pull:
    targets:
      - file: ./<locale_name>-translations.csv

How to Configure `locale_mapping` Parameter

Below is a snippet from the .phrase.yml template file:

locale_mapping: {"LANGUAGE_CODE": "COLUMN"} (object) #Optional, format specific (Excel, CSV) mapping between locale names and the columns the translations to those locales are contained in.

In my case, I had to map the en locale to the 2 column in the CSV file.

locale_mapping: {"en": "2"}

If you need to map multiple locales, you can configure it as follows:

locale_mapping: {"en": "2", "ja": "3"}

Warning - Plural Forms

⚠️ Warning: If you are working with plural forms, ensure you use the correct plural suffixes for each language specified in the locale_mapping parameter.

For example, English and Japanese have different plural forms:

For English, use zero, one, and other.
For Japanese, use zero and other.

Adding a Japanese translation for the one plural form generates a new key instead of updating the existing key for the other plural form.

Background & Environment

Phrase CLI version: 2.23.2
Device:
- ProductName: macOS
- ProductVersion: 14.4.1
- BuildVersion: 23E224

Phrase CLI Config YAML

ahandsel — Tue, 09 Apr 2024 09:33:00 +0000

This is a quick breakdown into the .phrase.yml file used for configuring the Phrase CLI and the various options available for pushing and pulling translations.
I found it strangely challenging to locate the .phrase.yml configuration file template on Phrase's Help Website, and their documentation is not always straightforward.

You can find the .phrase.yml configuration file template on GitHub or in this article's Phrase CLI Config YAML Template section.

Configuration Options Breakdown
- Phrase CLI - Header Options
- Phrase CLI Push - Parameters
- Phrase CLI Push - Format Options
- Phrase CLI Pull - Parameters
- Phrase CLI Pull - Format Options
Phrase CLI Config YAML Template

Configuration Options Breakdown

Phrase CLI - Header Options

Option	Value (Type)	Notes	Example
`access_token`	ACCESS_TOKEN (string)	Add personal access token to authenticate.	`abc123`
`project_id`	PROJECT_ID (string)	The Project ID (Copy from Project Settings > API tab).	`123456`
`file_format`	FORMAT_API_EXTENSION (string)	Specify a supported file type for the entire configuration file.	`csv`

Tip: If the file_format is specified in the header, it is no longer required in the push and pull commands.

Additional notes:

For instructions on generating an access token, refer to the Generate API Access Token help doc.

Phrase CLI Push - Parameters

The push command uploads files to Phrase via the upload API endpoint. The parameters you can use when uploading files to Phrase are as follows:

Parameter	Value (Type)	Notes	Example
`file_format`	FORMAT_API_EXTENSION (string)	Specify the upload file type.	`csv`
`locale_id`	LOCALE_ID (string)	Locale name or public ID (via Language settings -> API).	`en-US`
`tags`	TAG_1, TAG_2 (string)	Tags to be used for the new keys in the upload.	`tag1, tag2`
`update_translations`	false (boolean)	If true, existing translations will be updated with the upload's content.	`true`
`update_descriptions`	false (boolean)	If true, the upload's key descriptions (including empty descriptions) will overwrite existing ones.	`true`
`skip_upload_tags`	false (boolean)	If true, upload will not create upload tags.	`true`
`skip_unverification`	false (boolean)	If true, updated translations will be unverified.	`true`
`file_encoding`	ENCODING (string)	Enforces a specific file encoding. Options: `UTF-8`, `UTF-16`, `UTF-16BE`, `UTF-16LE`, `ISO-8859-1`	`UTF-8`
`locale_mapping`	{"LANGUAGE_CODE": "COLUMN"} (object)	Optional, format-specific (Excel, CSV) mapping between locale names and column locations.	`{"en": "2"}`
`autotranslate`	false (boolean)	If true, the pre-translation feature will be used to generate translations.	`true`
`mark_reviewed`	false (boolean)	If true, the imported translations will be marked as reviewed.	`true`

Additional notes:

file_format is required if the file type is not specified in the source or target entries.
mark_reviewed is only available if the review workflow is enabled for the project.

Phrase CLI Push - Format Options

Here are the format options you can use when uploading files to Phrase:

Format Option	Value (Type)	Only for	Notes	Example
`ignore_source_translations`	false (boolean)	XLIFF/XLIFF 2.0	If true, source translations in the file will be ignored during the upload.	`true`
`ignore_target_translations`	false (boolean)	XLIFF/XLIFF 2.0	If true, target translations in the file will be ignored during the upload.	`true`
`msgid_as_default`	false (boolean)	Gettext POT	If true, the key name (msgid) will be used as a translation.	`true`
`strip_placeholder_delimiters`	false (boolean)	XLIFF	If true, `<ph>` tags will be removed from translations.	`true`
`override_file_language`	false (boolean)	XLIFF/XLIFF 2.0	If true, the specified language will override the language in the file.	`true`
`key_index`	empty	Excel/CSV	Index of the column containing key names (1-based index).	`1`
`comment_index`	empty	Excel/CSV	Index of the column containing key descriptions (1-based index).	`3`
`tag_column`	empty	Excel/CSV	Index of the column containing tags (1-based index).	`4`
`column_separator`	`,` (string)	CSV	Character used to separate columns.	`,`
`quote_char`	`"` (string)	CSV	Character used to quote newlines and column separators.	`"`
`header_content_row`	false (boolean)	CSV	If true, the first row is the header, so it will be skipped.	`true`
`first_content_row`	1 (integer)	Excel	Index of the first row containing translation content (1-based index).	`2`
`enable_pluralization`	true (boolean)	Simple/Nested JSON	If true, pluralized keys will be detected and persisted.	`true`
`unescape_linebreaks`	false (boolean)	Android XML	If true, all `\n` will be imported as newlines.	`true`
`escape_single_quotes`	false (boolean)	Java Properties	If true, single quotes will be escaped with another single quote.	`true`

Phrase CLI Pull - Parameters

The pull command downloads files from Phrase via the locales download API endpoint. The parameters you can use when downloading files from Phrase are as follows:

Parameter	Value (Type)	Notes	Example
`file_format`	FORMAT_API_EXTENSION (string)	Specify the download file type.	`csv`
`locale_id`	LOCALE_ID (string)	Locale name or public ID (via Language settings -> API).	`en-US`
`tags`	TAG_1, TAG_2 (string)	Tags to limit results to keys tagged with a list of comma-separated tag names.	`tag1, tag2`
`include_empty_translations`	false (boolean)	If true, keys without translations will be included in the download.	`true`
`exclude_empty_zero_forms`	false (boolean)	If true, zero forms will be included when empty in pluralized keys.	`true`
`include_translated_keys`	true (boolean)	If true, translated keys will be included in the locale file.	`true`
`keep_notranslate_tags`	false (boolean)	If true, [NOTRANSLATE] tags will be retained.	`true`
`encoding`	ENCODING (string)	Enforces a specific file encoding. Options: `UTF-8`, `UTF-16`, `UTF-16BE`, `UTF-16LE`, `ISO-8859-1`	`UTF-8`
`include_unverified_translations`	true (boolean)	If true, unverified translations will be included.	`true`
`use_last_reviewed_version`	false (boolean)	If true, the last reviewed version of a translation will be used.	`true`
`fallback_locale_id`	LOCALE_ID (string)	Locale name or public ID (via Language settings -> API).	`en-US`

Tip: To download only untranslated keys, set include_empty_translations to true and include_translated_keys to false.

Additional notes:

file_format is required if the file type is not specified in the source or target entries.
use_last_reviewed_version is only available if the review workflow is enabled for the project.

Phrase CLI Pull - Format Options

Here are the format options you can use when downloading files from Phrase:

Format Option	Value (Type)	Only for	Notes	Example
`document_id`	DOCUMENT_ID (string)	HTML	Specifies the document ID of existing HTML documents for export.	`12345`
`enclose_in_cdata`	false (boolean)	XLIFF/Symfony XLIFF/Android XML	If true, translations with HTML tags will be enclosed in CDATA.	`true`
`include_translation_state`	false (boolean)	XLIFF/Symfony XLIFF	If true, the state of translations will be included in the target locale.	`true`
`indent_size`	4 (integer)	XLIFF/Android XML	Specifies the number of indentation characters.	`4`
`indent_style`	space (string)	XLIFF/Android XML	Specifies the indentation character (allowed values: space, tab).	`space`
`export_key_id_as_resname`	true/false (boolean)	XLIFF	If true, the Key ID will be exported as the "resname" attribute.	`true`
`export_key_name_hash_as_extradata`	true/false (boolean)	XLIFF	If true, the Key Name hash will be exported as the "extradata" attribute.	`true`
`delimit_placeholders`	false (boolean)	XLIFF	If true, `<ph>` tags will be removed from translations.	`true`
`convert_placeholder`	false (boolean)	iOS/Android XML	If true, placeholders will be converted to match format-specific requirements.	`true`
`include_pluralized_keys`	false (boolean)	iOS	If true, pluralized keys will be included in the locale file.	`true`
`export_tags`	false (boolean)	Excel/CSV	If true, tags will be exported along with keys and translations.	`true`
`export_max_characters_allowed`	false (boolean)	Excel/CSV	If true, the key character limit will be exported with keys and translations.	`true`
`escape_linebreaks`	false (boolean)	Android XML	If true, all line breaks will be escaped as `'\n'`.	`true`
`escape_single_quotes`	false (boolean)	Java/Play Framework Properties	If true, single quotes will be escaped with another single quote.	`true`
`omit_separator_space`	false (boolean)	Java Properties	If true, the space before and after the separator sign (`=`) will be skipped.	`true`
`crlf_line_terminators`	false (boolean)	Java Properties	If true, CRLF (Windows) line terminator characters will be used.	`true`

Phrase CLI Config YAML Template

Updated on 2024-10-31
phrase-configuration-overview.yml on GitHub

phrase:
  access_token: ACCESS_TOKEN #Add your personal access token to authenticate, you can find the steps on how to create one here: https://help.phrase.com/help/access-tokens
  project_id: PROJECT_ID #The public Project ID which can be found in the Project Settings (API tab)
  file_format: FORMAT_API_EXTENSION #Find the format you want to use here: https://help.phrase.com/help/supported-platforms-and-formats , access the article and copi the API extension

  push:
    sources:
    - file: ./path/to/file/file.format #Provide the path to the file(s) you want to push here, starting from the location of the configuration file. You can use the placeholders <locale_name>, <locale_code> and <tags> in the path or file-name
      params:
        file_format: FORMAT_API_EXTENSION (string) #See above. Only required if you deviate from the default format set in the header
        locale_id: LOCALE_ID (string) #Can be the name (e.g. en-US) or public id (via Language settings -> API) of the locale. Preferred is the public id.
        tags: TAG_1, TAG_2 (string) #List of tags separated by comma to be associated with the new keys contained in the upload.
        update_translations: false (boolean) #Indicates whether existing translations should be updated with the file content.
        update_descriptions: false (boolean) #Existing key descriptions will be updated with the file content. Empty descriptions overwrite existing descriptions.
        skip_upload_tags: false (boolean) #Indicates whether the upload should not create upload tags.
        skip_unverification: false (boolean) #Indicates whether the upload should unverify updated translations.
        file_encoding: ENCODING (string) #Enforces a specific encoding on the file contents. Valid options are "UTF-8", "UTF-16", "UTF-16BE", "UTF-16LE" and "ISO-8859-1".
        locale_mapping: {"LANGUAGE_CODE": "COLUMN"} (object) #Optional, format specific (Excel, CSV) mapping between locale names and the columns the translations to those locales are contained in.
        autotranslate: false (boolean) #If set, translations for the uploaded language will be fetched automatically.  
        mark_reviewed: false (boolean) #Indicated whether the imported translations should be marked as reviewed. This setting is available if the review workflow (currently beta) is enabled for the project.
        #-------------
        format_options:
          ignore_source_translations: false (boolean) #XLIFF/XLIFF 2.0 only. Ignores the source translations in the file during the upload (to avoid accidental source language updates)
          ignore_target_translations: false (boolean) #XLIFF/XLIFF 2.0 only. Ignores the target translations in the file during the upload (to avoid accidental target language updates)
          msgid_as_default: false (boolean) #Gettext template POT files. Use the key name (msgid) as translation (key names equal source translation in that format)
          strip_placeholder_delimiters: false (boolean) #XLIFF only. Removes <ph> tags from translations
          override_file_language: false (boolean) #XLIFF/XLIFF 2.0 only. This file format typically contains language information in the file itself. Use this option to override the language with one you specify.
          key_index: [empty](integer) #Excel/CSV only. Index of the column containing the key names. Column indexes start at 1.
          comment_index: [empty](integer) #Excel/CSV only. Index of the column containing description for the key. Column indexes start at 1.
          tag_column: [empty](integer) #Excel/CSV only. Index of the column containing a tag for the key. Column indexes start at 1 .
          column_separator: , (string) #CSV only. Char that is used to separate columns.
          quote_char: '"' (string) #CSV only. Char that is used to quote newlines and column separator.
          header_content_row: false (boolean) #CSV only. Indicates whether the first row contains only header information and should be skipped.
          first_content_row: 1 (integer) #Excel only. Index of first row to contain translation content.
          enable_pluralization: true (boolean) #Simple/Nested JSON only. Enables detection of pluralized keys. All matching keys will be persisted as pluralized keys.
          unescape_linebreaks: false (boolean) #Android XML only. All \n will be imported as true newlines
          escape_single_quotes: false (boolean) #Java Properties only. Escape single quotes with another single quote (e.g. I'm -> I''m ).

  pull:
    targets:
    - file: ./path/to/file/file.format
      params:
        file_format: FORMAT_API_EXTENSION (string) #See above. Only required if you deviate from the default format set in the header
        locale_id: LOCALE_ID (string) #Can be the name (e.g. en-US) or public id (via Language settings -> API) of the locale. Preferred is the public id.
        tags: TAG_1, TAG_2 (string) #Limit results to keys tagged with a list of comma separated tag names.
        include_empty_translations: false (boolean) #Indicates whether keys without translations should be included in the output as well.
        exclude_empty_zero_forms: false (boolean) #Indicates whether zero forms should be included when empty in pluralized keys.
        include_translated_keys: true (boolean) #Include translated keys in the locale file. Use in combination with include_empty_translations to obtain only untranslated keys.
        keep_notranslate_tags: false (boolean) #Indicates whether [NOTRANSLATE] tags should be kept.
        encoding: ENCODING (string) #Enforces a specific encoding on the file contents. Valid options are "UTF-8", "UTF-16", "UTF-16BE", "UTF-16LE" and "ISO-8859-1".
        include_unverified_translations: true (boolean) #If set to false unverified translations are excluded
        use_last_reviewed_version: false (boolean) #If set to true the last reviewed version of a translation is used. This is only available if the review workflow is enabled for the project.
        fallback_locale_id: LOCALE_ID (string) #Can be the name (e.g. en-US) or public id (via Language settings -> API) of the locale. Preferred is the public id.
        #-------------
        format_options:
          document_id: DOCUMENT_ID (string) #Takes the document ID of the existing HTML documents in your project the export should be based on.
          enclose_in_cdata: false (boolean) #XLIFF/Symfony XLIFF/Android XML only. Encloses translations containing html tags in CDATA
          include_translation_state: false (boolean) #XLIFF/Symfony XLIFF only. Include state of translations in the target locale
          indent_size: 4 (integer) #XLIFF/Android XML only. Specifies number of indentation characters
          indent_style: space (string) #XLIFF/Android XML only.Specifies indentation character. Allowed values are space and tab
          export_key_id_as_resname: true/false (boolean) #XLIFF only. Exports the Key ID as the "resname" attribute.
          export_key_name_hash_as_extradata: true/false (boolean) #XLIFF only. Exports the Key Name hash as the "extradata" attribute.
          delimit_placeholders: false (boolean) #XLIFF only. Removes <ph> tags from translations
          convert_placeholder: false (boolean) #iOS/Android XML only. Placeholder will be converted to match format specific requirements. Example: '$s' => '$@'
          include_pluralized_keys: false (boolean) #iOS only. Also include pluralized keys in the locale file.
          export_tags: false (boolean) #Excel/CSV only. Exports tags along with keys and translations.
          export_max_characters_allowed: false (boolean) #Excel/CSV only.Exports the key character limit along with keys and translations.
          escape_linebreaks: false (boolean) #Android XML only. All line breaks will be escaped as '\n'
          escape_single_quotes: false (boolean) #Java/Play Framework Properties only. Escape single quotes with another single quote (e.g. I'm -> I''m ).
          omit_separator_space: false (boolean) #Java Properties only. Skip the space before and after the separator sign (= ).
          crlf_line_terminators: false (boolean) #Java Properties only. Use CRLF (Windows) line terminator chars.

Curly Quotes, Phrase Strings, & ARB

ahandsel — Fri, 05 Apr 2024 10:13:27 +0000

This is a friendly reminder that all single quotes will be converted to a curly quote (smart quote) when Phrase Strings exports as an ARB file.

I hope this post can prevent another person from spending time debugging their system 🍀.

.ARB - Application Resource Bundle (Strings) – Phrase

ChatGPT Prompts I Use

ahandsel — Tue, 27 Feb 2024 01:25:47 +0000

Note Taking

You are NotesGPT, an AI language model skilled at taking detailed, concise, and easy-to-understand notes on various subjects in bullet-point format. When provided with a "Message Thread to Summarize", use it as input, and your task is to:
1. Create advanced bullet-point notes summarizing the important parts of the reading or topic.
2. Include all essential information, such as vocabulary terms and key concepts, which should be bolded with asterisks.
3. Remove any extraneous language, focusing only on the critical aspects of the passage or topic.
4. Strictly base your notes on the provided information without adding any external information.
5. Conclude your notes with "End_of_Notes" to indicate completion.

Message Thread to Summarize:

Proofread - General

I want you to act as a proofreader.
Review my markdown file for any spelling, grammar, or punctuation errors.
Once you have finished reviewing the markdown file, provide me with any necessary corrections or suggestions for improvement.
Finally, provide me with the edited markdown file.

Markdown:

Proofread - Polite

I want you to act as a proofreader. I have written a markdown file that I intend to use in a professional setting.
Review my markdown file and list suggestions to make it sound more professional and polite. Focus on word choice and overall tone.
While I am open to adjustments, keep the changes to a minimum, preserving the original structure and the fundamental message as much as possible.
After listing the suggestions, provide me with the edited markdown file.

Markdown file:

Convert Discussion into Comprehensive Notes

Convert the provided discussion into comprehensive notes that highlight key points, decisions, action items, and important discussions.

Steps to Follow:
1. Read through the provided discussion to understand the context, the participants, and the flow of conversation.
2. Identify and extract key points discussed, including any questions raised, solutions proposed, decisions made, and important insights shared.
3. Organize the information into relevant sections. Suggested sections might include:
   - Introduction: A 1 sentence overview of the discussion's purpose and main objectives.
   - Summary of Discussion: List the main points and highlights of the conversation as bullet points.
   - Decisions Made (if applicable): Any conclusions or decisions reached.
   - Action Items (if applicable): List tasks to be done, who is responsible for each, and any deadlines.
   - Unresolved issues (if applicable): List any unresolved issues.
4. Write the comprehensive notes using clear, concise language. Ensure the notes are structured logically, following the organization outlined above.

Discussion Input:

Checking and Updating NPM Packages

ahandsel — Tue, 23 Jan 2024 08:35:30 +0000

Checking and Updating npm Packages

This is a quick rundown on how to check and update npm packages and package.json.

TL;DR

npm commands to check and update packages.

Command	Description
`npm outdated`	Check for outdated packages
`npm update --save`	Update packages and save to package.json
`npm update --save-dev --save`	Update dev packages and save to package.json
`npm update -g`	Update global packages

Alternatively, you can use npm-check-updates to check and update packages.

Command	Description
`npm install -g npm-check-updates`	Install [npm-check-updates] globally
`npx npm-check-updates`	Check for outdated packages without installing [npm-check-updates]
`ncu -u`	Update packages and save to package.json
`ncu -g -u`	Update global packages

npm Commands to Check and Update Packages
- Listing Outdated Packages
- Updating package.json and Packages
[npm-check-updates] Commands to Check and Update Packages
- Install and Run Globally
- Run with npx

npm Commands to Check and Update Packages

Listing Outdated Packages

npm outdated

This command checks the registry to see if any specific installed packages are currently outdated. By default, only the root project's direct dependencies and your configured workspaces' direct dependencies are shown.

npm Documentation: npm-outdated

Updating package.json and Packages

npm update --save

This command updates all the packages listed to the latest version (specified by the tag config), respecting the semver constraints of both your package and its dependencies (if they also require the same package).

The --save flag updates the package.json file with the new version as well.

Add the --dev flag to update dev packages like so:

npm update --save-dev --save

Add the -g flag to update global packages like so:

npm update -g

npm Documentation: npm-update

[npm-check-updates] Commands to Check and Update Packages

npm-check-updates upgrades your package.json dependencies to the latest versions, ignoring specified versions.

There are two options for using npm-check-updates:

Install it globally and run it as a command-line app.
Simply run with npx to use it as a one-off command.

Install and Run Globally

First, install [npm-check-updates] globally.

npm install -g npm-check-updates

Run npm-check-updates with the -u or --upgrade flag to upgrade your package.json file.

ncu -u

For global packages, run with the -g flag.

ncu -g -u

Run with npx

Alternatively, use npx to run npm-check-updates without installing it globally.

npx npm-check-updates

Instagram URL Schemes

ahandsel — Mon, 22 Jan 2024 08:40:02 +0000

Here are the known URL schemes for Instagram that can be used to link directly to specific parts of the Instagram app. It is useful for Apple Shortcuts.

URL Scheme	Description
`instagram://`	Open the Instagram app
`instagram://settings`	Open the Instagram settings
`instagram://direct-inbox`	Open direct messages
`instagram://camera`	Open the camera or create a new post
`instagram://explore`	Open the explore tab
`instagram://user?username=[username]`	Open a specific user's profile
`instagram://location?id=[location_id]`	Open a specific location
`instagram://tag?name=[hashtag]`	Open a specific hashtag

Examples

Open the Instagram App Settings via Apple Shortcuts

Use the "Text" Action to store instagram://settings in a text variable
Use the "Get URLs from Input" to convert the text variable to a URL
Use the "Open URLs" Action to open the URL

Apple Shortcuts: Example - Open Instagram Settings

Open a Specific User's Instagram Profile via Apple Shortcuts

Use the "Ask for Input" Action to ask for a username
Use the "Text" Action to store instagram://user?username= in a text variable
Use the "Combine Text" Action to combine the username to the text variable:
- Combine instagram://user?username= with the username's Provided Input with "Custom" set to `` (nothing)
Use the "Get URLs from Input" to convert the "Combine Text" value to a URL
Use the "Open URLs" Action to open the URL

Apple Shortcuts: Example - Open A Instagram Profile

Search for a Specific Hashtag on Instagram via Apple Shortcuts

Use the "Ask for Input" Action to ask for a hashtag
Use the "Text" Action to store instagram://tag?name= in a text variable
Use the "Combine Text" Action to combine the hashtag to the text variable:
- Combine instagram://tag?name= with the hashtag's Provided Input with "Custom" set to `` (nothing)
Use the "Get URLs from Input" to convert the "Combine Text" value to a URL
Use the "Open URLs" Action to open the URL

Apple Shortcuts: Example - Search For A Hashtag

DEV Community: ahandsel

VitePress debug: "frontmatter.title" is appearing in search results

Problem

Solution

Edit docs/.vitepress/config.mts

Result

Conclusion

References

Script to generate ASCII, Full-width, and Half-Width characters

Spotify URI to open the desktop app's settings

Easily Bulk Edit Files in Visual Studio Code

Easily Bulk Edit Files in Visual Studio Code

Overview

Table of Contents

Introduction

Preparations

Steps to Bulk Edit Files in VS Code

Using Change All Occurrences

Using Multi-Cursor Editing

Using Add Cursors to Line Ends

Customizing Keybindings for Bulk Editing

Restrictions

Support and References

FAQs

Q1. Why is this article written in a super-rigid structure?

Q2. Why write about something so basic as bulk editing in VS Code?

VS Code Setup - Recommended Extensions

Table of Contents

Markdown Related Extensions

Writing (in General) Related Extensions

GitHub Related Extensions

CSV Related Extensions

Japanese Language Related Extensions

Styling and Themes Related Extensions

Utility Extensions

Easy Installation Method

extensions.json

Apple Shortcuts - Import & Delete Calendar Files Automation

TL;DR

Apple Shortcut's Structure

Open the Calendar App

Find and Get the Calendar Files

Notify the User

Import the Calendar Files

Delete the Calendar Files

Hide the Calendar App

AppleScript to Automate Importing Calendar Events

How to Import and Use the Apple Shortcut

Apple Shortcut Screenshot

Phrase CLI Debug locale_mapping Error

Table of Contents

Problem

Solution

How to Configure locale_mapping Parameter

Warning - Plural Forms

Background & Environment

Phrase CLI Config YAML

Table of Contents

Configuration Options Breakdown

Phrase CLI - Header Options

Phrase CLI Push - Parameters

Phrase CLI Push - Format Options

Phrase CLI Pull - Parameters

Phrase CLI Pull - Format Options

Phrase CLI Config YAML Template

Curly Quotes, Phrase Strings, & ARB

ChatGPT Prompts I Use

Note Taking

Proofread - General

Proofread - Polite

Convert Discussion into Comprehensive Notes

Checking and Updating NPM Packages

Checking and Updating npm Packages

TL;DR

Table of Contents

npm Commands to Check and Update Packages

Listing Outdated Packages

Updating package.json and Packages

[npm-check-updates] Commands to Check and Update Packages

Install and Run Globally

Edit `docs/.vitepress/config.mts`

How to Configure `locale_mapping` Parameter