<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
    xmlns:wiki="http://purl.org/rss/1.0/modules/wiki/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:cc="http://web.resource.org/cc/"
    xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<docs>http://blogs.law.harvard.edu/tech/rss</docs>
<title>Marcin Borkowski: Homepage</title>
<link>https://mbork.pl/Homepage</link>
<atom:link href="https://mbork.pl?action=rss" rel="self" type="application/rss+xml" />
<description>Strona domowa Marcina Borkowskiego</description>
<pubDate>Mon, 31 Aug 2026 19:13:28 GMT</pubDate>
<lastBuildDate>Mon, 31 Aug 2026 19:13:28 GMT</lastBuildDate>
<generator>Oddmuse</generator>

<item>
<title>Developing Claude Code skills</title>
<link>https://mbork.pl/2026-08-31_Developing_Claude_Code_skills</link>
<guid>https://mbork.pl/2026-08-31_Developing_Claude_Code_skills</guid>
<description>As I’ve mentioned some time ago, I’ve been using Claude Code for some time now. Now, a disclaimer is in place. I’m still a bit skeptical about the current “AI” hype – in particular, I really avoid using the term “AI”. I consider it a very misleading marketing gimmick. When non-technical people hear the phrase “artificial intelligence”, a computational model capable of generating more or less random sequence of letters which sometimes create a semblance of “understanding” or “intelligence” is probably not what they think. Well, I am really a layman, too – I have some extremely vague understanding what happens inside these “chatbots”, but other than that they seem a bit magical to me as well – but my point is, they are really closer to a giant spreadsheet with billions (or even more) of cells than to Skynet. Anyway – even I have to admit that what Claude Code is able to do is pretty impressive. However, I quickly discovered that the OOTB experience is less than ideal. One of the easier ways to enhance Claude (and other LLMs, apparently) is by writing skills, which are basically reusable prompts or procedures for performing some tasks, written in natural language.</description>
<pubDate>Mon, 31 Aug 2026 19:13:28 GMT</pubDate>
<comments>https://mbork.pl/Comments_on_2026-08-31_Developing_Claude_Code_skills</comments>
<dc:contributor>mbork</dc:contributor>
<wiki:status>new</wiki:status>
<wiki:importance>major</wiki:importance>
<wiki:version>1</wiki:version>
<wiki:history>https://mbork.pl?action=history;id=2026-08-31_Developing_Claude_Code_skills</wiki:history>
<wiki:diff>https://mbork.pl?action=browse;diff=1;id=2026-08-31_Developing_Claude_Code_skills</wiki:diff>
</item>

<item>
<title>Transforming yanked text</title>
<link>https://mbork.pl/2026-08-24_Transforming_yanked_text</link>
<guid>https://mbork.pl/2026-08-24_Transforming_yanked_text</guid>
<description>Recently I found myself killing and yanking more often than ever. One problem with that is that the capitalization and punctuation of what I have yanked is often wrong. As a (pretty stupid) example, I might see the sentence “This is bad.”, and I might want to write another one: “He thinks that this is bad, and he’s right.” If I use kill-sentence (M-k) or backward-kill-sentence (C-x DEL), I have the whole This is bad. in the kill ring, but what I need to yank is this is bad (with lower-case “t” and without the period), so I need to make both changes after yanking. After several dozen such cases I thought, this is Emacs, I shouldn’t be doing this manually!</description>
<pubDate>Mon, 24 Aug 2026 19:01:51 GMT</pubDate>
<comments>https://mbork.pl/Comments_on_2026-08-24_Transforming_yanked_text</comments>
<dc:contributor>mbork</dc:contributor>
<wiki:status>new</wiki:status>
<wiki:importance>major</wiki:importance>
<wiki:version>1</wiki:version>
<wiki:history>https://mbork.pl?action=history;id=2026-08-24_Transforming_yanked_text</wiki:history>
<wiki:diff>https://mbork.pl?action=browse;diff=1;id=2026-08-24_Transforming_yanked_text</wiki:diff>
</item>

<item>
<title>A text expander for Android</title>
<link>https://mbork.pl/2026-08-17_A_text_expander_for_Android</link>
<guid>https://mbork.pl/2026-08-17_A_text_expander_for_Android</guid>
<description>Like many Emacs users, I’m a heavy Org mode user. Some time ago I decided that I need a way to access at least some of my Org files on my (Android) phone.</description>
<pubDate>Mon, 17 Aug 2026 18:06:50 GMT</pubDate>
<comments>https://mbork.pl/Comments_on_2026-08-17_A_text_expander_for_Android</comments>
<dc:contributor>mbork</dc:contributor>
<wiki:status>new</wiki:status>
<wiki:importance>major</wiki:importance>
<wiki:version>1</wiki:version>
<wiki:history>https://mbork.pl?action=history;id=2026-08-17_A_text_expander_for_Android</wiki:history>
<wiki:diff>https://mbork.pl?action=browse;diff=1;id=2026-08-17_A_text_expander_for_Android</wiki:diff>
</item>

<item>
<title>Emphasizing a region in Org mode</title>
<link>https://mbork.pl/2026-08-10_Emphasizing_a_region_in_Org_mode</link>
<guid>https://mbork.pl/2026-08-10_Emphasizing_a_region_in_Org_mode</guid>
<description>One of the most basic features of Org mode is its markup. It is basically the Markdown of the Emacs world (although some people, like Karl Voit, claim that it’s superior to Markdown), and it lets do basic things like italic, bold or verbatim very easily – at least if you’re writing text. I, on the other hand, happen to edit text pretty often. This is very different from writing. When I write, typing a slash before and after something I want to emphasize is easy. When I edit and just want to make some text bold, putting stars around it is much less convenient.</description>
<pubDate>Mon, 10 Aug 2026 20:35:30 GMT</pubDate>
<comments>https://mbork.pl/Comments_on_2026-08-10_Emphasizing_a_region_in_Org_mode</comments>
<dc:contributor>mbork</dc:contributor>
<wiki:status>new</wiki:status>
<wiki:importance>major</wiki:importance>
<wiki:version>1</wiki:version>
<wiki:history>https://mbork.pl?action=history;id=2026-08-10_Emphasizing_a_region_in_Org_mode</wiki:history>
<wiki:diff>https://mbork.pl?action=browse;diff=1;id=2026-08-10_Emphasizing_a_region_in_Org_mode</wiki:diff>
</item>
</channel>
</rss>
