Bug: Effort prompt write malformed input in agenda file even after reporting the error [9.1.9 (release_9.1.9-65-g5e4542 @ /usr/local/share/emacs/26.3/lisp/org/)]

2019-11-09 Thread Firmin Martin
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: Bug: open pdfview link causes severe memory allocation

2020-05-01 Thread Firmin Martin
cond point is still relevant. I reported this issue to ~org-pdftools~ which inherit the issue from the unmaintained ~org-pdfview~ : https://github.com/fuxialexander/org-pdftools/issues/35 Best, Firmin Martin

Bug: open pdfview link causes severe memory allocation [9.3.6 (9.3.6-60-gf3c137-elpaplus @ /home/firmart/.emacs.d/elpa/org-plus-contrib-20200427/)]

2020-05-01 Thread Firmin Martin
severe bug that shouldn't happen. Best, Firmin Martin

Bug: LaTeX inline maths expression \(+\) wrongly toggles strike-through face

2020-12-01 Thread Firmin Martin
-linux-gnu, GTK+ Version 3.24.20, cairo version 1.16.0) of 2020-10-16 Package: Org mode version 9.4 (9.4-53-gc97446-elpa) Best, Firmin Martin

Re: Bug: LaTeX inline maths expression \(+\) wrongly toggles strike-through face

2020-12-03 Thread Firmin Martin
Thank you Tomas, it works like a charm! Hope that it will be patched. Best, Firmin Martin

Bug: LaTeX: inline maths expression in \textrm is not fully supported

2020-12-12 Thread Firmin Martin
Sometimes, we want to nest inline maths expression in \textrm to handle spaces easily and avoid repetition. Examples: 1. $A = \{n : \textrm{$n$ odd in $X$}\}$ 2. $A = \{n : \textrm{\(n\) odd in \(X\)}\}$ 3. \(A = \{n : \textrm{\(n\) odd in \(X\)}\}\) 4. \(A = \{n : \textrm{$n$ odd in $X$}\}\)

Re: Bug: LaTeX: inline maths expression in \textrm is not fully supported

2020-12-13 Thread Firmin Martin
ort, but if one would also want to export in HTML, the LaTeX expression is lost. I will stay with the "multiple \textrm" solution for now. Best, Firmin Eric S Fraga writes: > On Sunday, 13 Dec 2020 at 02:30, Firmin Martin wrote: >> Sometimes, we want to nest inline maths

Bug: Clock date range with the enclosing markup <> are not fully supported [9.4.4 (9.4.4-27-gb712b9-elpaplus)]

2021-03-12 Thread Firmin Martin
I have manually changed a clock date range in a task's logbook using the shortcut =C-c .= (org-time-stamp). It modified the Org timestamp to the date I wanted, but changed the enclosing markup from [] to <>. I didn't pay much attention on it as C-c C-c (org-ctrl-c-ctrl-c) updated correctly the