Where do you get your #emacs and #orgmode questions answered -- apart from here?

Comment diriez-vous : «Emacsdoka» ou «Emacsninja» ?
Cette question sur une personne ceinture noire en #Emacs est inspirée du «Vimdoka» de @fabi1cazenave (cf message précédent).
Pour répondre à cette question (ou pas)... RENDEZ-VOUS en visio ce mardi 6 mai à partir de 17h30 (et jusqu'à après 19h30 généralement) : c'est l'ATELIER Emacs mensuel, https://emacs-doctor.com/
Remarque : questions/réponses de tous niveaux sur LISP, #orgmode, Denote, dired et autre #format texte dans #Emacs sont possibles !

I am looking for an Emacs/Org mode package that lets me view the outline of a document in a separate window/buffer on the side (and potentially navigate throught it). Are there any good ones? #emacs #orgmode

#Pikchr (pikchr.org) is a great little piece of software from the SQLite folks. It parses a little language for describing diagrams with boxes and lines and things, and puts out SVG.

#OrgMode (orgmode.org) has, among many other things, a way you can make code notebooks, #OrgBabel. Like #Jupyter, but less webby, and inside #Emacs, and supporting many languages - even multiple in the same document - thence its name.

Thanks to the ob-pikchr package by @SReyCoyrehourcq, Pikchr is one of the languages you can just write in the middle of your document this way.

Pikchr supports #darkmode, and I've just made a pull request that gets ob-pikchr in on the dark-mode game.

https://github.com/reyman/ob-pikchr/pull/1

Many thanks to Sebastien for the help ob-pikchr has provided in diagramming my thoughts! You go use it too!

My iOS app made it to the App Store, please help me get the word out and boost

Journelly: like tweeting but for your eyes only (offline / powered by plain text)

https://lmno.lol/alvaro/journelly-like-tweeting-but-for-your-eyes-only

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.

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

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

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.

#TIL I can copy formatted text in #orgmode within #Emacs with `ox-clip-formatted-copy` from `ox-clip` package by jkitching https://github.com/jkitchin

Works nice with #Confluence

#18 [[bbb:OrgMeetup]] on Wed, May 14, 19:00 UTC+3

Another OrgMeetup will be scheduled on the second Wednesday of May,
in two weeks.

Previous meetup notes:
https://list.orgmode.org/87ecxkb1pv.fsf@localhost/T/#u
https://orgmode.org/worg/orgmeetup.html

URL: https://bbb.emacsverse.org/rooms/orgmeetup/join

CC: @sacha

Happy to announce that Scrim 1.0, an Org Protocol proxy for Emacs on macOS has launched on the App Store. Learn more about it at the link below!

http://yummymelon.com/devnull/announcing-scrim--an-org-protocol-proxy-for-emacs-on-macos.html

I bought the Udemy-course by Rainer König about org-mode and it is really useful. I already learned a lot even though I am using org-mode for some time now. There are a lot of little things I weren’t aware of that help me (like quick notes with C-c C-z). #orgmode #emacs #productivity

#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:

https://list.orgmode.org/87o6wirw8t.fsf@gnu.org/T/#u

https://www.reddit.com/r/orgmode/comments/1k8x7xo/join_the_org_mode_project_as_the_worg_maintainer/

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

Thanks for boosting this

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.*

Hello, here's my fediverse re- #introduction since I moved to #fediscience

I'm a computational biologist/bioinformatician, professor at UCLouvain in Brussels. I work with various types of omics data, with a special interest in #MassSpectrometry and #proteomics. I (co-)develop and maintain several #rstats and #Bioconductor packages. In addition to R, I use #emacs and #orgmode quite a bit.

Thanks for reading!

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

https://youtu.be/MeDo_Q2oOuk