/tech/ - Technology★

Give Neovim a shot. In particular this part:

>>954188 (OP)

> but without the legacy cruft and shitty rendering support

Neovim does the right thing by decoupling the GUI from the actual editor. Instead, the GUI is just another application which communicates with a headless Neovim instance over a well-defined API. You can swap GUIs like you change your underwear, or even embed Neovim in an existing editor or IDE.

>>954188 (OP)

It has much better rendering support than most, though. It even supports proportional fonts that actually work.

>>954192

Has neovim settled on a nice way to organize packages? When I used vim, it was an absolute mess. I want a central registry, and the ability to automatically update.

>>954192

The other problem with vim is that most of the packages are quite shitty compared to emacs. Other than the language, the only thing good about staying with emacs is the quality of the surrounding language modes.

>>954212

>have to install packages for every language

>completion is garbage, nobody has a problem with this because nobody actually uses emacs

>slow

>org-mode is ok but like all emacs stuff is incredibly overrated

>comes with a bunch of useless crap you'd only need if you lived in emacs in your tty

Guess how many plugins I have for vim.

>>954188 (OP)

SXEmacs?

Just use nano or gedit you complete autist.

>>954227

>Guess how many plugins I have for vim.

To be fair, that does depends on what you do.

>only need if you lived in emacs in your tty

I've never really liked the nest of keybindings you get from vim+tmux.

>>954241

I must say, gedit is a very fine editor these days. In fact GNOME 3.28 as a whole is getting to a level of comfy that OSX Snow Leopard had.

>>954210

> Has neovim settled on a nice way to organize packages?

Define nice...

> When I used vim, it was an absolute mess. I want a central registry

There is the official Vim website as a central repo, but no one uses it. Vim Awesome lists plugins, but all the info is extracted from the GitHub repo. The plugins are manually added to the website, so it's not just scraping GitHub blindly. No idea if that is what you have in mind.

https://vimawesome.com/

> and the ability to automatically update

The current package managers can do that. I use Vim-Plug and I only need to run :PlugUpdate to get my packages updated.

https://github.com/junegunn/vim-plug

There is also a manager (I forgot the name) which runs outside Vim, so you can set up a cronjob or something for updating your plugins. Vim plugin managers are really just git on autopilot, there isn't much to them.

>>954212

To be fair, Emacs has quite a headstart in that regard. Emacs was designed with scripting in mind based on the experience with TECO, while scripting in Vim was like an afterthought added in Vim 5.0. There is a reason why people want to use other languages like Python for scripting Vim.

However, Vim's idea of "lol, just recompile the entire thing when you want to add a language" led to most of these alternative languages rotting away. Neovim has done the right thing by making these languages external. If you like Lisp you can now script Neovim using Common Lisp, Racket or Clojure:

https://github.com/adolenc/cl-neovim

https://gitlab.com/HiPhish/neovim.rkt

https://github.com/clojure-vim/neovim-client

All of these are just retrofitted to the editor. It will take some time for people to begin making actual use of these features.

>>954227

>Guess how many plugins I have for vim.

That doesn't mean much. I have almost 50 plugins for Neovim. I did not use a recommended list of plugins, I picked each one myself (or wrote it myself) for various purposes.

>>954188 (OP)

>VIM is equally retarded so don't even suggest that to me

>Everyone gives him vim suggestions.

kek

>>954188 (OP)

But anon javascript is a lisp, we can make a good editor with the power of electron!

>>954227

>comes with a bunch of useless crap you'd only need if you lived in emacs in your tty

Someday it will come in handy. For example if you wanded to know what the date of Wednesday next week, you could do it with M-x calendar.

>>954241

i use geany. pretty comfy editor

>>954227

I don't get how you people even compare Vim to Emacs. One is an editor that you open to just edit some text and the other one is a way of life.

What makes emacs bad is:

* slow piece of shit

* fragmenting even more the lisp ecosystem instead of using something already used

* mandatory elips config file

* the "my editor is an OS" retardation

Honestly, I use it only because it can do terminal and GUI and because of all the packages (especially LSP support and auctex).

Just use Spacemacs if you want to complain

>>954312

Or, you know, have a calendar that doesn't depend on electricity.

>>954383

>>954389

Emacs is a way of life, but so is prostitution. Both are hard to feel good about.

>>954389

>mandatory elips config file

Emacs doesn't even have, nor use configuration files.

textadept+textredux

>>954684

>Both feel good and make you hard.

FTFY

>>954712

What is .emacs(.el)?

>>954911

Not necessary, you fucking moron.

>>954916

.vimrc isn't necessary either

>>954712

Fuck off, this is low IQ attempt at baiting someone so you can spout, "The lisp philosophy is that code is data". You know damn well what the guy means, and init / .emacs are literally used by Emacs to store all the (custom-set-variables crap, as soon as the user makes a single customization.

While not explicitly mandatory - you could even ignore it at startup, let's also not pretend you're going to get much use out of emacs without customizing a single option, or requiring a single package.

>>954911

It's an init file. It's a elisp program which is ran when you start emacs. If you don't really don't want to waste time running it, you can run it once and dump core and make a new emacs binary that has your changes saved.

>>954989

>code is data

Nope, I'm just arguing that an init file is not a config fiile. The init file can not only customize your emacs, but also extend it's functionality.

If you think that the init file is a config file, then you must also think that all emacs packages are just config files.

>>955092

I've used config files to enable plugins and hence extend functionality.

Checkmate tardo.