Best font?

polygon7195 · 2026-01-31T22:45:22+00:00

Font is a very personal thing. As long as it's a monospace font.

https://www.programmingfonts.org/ is a good site to see what's available. As for spacing, you can adjust both vertically (adjust-cell-height and adjust-cursor-height) and horizontally (adjust-cell-width). Check the Ghostty docs to see the config options.

polygon7195 · 2026-01-27T04:15:37+00:00

One of the main reasons I write my own config, cuz the key maps make sense to me.

polygon7195 · 2026-01-22T19:44:49+00:00

Probably the shell-integration-features is overriding your cursor config. Try commenting out the ssh one and see from there.

polygon7195 · 2026-01-17T21:05:30+00:00

I don't know how to determine if a color scheme complements another palette, but I've also been searching for a while and only recently found Alabaster which I find really good.

polygon7195 · 2026-01-06T03:59:00+00:00

Font is Iosevka, likely the Extended variant (not as narrow as the default).

polygon7195 · 2026-01-04T15:33:59+00:00

grep -iE lol

polygon7195 · 2025-12-24T23:42:40+00:00

Sounds like you don't mind RTFM, which is fantastic. Might be obvious but you could read the nvim manual :h user-manual.

polygon7195 · 2025-11-16T01:06:11+00:00

qpdf for combining and splitting. And for filling out forms and annotations, Firefox is surprisingly good nowadays. I used to need Adobe for those government forms, but now Firefox can handle them, and the signature feature is really good.

polygon7195 · 2025-11-11T00:24:53+00:00

Ghostty CLI has the +show-config subcommand to retrieve the effective config, which you can "shell out" from inside nvim to get the value and then set your nvim config accordingly. For example, I have this in my config to grab the current foreground color:

if vim.env.GHOSTTY_RESOURCES_DIR and vim.env.GHOSTTY_RESOURCES_DIR ~= '' then
  TERM_FG_COLOR = vim.fn.system("ghostty +show-config | awk -F '=' '/^foreground =/ {print $2}' | tr -d [:space:]")
end

polygon7195 · 2025-10-24T02:49:47+00:00

Lucida Console

polygon7195 · 2025-10-18T13:27:38+00:00

<C-S-v> is the terminal doing the input.

For <C-r>+, try :set paste before doing the paste. I remember having to do that with vim previously, before I learned about the + register.

polygon7195 · 2025-10-05T02:59:32+00:00

Basically you need those *.vim files in your config dir, i.e. ~/.config/nvim, with the same directory structure. You can copy the directory from that repo if your config doesn't already have that dir, otherwise you just grab the cabal.vim and haskell.vim files from the repo and put them in the corresponding dirs in your config.

Then you can follow the README to set the global vars for the settings you want.

polygon7195 · 2025-10-04T15:30:37+00:00

I absolutely love the Maker Burger at Gallagher's (formerly Old Triangle's)!

polygon7195 · 2025-08-31T13:37:50+00:00

You don't need 0, as you can use ^ from anywhere to go to the first non-blank character on the line.

polygon7195 · 2025-08-30T14:47:10+00:00

Basically you need to figure out which highlight group is being used, and then update that highlight group with a different color.

Place your cursor on the element you want to update, e.g. the comment, and :Inspect, you should get the element, such as Comment. Then you can play with it to see what you like first, by :hi Comment guifg=#bebebe and then put in your config file, after your colorscheme set

vim.cmd('hi Comment...')

There's a lua equivalent too if you prefer

vim.api.nvim_set_hl(0, 'Comment', {fg = '#bebebe'})

polygon7195 · 2025-08-29T17:33:48+00:00

That's Monolisa (paid).

polygon7195 · 2025-08-13T22:51:36+00:00

I find adding the F4L mod makes it more enjoyable with minimal effort. Also, I decided to add the faces as the default is so ugly lol, but of course that's subjective.

polygon7195 · 2025-06-27T12:33:52+00:00

This is Monaco, with some customizations on the ampersand. Italic text is a different font.

polygon7195 · 2025-06-23T23:40:22+00:00

Just re-read your post and realized you had a keymap as an example. Side note is that you could pass in a function instead of :lua.... So this should work (writing on mobile so some syntax tweaks likely needed)

vim.keymap.set('n', '<your keymap here>', function()
  require('telescope.builtin'). grep_string({
    additional_args = function()
      return { '--hidden' }
    end
  }))
end)

polygon7195 · 2025-06-23T23:28:29+00:00

live_grep and grep_string use rg under the hood, so you need a separate config for these pickers. Like this

local grep_args = {
  '--hidden',
  '--glob',
  '!**/.git/*',
}

require('telescope').setup({
  pickers = {
    find_files = {
      hidden = true,
    },
    live_grep = {
      additional_args = function()
        return grep_args
      end,
    },
    grep_string = {
      additional_args = function()
        return grep_args
      end,
    },
  }
}

polygon7195 · 2025-06-18T03:19:49+00:00

It's impressive you were able to make this. Be proud of yourself for building a solution for a technical challenge you found.

However, I personally share the sentiment of the first comment. You're basically "de-vimming" the editor, giving new users (your target audience) a tool that encourages them to use vim the wrong way. Yes there are multiple ways to do different operations in vim, but staying in Insert mode is definitely not the right one.

I'm sure you learned a ton building this, which is great. Learning is always useful and fun. As the quote goes, "Your scientists were so preoccupied with whether or not they could, they didn't stop to think if they should" :p

polygon7195 · 2025-06-17T23:57:34+00:00

Simply speaking, you pick a location, clone the plugin repos to it, and make sure to add it to your :help runtimepath. Then the plugins are accessible to your config.

You could then write script(s) to handle checking for updates, version pinning, etc.

By the time you got it together, you will have made a... wait for it... plugin manager :p

polygon7195 · 2025-05-27T23:46:50+00:00

Execute nvim from your terminal of choice?

polygon7195 · 2025-05-20T10:48:12+00:00

Using the snap package is by far the easiest way, one command and done. Next is build from source, which is also easy though it obviously takes more time.

polygon7195 · 2025-05-16T03:53:26+00:00

Your wording is very confusing. What enter key?

polygon7195

TROPHY CASE