Ok, #nVim / #vim and Telescope... I find it bizarre how it auto-ignores anything listed in a .gitignore file.
I still want to find and edit things like .env files, they just shouldn't be in Version Control.
And editing Telescope to explicitly allow certain file names even if they're listed in .gitignore seems to be impossible. Which leaves you choosing to show all hidden files, which I absolutely don't want because node_modules etc I never want.
@mattwilcox it looks like you can set up a separate keybinding to override the default behavior of fd to use the -no-ignore flag:
-- Custom function to find files ignoring .gitignore
local function find_files_ignore_gitignore()
telescope.builtin.find_files({
find_command = { 'fd', '--type', 'f', '--no-ignore' }
})
end
-- Bind the custom function to a key
vim.api.nvim_set_keymap('n', '<leader>fg', "<cmd>lua find_files_ignore_gitignore()<CR>", { noremap = true, silent = true })
@elroyjetson Hmm, I'll have a play with that thanks. Still find it a bit weird you cant just pass it a lits of files like the content of the gitignore already works. Or point to a file such as .telescopeignore while telling it to not parse gitignore
I don’t think #helix will replace #vim they have different models and vim is religion . Also #helix luck a lot of #vscode out of box ide features like import fix or linter auto fixes and suggestions etc. but I like editor . I am happy to learn how to add missed features !
@vpavlyshyn As a Vim user, I tried Helix several times, but the way selection and action are two distinct steps just seems a lot less flexible. Even with fluency, actions would always be slower.
However, the way it comes with batteries included is pretty neat, and if you don't have a working Vim setup, Helix allows you to start coding immediately with much less hassle.
• 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).
@jdll Le dimanche 26 mai à 13h, dans le cadre des #JdLL, je vous propose un atelier consacré à l’ergonomie des claviers où l’on mettra en œuvre deux types d’outils :
• #kalamine, pour créer ou modifier sa disposition de clavier préférée ;
• #kanata et #arsenik, pour émuler des fonctionnalités de claviers programmables sur son clavier de laptop.
@jdll Tout le weekend des #JdLL, on tiendra avec la communauté des #Ergonautes un stand dédié aux claviers ergonomiques. Il y aura plein de claviers à essayer : Ferris, Atreus, Model01, Planck, Preonic, Iris…
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 ❤️
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
@annika Typically <c-y> will accept . Many of the autocompletions are probably provided by nvim-cmp, rather than native. I don't personally use Lazyvim so I'm not sure how it's divided up.
@dpom I think the autocompletions themselves are coming from Intelephense via the LSP, but I do see a lot of nvim-cmp bindings in :imap. Thank you for the pointer, I'll see how much more I can tease out based on this
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.
In addition of using the minus key to open #Netrw for the current file's parent directory, I've now added some logic to Netrw buffers in my #Vim config that will try to position the cursor on the file that you've just edited, for additional continuity.
@aburka The solution is to pick one, and stick with it. I chose to only split with tmux. The different panes let me see the forest. When i need to see the trees, I’ll zoom the window so that it’s full screen.
The only time i split with vim nowadays, is if I need to copy from one part of a file to another part of the file.
if you need to use both equally, I’d suggest you update your leader / prefix bindings to make splits predictable.
@thet i do have hls set, but it only does the first part of that, not the replacement preview, that’s apparently a neovim feature (inccommand), and it’s quite enticing, there are apparently some old plugins in the same directions for vim for it, i’ll probably give them a shot, but i might also try (again) to move to neovim in the near future. My config is large and depends on many plugins, so it feels like it’ll be a whole project 😅 .
Productivity increases with the level of customization you are making in the tools you are using most often.
The downside is that the more used to these customizations you get, the more lost you'll feel when
using a system that is not configured as yours.
Simple example: create a new binding in #Vim or #Emacs. This is not only very common but
also very encouraged. After getting used to that, connect to a remote server.
The only instance of non-editor "vim" I've seen was in a piece by Dennett arguing against the existence of qualia. The argument was something like: 'Imagine the property of a dollar that gives it meaning. Let's call it "vim".'
But it comes with every installation of #Vim and #Neovim, so as someone who enjoys minimalism and likes to keep the number of additional plugins to a minimum, I feel like I should learn to use it and integrate it into my workflow.
But I've just used :Rexplore on a dirty file with 'nohidden' and it simply replaced my file's contents with the directory listing 😬
Also, don't make the mistake of looking at its source, or visiting the maintainer's "website" …
To be honest, I don't care that much for the splits to be equal in size. But I am using a tiling window manager, and whenever I'm opening a new terminal on the screen Vim is on, it will result in what was a 50:50 window split in Vim now being one window that's almost the same size as before and the other one being 1 row high, and that's unacceptable.
My favorite solution would be Vim tracking window sizes in percentages of the terminal, and trying to keep these constant, but this works too.
:syntax match WordsWithNumbers /\w*\d\w*/ containedin=ALL contains=@NoSpell
...but that will also prevent other highlighting from starting inside those words, which may or may not be an issue for you.
If it is an issue, you might be able to get around it by tacking on an extra contains=ALL, but it really depends on the rest of your syntax highlighting as to whether that will improve things or make it worse!
Curious about how many Vim/Neovim plugins you’re rocking? 🤔 Jump into your terminal, navigate to your Vim or Neovim configuration directory, and run this command: ls -alp | wc -l. I currently have 41 plugins, but I’m aiming to slim down to 30-35. How about you? Share your plugin count below! #Vim#Neovim#Plugins”
@seve_py@tartley When I redid my config of about 6 months from scratch, I ended up with way fewer plugins than before. There truly were a good amount that I just installed for fun or that I quickly got used to not having (sometimes leading me to use more idiomatic practices). It’s a good thing to try every now and then, free time permitting. But there’s also no harm in having a bunch of plugins you like!
