I've added the R.nvim plugin to #Neovim. It splits the window into panels for editing, viewing output and browsing objects, and it offers everything I'd expect in an R IDE.
It hardly needs any configuration besides registering its own existence. It's comprehensive, thoughtful and underrated, and it's my preferred way to write R code.
trouble's approach gives me more of the IDE/IntelliJ energy whereas telescope gives me more of the Sublime Text pop-over that (IMO) it pioneered (to me).
Does anyone use one over/instead of the other and if so, why?
Aussi improbable que cela puisse paraître, j'ai mis à jour mon livre sur #vim 12 ans après 😅 https://vimebook.com/fr
Le contenu reste sensiblement le même, j'ai juste refait tous les screenshots, vérifié tous les liens, utilisé vim-plug au lieu de pathogen, fzf au lieu de ctrlp, vim-fern au lieu de TheNerdTree. Bref, c'est pareil, mais en mieux. Reste la version anglaise à mettre à jour, puis passer à l'écriture du prochain sur #neovim !
Merci pour tous les retours que j'ai eu ici ❤️
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.
• de 10h à 11h, une conférence « ergonomie vimiste » pour découvrir ou approfondir l’ergonomie des éditeurs modaux (tous niveaux) ;
• de 16h à 18h, un atelier « tupperVim » pour partager des connaissances sur nos éditeurs préférés (niveaux débrouillés / confirmés / experts).
I'm about to update my book on #vim but as I am now mostly using #neovim, I'm a little bit outdated about #vim plugin management. What would you recommend instead of pathogen (for vim, not for neovim)?
I'm playing around with #LazyVim and a clean config. Not sure if this is a LazyVim question, or a #Vim question, or an #nvim question, but what are the keyboard shortcuts for these autocomplete dropdowns? Is this "omni" completion?
<c-n> for next item, <c-p> for previous, enter to accept the suggestion? Is there anything else? I'm not sure where to find these in the help
With the minus key being the default #Netrw (and oil.nvim) shortcut for "change into parent directory", TJ DeVries suggested to globally (i.e. in normal edit buffers) map minus to "open Netrw (or oil) in the current window", and I think that's really clever.
Like, <CR> moves down into a directory or file, and - moves up into the parent directory – either of the directory you're currently browsing, or the file you're currently editing. Like a global "zoom out" key.
Recently picked up that an "IDE" is a largely uncustomized, out-of-the-box experience, and that (Neovimmers) call the result of their customizations a "PDE", a "Personal Development Environment" instead.
Made me wonder:
Is the notion that IDE's are what they are, mostly unchangable, a common one?
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
Ich habe gerade mit „Erschrecken“ festgestellt, wie lange ich schon PhpStorm nicht mehr geöffnet habe. Das war eine Update-Orgie, die einem Windows alle Ehre gemacht hätte. Und dabei wollte ich nur schnell mal einen Blick auf den Datenbank-Client werfen. Weil ich sowas in der Art jetzt auch direkt in neovim habe: https://www.insomniaonline.de/ein-datenbank-client-in-neovim#neovim#database