101010.pl is one of the many independent Mastodon servers you can use to participate in the fediverse.
101010.pl czyli najstarszy polski serwer Mastodon. Posiadamy wpisy do 2048 znaków.

Server stats:

486
active users

#vim

4 posts4 participants1 post today
Continued thread

The split keyboard didn't work for me:
- Too much hassle carrying it around and setting it up every time.
- Just a fraction more comfortable typing, but lack of the trackpoint and touchpad makes them less ergonomic (literally more painful to use).

Too more things to try:
- To setup a monitor at home location to uncurl my back a bit.
- To configure meow modal editing :: less modifiers usage, less wrist bending. BTW, it's far better modal editing than Vim's.

[1/1]

#keyboard#emacs#vim

I came across a program that I might find useful[1] (at least until I decide if I can replace #Obsidian with something based on #vim) but it requires cargo to install it, which require #rustlang and its ecosystem.

Since I don't plan on programming in #rust is the hassle to install it worth it?

[1] github.com/erikjuhani/basalt

GitHubGitHub - erikjuhani/basalt: TUI Application to manage Obsidian notes directly from the terminalTUI Application to manage Obsidian notes directly from the terminal - erikjuhani/basalt
vi/m users, do you remap Esc?

#vi #vim
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

Vim Protip: change the background color to black after setting the colorscheme.

" ~/.vimrc
colorscheme ...
syntax on

highlight Normal ctermbg=black
highlight LineNr ctermbg=black
highlight NonText ctermbg=black

" ~/.gvimrc
highlight Normal guibg=black
highlight LineNr guibg=black
highlight NonText guibg=black

Trying out new Vim colorschemes. Curious what others use? I'm looking for a bright theme (aka not pastel) that goes well with a black background. Also want different colors for keywords vs names/identifiers; i.e. class and Foo should have different colors. Please no colorschemes that set gui=italic!

I like molokai, but it uses the same color for keywords and identifiers. I also like abstract, but it uses italics.

Trying out new Vim colorschemes. Curious what other Rubyists/Crystalers use? I'm looking for a bright theme (aka not pastel) that goes well with a black background. Also want different colors for keywords vs names/identifiers; i.e. `class` and `Foo` should have different colors. Please no colorschemes that set `gui=italic`!

I like molokai, but it uses the same color for keywords and identifiers. I also like abstract, but it uses italics.

Recently started learning #morsecode , although it's completely useless to me. Sometimes it helps to understand why things developed like they did when you go back in time, when remote communication started. And I love having a #lowtech fallbacks.

It's like learning #ed in order to understand concepts of #vim.

Replied in thread

@bortzmeyer Mais alors... « Oui, #Emacs est la réponse à toutes vos questions : la prise de notes, la rédaction de documents, le courriel, l'écriture de code, le tableur, l'organisation des tâches, le calendrier, le microblogging et tout le reste ! »
Sans oublier, en préambule : « Le #format texte est ultrapuissant à condition d'utiliser avec un éditeur de texte puissant. »
Et là, parfois, peut se glisser ceci : « #Vim est aussi un éditeur de texte puissant. Mais il ne fait pas OS comme Emacs. »

Markdown, Emacs, and Vim walked into a bar…
…and thanks to some rather pleasant people hereabouts, we have some punchlines in this week's #ptpl.

The good news is, of course that the way you edit and format matters very little so long as you're having fun doing it.

#emacs #vim #markdown

Blog ellanew.com/ptpl/161-2025-06-1
Medium medium.com/@miscellaneplans/ma

ellanew.comPTPL 161 · Markdown, Emacs, and Vim Walked Into a Bar… - Ellane WWhatever the punchline, the way you format matters less than how much fun you're having doing it