[PATCH] Grammar and style corrections for Worg

Hello, I have attached 4 patches with grammar and style corrections for worg-about.org Best regards, Raoul Comninos From cc65944bfa4ffb43e6ddb0b2a8fb85d61c40d42f Mon Sep 17 00:00:00 2001 From: Raoul Comninos Date: Sat, 3 May 2025 07:56:23 +0200 Subject: [PATCH 1/4] worg-about.org: Remove redundant

Re: commit d2e1c6789 incompatible with non-dev Emacs versions?

Ihor Radchenko writes: > I have executed steps 1-4. > May you help with backporting Stefan's commit, according to the usual > process? Sure. The changes from Emacs's 7c82cc8b975 adapted to Org's current main (75f3cad71) would be something like the following, but... --8<---cut here--

Re: [PATCH] Fix for cache error when using org-publish-find-(title|date)

> What about the call to `org-publish-cache-get-file-property' in > `org-publish-index-generate-theindex'? I was not familiar with the usage of theindex, but I confirmed the same cache error can occur if called when `org-publish-transient-cache' is nil. I've added that to my patch as well. >> I

[FR] file+olp+datetree accepting function to select target file

Hi, I've been using file+olp+datetree in my org-capture-templates and I really appreciate the recent enhancements made to datetrees. However, in my personal usage of fole+olp+datetree, I actually found the default possible target specifications lacking. As per the docstring, they are currently:

[PATCH] BUGFIX for dpi calculation

Hello, TL;DR: `org--get-display-dpi` calculated the dpi with data from different monitors, i fixed it and now it returns the highest correct dpi. I noticed that when I connected my laptop to a new monitor the latex fragment scaling changed. So I looked under `org-create-formula-image` (org.el)

How to find the function of a dispatched command ?

I use "C-h i" a lot to find the associated function with a key. This doesn't work for me for dispatched functions. For instance, the keystrokes for 'org-texinfo-export-to-info' is 'C-c C-e i i', but 'C-h c' (or C-h k') tells me 'org-export-dispatch' after I type 'C-c C-e' -- I can't figure out ho

[BUG] org-capture-templates datetree does not respect org-blank-before-new-entry [9.8-pre (release_9.7.29-321-g277344 @ /Users/izanami/.config/emacs/straight/build/org/)]

Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See https://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org mailing list. --

Re: [PATCH] worg-about.org: Fixed several grammatical errors

On Fri, May 02 2025, kwen-ai-kant via "General discussions about Org-mode." wrote: > 'Example of codes' is the error, for me. Yes. "Code samples", "Code snippets" or "Code examples" would all work. > 'Other Org-ers around' is also not idiomatic to my non-American > ear. 'Other Org-ers', 'Org-e

Re: Differences in GNU ELPA Org-mode version

Hi Ihor, Sorry for the confusion. Best, Bruno Em sex., 2 de mai. de 2025, 14:02, Ihor Radchenko escreveu: > Bruno Cardoso writes: > > > Last year I asked about a template expansion feature in Org capture. > This patch was then applied: > https://lists.nongnu.org/archive/html/emacs-orgmode/20

Re: [PATCH] worg-about.org: Fixed several grammatical errors

Thank you Ihor. As I understand you, you are requesting the following approach: - That one not change existing STARTUP options in org files as a rule, and discuss any first - Avoid the passive form, that is, use "change" instead of "changed" - Each commit should focus on one type of change only -

Re: [PATCH] worg-about.org: Fixed several grammatical errors

> > > > > Worg was started by [[http://bzg.fr][Bastien]] in the hope that other > > > > > Org-ers around will > > > > > -bite into this and start sharing tutorials, example of codes, etc. > > > > > +participate and start sharing tutorials, example of codes, etc. > > > > > > > > Hmm. I am wondering

ox-html anchor

Hello, I am modifying the ox-html options to add KEYWORD/OPTION and while modify `org-html-allow-name-attribute-in-anchors', I wanted to know more about the anchors. In an Org-mode document exported to HTML, anchors are the link that point to somewhere else in the HTML document ? Used only in wi

Re: Calling org-agenda Export asynchrously

Henrik Frisk writes: > I would like to have a script call org-agenda tat exports my agenda in an > .ics file. I have this working fine in emacs (C-c a e in my setup). This > locks emacs for the time it takes to parse the agenda files. There are ways > to shorten this that I have tried, but is the

Re: [PATCH] worg-about.org: Fixed several grammatical errors

On Fri, May 02 2025, Ihor Radchenko wrote: >>> > Worg was started by [[http://bzg.fr][Bastien]] in the hope that other >>> Org-ers around will >>> > -bite into this and start sharing tutorials, example of codes, etc. >>> > +participate and start sharing tutorials, example of codes, etc. >>> >>>

Re: Differences in GNU ELPA Org-mode version

Bruno Cardoso writes: > Last year I asked about a template expansion feature in Org capture. This > patch was then applied: > https://lists.nongnu.org/archive/html/emacs-orgmode/2024-06/msg00057.html Yup. The patch was applied onto the development branch of Org mode (main). That branch is what

Re: Question about contribution to improve svg handling in latex export

Emin Martinian writes: > Briefly speaking, the current latex export of SVG files does not work out > of the box and requires adding --shell-escape to the latex args and also > installing inkscape. Even with those, I found the process brittle. If we > are going to require inkscape for SVG handling

Question about contribution to improve svg handling in latex export

I recently suggested a pull request to el-easydraw to improve latex export of SVG files since the current SVG handling seems clunky. The maintainer of that project suggested I contact someone at Org-mode to see if it makes more sense to make that co

Re: [PATCH] worg-about.org: Fixed several grammatical errors

Gnarled Grip writes: >> A common convention for commit messages is avoiding passive verbs. >> > > Fixed is not actually passive. Do you mean you'd prefer I use present tense > instead of past? I.e. fix, rather than fixed? Yup. See https://orgmode.org/worg/org-contribute.html#org4b5d498 >> > -#+

Re: Emacs-Org Mode | Cycling of states TODO - DONE

Subramanian S writes: > Org mode version 9.6.15 (release_9.6.15 @ /usr/share/emacs/29.3/lisp/org/) > >- The exact steps that I have taken in a emacs -q session: > 1. Open a new .org file. > 2. Add a line: - TODO Testing. Note that TODO makes no sense here. It is not a heading, b

Re: [PATCH] worg-about.org: Fixed several grammatical errors

On Fri, May 2, 2025 at 5:47 PM Ihor Radchenko wrote: > > A common convention for commit messages is avoiding passive verbs. > Fixed is not actually passive. Do you mean you'd prefer I use present tense instead of past? I.e. fix, rather than fixed? > > -#+STARTUP:align fold nodlcheck hidest

Re: [PATCH] Re: Q: org-export-headline-levels doc problem?

David Masterson writes: > Patch (from git format-patch) attached. > > From 651863abef42faaabf60d829503f0da9393cfc88 Mon Sep 17 00:00:00 2001 > From: David Masterson > Date: Wed, 30 Apr 2025 22:53:20 -0700 > Subject: [PATCH] Cleanup documentation on definition of "headline level" Thanks! Applied

Re: [PATCH] lisp/org-capture.el: cancel new clock when capture is killed

Bibek Panthi writes: > When a clock is started due to :clock-in t, it is saved when :clock-keep > is t. But this should only be done when capture is finalized and not > when killed/aborted. This change adds a check to ensure that the clock > is not kept when the capture was aborted. > From 102

Re: [PATCH] worg-about.org: Fixed several grammatical errors

Raoul Comninos writes: > worg-about.org | 22 +++--- > 1 file changed, 11 insertions(+), 11 deletions(-) Thanks for the patch! Here are my comments > worg-about.org: Fixed several grammatical errors A common convention for commit messages is avoiding passive verbs. worg-a

Re: commit d2e1c6789 incompatible with non-dev Emacs versions?

Kyle Meyer writes: >> What about the following plan: >> >> 1. Revert d2e1c6789 on bugfix >> 2. Apply my patch on bugfix >> 3. Revert 452584d9db53 on main >> 4. Merge bugfix into main >> 5. Adapt Stefan's commit and apply it on main only (to be extra safe) >> 6. Re-apply a different version of 452

Re: commit d2e1c6789 incompatible with non-dev Emacs versions?

Ihor Radchenko writes: > Kyle Meyer writes: [...] >> [*] ... at the very least, the changes from Org's 2d9e70b80 >> (org-edit-src-*: When writing back, do not displace point in undo >> list, 2024-07-09) should be considered. Plus, for compatibility, I >> think we'd want to keep org-r

[PATCH] worg-about.org: Fixed several grammatical errors

--- worg-about.org | 22 +++--- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/worg-about.org b/worg-about.org index 666ddd2a..a701d31c 100644 --- a/worg-about.org +++ b/worg-about.org @@ -1,6 +1,6 @@ #+TITLE: About Worg #+AUTHOR: Worg people -#+STARTUP:

Re: Emacs new literate configuration approach

Hello Ihor, Thanks for your reply, > So, it appears to me that you are re-implementing the customization UI. It is important for me to stress on the fact that this idea is essentially towards all users already using, or planning to use, org to customize Emacs. > Having a text version of cu

Re: commit d2e1c6789 incompatible with non-dev Emacs versions?

Kyle Meyer writes: >> -(org-replace-buffer-contents write-back-buf 0.1 nil) >> +(replace-region-contents beg end write-back-buf 0.1 nil) > > Is it valid to pass a buffer as the third argument of > replace-region-contents on Emacs 30 or earlier? If I understand > correctly, that c