Kerem Bozdas

FlashSpace Raycast Extension

2026-05-08T09:27:00+00:00

I published a Raycast extension extension that lets you control FlashSpace without leaving your keyboard. If you use FlashSpace to manage virtual workspaces on macOS now you can do so from within Raycast.

Features

Details

Longman Dictionary Desktop and TUI Clients

2026-05-07T16:32:00+00:00

I’ve just released two clients for the Longman Dictionary of Contemporary English (LDOCE 5th ed.): a fork of Qt-based desktop client and a terminal client written in Rust.

ldoce5viewer

My updated fork of the original LDOCE viewer. I kept the original project as a base and applied fixes and improvements so it works well on modern systems. Notable changes are:

Migration from Qt4 to Qt5
Automatic Dark Mode Support
Complete Python 3 Migration

ldoce5viewer-tui

A Rust rewrite of the original Python TUI implementation. It brings a snappy, keyboard-driven experience to the terminal while keeping the same familiar workflow. The rewrite focuses on performance, responsiveness, and portability; if you prefer working inside the terminal, the Rust client is lightweight and fast while preserving the features people liked in the original Python version.

Notable features:

Terminal-first, keyboard-driven UI with low latency and small memory footprint
Vim-style navigation, browser-like history, find-in-page and Zen mode
Tantivy-powered full-text search with advanced filters overlay
Live incremental (prefix) search while you type
Audio playback support from the terminal
In-terminal picture rendering on Kitty/iTerm2, Unicode block fallback elsewhere
Single-binary builds via Cargo and cross-platform support

Both projects are available on GitHub:

Check the repositories for releases, installation instructions, and pre-built binaries.

Happy hacking!

How to continue using master branch in Git

2025-11-22T07:19:00+00:00

Git v2.28.0 adds configuration options to allow users to define their preferred default branch name for new repositories. Also, in this version the default branch was changed from master to main.

Configuring Local Repositories

If you prefer to stick with master, you can set a global configuration that git init will respect:

$ git config --global init.defaultBranch "master"

Now, every time you run git init, your repository will start with master instead of main.

The Problem with Cloning

While init.defaultBranch enforces your preference for new local repositories, forks inherit the upstream repository’s default branch. If you have muscle memory for git push origin master or simply prefer the consistency of master across all your personal projects, this is annoying. You have to manually rename the branch, push the new branch, update the default branch on the remote, and delete the old one.

Automating the Fix

To solve this, I wrote a small Ruby script that wraps git clone. It checks if the repository belongs to github.username, clones the repository, renames default branch to master, pushes the master branch, uses gh to change default branch to master, and deletes the old branch.

First, make sure you have your GitHub username configured:

$ git config --global github.username "krmbzds"

Here is the script, which I’ve named git-clone:

#!/usr/bin/env ruby

repo_url = ARGV[0] || abort("Usage: #{$PROGRAM_NAME} ")
user = `git config github.username 2>/dev/null`.strip
exec("git", "clone", repo_url) if user.empty? || !repo_url.match?(%r{[:/](#{Regexp.escape(user)})/})

if system("git", "clone", repo_url)
  dir = File.basename(repo_url, ".git")

  system("which", "gh", out: File::NULL) &&
    (owner, repo_name = repo_url.match(%r{github\.com[:/](.+?)/(.+?)(?:\.git)?$}).captures) &&
    system("git", "-C", dir, "checkout", "-b", "master", "origin/main") &&
    system("git", "-C", dir, "push", "-u", "origin", "master") &&
    system("gh", "api", "--silent", "repos/#{owner}/#{repo_name}", "-X", "PATCH", "-f", "default_branch=master") &&
    system("git", "-C", dir, "branch", "-D", "main") &&
    system("git", "-C", dir, "push", "origin", "--delete", "main")
end

Currently the script only works for GitHub repositories. However, you can easily adapt or extend it.

Usage

To use this script without replacing your system git binary, you can define a shell function in your .zshrc or .bashrc. This function will intercept git clone commands and route them to our script, while passing all other commands to the standard git binary.

git() {
  if [ "$1" = "clone" ]; then
    shift
    ~/bin/git-clone "$@"
  else
    command git "$@"
  fi
}

For the script to work you need to install gh and login with:

$ gh auth login

Now you can clone any repository like usual:

$ git clone https://github.com/krmbzds/rails
Cloning into 'rails'...
remote: Enumerating objects: 763230, done.
remote: Counting objects: 100% (124/124), done.
remote: Compressing objects: 100% (77/77), done.
remote: Total 763230 (delta 75), reused 47 (delta 47), pack-reused 763106 (from 3)
Receiving objects: 100% (763230/763230), 216.12 MiB | 6.72 MiB/s, done.
Resolving deltas: 100% (570644/570644), done.
branch 'master' set up to track 'origin/main'.
Switched to a new branch 'master'
Total 0 (delta 0), reused 0 (delta 0), pack-reused 0 (from 0)
remote:
remote: Create a pull request for 'master' on GitHub by visiting:
remote:      https://github.com/krmbzds/rails/pull/new/master
remote:
To https://github.com/krmbzds/rails
 * [new branch]            master -> master
branch 'master' set up to track 'origin/master'.
Deleted branch main (was 8aebd0b507).
To https://github.com/krmbzds/rails
 - [deleted]               main

Now all your forks will use master.

Happy hacking!

New release: turkish_id v1.7.0

2024-11-10T13:15:00+00:00

I’ve released a new version of turkish_id gem.

Now, it supports querying ID numbers for people that are not a Turkish citizen but are registered in the blue card registry. The numerical validation works the same way, so no differences there. There is a separate endpoint for querying ID numbers that are in the blue card registry; hence the new foreigner_registered? method.

Here’s how you can use it. First, create a new instance:

identity_number = TurkishId.new("99911494534")

Use valid? method to check numerical validity:

identity_number.valid?  #=> true

Use foreigner_registered? method to query the foreigner registry:

identity_number.foreigner_registered?("Yukihiro", "Matsumoto", 14, 4, 1965)  #=> false

And that’s how you can query a person with a blue card. Hope you find it helpful.

Happy hacking!

My newfound appreciation for LuaSnip

2023-04-19T07:49:00+00:00

Are you familiar with Neovim, the popular text editor? If so, you may have heard of LuaSnip, a snippet engine written entirely in Lua.

I recently wanted to add my own snippet to create Sidekiq workers. During my search, I came across a YouTube playlist called LuaSnip Zero to Hero. s1n7ax does a great job explaining how to write snippets in Lua. I recommend anyone interested in writing their own Lua snippets to watch it.

Whether it’s XML or JSON-based, most snippet engines come with their own syntax definitions which are often encumbered with constraints. I have dealt with them in the past. After playing around with Lua snippets, I was amazed how flexible they are. You have to see it to believe it. So check it out.

Here’s the snippet I wrote for creating an ActiveRecord Job:

.config/nvim/snippets/rails.lua

local luasnip = require("luasnip")
local fmt = require("luasnip.extras.fmt").fmt

local s = luasnip.snippet
local t = luasnip.text_node
local c = luasnip.choice_node
local i = luasnip.insert_node

luasnip.add_snippets("rails", {
  s(
    "job",
    fmt(
      [[
      class {}Job < ActiveJob::Base
        queue_as :{}
        sidekiq_options retry: {}, backtrace: {}

        def perform({})
          {}
        end
      end
      ]],
      {
        i(1, "Example"),
        c(2, { t("default"), t("low"), t("high"), t("critical") }),
        i(3, "25"),
        i(4, "false"),
        i(5, "*args"),
        i(6),
      }
    )
  ),
})

I had to add this line to load my custom snippets in my lsp-zero config:

lua/config/plugins/lsp-zero.lua

require("luasnip.loaders.from_lua").load({ paths = vim.fn.stdpath("config") .. "/snippets/" })
require("luasnip.loaders.from_vscode").lazy_load() -- friendly-snippets

Go wild!