gitmoji VS Vim

My commit messages are pretty good though. I put some effort/thought into them not just for the repo/git purposes, but it also helps me mentally keep track of what I have done / have to do just in the general carry-on coding. I even prefix messages with an emoji, similar to the guidelines on https://gitmoji.dev/

You may also turn on GitMoji convention if you prefer your messages baked with emojis 🤠

I use Gitmoji:

https://github.com/carloscuesta/gitmoji

OpenCommit leverages the conventional commits convention, ensuring your commit messages are both concise and informative. Want a little fun in your commits? Enable the GitMoji setting!

The library uses conventional commits convention which makes commits concise and comprehensive. You can also turn on GitMoji setting if you like.

At a previous job we used https://gitmoji.dev, which scrumoji is based on. At some point I started using the ladybug emoji for bugs because it's actually a bug while my colleagues kept using the caterpillar emoji because they preferred caterpillars. I thought it was a nice way to bring some individuality into our commit messages!

It's the first time I see someone combining gitmoji with conventional commits (I use the later now for all my project, to generate my changelogs automatically with with git-cliff.)

It still happens today: https://github.com/carloscuesta/gitmoji

Let’s get to it! To create your service file, you can use Vim (if you enjoy a challenge) or Nano as your editor, and I will be using Nano. Thank you and God bless 🙏🏿. So to create your service file in the appropriate directory, you will execute the command

When you use NeoVim/Vim, you should type :next after :w (save) in order to switch files.

I used to be a pretty heavy Vim user (RIP Bram), but when I started doing a lot of remote pairing with less experienced devs I realised that they were sometimes having trouble following along when I was driving. Their experience was basically "click click click" some text whizzes around the screen.

From what I can tell the reason is that that’s the way it was always done. As I understand it, back in the days before there were distributed version control systems, Bram was the only one who could commit to the code-base so he would credit the actual author of a submitted patch in the commit message. He continued this practice after the Vim project moved to Mercurial (and Git).

Related discussion: https://github.com/vim/vim/issues/1554

From what I've read[1], vim9script was pushed and developed almost exclusively by Bram. With him, a lot of the knowledge about its internals and vision for its future dies.

[1]: https://github.com/vim/vim/discussions/12736#discussioncomme...

Sending heartfelt condolences to Bram's family. His last commit is just one month ago: https://github.com/vim/vim/commit/4c0089d696b8d1d5dc40568f25.... I wonder who else has access to vim.org and the official git repository and if there will be anyone step up to become vim's BDFL.

Vim

So I did some digging and I found out that vim-polyglot uses a different syntax file than Vim's default for PHP files. When I loaded vim-polyglot's syntax file into my ~/.vim/syntax, I encountered the same issue as you.

There's currently a discussion to pick an alternative grammar system in Vim; tree-sitter is among the options that are being considered.

I believe Vim is considering it currently and someone has a working(?) prototype: https://github.com/vim/vim/issues/9087