I wanted that same experience in WezTerm. So I built wezterm-cmdpicker. - Source: dev.to / 5 months ago

A month ago, I came across WezTerm, a new GPU-accelerated, cross-platform terminal emulator written in Rust (and I’m not a Rust fanboy, for real!). It piqued my interest, so I decided to give it a try. - Source: dev.to / almost 2 years ago

2) Examples of text editors that make use of features of the gui window manager the text editor is run under: gvim, gedit, leafpad[5], overleaf[6] 3) text editor with 'run-time' presentation extension of protocols such as html : vim live server[7] 4) write one's own custom interface to use with bashed[8] ---- [0] : intro to terminal multiplexers (part 1) : https://www.youtube.com/watch?v=R0upAE692fY [1] :... - Source: Hacker News / almost 2 years ago

I used Lua for years to configure my awesomewm desktop environment. Then, I started using it to configure my Wezterm. Since I bumped into an Emacs bug (lsp-mode bug to be fair), I switched quickly to Neovim after 20 years of Emacs, and I am using Lua to configure my Neovim. Last but not least, OpenResty gives my Nginx superpowers with Lua. - Source: dev.to / almost 2 years ago

While WezTerm is a great terminal with sane defaults, it doesn't provide The default key binding to open the configuration file and edit it. That is Understandable, everyone may have their own preference for that. Here we will Figure out the recipe that would work everywhere and abide by modern standards. - Source: dev.to / about 2 years ago

I have a small "GitHub summarizer" agent: one system prompt, one job — answer questions about my GitHub account by calling the GitHub MCP server. I duplicated its configuration (MAVERIK supports this directly — same model, same prompt, same everything) and changed one field on the copy: the set of attached MCP servers, adding deepwiki, microsoft-learn, and context7. Neither agent needs any of those three for the... - Source: dev.to / 11 days ago

GitHub's official MCP server is excellent — and GitHub is narrowing its default toolset and consolidating PR tools into fewer, more capable ones, explicitly to cut tool bloat and improve agent reasoning. The implication is hard to miss: even one of the best API companies on the planet is learning that a 1:1 mapping from product API to agent tools isn't the right shape. - Source: dev.to / about 2 months ago

The official GitHub MCP server registers 83 tools. Most people set it up for reading code and managing issues. What they don't realise is they've also handed their agent the keys to:. - Source: dev.to / about 2 months ago

A lot of people use MCP servers to connect Claude to tools. I'm not generally a fan. MCP servers load a lot of information into context and often don't do everything that the API can. Last I looked, even the official Github MCP Server is guilty of this. I'd rather write tools directly, to my specifications. - Source: dev.to / 4 months ago

Rather than manually searching through repositories, I used Kiro with the GitHub MCP server to:. - Source: dev.to / 4 months ago