eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Server stats:

225
active users

#VIM

4 posts4 participants1 post today

Following up from a recent post I saw, I asked a #ai #chatbot to make up 3 personas based on #emacs, #vim and #vscode. The outcome was rather predictable:

```
**Richard (Emacs User)**

* **Core Drive:** Ultimate control and extensibility. Richard sees Emacs not just as an editor, but as an operating system for his programming life.
* **Cognitive Style:** Deeply analytical and enjoys understanding underlying mechanisms. He thrives on dissecting problems and building intricate, interconnected solutions.
* **Workflow:** Highly customizable and ritualistic. Richard has spent years tuning his environment, developing bespoke functions and keybindings that automate complex tasks. He likely uses Emacs for everything from writing code to managing email and reading RSS feeds.
* **Temperament:** Patient, persistent, and deeply intellectual. He's not afraid of a steep learning curve and finds satisfaction in mastering complex systems. He may be perceived as a purist or a bit of a Luddite by some, but he values depth over breadth.
* **Social Interaction:** Might be more reserved, comfortable in his well-crafted digital space. He enjoys engaging in deep technical discussions but might find casual chat less stimulating.

**Eric (Vim User)**

* **Core Drive:** Peak editing efficiency and modal mastery. Eric views editing as a craft where speed, precision, and fluidity are paramount.
* **Cognitive Style:** Tactical and focused on immediate, high-impact actions. He excels at identifying patterns and applying sequences of commands to achieve results rapidly.
* **Workflow:** Optimized for speed and minimal hand movement. Eric's muscle memory is his primary tool. His environment is likely lean, with essential plugins, designed for quick context switching and fluid navigation through code.
* **Temperament:** Pragmatic, results-oriented, and often confident. He appreciates elegant solutions that are immediately effective. He might be seen as sharp and direct, valuing brevity in communication as much as in editing.
* **Social Interaction:** Likely enjoys banter and competitive coding challenges. He's often passionate about his tools and enjoys sharing tips and tricks, but can also be fiercely opinionated about the superiority of his chosen method.

**Steve (VS Code User)**

* **Core Drive:** Broad functionality and seamless integration. Steve wants a powerful, all-in-one tool that "just works" and connects easily with other development services.
* **Cognitive Style:** Pragmatic and solution-oriented, valuing immediate utility and a low barrier to entry. He's adept at leveraging existing tools and readily adopts new features that enhance productivity.
* **Workflow:** Highly curated but less "built from scratch." Steve likely utilizes a rich ecosystem of extensions to add specific functionalities (linters, debuggers, Git integration, etc.). His environment is productive with minimal initial configuration, and he enjoys the visual feedback VS Code provides.
* **Temperament:** Sociable, adaptable, and generally enthusiastic. He enjoys collaboration and is quick to adopt popular trends and tools that streamline team workflows. He might prioritize getting the job done with the most accessible, well-supported tools.
* **Social Interaction:** Very team-oriented and collaborative. He's likely to be involved in code reviews, pair programming, and actively seeking out the best tools to facilitate team success. He's often an early adopter of new technologies.
```

I had tried #emacs in the past… mostly with that german pornographic mental pain in the ass and leaving it shortly. just envying all folks who found it useful after all. It’s been magic to observe emacs people at work. But now with #helix being smooth like silk to me… I just figured it out, I’m more a #vim person, not emacs person and that’s fine. :)

Created a Neovim :neovim: configuration for writing Ansible playbooks/roles/collections. With linting, auto-completion, highlighting of blocks, indentation, git integration and nice UI.

If someone is interested, I put it on my Codeberg here: codeberg.org/Larvitz/nvim-ansi together with a README.md, that explains keybindings, installation instructions etc.

It's also good for Python software development and contains the LSP definitions for that as well. But the primary goal, was to create an Ansible development environment with all bells and whistles :-)

#nvim#neovim#vim

Spent the afternoon using vim to edit out a schema design plus notes.

What a relief it is to not have to go back and “fix” the intended spellings and inadvertent capitalizations for each line.

Stupid AI🔥

I can type almost as fast as my brain using muscle memory and vim.

(Yeah, yeah emacs if you prefer)

#vim#noai#ai
Replied in thread

@arveed @ploum @loevenbruck juste pour recontextualiser : je suis très content d’être passé à #ergol. J’ai plein d’avantages (notamment dans mon utilisation de #vim et de claviers plus compacts) qui font que je ne reviendrai pas en arrière. Mais clairement avoir 15 ans de bépo en touch typing dans les doigts pénalise ma transition.
Je pensais juste que je retrouverai le confort que j’avais en bépo plus vite, mais force est de constater que non, mais je suis sûr que ça va venir !

I've been using the #HelixEditor as my daily driver for the better part of a year now and I couldn't be more happy with it. I've managed to get a near-IDE setup and experience thanks to zellij and some awesome TUI tools.
This article aligns well with my experience, I recommend reading it if you're "modal editor curious" or dissatisfied with your (neo)vim config maintenance burden.

herecomesthemoon.net/2025/06/i

MOND←TECH MAGAZINE · I really like the Helix editor.‘Search & Replace’ popup windows are bad user interface design.
Replied in thread

@ploum @insolit @fabi1cazenave bonne idée pour l’article 😊
Le mapping c’est celui-ci : github.com/vjousse/dotfiles/bl
Altrgr+r ou Altgr-t en #Ergol ça fait + et - pile poil là où j et k sont placés habituellement pour #vim
Donc c’est comme si j’avais mes touches j k à l’emplacement #vim classique sauf que je dois rajouter Altgr pour les activer.
Yes pour le / j’utilise Altgr+i !

GitHubdotfiles/nvim-lazy/lua/core/keymaps.lua at master · vjousse/dotfilesMy very own dotfiles (sway, neovim, zsh, wezterm). Contribute to vjousse/dotfiles development by creating an account on GitHub.
Hey fedi friends, what are the differences in USES and config options listed at #freshports for a #FreeBSD #port? I am familiar with USE in #Gentoo #Linux, which seem to be the config options here? For #Gentoo it is very common to use different USE settings for a packages, but for #FreeBSD I read from porter's handbook there are not many USE items and they looked different from the term in #Gentoo. I am still trying to wrap my head around what is happening that whenever I try to build a port, like #vim or #git in tiny flavors, I constantly noticed #Perl #Bash #lua #Rust #Python and all other seemingly unrelated stuff get pulled in. #BSD #RunBSD #Unix #FOSS
www.freshports.orgFreshPorts -- The Place For Ports - Most recent commitsMost recent commits