vidar is a highly experimental Go editor, written in Go, using gxui
UNLICENSE License
Vidar is the Norse god of silence, patience, and revenge. Sounds perfect for an editor, right?
The code repository and development has moved from github to https://git.sr.ht/~nelsam/vidar.
Vidar is a text editor written in go, designed for writing go. It supports plugins, performs reasonably well, and has some nice go-specific features that help with navigating go code. While I don't think it's going to replace your favorite editor, I am pretty damn proud of what we've got, and I think it will support most use cases fairly well. Panics are caught before any in-progress work is lost most of the time (we prioritize fixing those problems quickly), input is reasonably responsive, the usual editor features (copy/paste, find, regexp find, etc) are mostly working as you'd expect, and language-specific features can be loaded per file.
$ go get github.com/nelsam/vidar
$ vidar
If you're running linux, you will also probably want to install plugins, since most go-specific features are kept out of the main editor source code. See the Makefile for plugin build and install commands.
Other OSes will currently get all the go plugins baked directly into the binary.
I'm only supporting the latest stable version of Go. This doesn't necessarily mean that vidar won't work with older versions, but I promise nothing.
gocode
plugin to workgoimports
plugin to work
godef
plugin to workVidar uses xdg to decide where to save config
files. On linux systems, this will probably end up in ~/.config/vidar/
; for Windows
and OS X, you'll likely need to check the xdg package to see what it uses.
Config files are written as toml
by default, but can be parsed from json
or yaml
as well. Currently, there are three config files:
fonts
list, which should be a list of namesInconsolata-Regular
and PTM55F
.name
, path
, and gopath
keys. This can beadd-project
command (ctrl-shift-n
by default).Vidar started as a repository that I had named gxui_playground
. It was quite literally just a place
for me to mess around with gxui. Three weeks later, I had something
that I was actually starting to use for development.
Vidar is still missing some important features, but it's pretty close to being a fully featured editor. It's definitely much more respectable for editing go code than for editing other types of files, but with the plugin system in place, that's less and less a core problem with the editor, and more a problem with the lack of support from third party plugins.
These are all planned, but have yet to be implemented.