mastodontech.de ist einer von vielen unabhängigen Mastodon-Servern, mit dem du dich im Fediverse beteiligen kannst.
Offen für alle (über 16) und bereitgestellt von Markus'Blog

Serverstatistik:

1,5 Tsd.
aktive Profile

#vim

7 Beiträge7 Beteiligte0 Beiträge heute

I've been sitting in my comfy #Markdown cottage, sipping a nice warm drink and eyeing off Vim and Emacs out the window. Wondering if I'll go play with one or the other, or leave 'em both to it.

But then it hit me — I'm a Keyboard Maestro user who's always making macros for things I do often, using keyboard shortcuts that often begin with ":" followed by a series of letters.

Well I'll be! I've been creating a vi-like environment for years without knowing what I was doing.

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

TUI Application to manage Obsidian notes directly from the terminal - 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
Antwortete im 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 !

My very own dotfiles (sway, neovim, zsh, wezterm). Contribute to vjousse/dotfiles development by creating an account on GitHub.
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.
Antwortete im Thread

@sfwrtr If you want to use these in vim, you need to convert them as follows:

  • | becomes \|
  • (?: becomes \%(
  • ) becomes \)
  • \b at the beginning of a word becomes \<
  • \b at the end of a word becomes \>

That is:

  1. can\>\|can't\|can not\|could\>\|couldn't\|cannot\|shall\>\|shan't\|shall not\|should\>\|shouldn't\|should not\|would not\|\<would\>\|\<wouldn't\|with\>\|without\|\<were\>\|\<weren't\>\|neither\|\<either

  2. write\>\|\<right\|lead\>\|\<led\>\|lede\|choose\|chose\|\<to\>\|\<too\>\|\<two\>\|\<it\>\|\<it's\>\|\<lay\>\|\<lie\|\<lain\|dye\|\<die\|\<dying\|\<loss\|loose\|losing\|loosing\|access\|assess\|accept\|except

  3. ly\>\|\<about\>\|almost\|already\|barely\|\<bit\>\|begin\|\<began\>\|\can\|certain\|generally\|\<guess\|\<just\>\|kind\|\<like\|maybe\|mostly\|near\|course\|pretty\|perhaps\|possibly\|potentially\|really\|probably\|\<seem\|\<some\>\|sort\|start\|\<still\>\|surprisingly\|suppose\|\<think\>\|usually\|could\|\<saw\>\|\<heard\>\|\<felt\>\|\<knew\>\|\<read\>\|noticed\|recognized\|\<and\>\|\<but\>\|\%(I\|he\|she\) could \%(see\|hear\|taste\|touch\)\|\%(I\|he\|she\) \%(saw\|hear\|knew\|read\|felt\|noticed\|recognized\) that

Also, make sure hlsearch is on so all matches are highlighted visually.

Helix-Vim – A Vim-like configuration for Helix

I like Helix, also because I'm a Rust fanboy, but I'm used to Vim use and only now discover this configuration. Let me delve deeper into the configuration of the editor again.

🧑‍💻 github.com/LGUG2Z/helix-vim

A Vim-like configuration for Helix. Contribute to LGUG2Z/helix-vim development by creating an account on GitHub.
GitHubGitHub - LGUG2Z/helix-vim: A Vim-like configuration for HelixA Vim-like configuration for Helix. Contribute to LGUG2Z/helix-vim development by creating an account on GitHub.
#helix#vim#code
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.