• 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.
  • ‘Dear Data Subject’ and other great ways to start an email.
    • Matomo.
    • They mention that they are now using a data broker for “customer and prospect data enrichment”.
      • “We process this personal data on the basis of legitimate interest. Without the information we will not be able to customise our communications with you to best meet your needs”.
      • I find the wording a bit weaselly to be honest. Better would be “We want this information so we can more likely retain and get new customers”. Fine – just be honest about it.
      • You can opt-out. Not opt-in?
  • Using Python in org, I was getting: Importmagic and/or epc not found.