<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[&quot;The history of #Emacs completion frameworks is a progression from monolithic solutions toward composable ones.&quot;]]></title><description><![CDATA[<p>"The history of <a href="https://fediscience.org/tags/Emacs" rel="tag">#<span>Emacs</span></a> completion frameworks is a progression from monolithic solutions toward composable ones."</p><p>This is a comprehensive summary, with a thorough and fair history. A long read, but worth it.</p><p>I plateaued at <a href="https://fediscience.org/tags/Vertico" rel="tag">#<span>Vertico</span></a> <a href="https://fediscience.org/tags/Orderless" rel="tag">#<span>Orderless</span></a> <a href="https://fediscience.org/tags/Marginalia" rel="tag">#<span>Marginalia</span></a> <a href="https://fediscience.org/tags/Consult" rel="tag">#<span>Consult</span></a> years ago. Maybe time to learn the others, one at a time.</p><p></p><div class="card col-md-9 col-lg-6 position-relative link-preview p-0">



<a href="https://www.chiply.dev/post-vompeccc" title="VOMPECCC: A Modular Completion Framework for Emacs">
<img src="http://sveltekit-prerender/images/vompeccc-banner.jpeg" class="card-img-top not-responsive" style="max-height:15rem" alt="Link Preview Image" />
</a>



<div class="card-body">
<h5 class="card-title">
<a href="https://www.chiply.dev/post-vompeccc">
VOMPECCC: A Modular Completion Framework for Emacs
</a>
</h5>
<p class="card-text line-clamp-3">Completion is not a feature or UI, but instead it is a system composed of at least half a dozen orthogonal concerns that most users never think about separately...</p>
</div>
<a href="https://www.chiply.dev/post-vompeccc" class="card-footer text-body-secondary small d-flex gap-2 align-items-center lh-2">



<img src="https://www.chiply.dev/favicon.svg" alt="favicon" class="not-responsive overflow-hiddden" style="max-width:21px;max-height:21px" />



<p class="d-inline-block text-truncate mb-0">Charlie Holland's Blog <span class="text-secondary">(www.chiply.dev)</span></p>
</a>
</div><p></p><p><span><a href="/user/oantolin%40mathstodon.xyz">@<span>oantolin</span></a></span> <span><a href="https://mastodon.world/@minad">@<span>minad</span></a></span> </p><p><a href="https://fediscience.org/tags/emacs" rel="tag">#<span>emacs</span></a></p>]]></description><link>https://board.circlewithadot.net/topic/82b9daa3-a305-40e4-876f-572a6c69e560/the-history-of-emacs-completion-frameworks-is-a-progression-from-monolithic-solutions-toward-composable-ones.</link><generator>RSS for Node</generator><lastBuildDate>Thu, 14 May 2026 23:24:53 GMT</lastBuildDate><atom:link href="https://board.circlewithadot.net/topic/82b9daa3-a305-40e4-876f-572a6c69e560.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 20 Apr 2026 22:32:23 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to &quot;The history of #Emacs completion frameworks is a progression from monolithic solutions toward composable ones.&quot; on Tue, 21 Apr 2026 19:41:33 GMT]]></title><description><![CDATA[<p><span><a href="/user/jameshowell%40fediscience.org">@<span>jameshowell</span></a></span> Composability, where each module does one thing well and has a clean interface to the others, is a worthy goal. But from the user perspective, completion _is_ one thing, so why should we need to coordinate and configure seven or eight packages to get it working? </p><p>Yes, as the article says, there are many _potentially_ orthogonal concerns in completion, but when you separate them into different user packages, you've pushed too much of the complexity of their interaction onto the user.</p><p>The solution, apparently, is to add another layer of abstraction: emacs configuration kits. It all seems a bit much.</p>]]></description><link>https://board.circlewithadot.net/post/https://functional.cafe/users/wirthy/statuses/116444397123649129</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://functional.cafe/users/wirthy/statuses/116444397123649129</guid><dc:creator><![CDATA[wirthy@functional.cafe]]></dc:creator><pubDate>Tue, 21 Apr 2026 19:41:33 GMT</pubDate></item><item><title><![CDATA[Reply to &quot;The history of #Emacs completion frameworks is a progression from monolithic solutions toward composable ones.&quot; on Tue, 21 Apr 2026 18:55:29 GMT]]></title><description><![CDATA[<p><span><a href="/user/oantolin%40mathstodon.xyz">@<span>oantolin</span></a></span> <span><a href="/user/kickingvegas%40sfba.social">@<span>kickingvegas</span></a></span> <span><a href="/user/jameshowell%40fediscience.org">@<span>jameshowell</span></a></span> <span><a href="/user/minad%40mastodon.world">@<span>minad</span></a></span> Nah, not just character by character. Japanese IME for example you typically type in a whole sentence phonetically (and see the kana and first choice kanji appear as you go - sometimes that charges as you type in more giving it more context), then manually fix up any wrong inferences (eg left/right cursors to jump to position in sentence, then up/down or space/shift-space to cycle suggestions for that fragment). Then enter to finalise that sentence.</p>]]></description><link>https://board.circlewithadot.net/post/https://fediscience.org/users/pjacock/statuses/116444215973164750</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://fediscience.org/users/pjacock/statuses/116444215973164750</guid><dc:creator><![CDATA[pjacock@fediscience.org]]></dc:creator><pubDate>Tue, 21 Apr 2026 18:55:29 GMT</pubDate></item><item><title><![CDATA[Reply to &quot;The history of #Emacs completion frameworks is a progression from monolithic solutions toward composable ones.&quot; on Tue, 21 Apr 2026 17:34:47 GMT]]></title><description><![CDATA[<p><span><a href="/user/tchauhan%40mastodon.mit.edu">@<span>tchauhan</span></a></span> Yes. <a href="https://fediscience.org/tags/Emacs" rel="tag">#<span>Emacs</span></a>-sphere, these two are your guys and they deserve your thanks!</p><p><span><a href="/user/minad%40mastodon.world">@<span>minad</span></a></span> <span><a href="/user/oantolin%40mathstodon.xyz">@<span>oantolin</span></a></span></p>]]></description><link>https://board.circlewithadot.net/post/https://fediscience.org/users/jameshowell/statuses/116443898658481633</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://fediscience.org/users/jameshowell/statuses/116443898658481633</guid><dc:creator><![CDATA[jameshowell@fediscience.org]]></dc:creator><pubDate>Tue, 21 Apr 2026 17:34:47 GMT</pubDate></item><item><title><![CDATA[Reply to &quot;The history of #Emacs completion frameworks is a progression from monolithic solutions toward composable ones.&quot; on Tue, 21 Apr 2026 17:22:14 GMT]]></title><description><![CDATA[<p><span><a href="/user/tchauhan%40mastodon.mit.edu">@<span>tchauhan</span></a></span> <span><a href="/user/jameshowell%40fediscience.org">@<span>jameshowell</span></a></span> <span><a href="/user/oantolin%40mathstodon.xyz">@<span>oantolin</span></a></span> You could try Drepl for a Python REPL with better completion. I have not used it so far, so I don't know how well it works in practice.</p><p></p><div class="card col-md-9 col-lg-6 position-relative link-preview p-0">



<a href="https://github.com/astoff/drepl" title="GitHub - astoff/drepl: REPL protocol for the dumb terminal">
<img src="https://opengraph.githubassets.com/072d871b3e46e7b921b6e01a209a3283e5cf2e2f3412c4ca9bab292b42e14555/astoff/drepl" class="card-img-top not-responsive" style="max-height:15rem" alt="Link Preview Image" />
</a>



<div class="card-body">
<h5 class="card-title">
<a href="https://github.com/astoff/drepl">
GitHub - astoff/drepl: REPL protocol for the dumb terminal
</a>
</h5>
<p class="card-text line-clamp-3">REPL protocol for the dumb terminal. Contribute to astoff/drepl development by creating an account on GitHub.</p>
</div>
<a href="https://github.com/astoff/drepl" class="card-footer text-body-secondary small d-flex gap-2 align-items-center lh-2">



<img src="https://github.githubassets.com/favicons/favicon.svg" alt="favicon" class="not-responsive overflow-hiddden" style="max-width:21px;max-height:21px" />



<p class="d-inline-block text-truncate mb-0">GitHub <span class="text-secondary">(github.com)</span></p>
</a>
</div><p></p>]]></description><link>https://board.circlewithadot.net/post/https://mastodon.world/ap/users/115640105216100381/statuses/116443849338851294</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://mastodon.world/ap/users/115640105216100381/statuses/116443849338851294</guid><dc:creator><![CDATA[minad@mastodon.world]]></dc:creator><pubDate>Tue, 21 Apr 2026 17:22:14 GMT</pubDate></item><item><title><![CDATA[Reply to &quot;The history of #Emacs completion frameworks is a progression from monolithic solutions toward composable ones.&quot; on Tue, 21 Apr 2026 17:04:59 GMT]]></title><description><![CDATA[<p><span><a href="/user/tchauhan%40mastodon.mit.edu">@<span>tchauhan</span></a></span> cape-dabbrev is similar to dabbrev-capf, but a little more polished. dabbrev-capf had bugs in the past, but I think they are fixed at least in Emacs 31. Regarding Python REPL completion I cannot help. All I know is that the Capf is broken. <span><a href="/user/jameshowell%40fediscience.org">@<span>jameshowell</span></a></span> <span><a href="/user/oantolin%40mathstodon.xyz">@<span>oantolin</span></a></span></p>]]></description><link>https://board.circlewithadot.net/post/https://mastodon.world/ap/users/115640105216100381/statuses/116443781512963822</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://mastodon.world/ap/users/115640105216100381/statuses/116443781512963822</guid><dc:creator><![CDATA[minad@mastodon.world]]></dc:creator><pubDate>Tue, 21 Apr 2026 17:04:59 GMT</pubDate></item><item><title><![CDATA[Reply to &quot;The history of #Emacs completion frameworks is a progression from monolithic solutions toward composable ones.&quot; on Tue, 21 Apr 2026 16:42:09 GMT]]></title><description><![CDATA[<p><span><a href="/user/minad%40mastodon.world">@<span>minad</span></a></span> <span><a href="/user/jameshowell%40fediscience.org">@<span>jameshowell</span></a></span> <span><a href="/user/oantolin%40mathstodon.xyz">@<span>oantolin</span></a></span> Wow, hello Daniel and Omar, so wonderful to run into you on here. Much respect for your contributions to making emacs usable for forever-noobs like me!</p><p>I think last time I used cape I couldn't understand how cape-dabbrev is different from dabbrev (I understand now...). I will give it a go too! </p><p>I am especially struggling with my python vterm REPL though. I see a wall-of-text dump of all the candidates from the code as well as the REPL buffer! Any pointers?</p>]]></description><link>https://board.circlewithadot.net/post/https://mastodon.mit.edu/users/tchauhan/statuses/116443691735587387</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://mastodon.mit.edu/users/tchauhan/statuses/116443691735587387</guid><dc:creator><![CDATA[tchauhan@mastodon.mit.edu]]></dc:creator><pubDate>Tue, 21 Apr 2026 16:42:09 GMT</pubDate></item><item><title><![CDATA[Reply to &quot;The history of #Emacs completion frameworks is a progression from monolithic solutions toward composable ones.&quot; on Tue, 21 Apr 2026 16:29:19 GMT]]></title><description><![CDATA[<p><span><a href="/user/oantolin%40mathstodon.xyz">@<span>oantolin</span></a></span> <br />This text on Chinese IMEs and seeing what contemporary implementations of it can do has shown me how much incremental completion and filtering has changed the game for computer input. </p><p></p><div class="card col-md-9 col-lg-6 position-relative link-preview p-0">

<div class="card-body">
<h5 class="card-title">
<a href="https://mitpress.mit.edu/9780262047517/the-chinese-computer/">
Access Denied
</a>
</h5>
<p class="card-text line-clamp-3"></p>
</div>
<a href="https://mitpress.mit.edu/9780262047517/the-chinese-computer/" class="card-footer text-body-secondary small d-flex gap-2 align-items-center lh-2">



<img src="https://mitpress.mit.edu/favicon.ico" alt="favicon" class="not-responsive overflow-hiddden" style="max-width:21px;max-height:21px" />



<p class="d-inline-block text-truncate mb-0"> <span class="text-secondary">(mitpress.mit.edu)</span></p>
</a>
</div><p></p><p><span><a href="/user/jameshowell%40fediscience.org">@<span>jameshowell</span></a></span> <span><a href="/user/minad%40mastodon.world">@<span>minad</span></a></span></p>]]></description><link>https://board.circlewithadot.net/post/https://sfba.social/users/kickingvegas/statuses/116443641278742946</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://sfba.social/users/kickingvegas/statuses/116443641278742946</guid><dc:creator><![CDATA[kickingvegas@sfba.social]]></dc:creator><pubDate>Tue, 21 Apr 2026 16:29:19 GMT</pubDate></item><item><title><![CDATA[Reply to &quot;The history of #Emacs completion frameworks is a progression from monolithic solutions toward composable ones.&quot; on Tue, 21 Apr 2026 16:20:33 GMT]]></title><description><![CDATA[<p><span><a href="/user/kickingvegas%40sfba.social">@<span>kickingvegas</span></a></span> I thought IMEs were mechanisms to type single characters and that most of them do not involve incremental completion and filtering!</p><p>EDIT: Your Wikipedia link agrees with my recollection. <span><a href="/user/jameshowell%40fediscience.org">@<span>jameshowell</span></a></span> <span><a href="https://mastodon.world/@minad">@<span>minad</span></a></span></p>]]></description><link>https://board.circlewithadot.net/post/https://mathstodon.xyz/users/oantolin/statuses/116443606761102368</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://mathstodon.xyz/users/oantolin/statuses/116443606761102368</guid><dc:creator><![CDATA[oantolin@mathstodon.xyz]]></dc:creator><pubDate>Tue, 21 Apr 2026 16:20:33 GMT</pubDate></item><item><title><![CDATA[Reply to &quot;The history of #Emacs completion frameworks is a progression from monolithic solutions toward composable ones.&quot; on Tue, 21 Apr 2026 16:17:39 GMT]]></title><description><![CDATA[<p><span><a href="/user/oantolin%40mathstodon.xyz">@<span>oantolin</span></a></span> <span><a href="/user/jameshowell%40fediscience.org">@<span>jameshowell</span></a></span> <span><a href="/user/minad%40mastodon.world">@<span>minad</span></a></span> While I largely agree with the points made in the completion post, I wonder if there’s a need to introduce more jargon. Isn’t a completion framework just another name for an IME (input method editor)? <a href="https://en.wikipedia.org/wiki/Input_method" rel="nofollow noopener"><span>https://</span><span>en.wikipedia.org/wiki/Input_me</span><span>thod</span></a></p>]]></description><link>https://board.circlewithadot.net/post/https://sfba.social/users/kickingvegas/statuses/116443595346170080</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://sfba.social/users/kickingvegas/statuses/116443595346170080</guid><dc:creator><![CDATA[kickingvegas@sfba.social]]></dc:creator><pubDate>Tue, 21 Apr 2026 16:17:39 GMT</pubDate></item><item><title><![CDATA[Reply to &quot;The history of #Emacs completion frameworks is a progression from monolithic solutions toward composable ones.&quot; on Tue, 21 Apr 2026 16:17:02 GMT]]></title><description><![CDATA[<p><span><a href="https://mastodon.world/@minad">@<span>minad</span></a></span> Same here, except I use M-h (not a lot paragraphs to mark in that type of buffer). <span><a href="/user/tchauhan%40mastodon.mit.edu">@<span>tchauhan</span></a></span> <span><a href="/user/jameshowell%40fediscience.org">@<span>jameshowell</span></a></span></p>]]></description><link>https://board.circlewithadot.net/post/https://mathstodon.xyz/users/oantolin/statuses/116443592948999975</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://mathstodon.xyz/users/oantolin/statuses/116443592948999975</guid><dc:creator><![CDATA[oantolin@mathstodon.xyz]]></dc:creator><pubDate>Tue, 21 Apr 2026 16:17:02 GMT</pubDate></item><item><title><![CDATA[Reply to &quot;The history of #Emacs completion frameworks is a progression from monolithic solutions toward composable ones.&quot; on Tue, 21 Apr 2026 16:08:21 GMT]]></title><description><![CDATA[<p><span><a href="/user/oantolin%40mathstodon.xyz">@<span>oantolin</span></a></span> I use consult-history for both (repl and minibuffer), but mainly because I've bound it to the more convenient key (M-r).<br /><span><a href="/user/tchauhan%40mastodon.mit.edu">@<span>tchauhan</span></a></span> <span><a href="/user/jameshowell%40fediscience.org">@<span>jameshowell</span></a></span></p>]]></description><link>https://board.circlewithadot.net/post/https://mastodon.world/ap/users/115640105216100381/statuses/116443558809725817</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://mastodon.world/ap/users/115640105216100381/statuses/116443558809725817</guid><dc:creator><![CDATA[minad@mastodon.world]]></dc:creator><pubDate>Tue, 21 Apr 2026 16:08:21 GMT</pubDate></item><item><title><![CDATA[Reply to &quot;The history of #Emacs completion frameworks is a progression from monolithic solutions toward composable ones.&quot; on Tue, 21 Apr 2026 15:10:28 GMT]]></title><description><![CDATA[<p><span><a href="https://mastodon.world/@minad">@<span>minad</span></a></span> Now that I've gotten used to corfu instead of consult-completion-in-region, I should probably switch to cape-history in REPLs and shells. For minibuffer history, I might stick with consult-history. Which do you use for minibuffer history, Daniel? <span><a href="/user/tchauhan%40mastodon.mit.edu">@<span>tchauhan</span></a></span> <span><a href="/user/jameshowell%40fediscience.org">@<span>jameshowell</span></a></span></p>]]></description><link>https://board.circlewithadot.net/post/https://mathstodon.xyz/users/oantolin/statuses/116443331168503589</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://mathstodon.xyz/users/oantolin/statuses/116443331168503589</guid><dc:creator><![CDATA[oantolin@mathstodon.xyz]]></dc:creator><pubDate>Tue, 21 Apr 2026 15:10:28 GMT</pubDate></item><item><title><![CDATA[Reply to &quot;The history of #Emacs completion frameworks is a progression from monolithic solutions toward composable ones.&quot; on Tue, 21 Apr 2026 15:07:12 GMT]]></title><description><![CDATA[<p><span><a href="/user/jameshowell%40fediscience.org">@<span>jameshowell</span></a></span> I'm currently listening to the previous post in the series¹ and agreeing with pretty much everything.</p><p>¹ <a href="https://www.chiply.dev/post-icr-primer" rel="nofollow noopener"><span>https://www.</span><span>chiply.dev/post-icr-primer</span><span></span></a></p><p> <span><a href="https://mastodon.world/@minad">@<span>minad</span></a></span></p>]]></description><link>https://board.circlewithadot.net/post/https://mathstodon.xyz/users/oantolin/statuses/116443318372664370</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://mathstodon.xyz/users/oantolin/statuses/116443318372664370</guid><dc:creator><![CDATA[oantolin@mathstodon.xyz]]></dc:creator><pubDate>Tue, 21 Apr 2026 15:07:12 GMT</pubDate></item><item><title><![CDATA[Reply to &quot;The history of #Emacs completion frameworks is a progression from monolithic solutions toward composable ones.&quot; on Tue, 21 Apr 2026 12:27:19 GMT]]></title><description><![CDATA[<p><span><a href="/user/jameshowell%40fediscience.org">@<span>jameshowell</span></a></span> <span><a href="https://mastodon.world/@minad">@<span>minad</span></a></span> <span><a href="/user/oantolin%40mathstodon.xyz">@<span>oantolin</span></a></span> Karthinks has a nice article on embark that I've been meaning to figure out for a while. You might want to take a look at it: </p><p></p><div class="card col-md-9 col-lg-6 position-relative link-preview p-0">



<a href="https://karthinks.com/software/fifteen-ways-to-use-embark/" title="Fifteen ways to use Embark">
<img src="https://karthinks.com/img/emacs-pattern.png" class="card-img-top not-responsive" style="max-height:15rem" alt="Link Preview Image" />
</a>









<div class="card-body">
<h5 class="card-title">
<a href="https://karthinks.com/software/fifteen-ways-to-use-embark/">
Fifteen ways to use Embark
</a>
</h5>
<p class="card-text line-clamp-3">Where I collect notes. Sometimes you have to write to be able to think.</p>
</div>
<a href="https://karthinks.com/software/fifteen-ways-to-use-embark/" class="card-footer text-body-secondary small d-flex gap-2 align-items-center lh-2">



<img src="https://karthinks.com/favicon.ico" alt="favicon" class="not-responsive overflow-hiddden" style="max-width:21px;max-height:21px" />



<p class="d-inline-block text-truncate mb-0"> <span class="text-secondary">(karthinks.com)</span></p>
</a>
</div><p></p>]]></description><link>https://board.circlewithadot.net/post/https://mathstodon.xyz/users/aksharvarma/statuses/116442689656003047</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://mathstodon.xyz/users/aksharvarma/statuses/116442689656003047</guid><dc:creator><![CDATA[aksharvarma@mathstodon.xyz]]></dc:creator><pubDate>Tue, 21 Apr 2026 12:27:19 GMT</pubDate></item><item><title><![CDATA[Reply to &quot;The history of #Emacs completion frameworks is a progression from monolithic solutions toward composable ones.&quot; on Tue, 21 Apr 2026 11:56:06 GMT]]></title><description><![CDATA[<p><span><a href="/user/tchauhan%40mastodon.mit.edu">@<span>tchauhan</span></a></span> Another example is `cape-history` vs `consult-history`, which you can use in Comint, Shell or Eshell buffers. `cape-history` displays the candidates via in-buffer completion (e.g. Corfu) while `consult-history` displays the candidates via `completing-read` (e.g. Vertico).<br /><span><a href="/user/jameshowell%40fediscience.org">@<span>jameshowell</span></a></span> <span><a href="/user/oantolin%40mathstodon.xyz">@<span>oantolin</span></a></span></p>]]></description><link>https://board.circlewithadot.net/post/https://mastodon.world/ap/users/115640105216100381/statuses/116442566897389762</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://mastodon.world/ap/users/115640105216100381/statuses/116442566897389762</guid><dc:creator><![CDATA[minad@mastodon.world]]></dc:creator><pubDate>Tue, 21 Apr 2026 11:56:06 GMT</pubDate></item><item><title><![CDATA[Reply to &quot;The history of #Emacs completion frameworks is a progression from monolithic solutions toward composable ones.&quot; on Tue, 21 Apr 2026 11:24:34 GMT]]></title><description><![CDATA[<p><span><a href="/user/jameshowell%40fediscience.org">@<span>jameshowell</span></a></span> Embark is easy to get started with. For example move point to a symbol and run `M-x embark-act`. It should display the available actions. If you want to invoke the standard action, e.g., jump to symbol, invoke `M-x embark-dwim` on a symbol to point. Of course Embark recognizes many more object types at point than symbols. This means we get lots of context dependent commands.<br /><span><a href="/user/oantolin%40mathstodon.xyz">@<span>oantolin</span></a></span></p>]]></description><link>https://board.circlewithadot.net/post/https://mastodon.world/ap/users/115640105216100381/statuses/116442442897356722</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://mastodon.world/ap/users/115640105216100381/statuses/116442442897356722</guid><dc:creator><![CDATA[minad@mastodon.world]]></dc:creator><pubDate>Tue, 21 Apr 2026 11:24:34 GMT</pubDate></item><item><title><![CDATA[Reply to &quot;The history of #Emacs completion frameworks is a progression from monolithic solutions toward composable ones.&quot; on Tue, 21 Apr 2026 11:20:56 GMT]]></title><description><![CDATA[<p><span><a href="/user/tchauhan%40mastodon.mit.edu">@<span>tchauhan</span></a></span> What do you find difficult about Cape? </p><p>Cape basically provides a bunch of completion backends, so called Capfs. You can either add the Capfs to the `completion-at-point-functions` list, or invoke them directly, for instance `M-x cape-emoji` or `M-x cape-file`.</p><p>Another way to think of it - Cape is to Corfu what Consult is to Vertico.</p><p><span><a href="/user/jameshowell%40fediscience.org">@<span>jameshowell</span></a></span> <span><a href="/user/oantolin%40mathstodon.xyz">@<span>oantolin</span></a></span></p>]]></description><link>https://board.circlewithadot.net/post/https://mastodon.world/ap/users/115640105216100381/statuses/116442428630409608</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://mastodon.world/ap/users/115640105216100381/statuses/116442428630409608</guid><dc:creator><![CDATA[minad@mastodon.world]]></dc:creator><pubDate>Tue, 21 Apr 2026 11:20:56 GMT</pubDate></item><item><title><![CDATA[Reply to &quot;The history of #Emacs completion frameworks is a progression from monolithic solutions toward composable ones.&quot; on Tue, 21 Apr 2026 11:20:24 GMT]]></title><description><![CDATA[<p><span><a href="/user/minad%40mastodon.world">@<span>minad</span></a></span> <span><a href="/user/oantolin%40mathstodon.xyz">@<span>oantolin</span></a></span> I've had Embark installed all this time and once a year or so I think to try it. It always startles me. I feel like an australopithecine who found a blowtorch.</p><p>Seems a small effort would pay off disproportionately though. Sometimes I'm just an old man stuck in my habits.</p>]]></description><link>https://board.circlewithadot.net/post/https://fediscience.org/users/jameshowell/statuses/116442426568818190</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://fediscience.org/users/jameshowell/statuses/116442426568818190</guid><dc:creator><![CDATA[jameshowell@fediscience.org]]></dc:creator><pubDate>Tue, 21 Apr 2026 11:20:24 GMT</pubDate></item><item><title><![CDATA[Reply to &quot;The history of #Emacs completion frameworks is a progression from monolithic solutions toward composable ones.&quot; on Tue, 21 Apr 2026 11:11:53 GMT]]></title><description><![CDATA[<p><span><a href="/user/jameshowell%40fediscience.org">@<span>jameshowell</span></a></span> I definitely recommend to add Embark to the mix. Embark is like a left click or right click menu for objects at point (or in the completion minibuffer), but keyboard driven. <span><a href="/user/oantolin%40mathstodon.xyz">@<span>oantolin</span></a></span></p>]]></description><link>https://board.circlewithadot.net/post/https://mastodon.world/ap/users/115640105216100381/statuses/116442393041037145</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://mastodon.world/ap/users/115640105216100381/statuses/116442393041037145</guid><dc:creator><![CDATA[minad@mastodon.world]]></dc:creator><pubDate>Tue, 21 Apr 2026 11:11:53 GMT</pubDate></item><item><title><![CDATA[Reply to &quot;The history of #Emacs completion frameworks is a progression from monolithic solutions toward composable ones.&quot; on Tue, 21 Apr 2026 10:59:26 GMT]]></title><description><![CDATA[<p><span><a href="/user/jameshowell%40fediscience.org">@<span>jameshowell</span></a></span><br />Very nice article. I have used some of the parts before, but the big picture is now alot more clear.<br /><span><a href="/user/oantolin%40mathstodon.xyz">@<span>oantolin</span></a></span> <span><a href="https://mastodon.world/@minad">@<span>minad</span></a></span> </p><p><a href="https://ruhr.social/tags/Emacs" rel="tag">#<span>Emacs</span></a> <a href="https://ruhr.social/tags/Vertico" rel="tag">#<span>Vertico</span></a> <a href="https://ruhr.social/tags/Orderless" rel="tag">#<span>Orderless</span></a> <a href="https://ruhr.social/tags/Marginalia" rel="tag">#<span>Marginalia</span></a> <a href="https://ruhr.social/tags/Consult" rel="tag">#<span>Consult</span></a> <a href="https://ruhr.social/tags/emacs" rel="tag">#<span>emacs</span></a></p>]]></description><link>https://board.circlewithadot.net/post/https://ruhr.social/users/chfkch/statuses/116442344074936504</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://ruhr.social/users/chfkch/statuses/116442344074936504</guid><dc:creator><![CDATA[chfkch@ruhr.social]]></dc:creator><pubDate>Tue, 21 Apr 2026 10:59:26 GMT</pubDate></item><item><title><![CDATA[Reply to &quot;The history of #Emacs completion frameworks is a progression from monolithic solutions toward composable ones.&quot; on Tue, 21 Apr 2026 00:40:28 GMT]]></title><description><![CDATA[<p><span><a href="/user/jameshowell%40fediscience.org">@<span>jameshowell</span></a></span> </p><p>I already feel like I should start a binder of cheat sheets.</p>]]></description><link>https://board.circlewithadot.net/post/https://toot.cat/users/zygmyd/statuses/116439910213882362</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://toot.cat/users/zygmyd/statuses/116439910213882362</guid><dc:creator><![CDATA[zygmyd@toot.cat]]></dc:creator><pubDate>Tue, 21 Apr 2026 00:40:28 GMT</pubDate></item><item><title><![CDATA[Reply to &quot;The history of #Emacs completion frameworks is a progression from monolithic solutions toward composable ones.&quot; on Mon, 20 Apr 2026 23:37:25 GMT]]></title><description><![CDATA[<p><span><a href="/user/jameshowell%40fediscience.org">@<span>jameshowell</span></a></span> <span><a href="/user/oantolin%40mathstodon.xyz">@<span>oantolin</span></a></span> <span><a href="/user/minad%40mastodon.world">@<span>minad</span></a></span> </p><p>A fantastic read, thanks for sharing ! </p><p>Have to find the time to look at prescient and embark. Cape is too complex for me. I do use corfu and it works great except for the python-shell.</p>]]></description><link>https://board.circlewithadot.net/post/https://mastodon.mit.edu/users/tchauhan/statuses/116439662308552334</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://mastodon.mit.edu/users/tchauhan/statuses/116439662308552334</guid><dc:creator><![CDATA[tchauhan@mastodon.mit.edu]]></dc:creator><pubDate>Mon, 20 Apr 2026 23:37:25 GMT</pubDate></item></channel></rss>