• A ‘trick’ I use when I have some issue with a particular file in my pipeline on my remote server.
    • In org-publish-project-alist, set :base-extension "foo".
      • By default it is “org”, looking at all files with org extension.
      • By setting it to foo, the publish process won’t find any files. Except..
    • Set up :include to include the file that’s got the issue.
      • e.g. :include ("file-with-a-problem.org")
    • There’s probably a better way of doing it than this, but it gets me by for now.
  • Nice, I replaced a cl-loop with a mapconcat in some of my output formatting, e.g. in . mapconcat feels a bit more functional style, and it also gets rid of the superfluous parentheses I had in the output.
  • I might try and add to my published garden.
  • Trying out on desktop.
    • While on mobile I found them incredibly helpful, I actually find it all of the autosuggestions a bit distracting at first.
    • I’ll see how it pans out.

2024-03-02

Leave a Reply

Your email address will not be published. Required fields are marked *

To respond on your own website, enter the URL of your response which should contain a link to this post's permalink URL. Your response will then appear (possibly after moderation) on this page. Want to update or remove your response? Update or delete your post and re-enter your post's URL again. (Find out more about Webmentions.)