#macvim — Public Fediverse posts

@strigohabro Ich benutze #MacVim.

https://macvim.org

#Editor #Mac #macOS #vi #vim

@Bastianoso #MacVim (ja wirklich)

Why does #MacVim (in #homebrew) depend on python, llvm, lua, rust, and ruby? That seems insane.

I've just found that #MacVIm allows you to make its windows transparent. I love it!

Here are a few more icons. Ping me for .icns files.

#Zed #vim #MacVim #VSCode #SublimeText #Emacs #icon #icons

I'm trying #Zed. I like it a lot. It's got a #vim mode, it's very incomplete but it’s got the basics covered. It's got a minimalistic UI but it's unmistakably Graphical UI. It's got tabs, and status bars, and command bar. It also has a project navigator. A thing that I wanted in MacVim for a long time. Zed's also got a decent tools integrations. LSP works out of the box (I'm using ruby-lsp, it's OK). It autoformats code (with RuboCop in the Ruby case). It's got syntax-based task. This means I can run a single spec or a group of specs right from the editor (it's got built in terminal) and I don't need to fiddle with rspec arguments as I edit code. I can rerun the task on hotkey. Most of this was possible in vim for a long time but required extensive configuration.

There was one big issue though. Zed’s got a black icon. #MacVim’s icon is green. I was loosing my editor in the dock and app switcher all the time. So I fixed it for me. I made a green Zed icon.

Let me know if anyone has a similar issue and want an icon in colours you're used to.

BTW, try Zed. It’s great.

I actually already did this in 2018 when #vim 8.1 came out. I was using #MacVim back then, simply because it was rendering text much faster than all the terminal apps available at the time. The new built-in terminal in 8.1 was a huge feature. It allowed me to stop switching between MacVim and the terminal all the time and still enjoy a fast vim experience. Eventually faster terminals like #alacritty, #kitty and #wezterm and also #neovim made me switch back to the terminal again.

#MacVim 2023 retrospective and roadmap: https://github.com/macvim-dev/macvim/discussions/1472

“In general, MacVim does not see a lot of pull requests or community involvement, which I am trying to understand more. Does that indicate that the project is mostly mature and doesn't need much changes? Or that it mostly serves as a downstream project to Vim and most changes go to Vim itself? Or that the development model makes it hard for contributors to get their feet wet, or submit patches?”

MacVim Protip: For those who find #MacVim's default font size and colour schemes utterly unfuckingreadable, you can change these in your ~/.gvimrc file.

For example:

set guifont=Monaco:h18
colorscheme blue

Which produces a much larger, and visually-distinct, buffer.

There are other fonts, sizes, and colour schemes.

You can list schemes installed from your shell via:

$ ls /usr/share/vim/vim81/colors | grep .vim

See: https://linuxhandbook.com/vim-color-schemes/

You might be able to list fonts from within vim via:

:set guifont=*

... which is supposed to display a fonts chooser but fails to do so for me.

#MacVim #gvim #vim #MacOS #tips

Hello #neovim community! 🤓

I have a question for you. How do you deal with “Open with” context menus and neovim?

It runs in the terminal and cannot be registered as the default application for file types?

Is there some way to make that possible on #macOS? I would love to be able to simply right-click a file and choose neovim or double click it and neovim opens.

I guess applications like #neovide or #macvim would/could offer this, but not bare neovim. 🤔

Thank you for any tips on that! 👍🏼

OK, so I have a little #Vim or rather #MacVim question. I've used my .gvimrc file for well over a decade and had to make a couple of changes to get it to work on Mac (used to be on Windows).

One thing I can't figure out is I had mapped Ctrl + F6 (I think it was F5 before) to run #Perl Tidy. I thought I had this working again, but Ctrl + F6 or Cmd + F6 doesn't do anything.

Anyone got a clue?

My main editor used to be gVim, but over the years it became VSCode. I like the integrated terminals and code completion with documentation, when it works.
I think Vim is able to do the same, but never got it to work properly. Or forgot how it worked after a while.
I still use Vim for the occasional quick bulk edits though, but am thinking of switching back to it. Maybe.

#vim #MacVim #VSCode #editors #programming

Yes! A backdoor update of #Vim by making "vim" an alias pointing to the #MacVim included Vim binary worked, and it comes compiled with both +keymap and +langmap! In my case the path was:

alias vim='/Applications/MacVim.app/Contents/MacOS/Vim'

OK can somebody please tell me why #MacVim is such a turd on all my computers? Like I open the app and it just doesn't show any windows?