# vim Published articles for vim. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Security updates for Tuesday DevFeed: [Security updates for Tuesday]() Original publisher: [Read original article]() Author: jzb Published: 2026-09-15T13:10:46Z Content type: news Language: en Sources: [LWN.net]() Topics: [Security](), [Debian](), [Fedora](), [Ubuntu](), [Linux](), [Grafana](), [nginx]() Tags: [debian](), [grafana](), [hat](), [java](), [linux](), [mozilla](), [network](), [nginx](), [openssl](), [php](), [podman](), [python](), [rust](), [security](), [systemd](), [ubuntu](), [updates](), [vim]() ### AI overview Debian, Fedora, Mageia, Red Hat, SUSE, and Ubuntu issued security updates for a broad range of packages and components, including Linux-related tools, libraries, servers, programming environments, and desktop software. ### Source excerpt Security updates have been issued by Debian (network-manager-l2tp and urwid), Fedora (perl-Dancer2, perl-Data-Entropy, perl-DBI, perl-Protocol-HTTP2, podman-tui, rust-lru, and rust-lru0.16), Mageia (bzip2, cups-filters, libcupsfilters, libssh2, perl-Authen-SASL, perl-HTML-FormFu, tar, unzip, and zip), Red Hat (grafana and image-builder), SUSE (389-ds, acl, attr, apache2-mod_auth_openidc, apr-util, aws-nitro-enclaves-cli, bzip2, c-ares, clamav, cpio, curl, dhcpcd, dovecot23, dovecot24, dracut, emacs, fuse-overlayfs, go1.25-openssl, go1.26-openssl, google-cloud-sap-agent, google-osconfig-agent, govulncheck-vulndb, gstreamer-devtools, gzip, helm, java-17-openjdk, java-21-openjdk, java-25-openjdk, jq, libBasicUsageEnvironment2, libgpg-error, libidn, librest, libusb-1_0, libvirt, LibVNCServer, libzypp, zypper, lkl, mcphost, MozillaFirefox, mozilla-nspr, mozilla-nss, rust-cbindgen, MozillaFirefox, mozilla-nss, mozilla-nspr, rust-cbindgen, MozillaFirefox, MozillaFirefox-branding-SLE, mozilla-nspr, mozilla-nss, rust-cbindgen, msgpack-c, multipath-tools, NetworkManager, openexr, openssl-3, perl-Protocol-HTTP2, perl-URI, php-composer2, postgresql14, postgresql15, postgresql16, postgresql17, postgresql18, python-aiohttp, python-cryptography, python-h2, python-ruff, python-sqlparse, python311, python312, python39.SUSE_SLE-15-SP3_Update, rav1e, rpcbind, sssd, systemd, tomcat, tomcat11, ucode-intel, udisks2, vim, and wicked2nm), and Ubuntu (cgit, dracut, freeciv, konsole, libinput, linux-azure, linux-nvidia-7.0, nginx, vips, and yelp). ## Tools DevFeed: [Tools]() Original publisher: [Read original article]() Author: Kaushik Gopal Published: 2026-09-15T04:00:36.743345Z Content type: article Language: en Sources: [Kaushik Gopal's Site]() Topics: [Programming](), [Cloudflare](), [Terminal](), [Vim](), [Hugo](), [Firefox](), [macOS](), [Obsidian](), [Font]() Tags: [cloudflare](), [firefox](), [hugo](), [mac](), [macos](), [programming](), [programming-font](), [terminal](), [tools](), [vim]() ### AI overview A personal tools page listing services, programming tools, macOS applications, audio equipment, desk items, and physical products. It mentions Buttondown, a customized Hugo site deployed on Cloudflare Pages, Ghostty, tmux, Vim, Zed, Obsidian, Raycast, Firefox, CleanShot, and Logic Pro. ### Source excerpt Bits ## Services ### Newsletter via Buttondown Statically generate site with Henry (highly customized Hugo theme) Deployed on Cloudflare Pages Programming ### Berkeley Mono is my programming font of choice Ghostty for terminal stuff (along with tmux) Within the terminal I'm almost entirely using Vim. Zed as my regular text editor MacOS ### Obsidian for notes & todos Raycast is my launcher Firefox for browsing CleanShot for screenshots on my mac Logic Pro for editing AI Stuff ### With AI evolving so fast, my tag ai-model-choice is a better place to track what I'm using. Atoms ## Desk ### Nordik Leather Desk Mat LEUCHTTURM1917 Soft cover journal dotted Uniball Deluxe 0.5mm Micro pens Audio ### Earthworks Ethos - 400 microphone USBPre 21 audio interface AirPods Max (yes for podcasting!) Physical ### I drive a Tesla Model Y (and eagerly waiting to move to an R3) These are no longer sold but are built like a tank. I'd probably pick the Motu 2 if my USBPre 2 ever fails ↩︎ ## Seven years of bitwise: a weekend project, a Hackernews front page, and the long road into Debian DevFeed: [Seven years of bitwise: a weekend project, a Hackernews front page, and the long road into Debian]() Original publisher: [Read original article]() Author: Ramon Published: 2026-09-11T15:21:24Z Content type: opinion Language: en Sources: [Ramon Fried]() Topics: [Software](), [Command-line interface](), [Debian]() Tags: [c](), [command-line](), [debian](), [hacker-news](), [linux](), [ncurses](), [open-source](), [packaging](), [software](), [vim]() ### AI overview A developer reflects on seven years of maintaining bitwise, a terminal calculator, from its initial release through feature development, Hacker News attention, and packaging in Debian and other distributions. ### Source excerpt I started bitwise because I was tired of opening the KDE calculator. Seven years, one Hacker News front page and sixteen distributions later, here's what I learned -- mostly about how hard it is to get software to people. ## What is the Super key in Omarchy? DevFeed: [What is the Super key in Omarchy?]() Original publisher: [Read original article]() Author: Roger Perkin Published: 2026-09-11T09:52:11Z Content type: tutorial Language: en Sources: [Roger Perkin Network Automation Consultant]() Topics: [navigation](), [Cheat sheet](), [configuration](), [Terminal](), [App]() Tags: [cheat-sheet](), [commands](), [faq](), [shortcuts](), [terminal](), [vim](), [windows]() ### AI overview This tutorial explains that Omarchy uses the Super key as the primary modifier for system navigation and shortcuts. It describes ten shortcut categories, including launching applications, closing windows, opening a terminal, changing layouts, viewing keybindings, navigating windows, switching workspaces, and moving windows between workspaces. ### Source excerpt In Omarchy, the Super key acts as the primary modifier key for almost all system navigation and shortcuts, functioning as the Windows key on standard keyboards or the Command key on a Mac layout Based on standard Omarchy configurations and recent Hyprland window manager defaults, here are the top 10 essential Super key combinations you need to know for ... ## Vim wants you to control, VSCode wants you to consume DevFeed: [Vim wants you to control, VSCode wants you to consume]() Original publisher: [Read original article]() Author: Hillel Wayne Published: 2026-08-18T16:26:05Z Content type: opinion Language: en Sources: [Newsletter feed for Hillel Wayne's Newsletter]() Topics: [Vim](), [Neovim](), [Visual Studio Code](), [configuration](), [Emacs]() Tags: [command-line](), [config](), [configuration](), [vim](), [vscode]() ### AI overview The article contrasts Vim and Neovim's programmable, state-oriented configuration with VSCode's static configuration and fixed built-in commands. It argues that Vim-based editors provide substantially more direct control over editor behavior, while also requiring more configuration and commitment. ### Source excerpt Newsletter updates were sporadic in July because of two weddings, two conferences (with two different talks!), and finishing Logic for Programmers. Huge thank you to everybody who bought a copy, as well as for your patience with the schedule. There's some podcast appearances, a conf talk, and a book sale at the end of this post. Newsletter updates will be sporadic in August because I just started my Developer Educator job at Antithesis. I'll have less time to write because I'll be working 40 hour workweeks, about 8 hours of which being actual work and the other 32 being bashing my head against NixOS. NixOS is the standard developer OS at the company. It's also a notoriously difficult distro to learn even for Linux heads, and I'm coming from Windows. The only way I am going to get anywhere is to go all in and commit fully to the NixOS philosophy.1 For one, I'm seeing how long I can last without my customary 2000-line Neovim config. Which immediately raises the question as to why I have 2000 lines of Neovim config. It's because Vim2 (and Emacs) think of configuration in a very different way than more popular editors do. Control and Consumption Say we want to make ctrl+n to save the current file. In VSCode, you put this in keybindings.json: [ { "key": "ctrl+n", "command": "workbench.action.files.save" } ] In Neovim, you put this in init.lua: vim.keymap.set('n', '', function() vim.cmd.write() end) Now, a couple of differences to see. First, the VSCode example is invoking a fixed, built-in command, while Neovim can bind an arbitrary function. Second, in VSCode you edit a static configuration file with static data, while in Neovim you execute a command that edits the running editor state. In fact, it doesn't even need to be in a configuration file: you can add a new keymap directly from the command line. Though you'd probably instead do that command in the OG Vim way: map :w And that does something different than a function: it makes pressing ctrl+n mean "d ## Vim: por qué merece la pena frente a nano DevFeed: [Vim: por qué merece la pena frente a nano]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-08-01T13:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Vim](), [POSIX](), [Unix]() Tags: [alpine](), [distro](), [editor](), [posix](), [unix](), [vim]() ### AI overview A practical Spanish tutorial explaining why Vim is worth learning instead of nano. It covers how to exit, save, undo, and redo, then argues that Vim is widely available on Unix systems because vi is required by POSIX. It also discusses BusyBox, Alpine, and Vim's modes. ### Source excerpt Vim parece complicado pero no lo es: aprende a salir, moverte y editar con lo mínimo imprescindible, sin miedo y sin memorizar todo de golpe. ## Vim Classic 8.3.0 released DevFeed: [Vim Classic 8.3.0 released]() Original publisher: [Read original article]() Author: June 2 Published: 2026-06-02T00:00:00Z Content type: release Language: en Sources: [Drew DeVault]() Topics: [Vim]() Tags: [release](), [vim]() ### AI overview The author announces the first release of Vim Classic, a fork of Vim, version 8.3.0. ### Source excerpt Following up on my earlier announcement that I was forking Vim, I'm happy to announce the first release of my fork today: Vim Classic 8.3.0. I have written a release announcement for vim-classic.org, which you can read here. Happy editing! ## A eulogy for Vim DevFeed: [A eulogy for Vim]() Original publisher: [Read original article]() Author: March Published: 2026-03-25T00:00:00Z Content type: opinion Language: en Sources: [Drew DeVault]() Topics: [Vim](), [genai]() Tags: [personal](), [thoughts](), [vim]() ### AI overview The author reflects on Vim's profound personal importance, mourns its creator Bram Moolenaar, and considers Bram's values and legacy. The article also criticizes the environmental and social costs the author associates with generative AI. ### Source excerpt Vim is important to me. I'm using it to write the words you're reading right now. In fact, almost every word I have ever committed to posterity, through this blog, in my code, all of the docs I've written, emails I've sent, and more, almost all of it has passed through Vim. My relationship with the software is intimate, almost as if it were an extra limb. I don't think about what I'm doing when I use it. All of Vim's modes and keybindings are deeply ingrained in my muscle memory. Using it just feels like my thoughts flowing from my head, into my fingers, into a Vim-shaped extension of my body, and out into the world. The unique and profound nature of my relationship with this software is not lost on me. A picture of my right hand, with the letters "hjkl" tattooed on the wrist I didn't know Bram Moolenaar. We never met, nor exchanged correspondence. But, after I moved to the Netherlands, Bram's home country, in a strange way I felt a little bit closer to him. He passed away a couple of years after I moved here, and his funeral was held not far from where I lived at the time. When that happened, I experienced an odd kind of mourning. He was still young, and he had affected my own life profoundly. He was a stranger, and I never got to thank him. The people he entrusted Vim to were not strangers, they knew Bram and worked with him often, and he trusted them. It's not my place to judge their work as disrespectful to his memory, or out of line with what he would have wanted. Even knowing Bram only through Vim, I know he and I disagreed often. However, the most personal thing I know about Bram, and that many people remember about him, was his altruistic commitment to a single cause: providing education and healthcare to Ugandan children in need. So, at the very least, I know that he cared. I won't speculate on how he would have felt about generative AI, but I can say that GenAI is something I care about. It causes a lot of problems for a lot of people. It drives rising ene ## Some Fun Software Facts DevFeed: [Some Fun Software Facts]() Original publisher: [Read original article]() Author: Hillel Wayne Published: 2025-12-10T18:45:37Z Content type: article Language: en Sources: [Newsletter feed for Hillel Wayne's Newsletter]() Topics: [Software](), [Algorithms, Complexity](), [Simulation](), [ASCII](), [Vim](), [Cloudflare]() Tags: [algorithms](), [ascii](), [cloudflare](), [simulation](), [software](), [vim]() ### AI overview A year-end newsletter shares miscellaneous software facts, including a Game of Life implementation of Tetris, leap-second handling, Vim's computational capabilities, ASCII history, impractical faster algorithms, Cloudflare's lava-lamp randomness, and historical sorting-algorithm details. ### Source excerpt Last newsletter of the year! First some news on Logic for Programmers. Thanks to everyone who donated to the feedchicago charity drive! In total we raised $2250 for Chicago food banks. Proof here. If you missed buying Logic for Programmers real cheap in the charity drive, you can still get it for $10 off with the holiday code hannukah-presents. This will last from now until the end of the year. After that, I'll be raising the price from $25 to $30. Anyway, to make this more than just some record keeping, let's close out with something light. I'm one of those people who loves hearing "fun facts" about stuff. So here's some random fun facts I accumulated about software over the years: In 2017, a team of eight+ programmers successfully implemented Tetris as a game of life simulation. The GoL grid had an area of 30 trillion pixels and implemented a full programmable CPU as part of the project. Computer systems have to deal with leap seconds in order to keep UTC (where one day is 86,400 seconds) in sync with UT1 (where one day is exactly one full earth rotation). The people in charge recently passed a resolution to abolish the leap second by 2035, letting UTC and UT1 slowly drift out of sync. Vim is Turing complete. The backslash character basically didn't exist in writing before 1930, and was only added to ASCII so mathematicians (and ALGOLists) could write /\ and \/. It's popular use in computing stems entirely from being a useless key on the keyboard. Galactic Algorithms are algorithms that are theoretically faster than algorithms we use, but only at scales that make them impractical. For example, matrix multiplication of NxN is normally O(N^2.81). The Coppersmith Winograd algorithm is O(N^2.38), but is so complex that it's vastly slower for even 10,000 x 10,000 matrices. It's still interesting in advancing our mathematical understanding of algorithms! Cloudflare generates random numbers by, in part, taking pictures of 100 lava lamps. Mergesort is older than bubblesor ## Why modal editing became associated with Vim DevFeed: [Why modal editing became associated with Vim]() Original publisher: [Read original article]() Author: Hillel Wayne Published: 2025-10-21T16:46:24Z Content type: article Language: en Sources: [Newsletter feed for Hillel Wayne's Newsletter]() Topics: [Vim](), [GUI]() Tags: [keyboard](), [shortcuts](), [vim]() ### AI overview The article explains modal editing, focusing on how Vim uses modes to assign different functions to the same keys. It argues that modal editing's popularity likely followed from vi's historical success rather than from an obviously superior feature. ### Source excerpt A while back my friend Pablo Meier was reviewing some 2024 videogames and wrote this: I feel like some artists, if they didn't exist, would have the resulting void filled in by someone similar (e.g. if Katy Perry didn't exist, someone like her would have). But others don't have successful imitators or comparisons (thinking Jackie Chan, or Weird Al): they are irreplaceable. He was using it to describe auteurs but I see this as a property of opportunity, in that "replaceable" artists are those who work in bigger markets. Katy Perry's market is large, visible and obviously (but not easily) exploitable, so there are a lot of people who'd compete in her niche. Weird Al's market is unclear: while there were successful parody songs in the past, it wasn't clear there was enough opportunity there to support a superstar. I think that modal editing is in the latter category. Vim is now very popular and has spawned numerous successors. But its key feature, modes, is not obviously-beneficial, to the point that if Bill Joy didn't make vi (vim's direct predecessor) fifty years ago I don't think we'd have any modal editors today. A quick overview of "modal editing" In a non-modal editor, pressing the "u" key adds a "u" to your text, as you'd expect. In a modal editor, pressing "u" does something different depending on the "mode" you are in. In Vim's default "normal" mode, "u" undoes the last change to the text, while in the "visual" mode it lowercases all selected text. It only inserts the character in "insert" mode. All other keys, as well as chorded shortcuts (ctrl-x), work the same way. The clearest benefit to this is you can densely pack the keyboard with advanced commands. The standard US keyboard has 48ish keys dedicated to inserting characters. With the ctrl and shift modifiers that becomes at least ~150 extra shortcuts for each other mode. This is also what IMO "spiritually" distinguishes modal editing from contextual shortcuts. Even if a unimodal editor lets you change a k ## Notes on switching to Helix from vim DevFeed: [Notes on switching to Helix from vim]() Original publisher: [Read original article]() Author: Julia Evans Published: 2025-10-10T00:00:00Z Content type: opinion Language: en Sources: [Julia Evans]() Topics: [Vim](), [Neovim](), [configuration]() Tags: [comparison](), [configuration](), [switching](), [vim]() ### AI overview The article records the author's experience switching from Vim and Neovim to the Helix text editor after three months of use. It discusses Helix's built-in language server support, repository search with match context, quick-reference help, multiple cursors, buffer switching, and several differences or annoyances compared with Vim and Neovim. ### Source excerpt Hello! Earlier this summer I was talking to a friend about how much I love using fish, and how I love that I don't have to configure it. They said that they feel the same way about the helix text editor, and so I decided to give it a try. I've been using it for 3 months now and here are a few notes. why helix: language servers I think what motivated me to try Helix is that I've been trying to get a working language server setup (so I can do things like "go to definition") and getting a setup that feels good in Vim or Neovim just felt like too much work. After using Vim/Neovim for 20 years, I've tried both "build my own custom configuration from scratch" and "use someone else's pre-buld configuration system" and even though I love Vim I was excited about having things just work without having to work on my configuration at all. Helix comes with built in language server support, and it feels nice to be able to do things like "rename this symbol" in any language. the search is great One of my favourite things about Helix is the search! If I'm searching all the files in my repository for a string, it lets me scroll through the potential matching files and see the full context of the match, like this: For comparison, here's what the vim ripgrep plugin I've been using looks like: There's no context for what else is around that line. the quick reference is nice One thing I like about Helix is that when I press g, I get a little help popup telling me places I can go. I really appreciate this because I don't often use the "go to definition" or "go to reference" feature and I often forget the keyboard shortcut. some vim -> helix translations Helix doesn't have marks like ma, 'a, instead I've been using Ctrl+O and Ctrl+I to go back (or forward) to the last cursor location I think Helix does have macros, but I've been using multiple cursors in every case that I would have previously used a macro. I like multiple cursors a lot more than writing macros all the time. If I want to ## Some terminal frustrations DevFeed: [Some terminal frustrations]() Original publisher: [Read original article]() Author: Julia Evans Published: 2025-02-05T16:57:00Z Content type: article Language: en Sources: [Julia Evans]() Topics: [Terminal](), [Command-line interface](), [systems](), [Linux](), [Mastodon]() Tags: [bash](), [cli](), [linux](), [shortcuts](), [ssh](), [switching](), [systems](), [terminal](), [vim]() ### AI overview The article analyzes responses from a terminal-use survey completed by 1,600 people. It groups common frustrations into difficulty remembering CLI syntax, redirects, and keyboard shortcuts; differences between operating systems, shells, editors, and command versions; and problems with SSH environments, servers, containers, and terminal colors. The author notes that most respondents were experienced terminal users and that the survey methodology was informal. ### Source excerpt A few weeks ago I ran a terminal survey (you can read the results here) and at the end I asked: What's the most frustrating thing about using the terminal for you? 1600 people answered, and I decided to spend a few days categorizing all the responses. Along the way I learned that classifying qualitative data is not easy but I gave it my best shot. I ended up building a custom tool to make it faster to categorize everything. As with all of my surveys the methodology isn't particularly scientific. I just posted the survey to Mastodon and Twitter, ran it for a couple of days, and got answers from whoever happened to see it and felt like responding. Here are the top categories of frustrations! I think it's worth keeping in mind while reading these comments that 40% of people answering this survey have been using the terminal for 21+ years 95% of people answering the survey have been using the terminal for at least 4 years These comments aren't coming from total beginners. Here are the categories of frustrations! The number in brackets is the number of people with that frustration. I'm mostly writing this up for myself because I'm trying to write a zine about the terminal and I wanted to get a sense for what people are having trouble with. remembering syntax (115) People talked about struggles remembering: the syntax for CLI tools like awk, jq, sed, etc the syntax for redirects keyboard shortcuts for tmux, text editing, etc One example comment: There are just so many little "trivia" details to remember for full functionality. Even after all these years I'll sometimes forget where it's 2 or 1 for stderr, or forget which is which for > and >>. switching terminals is hard (91) People talked about struggling with switching systems (for example home/work computer or when SSHing) and running into: OS differences in keyboard shortcuts (like Linux vs Mac) systems which don't have their preferred text editor ("no vim" or "only vim") different versions of the same command (like Ma ## Vim Roadmap 2025 DevFeed: [Vim Roadmap 2025]() Original publisher: [Read original article]() Author: Conrad Irwin Published: 2025-01-22T00:00:00Z Content type: opinion Language: en Sources: [Zed Industries - Blog]() Topics: [Vim](), [Neovim](), [User Experience]() Tags: [2025](), [keyboard](), [user-experience](), [vim]() ### AI overview The article outlines Zed's 2025 roadmap for Vim mode. It describes current improvements, including operator support, command-palette work, and Vim plugin integrations, then identifies planned work around editor-adjacent workflows, Vim compatibility, multi-cursor support, persistent state, collaboration shortcuts, and Git integration. ### Source excerpt What's next for Vim mode in Zed? ## What's involved in getting a "modern" terminal setup? DevFeed: [What's involved in getting a "modern" terminal setup?]() Original publisher: [Read original article]() Author: Julia Evans Published: 2025-01-11T09:46:01Z Content type: opinion Language: en Sources: [Julia Evans]() Topics: [Terminal](), [Shell](), [Neovim](), [Vim](), [Git](), [Firefox]() Tags: [autocomplete](), [commands](), [config](), [firefox](), [git](), [history](), [ls](), [terminal](), [vim]() ### AI overview The article discusses what a modern terminal setup means to the author, including safe multiline paste, persistent shell history, useful prompts, 24-bit color, clipboard integration, command-specific autocomplete, shell colors, synchronized themes, automatic terminal recovery, keybindings, and scroll-wheel support. It emphasizes that achieving these conveniences requires coordinating the shell, terminal emulator, text editor, operating system, and applications. ### Source excerpt Hello! Recently I ran a terminal survey and I asked people what frustrated them. One person commented: There are so many pieces to having a modern terminal experience. I wish it all came out of the box. My immediate reaction was "oh, getting a modern terminal experience isn't that hard, you just need to....", but the more I thought about it, the longer the "you just need to..." list got, and I kept thinking about more and more caveats. So I thought I would write down some notes about what it means to me personally to have a "modern" terminal experience and what I think can make it hard for people to get there. what is a "modern terminal experience"? Here are a few things that are important to me, with which part of the system is responsible for them: multiline support for copy and paste: if you paste 3 commands in your shell, it should not immediately run them all! That's scary! (shell, terminal emulator) infinite shell history: if I run a command in my shell, it should be saved forever, not deleted after 500 history entries or whatever. Also I want commands to be saved to the history immediately when I run them, not only when I exit the shell session (shell) a useful prompt: I can't live without having my current directory and current git branch in my prompt (shell) 24-bit colour: this is important to me because I find it MUCH easier to theme neovim with 24-bit colour support than in a terminal with only 256 colours (terminal emulator) clipboard integration between vim and my operating system so that when I copy in Firefox, I can just press p in vim to paste (text editor, maybe the OS/terminal emulator too) good autocomplete: for example commands like git should have command-specific autocomplete (shell) having colours in ls (shell config) a terminal theme I like: I spend a lot of time in my terminal, I want it to look nice and I want its theme to match my terminal editor's theme. (terminal emulator, text editor) automatic terminal fixing: If a programs prints out some ## Getting comfortable with psql DevFeed: [Getting comfortable with psql]() Original publisher: [Read original article]() Author: Map Published: 2024-11-11T15:57:56Z Content type: tutorial Language: en Sources: [Craig Kerstiens]() Topics: [Command-line interface](), [Database]() Tags: [cli](), [commands](), [config](), [database](), [pager](), [postgres](), [psql](), [query](), [tables](), [timing](), [vim]() ### AI overview A practical introduction to getting comfortable with psql, the PostgreSQL command-line interface. It covers utility commands, describing tables, configuration options, query timing, output formatting, pager settings, and editing queries with an external editor. ### Source excerpt psql is a CLI editor that ships with Postgres. It's incredibly powerful for working with Postgres, and doesn't take too much of a learning curve to start to get comfortable so you can really feel like an expert working with your database. Just a rundown of a few things to get you started: Once connected in psql you can get an idea of all utility commands available with: \? A handy thing I use all the time is \d. \d will describe the tables within database. You can also add a table/index/etc. onto it to describe that specific table such as: \d accounts There are a number of options you can set in your psqlrc (config) file to customize your CLI experience. But you can also toggle those when directly working in psql. \timing will give you the time it took to run your query \x auto will autoformat your text output \pset pager 0 turns off your pager or 1 to turn it back on Oh and for editing a query in your editor of choice. Make sure you set your $EDITOR enviroment variable to the editor of your choice, though the only right choice is vim: \e Just a few things to get you started working with psql. Your browser does not support video ## macOS Keyboard Shortcut Localization DevFeed: [macOS Keyboard Shortcut Localization]() Original publisher: [Read original article]() Author: Conrad Irwin Published: 2024-11-08T00:00:00Z Content type: article Language: en Sources: [Zed Industries - Blog]() Topics: [Localization (l10n)](), [macOS](), [ASCII](), [Vim]() Tags: [ascii](), [japanese](), [keyboard](), [layout](), [macos](), [shortcuts](), [vim]() ### AI overview Zed 0.162 changes keyboard shortcut handling so shortcuts work across Cyrillic, Japanese IME-based, and non-US Latin keyboard layouts. The update changes modifier requirements, coordinates shortcut processing with IMEs, and uses macOS Latin-based layouts for non-Latin keyboards. ### Source excerpt How macOS shortcuts work on different layouts. ## Why Zed Uses Its Own Vim Mode Instead of Embedding Neovim DevFeed: [Why Zed Uses Its Own Vim Mode Instead of Embedding Neovim]() Original publisher: [Read original article]() Author: Thorsten Ball, Conrad Irwin Published: 2024-06-13T00:00:00Z Content type: article Language: en Sources: [Zed Industries - Blog]() Topics: [Neovim](), [Vim]() Tags: [video](), [vim](), [zed]() ### AI overview A Zed Decoded article discusses Zed's Vim mode, including its supported features, limitations, and the reasons Zed does not embed Neovim. ### Source excerpt In this episode of Zed Decoded, Thorsten talks Conrad about Zed's Vim mode and asks him: why not just embed Neovim? ## Nix Weekly Recap: 2024-03-17 DevFeed: [Nix Weekly Recap: 2024-03-17]() Original publisher: [Read original article]() Published: 2024-03-17T00:00:00Z Content type: news Language: en Sources: [nixpkgs.news]() Topics: [Nix](), [Release notes](), [releases](), [Caching](), [Deployment](), [JSON Web Tokens](), [Linux](), [macOS](), [Vim](), [vs-code](), [GitHub](), [GitHub Actions]() Tags: [announcements](), [authentication](), [cache](), [caching](), [community](), [deployment](), [github-actions](), [gitlab](), [linux](), [macos](), [news](), [recap](), [release](), [release-notes](), [repository](), [vim](), [vs-code](), [weekly]() ### AI overview A weekly recap of Nix community discussions, the Nix 2.21 release, FlakeHub Cache's private beta, portable services-flake, the teraflops deployment tool, a Vim port, and new Nixpkgs packages. ### Source excerpt Weekly recap of the announcements and activity in the Nix community and on the NixPkgs package repository. ## Between Editors and IDEs, Where Zed Falls DevFeed: [Between Editors and IDEs, Where Zed Falls]() Original publisher: [Read original article]() Author: Thorsten Ball Published: 2024-03-13T00:00:00Z Content type: article Language: en Sources: [Zed Industries - Blog]() Topics: [ide](), [Vim](), [Emacs](), [Ruby]() Tags: [emacs](), [ide](), [interviews](), [latency](), [minimalism](), [performance](), [ruby](), [vim](), [vs]() ### AI overview An interview with Zed's co-founders explores the product philosophy behind Zed, including where it sits between a lightweight editor and a full IDE. They discuss balancing powerful features with a fast, minimal user experience, as well as approaches to extensibility and scriptability. ### Source excerpt Thorsten interviews co-founders Nathan, Max, Antonio about the product philosophy behind Zed and how they think about text editing along multiple axes: Emacs vs. Vim, IDE vs. Editor, Batteries included vs. Extensibility. ## Zed2 Development Progress Report DevFeed: [Zed2 Development Progress Report]() Original publisher: [Read original article]() Author: Joseph Lyons Published: 2023-12-04T00:00:00Z Content type: article Language: en Sources: [Zed Industries - Blog]() Topics: [ide](), [ui](), [telemetry](), [Terminal](), [Vim](), [Open Source]() Tags: [autocomplete](), [bugs](), [collaboration](), [community](), [features](), [open-source](), [progress-report](), [telemetry](), [terminal](), [ui](), [vim]() ### AI overview This progress report describes the Zed team's three-phase transition from Zed1 to Zed2: making the editor runnable, adding productivity features, and completing larger flagship features. The team aimed to release a working Zed2 preview by the end of 2023 and planned to open source it after Zed2 superseded Zed1. ### Source excerpt Progress report on Zed2 ## Zed Weekly: #21 DevFeed: [Zed Weekly: #21]() Original publisher: [Read original article]() Author: Joseph Lyons Published: 2023-09-29T00:00:00Z Content type: article Language: en Sources: [Zed Industries - Blog]() Topics: [Development](), [Storybook](), [Prettier](), [Vim](), [ui]() Tags: [feature](), [improvements](), [storybook](), [ui-components](), [vim]() ### AI overview A weekly development update for Zed covering Prettier integration, improved language-server logs, a Storybook setup for rebuilding the UI, Vim mode updates, collaboration work, and dashboard chart optimization. ### Source excerpt Improving following in collaboration, polishing channels, and continuing to rebuild Zed's UI ## Zed Weekly: #19 DevFeed: [Zed Weekly: #19]() Original publisher: [Read original article]() Author: Nathan Sobo Published: 2023-09-11T00:00:00Z Content type: article Language: en Sources: [Zed Industries - Blog]() Topics: [Graphs](), [Refactoring](), [Rust](), [ui](), [AI search](), [Prettier](), [Vim]() Tags: [feature](), [graph](), [interfaces](), [palette](), [refactoring](), [retrieval](), [rust](), [search](), [vim](), [weekly]() ### AI overview Zed Weekly #19 reports progress on converting channel trees into a directed acyclic graph to support move, link, and unlink commands. It also covers GPUI layout and styling work, Rust UI development, Prettier integration, Vim emulation, keyboard shortcut improvements, inlay hint fixes, and semantic index reliability and retrieval experiments. ### Source excerpt DAG dangers, core feature improvements, and optimizing our semantic search ## Zed Weekly: #17 DevFeed: [Zed Weekly: #17]() Original publisher: [Read original article]() Author: Kirill Bulatov Published: 2023-08-22T00:00:00Z Content type: article Language: en Sources: [Zed Industries - Blog]() Topics: [Artificial Intelligence](), [Code](), [Algorithm](), [Caching](), [Embeddings](), [Optimization](), [tokenization](), [ui](), [Vim]() Tags: [ai](), [algorithm](), [code](), [embeddings](), [performance](), [tokenization](), [ui](), [vim]() ### AI overview Zed Weekly #17 covers work on AI features, including an inline assistant and incremental application of GPT-generated text. It also reports progress on the Semantic Index, Search UI, background operation queues, planned embeddings caching and tokenization optimizations, language server support, performance, and Vim emulation. ### Source excerpt Work on AI, language servers, channels and more. ## A brief and incomplete history of modal text editors DevFeed: [A brief and incomplete history of modal text editors]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2023-08-20T00:00:00Z Content type: article Language: en Sources: [Carlos Becker]() Topics: [Vim](), [Unix](), [Programming]() Tags: [editor](), [history](), [text](), [unix](), [vim]() ### AI overview The article provides a brief, explicitly incomplete history of modal text editors, covering the author's early experiences with Turbo C and Vim before discussing Ed, Ex, and Vi. It explains modal editing and describes how Vi developed from Ex and Ed. ### Source excerpt In this post I'm going to talk about some old text editors you probably never heard of, what is modal text editing, and why people like it so much. [Next page]()