<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Cli on NicoLabs</title>
		<link>http://blog.hellonico.info/tags/cli/</link>
		<description>Recent content in Cli on NicoLabs</description>
		<generator>Hugo</generator>
		<language>ja-JP</language>
		
		
		
		
			<lastBuildDate>Sat, 27 Jun 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="http://blog.hellonico.info/tags/cli/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Supercharging the Coni CLI with Embedded Subcommands</title>
				<link>http://blog.hellonico.info/posts/coni/embedded-subcommands/</link>
				<pubDate>Sat, 27 Jun 2026 00:00:00 +0000</pubDate>
				<guid>http://blog.hellonico.info/posts/coni/embedded-subcommands/</guid>
				<description>&lt;p&gt;One of the greatest strengths of the Coni language is its portability. We designed it so that the core interpreter and standard libraries are shipped as a single, static binary. You don&amp;rsquo;t need a bloated installation process; you just download the executable and you&amp;rsquo;re good to go.&lt;/p&gt;&#xA;&lt;p&gt;However, as the ecosystem grew—like the addition of our Android build pipeline—we found ourselves with a minor workflow annoyance. To invoke the Android APK builder, you had to run the script via its absolute path:&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
