Inline src org block element with containing inside item does not get exported when it contains a newline (was: Inline src block element not parsed correctly for export when in a list item)

Confirmed. Interestingly, I cannot reproduce the bug using my personal branch at https://github.com/yantar92/org. The fix should be lurking somewhere close... Kaushal Modi writes: > I believe I have come across a corner case issue where the inline src > block element doesn't get parsed as one,

Re: Ethical problems with MathJax as default - Was: Faulty SVG width

[[[ To any NSA and FBI agents reading my email: please consider]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > On the other hand, I think it is more preferable and more > privacy-conscious t

Re: Ethical problems with MathJax as default - Was: Faulty SVG width

[[[ To any NSA and FBI agents reading my email: please consider]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] In general, being free software does not automatically assure that the program has no

Re: Agenda without todos only if there is no other timestamp

On 2022-04-05 04:48, Karl Voit wrote: Hi, I've got following custom agenda for exporting: | ("n" "no TODO events +180d" | ((agenda "no TODO events +180d" | ((org-agenda-span 180) |(org-agenda-time-grid nil) |(org-agenda-entry-types '(:timestamp :sexp)) |

Re: bug#54731: Please, revert part of dd0727e1ec1 related to Org mode (`encode-time')

On 4/5/22 09:43, Max Nikulin wrote: Please, revert changes from dd0727e1ec1 related to Org to fix the daylight saving time and to mitigate merge conflicts during porting of future fixes in Org. Thanks for mentioning the problem. I installed the attached, which I hope suffices. This patch d

[PATCH v2] ol.el: add description format parameter to org-link-parameters

* ol.el (org-link-parameters): add parameter `:default-description', a string or a function. * (org-insert-link): if no description is provided (pre-existing or as an argument), next option is to use the `:default-description' (if non-nil) parameter to generate one. Default descriptions are predic

Re: Removing obsolete function `org-truely-invisible-p'.

On 05 Apr 2022, Ihor Radchenko wrote: Sorry for not being clear. I was referring to the commit message - it is what you commonly see in git log. Having something like commit-hash Mark function obsolete & fix spelling of its name in git log is confusing because it is unclear what the commit

Re: org-cite styles don't allow * in them

On Tue, Apr 5, 2022 at 12:11 PM John Kitchin wrote: > > Would you find it suitable to use [cite/command:pre @key post] in general? I think it's a reasonable approach that would appeal to some users who would treat org as a front-end to LaTeX primarily, and obviously previous org-ref users, and th

Linking by Message-ID

On 05/04/2022 13:14, Ihor Radchenko wrote: Karl Fogel writes: From: Ihor Radchenko Subject: Re: Removing obsolete function `org-truely-invisible-p'. To: Karl Fogel Cc: Org Mode Date: Sun, 19 Dec 2021 17:14:32 +0800 Message-ID: <87h7b5rm6f.fsf@localhost> I usually just lea

bug#54731: Please, revert part of dd0727e1ec1 related to Org mode (`encode-time')

Recently a bug with daylight saving time has been reported to the Org mode mail list: https://list.orgmode.org/paxpr06mb7760238f410cbe3203f78ee0c6...@paxpr06mb7760.eurprd06.prod.outlook.com Ignacio Casso. [BUG] org-agenda thinks timestamps after 23:00 correspond to the next day. Tue, 29 Mar 202

Re: org-cite styles don't allow * in them

Would you find it suitable to use [cite/command:pre @key post] in general? For portability, I suppose there could be a defcustom mapping if one wanted to leverage the oc-csl library with pretty minimal effort. I think two things need to be addressed to fix that. First is allowing a * in the style/

Re: problem with diary sexps

On 05/04/2022 18:22, Ihor Radchenko wrote: Christian Stuermer writes: And the problem is gone, after reverting (result (if calendar-debug-sexp (eval sexp t) (condition-case nil (eval sexp t) back to (result (if calendar-debug-sexp (

Re: org-cite styles don't allow * in them

On Sun, Apr 3, 2022 at 5:07 PM John Kitchin wrote: > > I was looking into using latex commands as styles in org-cite, e.g. > > [cite/citet:@key]. That example works fine, but [cite/citet*:@key] is not > allowed. Could that be allowed? I have no insight into the restriction, but I hope it can be

[PATCH] Document custom org agenda functions

--- org-tutorials/org-custom-agenda-commands.org | 40 +++- 1 file changed, 39 insertions(+), 1 deletion(-) diff --git a/org-tutorials/org-custom-agenda-commands.org b/org-tutorials/org-custom-agenda-commands.org index e54bcef3..5b55ebb5 100644 --- a/org-tutorials/org-custom-agen

Re: problem with diary sexps

On Tuesday, 5 Apr 2022 at 19:22, Ihor Radchenko wrote: > More accurate error can be found after setting calendar-debug-sexp to t. > I got the following backtrace clearly indicating lexical scope issue: Which makes sense. The diary code does use entry and date as global variables so really needs

Re: problem with diary sexps

Christian Stuermer writes: > And the problem is gone, after reverting > >(result (if calendar-debug-sexp (eval sexp t) > (condition-case nil > (eval sexp t) > > back to > >(result (if calendar-debug-sexp (eval sexp) > (conditi

Re: problem with diary sexps

On Tuesday, 5 Apr 2022 at 12:28, Christian Stuermer wrote: > I've had the same problem after updating org from git with entries like > The commit introducing it is > https://github.com/bzg/org-mode/commit/6d73cd34a07796c33f9435bfc8c9a19e67656c7a > > And the problem is gone, after reverting > >

[BUG] Exporting italic link with bang inside to html fails to parse the link [9.5.2 (N/A @ /gnu/store/89yvbijwnvsbpa5h33mvbgh1gy9w30n2-emacs-org-9.5.2/share/emacs/site-lisp/org-9.5.2/)]

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: problem with diary sexps

Hello! Eric S Fraga writes: I updated org today and now get Bad sexp at line 461 in /home/ucecesf/s/notes/diary.org: (let ((entry ) (date '(4 19 2022))) (diary-float t 2 3)) for a line that looks like <%%(diary-float t 2 3)> This has been in my diary for a very long time with no error.

Agenda without todos only if there is no other timestamp

Hi, I've got following custom agenda for exporting: | ("n" "no TODO events +180d" | ((agenda "no TODO events +180d" | ((org-agenda-span 180) |(org-agenda-time-grid nil) |(org-agenda-entry-types '(:timestamp :sexp)) |(org-agenda-skip-function |

Re: Remove old WORG page with Org Syntax (draft) in favour of new syntax page by Timothy

Hi Ihor, > Note that I don’t have write access to WORG. I guess you or Nicolas can > commit the change. Done > P.S. Christian also mentioned his confusion that both org-syntax and Org > manual contain syntax descriptions and it is unclear which document to > use. We may add a paragraph to org-sy

Re: Remove old WORG page with Org Syntax (draft) in favour of new syntax page by Timothy

Timothy writes: >> I am in favour of removing the old version completely and putting the >> new document at the old address >> >> >> The old version will remain accessible via git logs if absolutely >> necessary. > > That sounds good to me. Note tha

Re: org-agenda todos list sorted by earliest deadline first

Tested with "emacs -q", I got the same result. Le 5 avril 2022 09:14:43 GMT+02:00, Ihor Radchenko a écrit  : >Sébastien Gendre writes: > >> If I evaluate the same setq and define the same tasks, my result withe >> org-agenda tasks list are: >> >> Global list of TODO items of type: ALL >> Pres

Re: org-agenda todos list sorted by earliest deadline first

Sébastien Gendre writes: > If I evaluate the same setq and define the same tasks, my result withe > org-agenda tasks list are: > > Global list of TODO items of type: ALL > Press ‘N r’ (e.g. ‘0 r’) to search again: (0)[A$ > (1)TODO (2)DONE > test: TODO test1 > test

Re: Remove old WORG page with Org Syntax (draft) in favour of new syntax page by Timothy

Hi Ihor, > I am in favour of removing the old version completely and putting the > new document at the old address > > > The old version will remain accessible via git logs if absolutely > necessary. That sounds good to me. All the best, Timothy