social.dk-libre.fr is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
Decided to take part in the Vim Carnival hosted by @hyde
So how do I use vim, or neovim really? Check it out: https://claytonerrington.com/blog/how-i-use-neovim/
This is a great tool and has lots of features, and I'm still only scratching the surface of what I could do.
Woohoo ! Ma proposition de conférence au Capitole du Libre vient d’être acceptée : « Navigation Vim : la vie après HJKL »
https://cfp.capitoledulibre.org/cdl-2025/talk/review/W8LGZEQQH77PTPCN8UJ3WBXM3HKTZNZW
Ça sera le 15 ou 16 novembre à Toulouse. J’y serai tout le weekend, notamment sur le stand des #Ergonautes où on pourra parler #Quacken, #Arsenik, #Ergol, #QwertyLafayette…
Merci à l’équipe du @capitoledulibre de valider si vite les propositions, ça facilite l’organisation. Courage à vous !
Okay, so apparently in a recent version, #vim has changed the way that it determines whether the colors used are suitable for a light or dark background.
HOW DO I DISABLE THIS ENTIRELY?!?!?!
I don't want vim to ever change my color scheme. I only open vim in terminals with a black background, and...... I am dead serious here. I want it to run with "set background=light"
Yes, I know what background=light|dark does, you don't need to explain it to me.
Yes, I want the supposedly "good for light background text colors," on a dark background. That is how my eyes work.
My problem is, I have had "set background=light" in my ~/.vimrc for literally years now, and now, all of a sudden, vim is opening files with background set to dark. If I manually change it while in command mode, it does so. But is ignoring my ~/.vimrc.
Anyone have any ideas on a fix?
Edit:
For the curious, my ~/.vimrc works as intended in vim 9.1.1563. This behavior began when I updated to 9.1.1723. I'm too annoyed to deal with this right now, I have reverted to the earlier version.
It replaces Maps since you’re not going outside. 😅⌨️
This could be @nixCraft 's setup.
#Mobile #Advertising #Marketing #Technology #Design #Humor #Funny #Meme #TechMeme #Tech #Internet #Apps #Software #Digital #SocialMedia #Innovation #TechHumor #Technology #Smartphone #Google #YouTube #Media #Streaming #Apple #LinuxGaming #Gaming #Linux #OpenSource #TechNews #iOS #Android #FOSS #DeGoogle #Vim #Privacy #Security #Microsoft #Windows #DigitalLife #Coding #Programming #Development #Developers
Tabs vs spaces has always been a controversial topic. Thankfully, #vim isn't biased in any way.
To convert spaces to tabs, use `:set noexpandtab`, then `:retab!`.
Convert tabs to spaces with:
:set expandtab
:set tabstop=4
:set shiftwidth=4
:retab
@ploum What I mostly use, however, is a self-written program which is loosely based on "rem" but tailored to my needs. And while I would agree that a text-file-based calendar is suitable for most things (and the simplicity and elegance of the calendar.txt format appeals a lot to me), there are a few reasons why I would probably not want to rely on it alone:
* I would have to look up the dates for certain events like moving holidays or moondays by other means (and I would have to *remember* looking them up beforehand).
* I like to be able to be reminded about certain events in advance.
* Sometimes, I might be interested in recurring events rather far in the future, which I would likely not have entered manually in a text file at that point (this is rather an edge case, admittedly).
Yet, I like the calendar.txt format pretty much, and I guess I will use it alongside my own program for a while and see how it works out.
Also, it is pretty easy to create a #Vim syntax file for the format, which might make editing it even more pleasant!
(2/2)
La guida deinitiva per la degooglizzazione
💬 Rilanciato nel gruppo lemmy sull'Open Source: @opensource@diggita.com
TIL how to spell check in vim
https://blog.thomasdamgaard.dk/posts/2023/10/29/use-spell-checking-in-vim/
Today is officially the first day for the #Vim Carnival
September's topic is 'How do you use Vim?'
It's not specific to Vim, if you are interested, you can also write about #Neovim or #vi 😉
#blogging #blog #FLOSS #editors #terminals #carnivals #indieweb
#100DaysToOffload : 88/100
Lorsqu’un geek s’est définitevement mis à #ergol sur un clavier ergonomique, on dit qu’il est "casé"
Et vous savez le bruit que font les touches d’un ergonautes qui tape hyper rapidement dans #vim ? Elles font "jousssssss"
Et le bruit d’une blague particulièrement débile devant un auditoire silencieux ?
Elle fait "ploum"
De rien
poke @vjousse et @fabi1cazenave
Side effect imprévu et très appréciable de ne plus avoir de compte sur Facebook/Insta : tu n’es plus obligé de répondre à des messages random de joyeux anniversaire 😍
Autre side effect sympa ce jour là dans tes mails : tu as un rappel de qui a des infos sur toi alors que tu ne voudrais pas.
Content que cette date soit redevenu moins pénible pour moi ❤
(le premier qui me le souhaite ici devra se mettre à #vim immédiatement, alors faites attention à ce que vous faites, je vous vois ! 😁)
#Atuin update: I've come to rely on it. It's a must have for my daily shell usage. Works great everywhere ... except on #GitBashForWindows. Lots of problems there. Here's how I solved them:
* Install `ble.sh`. Use `curl` to do this. Do not get it with Git. Do not attempt to build from source.
* Install by sourcing `ble.sh` at the **end** of your `.bashrc`. That's how the instructions about getting it with `curl` tell you to do it. The Git based instructions want you to say something different in your `.bashrc`. You want the `curl` instructions.
* In my install, #Ble was too slow out-of-the-box. Missed keystrokes, etc. I copied the `blerc.template` from the GitHub repo to a local `~/.blerc`, and edited it to disable almost every kind of completion and also syntax highlighting. Speed is now acceptable. (Might be that my #Windows box is too slow. That seems unlikely.)
* I use `vi` mode; #Vim. `ble.sh` picks that up from my `.inputrc`; #Readline. I use #Starship for my prompt. I had to disable in `.blerc` the showing of my current `vi` state (insert, visual, command, etc) and also edit `.inputrc` to not add characters to the prompt to show insert vs command mode. Those changes let me have my normal `starship` prompt.
I do have one problem remaining. It's not related to `atuin`; it's related to the command line itself. In #Bash and #Zsh, it's easy for me to be on the command line and get what I've typed so far directly into my editor; #HelixEditor. Usually something like Esc-v or the like. `ble.sh` doesn't seem to have a way to do that, but maybe I just haven't found it yet.
Le LSP vue_ls qui a besoin de vtsls, mais j'ai beau configurer les deux, ça ne marche toujours pas. Je vais clamser. 💀
Bon je galère avec Neovim, j'ai besoin de votre aide.
J'ai treesitter et treesitter-textobjects.
J'essaye de réindenter un fichier .vue. Il y a donc un mélange de HTML, JavaScript et SCSS. Pour HTML et JS ça s'indente correctement, pas d'erreur dans l'arbre des noeuds.
En revanche, le SCSS ne s'indente pas bien. Il y a des ERROR dans l'arbre de TreeSitter. Après avoir joué un peu avec, j'ai l'impression que ça bug à cause de :has et de @\extend.
Avez-vous une idée pour m'aider à résoudre mon problème ?
Edit : j'ai aussi vue-language-server en LSP.
Merci par avance. Svp retoots 🙏
@ThierryStoehr Mince, j’avais jamais entendu parler du @CampusDuLibre ! Mais n’étant plus étudiant ni vacataire, je crains que cet évènement ne s’adresse pas à moi.
Par ailleurs, pendant ce weekend du 15-16 novembre 2025 il y a le #CapitoleDuLibre où on aura plein de choses à présenter : #Ergol, le #Quacken, peut-être aussi une conférence #Vim et un atelier #tupperVim… La vie est une suite douloureuse de choix !