<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Developer on Oscar&#39;s Notebook</title>
    <link>https://oscarchou.com/tags/developer/</link>
    <description>Recent content in Developer on Oscar&#39;s Notebook</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Sat, 20 Dec 2025 20:00:00 +1300</lastBuildDate><atom:link href="https://oscarchou.com/tags/developer/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>[Git/GPG] Fix the &#34;Inappropriate ioctl for device&#34; Error when Signing GPG Keys</title>
      <link>https://oscarchou.com/posts/troubleshoot/gpg-signing-failed-inappropriate-ioctl-for-device/</link>
      <pubDate>Sat, 20 Dec 2025 20:00:00 +1300</pubDate>
      
      <guid>https://oscarchou.com/posts/troubleshoot/gpg-signing-failed-inappropriate-ioctl-for-device/</guid>
      <description>This blog post details the common &amp;#34;Inappropriate ioctl for device&amp;#34; error encountered while setting up GPG signing on macOS, specifically when using GitHub repositories. It explains the root cause – a mismatch between GPG&amp;#39;s expectations for a terminal prompt and the current pinentry UI – and guides readers through a step-by-step solution involving installing the correct `pinentry-mac` program, configuring GPG&amp;#39;s `pinentry-program` path, and crucially, setting the `GPG_TTY` environment variable.  The article emphasizes the importance of setting the `GPG_TTY` variable correctly, particularly when using Fish Shell, to ensure proper interaction between GPG and the terminal.  It provides practical advice and troubleshooting tips for resolving this frustrating issue and successfully signing Git commits with GPG on macOS.</description>
    </item>
    
  </channel>
</rss>
