<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: songdora</title>
    <description>The latest articles on DEV Community by songdora (@songdora).</description>
    <link>https://dev.to/songdora</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4257481%2Fcde85079-9815-4477-8ead-6d464ea2e95e.png</url>
      <title>DEV Community: songdora</title>
      <link>https://dev.to/songdora</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/songdora"/>
    <language>en</language>
    <item>
      <title>O que muda no seu Markdown quando você move um cartão no Tolaria?</title>
      <dc:creator>songdora</dc:creator>
      <pubDate>Sat, 21 Nov 2026 14:38:06 +0000</pubDate>
      <link>https://dev.to/songdora/o-que-muda-no-seu-markdown-quando-voce-move-um-cartao-no-tolaria-2l03</link>
      <guid>https://dev.to/songdora/o-que-muda-no-seu-markdown-quando-voce-move-um-cartao-no-tolaria-2l03</guid>
      <description>&lt;p&gt;Seu quadro Kanban mostra o cartão em “Revisão”. Se você abrir a pasta de notas fora do aplicativo, consegue descobrir o que mudou? Essa é uma boa pergunta antes de colocar um cofre Markdown no Git ou migrar um projeto inteiro.&lt;/p&gt;

&lt;p&gt;A versão de &lt;strong&gt;18 de novembro do Tolaria&lt;/strong&gt; permite agrupar uma lista de notas por propriedade. Quando você arrasta um cartão entre colunas, o aplicativo atualiza a nota. Recolher ou ocultar uma coluna muda a visualização. As &lt;a href="https://github.com/refactoringhq/tolaria/releases/tag/v2026-11-18" rel="noopener noreferrer"&gt;notas oficiais da versão&lt;/a&gt; descrevem os dois comportamentos.&lt;/p&gt;

&lt;h2&gt;
  
  
  Compare duas cópias da mesma nota
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Abra uma pasta de teste. Crie uma nota com a propriedade que você usa para agrupar o quadro. No exemplo, a propriedade é &lt;code&gt;etapa&lt;/code&gt; e as colunas são &lt;code&gt;fila&lt;/code&gt; e &lt;code&gt;revisao&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Salve a nota e copie o arquivo &lt;code&gt;.md&lt;/code&gt; para fora do cofre como &lt;code&gt;antes.md&lt;/code&gt;. Isso evita que o aplicativo trate a cópia como outro cartão.&lt;/li&gt;
&lt;li&gt;Mova o cartão para a segunda coluna, confirme a propriedade na nota e aguarde o salvamento. Copie o mesmo arquivo de novo como &lt;code&gt;depois.md&lt;/code&gt;, no mesmo diretório de &lt;code&gt;antes.md&lt;/code&gt;.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Abra o terminal nesse diretório. O Git aceita comparar arquivos avulsos, inclusive fora de um repositório:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;git diff --no-index -- antes.md depois.md
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Em um par de arquivos de exemplo, a diferença aparece como &lt;code&gt;-etapa: fila&lt;/code&gt; e &lt;code&gt;+etapa: revisao&lt;/code&gt;. O código de saída &lt;strong&gt;1&lt;/strong&gt; indica que o Git encontrou diferenças. Confira as outras linhas da saída antes de concluir que só o status mudou. Se não aparecer nada, confira se você copiou o mesmo arquivo antes e depois de salvar, e se moveu o cartão em vez de só recolher uma coluna.&lt;/p&gt;

&lt;p&gt;Quem ainda vai instalar pode conferir o &lt;a href="https://download.sajueye.com/pt/download/tolaria/" rel="noopener noreferrer"&gt;guia de instalação do Tolaria em português&lt;/a&gt;. Eu mantenho o Sajueye Downloads e reuni ali as opções de instalação. No Linux, escolha o DEB para Debian ou Ubuntu, o RPM para Fedora, ou o AppImage se quiser executar o programa sem instalar um pacote do sistema.&lt;/p&gt;

</description>
      <category>markdown</category>
      <category>productivity</category>
      <category>tools</category>
      <category>braziliandevs</category>
    </item>
    <item>
      <title>Stirling PDF on Linux: pick the package, then verify the file</title>
      <dc:creator>songdora</dc:creator>
      <pubDate>Sat, 21 Nov 2026 14:30:38 +0000</pubDate>
      <link>https://dev.to/songdora/stirling-pdf-on-linux-pick-the-package-then-verify-the-file-47nd</link>
      <guid>https://dev.to/songdora/stirling-pdf-on-linux-pick-the-package-then-verify-the-file-47nd</guid>
      <description>&lt;p&gt;If you only need to edit a PDF on your own computer, you can start the Stirling PDF desktop app in Local Only mode. The first decision happens before launch: three Linux files in the 3.4.0 release have the same version and architecture, but they install differently.&lt;/p&gt;

&lt;h3&gt;
  
  
  Match the download to your machine
&lt;/h3&gt;

&lt;p&gt;Run &lt;code&gt;uname -m&lt;/code&gt; and check the result before opening the &lt;a href="https://github.com/Stirling-Tools/Stirling-PDF/releases/expanded_assets/v3.4.0" rel="noopener noreferrer"&gt;official 3.4.0 asset list&lt;/a&gt;. The three native Linux desktop packages in that release are for &lt;code&gt;x86_64&lt;/code&gt;. If your machine reports &lt;code&gt;aarch64&lt;/code&gt;, these are the wrong binaries. The desktop release list and the browser-based service are separate distribution options.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Where you want to run it&lt;/th&gt;
&lt;th&gt;File to look for&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Debian or Ubuntu, installed via the system package manager&lt;/td&gt;
&lt;td&gt;&lt;code&gt;Stirling-PDF-linux-x86_64.deb&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Fedora or RHEL, installed via the system package manager&lt;/td&gt;
&lt;td&gt;&lt;code&gt;Stirling-PDF-linux-x86_64.rpm&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;x86_64 Linux, without installing a system package&lt;/td&gt;
&lt;td&gt;&lt;code&gt;Stirling-PDF-linux-x86_64.AppImage&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h3&gt;
  
  
  Verify the file before giving it execute permission
&lt;/h3&gt;

&lt;p&gt;For the AppImage, run this from the folder where you saved it:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sha256sum -- Stirling-PDF-linux-x86_64.AppImage
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Compare the first field with the digest shown under &lt;strong&gt;that exact file&lt;/strong&gt; in the official asset list. GitHub prefixes the value with &lt;code&gt;sha256:&lt;/code&gt;. A checksum can confirm that the file you saved matches the one listed by the publisher. It is still important to verify which publisher and release page you are using. If the digest differs, stop and recheck the filename, release and download. The DEB and RPM have their own digests.&lt;/p&gt;

&lt;p&gt;Once verified, you can mark the AppImage executable through your file manager. To check the first launch on a personal device, select &lt;strong&gt;Continue without signing in&lt;/strong&gt;, open a non-sensitive test PDF, and confirm that the local tool you need is available. The &lt;a href="https://docs.stirlingpdf.com/Desktop/Connection-Modes/" rel="noopener noreferrer"&gt;official connection-mode guide&lt;/a&gt; explains how local tools differ from cloud-only tools and why a managed installation may require sign-in.&lt;/p&gt;

&lt;p&gt;I maintain Sajueye Downloads. My &lt;a href="https://download.sajueye.com/en/download/stirling-pdf/" rel="noopener noreferrer"&gt;English installation guide&lt;/a&gt; also covers the two Windows installer formats and the universal macOS disk image.&lt;/p&gt;

</description>
      <category>linux</category>
      <category>opensource</category>
      <category>software</category>
      <category>tools</category>
    </item>
  </channel>
</rss>
