#vimdiff
Live, measured metrics for the hashtag #vimdiff from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #vimdiff
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-08-01 05:49 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-08-01 05:49 UTCNo related tags with measured usage found for #vimdiff.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-08-01 05:49 UTCEverything below is measured over the latest 5 public posts (spanning ~56433 hours).
Posting hours (UTC)
Languages: English (5)
Avg boosts / post: 0.8
Top of the latest posts
For years I've been using `vim -d` (or `vimdiff`) on two or more files to compare them and see the differences. I just learned that there are special commands for working with diffs in `vimdiff`: `]c` moves the cursor to the next block of d
I was always scared of #Git's default merge tool, #vimdiff. But today i decided to learn the basics: https://www.rosipov.com/blog/use-vimdiff-as-git-mergetool/
Anyone know a faster way to get through merge conflicts? Preferably on the terminal, I'm imagining a 'git add -p' style interface that shows all conflicts in all tracked files but with options to accept current or incoming like in vs code.
What “vimdiff” means
WikipediaVim is a free and open-source text editor. Vim provides both a terminal screen user interface as well as a graphical user interface.
“Vim (text editor)” on Wikipedia (CC BY-SA) →#vimdiff across platforms
every network with a public tag surfaceFollow #vimdiff straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/vimdiff