I recently worked with SWWS (https://softwareworkers.it/) developing a minimalist CSS theme for their websites.
I think this is the first time I get to work a paid job using libre tools (GNU Guix and its packages) and be able to release the resulting work as a libre cultural work. It feels great 🙂
I'm writing a longer (as it seems) article on the lock-in effect of solutions like #Obsidian that are using open formats like #Markdown for storage. The file format is not the only thing that might lock you in.
I did already start with a list of arguments but also want to collect your ideas so that I don't forget a good argument.
Please, no emotions, just facts and objective arguments.
Reply here in this thread and I'll collect ideas from it. 🙇
The best time to learn #emacs and #orgmode is ten years ago. The second best time is today. I use #orgmode as my calendar and organiser, and each year I discover something more awesome in it. I didn't realise how good the exporter is and how well formed the HTML is, so now I'll keep my notes on astronomy literature in a new org file. Future proofing through flat text files FTW.
I'd like to use a workflow where each #Mastodon message that gets bookmarked by me is automatically screenshotted to PNG, archived in a local directory and its text content + image descriptions get added to a text file (preferably #orgdown) together with a link to the screenshot and the original message URL.
Wow, I can't believe I'm only just learning about the org-pretty-entities variable in #Emacs#orgmode. Setting it to t automatically transforms a lot of LaTeX fragments into unicode symbols in the buffer.
I've been using the $ delimiter around very small fragments (e.g. $\sigma^2$) and then using org-latex-preview to show it in the buffer. Much slower and clunkier obviously, I wish I had known about this a year or two ago! 🤦♂️
“The dev branch contains a lot of refactoring. I have been trying my best to make this change as smooth as possible for existing Org-remark users. I believe there is no break changes in the eye of users. My tests have been good so far. My old notes file work with no adjustments.”
This year I put a lot more work into #Orgro (https://orgro.org). I released a bunch of big features:
Search result navigation UI
SVG support
Editing support! 🎉
Undo/redo
Jump to/from footnotes
Support for local variables, #+STARTUP settings
(Soon!) Decryption/reencryption of Org Crypt sections
The wildest yak shave I went on was support for local variables: I made an entire Elisp execution engine in order to support the eval keyword! (Don't tell Apple 🤫)
Wrote a post providing some hard-learned guidance on defining tasks in #OrgMode. There are so many ways to define a task but some work better than others, particularly with agenda views.
First baby steps towards a #veilid install, then using #emacs#orgmode#clim#mcclim#lisp together for what will later be my veilid internetworked first application.
Minimal example for clim application frames inside run from inside orgmode.
They're working on a DB version in parallel that will provide better scalability, performance and realtime #collaboration (#RTC). They'll charge for RTC.
Unfortunately, this seems to be the end for #orgdown markup as they are implementing #Markdown only now and a conversion feature later on. 😞
Therefore, logseq is not an option for me any more and I'll need to think about a migration strategy for my wife.
I did not want to use the github link in the package.
A simple #Emacs mode which shows the clocked time today in the modeline. It uses the time clocked in org-agenda-files. The main goal is to always see how much I already worked, so I see more easily whether it is time to stop. #orgmode#productivity