I haven’t been able to find all the right groups of people on the fediverse. And this makes me sad. I follow a group of people in my field of work and a large # of people in the Apple development ecosystem.
People often talk about Emacs vs Vim. Every developer I’ve met uses Vim. Occasionally, some of the vim users will say they have previously emacs, but switched to vim.
So where are all the people who are currently using Emacs?
I’m not trolling or looking for an argument. I legit want to know!
• provides a standard 16(! not 8!) set of ANSI colors that actually correspond to the standard colors (i.e. green looks green, blue looks blue etc.)
• has good contrast between most of these colors, so that if a CLI tool decides to use gray-on-blue status bars, it’s still readable (this is actually the most important feature)
• uses neutral or warm colors (no blue-ish tint)
• optionally: has a 256-color variant for #Vim or #Neovim
Bon, après des essais de config pour Neovim via Flathub, j'ai dû casser un truc et je m'arrache les cheveux : en console, je ne peux même plus éditer un fichier avec « vim monfichier.txt» (oui, j'ai tjrs Vim), mais ça passe avec «sudo vim monfichier.txt» 😲
Je n'ai aucune idée comment rétablir tout ça et j'y ai passé 1 soirée… (no comment…).
Si quelqu'un peut me conseiller, ce serait formidable.
I’m thinking of writing a small plugin that defines a cmdline mapping to insert the first-level heading, if the current buffer contains a #Markdown document. The idea is that you have something in the file like
2023-09-25 Meeting Notes
and then, later on, do
:w <some-mapping>.md
which expands to
:w 2023-09-25 Meeting Notes.md
Questions:
• Does such a plugin already exist?
• What would be a good key for that? I’m thinking of <C-R><C-T>, see :h c_CTRL-R
Where would you put some basic per-filetype settings like whether to indent via tabs or spaces, indent width, etc., as someone who's basically only using #Vim (or rather #Neovim) and has EditorConfig working in it?
I'd also be interested in why. I'll add some thoughts myself in the following post.
This is the first Neovim release since Bram Moolenaar passed away and the archival/deprecation of both null-ls.nvim and packer.nvim.
Is anyone running into any issues with this release (particularly if you use null-ls or packer)? How are the Neovim distros (eg - NvChad, AstroNvim, LazyVim, LunarVim, etc.) performing after the update?
radical idea for vim config: do it like the config.d folders in /etc -- split a monolithic init.vim/init.lua into a bunch of files that get sourced in alphabetical order
Think I need to start planning for a total free software future. Been using Windows 10 for work and because it’s tolerable. Changed to VS Code because it’s a very good lightweight IDE. This #Recall spyware has forced me to conclude that #Microsoft have turned evil. I was optimistically naïve to think they might not be, in hindsight. So, must look to changing to Linux Mint everywhere, and getting my #NeoVim setup perfected. (May revisit #Helix, if it has a tree view now). As for Apple.. hmm.
Took some time tonight to write a very minimal #neovim#lua config, putting NVChad in the rear view mirror. It's just enough for me to do some #python coding and write in #markdown . I may be missing a few things but I understand it a lot more.
Was looking into understand why everyone talks about neovim instead of vim and found myself trying Helix and … wow out of the box I learned more how to use a vim-like editor than in one year on vim ???
Really not a fan of all this AI nonsense going on in IDEs. #Jetbrains with an un-uninstallable AI plugin (not to mention increasingly poor performance), #zed looks promising and luckily the AI stuff can be disabled but it’s lacking features because it’s new-ish. VSCode is a nope…
Anyone has recommendations for an alternative? I mainly work with #php#laravel#rust and #typescript. Obvious choice for me is #neovim or #helix but I’m finding it such a chore to get working, not to mention tooling.
More #neovim spring cleaning 🧹 Replaced the trusty vim-commentary with Comment.nvim. It's context aware and can use #treesitter to determine the correct commentstring for injected languages. 👍 https://github.com/numToStr/Comment.nvim
No, autocorrect and search engines, when I'm searching for nixvim, the system for configuring #neovim with #nix , I am not looking for the criminal sex cult NXIVM. I will never be looking for NXIVM, not this time, not ever.
I've tried, but I cannot get warm with #emacs anymore. Fish shell has grown on me very much, as well as fzf and #neovim and while #emacs is an amazing silo, it is still mostly a silo, trying to pull every workflow in.
Don't even miss org that much - Reminders does a surprisingly good job with kanban-like view and I have discovered mdcat for markdown document preview with images. Was never a big fan of magit - LazyGit and git cli do everything I need. Guess, I am a simple man, after all...
I've been studying #Emacs for a while now. My conclusion, so far (keeping in mind that I've been using #Vim / #Neovim for over 10 years), is that a strong reason to switch from one to the other would be an affinity for wanting to study elisp/lisp, including modern lisp languages like #clojure
I say this because Emacs is pure elisp, and it is, in fact, an incredibly powerful language... absurdly so, actually.
I had previously written about how to create a script that uses neovim and emulates the lua interpreter cli - now I finally got around to extract it into a dedicated project, with some instructions on how to use it with luarocks.