Jim Myhrberg
6d4665f3dd
The field_identifier type was recently removed from tree-sitter-go here: https://github.com/tree-sitter/tree-sitter-go/pull/71 This means that struct keys are no longer syntax highlighted as properties, which I dislike. Hence this new query targets the first element of a key/value pair, and marks the first element as a @property if it contains an identifier. I'm not sure if this undoes the goal of removing the field_identifier, but for now, it resolves my personal annoyance of struct keys not be highlighted as properties when creating a new instance of the struct.
jimeh's .emacs.d (a.k.a. Emacs Siren)
This is my personal Emacs config, currently nicknamed Emacs Siren, and heavily inspired by Emacs Prelude.
However, this is not some form of an Emacs starter kit, it's simply my personal config with any quirks, oddities, bugs, and man-eating errors I live with on a daily basis.
Requirements
- Emacs 26.1 or later.
Installation
-
Clone the repo to
~/.emacs.d:git clone git://github.com/jimeh/.emacs.d.git ~/.emacs.d - Launch Emacs and wait a few minutes while it installs all packages.
- Enjoy ^_^
Why not use Emacs Prelude?
Prelude is nice and all, but I don't need everything it does. I need a config that does what I need without having to potentially counter and/or work against some config framework. Hence I prefer rolling my own.
The way Prelude structures it's files and code however is very great, and something I took to heart when I started working on a rewrite of my config, and hence Emacs Siren was born.
Why call my config Emacs Siren?
I had been playing a lot of The Witcher 3: Wild Hunt, and decided to pick a name based on a enemy type from the game. "Siren" was short and kinda cool sounding.
