veganism.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Veganism Social is a welcoming space on the internet for vegans to connect and engage with the broader decentralized social media community.

Administered by:

Server stats:

233
active users

#orgmode

12 posts12 participants0 posts today

I just released version 0.2.5 of kanban.el for #Emacs #orgmode

The new version adds special handling for links within the file: do not add the file as prefix.

This makes HTML export actually usable when using 'file as scope.

melpa.org/#/kanban
hg.sr.ht/~arnebab/kanban.el

I needed this for the status info in my Article BSI IT Grundschutz (with Guile):
draketo.de/software/bsi-grunds

melpa.orgMELPAThe largest and most up-to-date repository of Emacs packages.

When opening an Org file, I like seeing the headers but prefer the drawers to be hidden. Here's a config that gives you that:

(setopt org-cycle-hide-drawer-startup t)
(setopt org-startup-folded 'nofold)

I've found this config especially useful if you use #journelly which puts a lot of useful meta-data into the drawers, but not what I necessarily want to see up-front.

Should I dare to do a "why #Markdown is one of the worst lightweight markup syntax languages there is"-session at a UX/UI-dominant #barcamp? 😜

C'mon, do push me over that cliff! 😆

Background: karl-voit.at/2017/09/23/orgmod 👉 it's related but would be a different focus since I won't push #orgdown that much - people can be happier with other LMLs as well as long as it's not the #MD hell. (Sneak preview: I'm writing a long article on all the MD issues in order to explain it once and for all since the Mastodon discussions are really annoying to me.)

public voit - Web-page of Karl Voit · Org Mode Syntax Is One of the Most Reasonable Markup Languages to Use for TextOrg Mode Syntax Is One of the Most Reasonable Markup Languages to Use for Text
#LML#AsciiDoc#rSt
Continued thread

Ça fait quelque temps que j'utilise le navigateur internet intégré à #emacs, #eww sous #android. C'est super plaisant, c'est comme si il y avait toujours le mode lecture activé par défaut. Et quelle légèreté et réactivité, pas de pub, pas de popup pénibles, en gros parce qu'il n'y a pas de JavaScript et que c'est intégré dans un environnement déjà complet.

En bonus, ça s'intègre très bien dans la gestion documentaire avec #orgmode.

Ça marche bien sur pas pour tout, mais étant degafamisé, la plupart des clients existent en natif sous emacs (mail, ebook, rss, mastodon, radio internet..)

#Emacs #OrgMode is looking for someone to maintain Worg, the community-driven documentation.

See the call for volunteer on the mailing list and on Reddit:

👉 list.orgmode.org/87o6wirw8t.fs

👉 reddit.com/r/orgmode/comments/

You can read Worg on orgmode.org/worg/ and access to its sources on git.sr.ht/~bzg/worg

Thanks for boosting this 🙏

list.orgmode.orgJoin the Org Mode project as the Worg maintainer

gptel-org-tools update.

1. Cloned to
https://codeberg.org/bajsicki/gptel-org-tools, and all future work will be happening on Codeberg.
2. Added
gptel-org-tools-result-limit and a helper function for it. This sets a hard limit on the number of characters a tool can return. If it's over that, the LLM is prompted to be more specific in its query. Not applied to all tools, just the ones that are likely to blow up the context window.
3. Added docstrings for the functions called by the tools, so LLMs can look up their definitions.
4. Improved the precision of some tool descriptions so instructions are easier to follow.
5. Some minor improvements w/r/t function names and calls, logic, etc. Basic QA.

Now, as a user:
1. I'm finding it increasingly frustrating that Gemma 3 refuses to follow instructions. So here's a PSA: Gemma 3 doesn't respect the system prompt. It treats it just the same as any other user input.
2. Mistral 24B is a mixed bag. I'm not sure if it's my settings or something else, but it fairly consistently ends up looping; it'll call the same tool over and over again with the exact same arguments. This happens with other models as well, but not nearly as frequently.
3. Qwen 2.5 14B: pretty dang good, I'd say. The Cogito fine-tune is also surprisingly usable.
4. Prompting: I have found that a good, detailed system prompt tends to /somewhat/ improve results, especially if it contains clear directions on where to look for things related to specific topics. I'm still in the middle of writing one that's accurate to my Emacs set-up, but when I do finish it, it'll be in the repository as an example.
5. One issue that I still struggle with is that the LLMs don't take any time to process the user request. Often they'll find some relevant information in one file, and then decide that's enough and just refuse to look any further. Often devolving into traversing directories /as if/ they're looking for something... and they get stuck doing that without end.

It all boils down to the fact that LLMs aren't intelligent, so while I have a reasonable foundation for the data collection, the major focus is on creating guardrails, processes and inescapable sequences. These will (ideally) railroad LLMs into doing actual research and processing before they deliver a summary/ report based on the org-mode notes I have.

Tags:
#Emacs #gptel #codeberg #forgejo #orgmode #orgql #llm #informationmanagement #gptelorgtools

PS. Links should work now, apparently profile visibility affects repo visibility on Codeberg. I would not have expected that.

PPS. Deleted and reposted because of strong anti-bridge sentiment on my part. Screw Bluesky and bots that repost to it. Defederated: newsmast.*

Summary card of repository bajsicki/gptel-org-tools
Codeberg.orggptel-org-toolsTooling for LLM interactions with org-mode. Requires gptel and org-ql.
Replied in thread

@pcdevil

I didn't receive such email (yet??)

I suppose it takes time to send it out to everyone. If you're curious, I can DM (or email) you what I received.

do you use an alternative?

I'm afraid I won't be much help here - I don't remember why I signed up for Todoist in the first place. I certainly never used it, so I've no clue what features it provides.

I'm using #OrgMode for my TODOs and agendas and whatnots. Works for me, because I practically live in #Emacs, but it's likely not a compelling option for anyone who doesn't.

Das #Barcamp #Graz 2025 wird in den #lightningtalks der Linuxtage angekündigt.

Save-the-date : 17.05.2025

Lightning talks sind #Kurzvorträge bei denen man sich kurzfristig zu einem (max. 5 Minuten langen) #Vortrag meldet.

Außerdem diesmal noch dabei:
#pijul, #msys2, #openwrt und #orgmode, Methoden zu #spam-Verhinderung, #softskills,
#private.coffee ,

pretalx.linuxtage.at/glt25/tal

pretalx.linuxtage.atLightning Talks Grazer Linuxtage 2025Kurzvorträge (max. 5 min) zu verschiedenen Themen. Quick talks (max. 5 min) about different topics.

I think I've found a substitude for task management in #OrgMode . #superproductivity includes the most important feature in orgmode: clocking.

It is a pity that known implementations of orgmode on mobile phones are not usable enough (like #orgzly (Revived) don't have enough support for clocking, #Emacs on Android is not user-friendly to operate on mobile phones).

gptel-org-tools update.

Edit: there's some kind of issue with
@Codeberg@social.anoxinon.de which prevents the link from working (returns 404). The old (but up to date) repo is here: https://git.bajsicki.com/phil/gptel-org-tools

1. Cloned to
https://codeberg.org/bajsicki/gptel-org-tools, and all future work will be happening on Codeberg.
2. Added
gptel-org-tools-result-limit and a helper function for it. This sets a hard limit on the number of characters a tool can return. If it's over that, the LLM is prompted to be more specific in its query. Not applied to all tools, just the ones that are likely to blow up the context window.
3. Added docstrings for the functions called by the tools, so LLMs can look up their definitions.
4. Improved the precision of some tool descriptions so instructions are easier to follow.
5. Some minor improvements w/r/t function names and calls, logic, etc. Basic QA.

Now, as a user:
1. I'm finding it increasingly frustrating that Gemma 3 refuses to follow instructions. So here's a PSA: Gemma 3 doesn't respect the system prompt. It treats it just the same as any other user input.
2. Mistral 24B is a mixed bag. I'm not sure if it's my settings or something else, but it fairly consistently ends up looping; it'll call the same tool over and over again with the exact same arguments. This happens with other models as well, but not nearly as frequently.
3. Qwen 2.5 14B: pretty dang good, I'd say. The Cogito fine-tune is also surprisingly usable.
4. Prompting: I have found that a good, detailed system prompt tends to /somewhat/ improve results, especially if it contains clear directions on where to look for things related to specific topics. I'm still in the middle of writing one that's accurate to my Emacs set-up, but when I do finish it, it'll be in the repository as an example.
5. One issue that I still struggle with is that the LLMs don't take any time to process the user request. Often they'll find some relevant information in one file, and then decide that's enough and just refuse to look any further. Often devolving into traversing directories /as if/ they're looking for something... and they get stuck doing that without end.

It all boils down to the fact that LLMs aren't intelligent, so while I have a reasonable foundation for the data collection, the major focus is on creating guardrails, processes and inescapable sequences. These will (ideally) railroad LLMs into doing actual research and processing before they deliver a summary/ report based on the org-mode notes I have.

Tags:
#Emacs #gptel #codeberg #forgejo #orgmode #orgql #llm #ai #informationmanagement #gptelorgtools

Phil's Gitgptel-org-toolsTooling for LLM interactions with org-mode. Requires gptel and org-ql.