Re: Subject: [BUG] Org request me to submit bug report; The error was: (error "Invalid search bound (wrong side of point)") [9.7.29 (9.7.29-79781b @ /home/mfl/.emacs.d/elpa/org-9.7.29/)]

kf writes: > Subject: [BUG] Org request me to submit bug report; The error was: (error > "Invalid search bound (wrong side of point)") [9.7.29 (9.7.29-79781b @ > /home/mfl/.emacs.d/elpa/org-9.7.29/)] > > Emacs : GNU Emacs 30.1 (build 1, x86_64-pc-linux-gnu, GTK+

Subject: [BUG] Org request me to submit bug report; The error was: (error "Invalid search bound (wrong side of point)") [9.7.29 (9.7.29-79781b @ /home/mfl/.emacs.d/elpa/org-9.7.29/)]

Subject: [BUG] Org request me to submit bug report; The error was: (error "Invalid search bound (wrong side of point)") [9.7.29 (9.7.29-79781b @ /home/mfl/.emacs.d/elpa/org-9.7.29/)] From: seniormba --text follows this line-- Remember to cover the basics, that is, what you expected

Re: Bug Report: Invalid Function Error after Natively Compiling =org-element=

Ihor Radchenko writes: > Vitus Schäfftlein writes: > >> After updating to emacs version 30.1 from version 29.4.4, I experience >> issues with =org-element-with-disabled-cache=. Specifically, creating an >> =org-roam= node with a template that sets a =#+category= yields the error >> =invalid-f

Re: Bug Report: Invalid Function Error after Natively Compiling =org-element=

Vitus Schäfftlein writes: > After updating to emacs version 30.1 from version 29.4.4, I experience issues > with =org-element-with-disabled-cache=. Specifically, creating an =org-roam= > node with a template that sets a =#+category= yields the error > =invalid-function org-element-with-disable

Bug Report: Invalid Function Error after Natively Compiling =org-element=

After updating to emacs version 30.1 from version 29.4.4, I experience issues with =org-element-with-disabled-cache=. Specifically, creating an =org-roam= node with a template that sets a =#+category= yields the error =invalid-function org-element-with-disabled-cache=. Here is a MWE you save to

Re: Bug Report: Org Agenda 'custom-initialize-reset: Cache must be active'

Zan Owsley writes: > My apologies - I realised the mistake in how I changed how I was setting > 'org-agenda-files'. Continued head-banging was what I needed. No problem. Closing. Canceled. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at .

Re: Bug Report: Org Agenda 'custom-initialize-reset: Cache must be active'

My apologies - I realised the mistake in how I changed how I was setting 'org-agenda-files'. Continued head-banging was what I needed. Zan On 12/10/24 11:06 AM, Zan Owsley wrote: Hi, Emacs version: 30.0.92. I had been using org-agenda fine for a while with the new version, but this just st

Bug Report: Org Agenda 'custom-initialize-reset: Cache must be active'

Hi, Emacs version: 30.0.92. I had been using org-agenda fine for a while with the new version, but this just started and my init.el has no bearing on making it continue to happen. This is being reproduced using 'emacs -Q' followed by evaluating '(setq org-agenda-files "~/sync/gtd/gtd.org")

Re: [BUG] Bug Report [9.6.6 (release_9.6.6 @ /usr/share/emacs/29.1/lisp/org/)]

[ Adding Org mailing list back to CC. Please use "reply all" to keep the conversation public ] Jerome writes: > This specific case (deleting a line and getting a bug) has only happened > once. Might also be worth noting that I only ever get bugs in this one org > file that I open, never in a

Re: [BUG] Bug Report [9.6.6 (release_9.6.6 @ /usr/share/emacs/29.1/lisp/org/)]

Jerome Siljan writes: > I deleted a line in my file and I got this error and the prompt to > report it > > Emacs : GNU Emacs 29.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version > 3.24.39, cairo version 1.18.0) > of 2024-01-10 > Package: Org mode version 9.6.6 (release_9.6.6 @ > /usr/share/emacs/29

[BUG] Bug Report [9.6.6 (release_9.6.6 @ /usr/share/emacs/29.1/lisp/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

Re: [BUG] Asked to submit bug report: parse error? [9.7-pre (release_9.6.11-935-g6d7c79 @ /Users/apc/.emacs.d/straight/build/org/)]

Alejandro Pérez Carballo writes: > I received the following message after trying to follow a search result > obtained via grep. > > ⛔ Warning (org-element): org-element--cache: Org parser error in > gpd.org::14519. Resetting. > The error was: (error "Invalid search bound (wrong side of point)"

[BUG] Asked to submit bug report: parse error? [9.7-pre (release_9.6.11-935-g6d7c79 @ /Users/apc/.emacs.d/straight/build/org/)]

nil]) " Please report this to Org mode mailing list (M-x org-submit-bug-report). Emacs : GNU Emacs 29.1 (build 2, aarch64-apple-darwin21.6.0, NS appkit-2113.60 Version 12.6.2 (Build 21G320)) of 2023-11-15 Package:

Re: Bug report for ox-icalendar: newlines should be CRLF

Jack Kamm writes: > I've pushed this change now: > https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=f4446ce795c924a1e115e360d3674f6ad89be845 Fixed. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development a

Re: Bug report for ox-icalendar: newlines should be CRLF

Jack Kamm writes: > writes: > >>> > There is a related issue about EOLs, not just \r\n -- each line should >>> > be a maximum of 75 characters; this is handled by >>> > org-icalendar-fold-string >>> >>> May you please provide a link to the iCalendar spec document section >>> describing this r

Re: Bug report for ox-icalendar: newlines should be CRLF

> It's in rfc5545 [1], referenced to from rfc7986 [2]. yes, that's it. There is also this validator that can check files against the spec: https://icalendar.org/validator.html Stpehen

Re: Bug report for ox-icalendar: newlines should be CRLF

writes: >> > There is a related issue about EOLs, not just \r\n -- each line should >> > be a maximum of 75 characters; this is handled by >> > org-icalendar-fold-string >> >> May you please provide a link to the iCalendar spec document section >> describing this requirement? > > It's in rfc55

Re: Bug report for ox-icalendar: newlines should be CRLF

On Fri, Apr 14, 2023 at 10:13:48AM +, Ihor Radchenko wrote: > "Stephen J. Eglen" writes: > > >> https://list.orgmode.org/87355ikzwk.fsf@localhost/T/#m180c100587d3d88ab5787942271a546b51891996 > > > > Thanks for copying me in on this. > > > > There is a related issue about EOLs, not just \r\n -

Re: Bug report for ox-icalendar: newlines should be CRLF

"Stephen J. Eglen" writes: >> https://list.orgmode.org/87355ikzwk.fsf@localhost/T/#m180c100587d3d88ab5787942271a546b51891996 > > Thanks for copying me in on this. > > There is a related issue about EOLs, not just \r\n -- each line should > be a maximum of 75 characters; this is handled by > org-

Re: Bug report for ox-icalendar: newlines should be CRLF

> Ihor Radchenko writes: > >> Sorry for the late reply. >> >> Do I understand correctly that all the ical lines must use \r\n? [1] > > Following up here that I have pushed a fix for the EOL issue in > ox-icalendar: > > https://list.orgmode.org/87355ikzwk.fsf@localhost/T/#m180c100587d3d88ab57879

Re: Bug report for ox-icalendar: newlines should be CRLF

Ihor Radchenko writes: > Sorry for the late reply. > > Do I understand correctly that all the ical lines must use \r\n? [1] Following up here that I have pushed a fix for the EOL issue in ox-icalendar: https://list.orgmode.org/87355ikzwk.fsf@localhost/T/#m180c100587d3d88ab5787942271a546b5189199

Re: Bug report for ox-icalendar: newlines should be CRLF

"Stephen J. Eglen" writes: > The lines from BEGIN:VEVENT to CATEGORIES:test inclusive have CR (^M) as well > as LF (^J) as newline [in the text above, I've converted the ^M to *** > to see them eaer. Is that intended? Uploading the file to > https://icalendar.org/validator.html gives me the err

Re: Bug report for ox-icalendar: newlines should be CRLF

Hello, just to confirm. The exporter is inconsistent in adding which kind of EOL sequence. Detlef Am Fri, 06 Jan 2023 08:30:41 + schrieb "Stephen J. Eglen" : > Hello, > > If I have a test file > > -- > > * test 1 > > <2

Bug report for ox-icalendar: newlines should be CRLF

Hello, If I have a test file -- * test 1 <2023-01-05 Thu 19:00-19:20> -- and then convert to an .ics file using C-c C-e c f I get the attached test.ics fil

Re: Bug report: org-preview-latex fails when using tramp

Timothy writes: > Confirmed. > > I just tried this by creating an Org file on a Debian server (I run OpenSUSE > with TexLive 2021). From looking at the `*Org Preview LaTeX Output*' buffer, > it > appears that the temp file is created on my local machine, and then the > process > is called on th

Re: [BUG] bug report [9.6 (9.6-??-e7ea951 @ /Users/anthonyle/.emacs.d/.local/straight/build-28.0.91/org/)]

legac...@icloud.com writes: > Your bug report will be posted to the Org mailing list. Could you please provide some more details on what happened? > Package: Org mode version 9.6 (9.6-??-e7ea951 @ > /Users/anthonyle/.emacs.d/.local/straight/build-28.0.91/org/) Now, from your Org v

[BUG] bug report [9.6 (9.6-??-e7ea951 @ /Users/anthonyle/.emacs.d/.local/straight/build-28.0.91/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

Re: Bug report

Looks like I was trying to be too clever. :) I used org-mode to write the bug report. The problem isn't that the formatting fails in source code blocks. I put it in one so that it would appear verbatim. If you copy the contents of the block into a normal paragraph, you should be able t

Re: Bug report

On Wednesday, 1 Jun 2022 at 23:24, Max Nikulin wrote: > > I think, it is org and #+begin_src is used to demonstrate a snippet of > org markup, so to reproduce the problem try it in a regular paragraph. Ah, sorry, missed the point entirely! -- : Eric S Fraga, with org release_9.5.3-520-g4dda0d

Re: Bug report

On 01/06/2022 22:37, Eric S Fraga wrote: On Wednesday, 1 Jun 2022 at 07:53, Topi Mäenpää wrote: I have trouble escaping a dollar sign in org-mode documents. I tried to enter the following: #+begin_src A (14 G$) B (6 G$) #+end_src You may use entities: \dollar I have no problem with this.

Re: Bug report

On Wednesday, 1 Jun 2022 at 07:53, Topi Mäenpää wrote: > I have trouble escaping a dollar sign in org-mode documents. I > tried to enter the following: > > #+begin_src > A (14 G$) B (6 G$) > #+end_src I have no problem with this. What version of org are you using? Out of curiosity, what languag

Bug report

* Bug report I have trouble escaping a dollar sign in org-mode documents. I tried to enter the following: #+begin_src A (14 G$) B (6 G$) #+end_src This may look weird to an American viewer, but in Finland we place all units (including monetary units) after the quantity. Anyhow, org-mode

Re: A question/bug report(?)

On 30/03/2022 12:14, Pedro Andres Aranda Gutierrez wrote: Thanks for answering :-) I'm currently solving the issue with #+BEGIN_export LaTeX \begin{verbatim}[commandchars=\\\{\}] student@juju:~$ \textbf{sudo bootstrap-juju.sh} \end{verbatim} #+END_export What I was wondering is whether we coul

Re: A question/bug report(?)

Hi Eric, Thanks for answering :-) I'm currently solving the issue with #+BEGIN_export LaTeX \begin{verbatim}[commandchars=\\\{\}] student@juju:~$ \textbf{sudo bootstrap-juju.sh} \end{verbatim} #+END_export What I was wondering is whether we could have something like: #+ATTR_LATEX :raw t :attrib

Re: A question/bug report(?)

On Tuesday, 29 Mar 2022 at 21:44, Max Nikulin wrote: > If LaTeX is the only export target then a more simple way exists: > > #+begin_export latex Yes, of course! -- : Eric S Fraga, with org release_9.5.2-420-g971eb6 in Emacs 29.0.50

Re: A question/bug report(?)

On 29/03/2022 20:12, Eric S Fraga wrote: I'm not sure but maybe you want to use a src block, #+begin_src latex :exports results ... #+end_src ? I am not entirely clear how you wish org to know what is "raw" and what is "LaTeX". If LaTeX is the only export target then a more simple way exists

Re: A question/bug report(?)

I'm not sure but maybe you want to use a src block, #+begin_src latex :exports results ... #+end_src ? I am not entirely clear how you wish org to know what is "raw" and what is "LaTeX". -- : Eric S Fraga, with org release_9.5.2-420-g971eb6 in Emacs 29.0.50

A question/bug report(?)

Hi, I'm using org-mode mainly to generate LaTEX (both documents and presentations). I'd like to know if there is any way to flag that the contents of an EXAMPLE block should be passed RAW to LaTEX. I need this to be able to include my colouring commands in some listings, which otherwise break beca

Re: [BUG] Bug Report Requested [9.5.2 (9.5.2-ga98ae4 @ /Users/apc/.emacs.d/straight/build/org/)]

Alejandro Pérez Carballo writes: > I was simply calling `org-agenda` when I was prompted to submit this report. > I'm submitting this as requested. Thanks for reporting! If you keep seeing the warning, please followup this thread showing the warning text. It will give us clues what went wrong

[BUG] Bug Report Requested [9.5.2 (9.5.2-ga98ae4 @ /Users/apc/.emacs.d/straight/build/org/)]

Hello, I was simply calling `org-agenda` when I was prompted to submit this report. I'm submitting this as requested. Thanks for all your good work on this, APC Emacs : GNU Emacs 28.0.90 (build 1, x86_64-apple-darwin19.6.0, NS appkit-1894.60 Version 10.15.7 (Build 19H1419)) of 2021-12-14

Re: Bug report: org-preview-latex fails when using tramp

Confirmed. I just tried this by creating an Org file on a Debian server (I run OpenSUSE with TexLive 2021). From looking at the `*Org Preview LaTeX Output*' buffer, it appears that the temp file is created on my local machine, and then the process is called on the remote machine. ┌ │ This is

Bug report: org-preview-latex fails when using tramp

Hello, Since the instructions say that bugs should be reported on the mailing list, I do so here. When visiting a file by tramp over ssh, doing latex preview fails. * Version Tag 9.4.6 (commit:652430128) * To reproduce: Create the following org file: #+begin_example * Testing formulas \[\xi^

Re: org-persist - bug report

Thanks. Worked for me

Re: org-persist - bug report

On 21/10/2021 23:03, Ihor Radchenko wrote: It was malformed add-hook call. Fixed in 5315773e8. Thank you, Ihor. I do not see problems I have noticed today anymore.

Re: org-persist - bug report

> Ihor Radchenko writes: > It was malformed add-hook call. Fixed in 5315773e8. Great! I've pulled org-mode and I can confirm I no longer see my org-persist errors. Excellent. I'm looking at the vc-diff buffer and it's amazing that such a small omission has such a major effect. Best wish

Re: org-persist - bug report

It was malformed add-hook call. Fixed in 5315773e8.

Re: org-persist - bug report

Ihor Radchenko writes: > ... There is no problem on Emacs 28, but I can see the error > using Emacs 26.3. I used the following command line from inside the Git > folder to run Emacs (debug.org is the provided minimal file): > > emacs -Q -L ./lisp -l org /tmp/debug.org > > Interestingly, the foll

Re: org-persist - bug report

Colin Baxter 😺 writes: > > M-x org-lint > > > Debugger entered--Lisp error: (error "Variable binding depth > > exceeds max-specpdl-size") ... org-filename-concat > > I can reproduce that. Then emacs just hangs. I have the latest org-mode. Thanks for another confirmation. I tried har

Re: org-persist - bug report

> Max Nikulin writes: > On 21/10/2021 02:04, Colin Baxter 😺 wrote: >> >> The max-specpdl-size error has happened again when I tried to add >> a note to an agenda item. Emacs hung and had to be killed. The >> debugger buffer was empty and the only other information given

org-persist? error "Variable binding depth exceeds max-specpdl-size" (was: org-persist - bug report)

Max Nikulin writes: > Ihor, I have seen your instructions for more debug info, but I have not > tried them yet. In the meanwhile I have tracked my problem down to to > the following minimal file > > --- >8 --- > #+begin_example org >,* H > #+end_example > --- 8< --- > > M-x org-lint > > Deb

Re: org-persist - bug report

On 21/10/2021 02:04, Colin Baxter 😺 wrote: The max-specpdl-size error has happened again when I tried to add a note to an agenda item. Emacs hung and had to be killed. The debugger buffer was empty and the only other information given was the message: mapc: Lisp nesting exceeds `max-lisp-eval-d

Re: org-persist - bug report

Colin Baxter 😺 writes: > > (setq org-element--cache-self-verify 'backtrace) > > (setq org-element--cache-self-verify-frequency 1) > > I set the above in my ~/.emacs > > > If a warning appears, backtrace could be helpful. If not, it > > should be something to do with org-element-ca

Re: Clarify bug report requirements wrt mailing list subscription

> subscribe to the list and confirm your email address. > > Moreover, that it seemingly is a soft requirement implies that I'm not > getting any feedback for some time about the status of my report. Indeed. Spam protections can cause problems. However, what are your expe

Clarify bug report requirements wrt mailing list subscription

Hi all, I find the instructions about bug reporting in [1] lacking a heads-up that subscription to the mailing list is a (soft?) prerequisite. It's true that it links to [2] which states: You can subscribe to the list from this web page. If you are not a member of the mailing list, your m

Re: org-persist - bug report

> Ihor Radchenko writes: > Colin Baxter 😺 writes: >> >> I just upgraded my org-mode to the latest version in >> >> git. Whenever I visited a certain org file, my Emacs became >> >> unusable. Any attempt to use M-x (execute-extended-command) >> >> resulted in max-specpdl-s

Re: org-persist - bug report

Colin Baxter 😺 writes: > >> I just upgraded my org-mode to the latest version in > >> git. Whenever I visited a certain org file, my Emacs became > >> unusable. Any attempt to use M-x (execute-extended-command) > >> resulted in max-specpdl-size errors as did using C-x C-c to exit

Re: org-persist - bug report

> Ihor Radchenko writes: > Alastair Burt writes: >> Hi there, >> >> I couldn't find an issue-tracking system for org-mode as they >> have for projects on github. So I'm emailing you directly. > Thanks! The bug reporting for Org mode is by email. You can send > e

Re: org-persist - bug report

Alastair Burt writes: > Hi there, > > I couldn't find an issue-tracking system for org-mode as they have for > projects on github. So I'm emailing you directly. Thanks! The bug reporting for Org mode is by email. You can send email to Org mailing list at emacs-orgmode@gnu.org (also, see "1.4 Fee

Re: Bug report: remote file python src output gives FileNotFound (+ suggested fix)

Hi Paul, I'm unable to reproduce the issue, and believe this issue has already been fixed in the latest version of org-mode. See this patch [1]. Could you please upgrade to Org 9.4 and test again? Thanks, Jack [1] https://orgmode.org/list/87h7t16red.fsf@pc.i-did-not-set--mail-host-address--so-t

Bug report: remote file python src output gives FileNotFound (+ suggested fix)

When working remotely, a python SRC block with a session and :results set to output will return a FileNotFoundError. To reproduce this bug: 1. Open a .org file remotely 2. Insert the following #+BEGIN_SRC python :results output :session check print("a") #+END_SRC 3. org-ctrl-c-ctrl-c in the code b

Re: Possible bug report: URL capitalization in online manual

Hi Ori, thanks a lot for taking the trouble to produce this file, very useful. I've now installed the rewrite rules on the server and all these links are redirecting correctly. Given the amount of Org documentation links living out there, that's really a good idea. > Versioned folders living sid

Re: Possible bug report: URL capitalization in online manual

Hi Bastien, Attached are the relevant URL aliases. When I initially saw the issue I thought it was a matter of a change to the way the docs are built, not old vs new documentation. That makes the list I've attached a little tricky to maintain. Of course within emacs is the best way for a user to

Re: Possible bug report: URL capitalization in online manual

Hi Ori, Ori writes: > I'm not sure which repo this all lives in but I believe since > information has been added to the paths, this should be easy. The > other direction would be trickier and would need the old scheme. > > Wherever the current filename has capital letters after the first > chara

Re: Possible bug report: URL capitalization in online manual

I'm not sure which repo this all lives in but I believe since information has been added to the paths, this should be easy. The other direction would be trickier and would need the old scheme. Wherever the current filename has capital letters after the first character, make an alias using the sent

Re: Possible bug report: URL capitalization in online manual

Hi Ori, Ori Barbut writes: > Not sure if this was intentional? Yes -- old html manual pages where still around and I deleted them, because they confused people. > If so would it make sense to alias the old URLs for people who have > linked to the manual over the years? Yes, such aliases would

Possible bug report: URL capitalization in online manual

It seems that sometime in the past week the capitalization scheme of URLs generated for the online manual has changed. For example I see as of 2020-02-02 per the cache on Bing, the following url worked: https://orgmode.org/manual/Structure-of-code-blocks.html The new URL is: https://orgmode.org/ma

Re: Bug: About org-submit-bug-report [9.3 (release_9.3 @ /usr/local/share/emacs/27.0.50/lisp/org/)]

Hi Michael, > I want to suggest to make `report-org-bug' and alias for the command > `org-submit-bug-report'. That's the name I expected (considering > "report-emacs-bug"), also some other Emacs packages name their bug > reporting command according to th

Re: Bug Report: Broken Link in Worg

Hi Joshua, Joshua Meyers writes: > In this page (https://orgmode.org/worg/org-gtd-etc.html) the link to > the "very instructive post by Pete Phillips" now directs to the > defunct gmane.org.  I think I tracked down the post it is supposed to > link to, so I don't want others to have to do this w

Re: org id update locations search sequence (was Re: bug report org mode)

Hi Samuel, I have difficulties understanding the proposal. Can you restate it as a MEC (Minimal Enhancing Change)? Thanks, -- Bastien

org id update locations search sequence (was Re: bug report org mode)

i have been wondering about the search sequence for this function. id updating is capable of being quite slow, which can be distracting when you follow a link and emacs hangs for a while, so i was thinking maybe this could be optimized. idk about data structures and searching, but i think the seq

Re: bug report org mode

Hi Siegmar, Siegmar Maier writes: > According to my examination the problem is with > org-id-update-id-locations. Removeing that column makes it work > again. > If I put that line behind it works also again Yes, `org-todo-keyword-faces' will be taken into account when set before any actual font

bug report org mode

Hi, I found following strange behaviour: with windwos 10 emacs-version: GNU Emacs 26.3 (build 1, x86_64-mingw32) of 2019-08-29 org-version: 9.3.1-elpaplus if I use following sequence the coloring of the keywords is not working: (org-id-update-id-locations) (setq org-id-link-to-org-use-id t) (setq

[FWD from emacs-orgmode] Re: Bug: About org-submit-bug-report [9.3 (release_9.3 @ /usr/local/share/emacs/27.0.50/lisp/org/)]

in emacs-orgmode (below). > I want to suggest to make `report-org-bug' and alias for the command > `org-submit-bug-report'. That's the name I expected (considering > "report-emacs-bug"), also some other Emacs packages name their bug > reporting command acco

Bug: About org-submit-bug-report [9.3 (release_9.3 @ /usr/local/share/emacs/27.0.50/lisp/org/)]

Hello, I want to suggest to make `report-org-bug' and alias for the command `org-submit-bug-report'. That's the name I expected (considering "report-emacs-bug"), also some other Emacs packages name their bug reporting command according to this scheme. The additi

Re: [O] Bug Report: Broken Link in Worg

Joshua Meyers writes: > In this page (https://orgmode.org/worg/org-gtd-etc.html) the link to > the "very instructive post by Pete Phillips" now directs to the > defunct gmane.org.  I think I tracked down the post it is supposed > to link to, so I don't want others to have to do this work again: >

[O] Bug Report: Broken Link in Worg

In this page (https://orgmode.org/worg/org-gtd-etc.html) the link to the "very instructive post by Pete Phillips" now directs to the defunct gmane.org. I think I tracked down the post it is supposed to link to, so I don't want others to have to do this work again: https://lists.gnu.org/archive/htm

Re: [O] Bug report: The link in the CDLaTeX section of the manual (11.5.3) is dead

Hello, Qqwy/Wiebe-Marten writes: > I think the link should be changed to one of: > > - https://staff.fnwi.uva.nl/c.dominik/Tools/cdlatex/ , which seems to be > the location that the original link was moved to. > > - https://github.com/cdominik/cdlatex , which is a repository containing > the lat

[O] Bug report: The link in the CDLaTeX section of the manual (11.5.3) is dead

Dear maintainers of org-mode, I was reading through the online manual today, and attempted to install `CDLaTeX` using the instructions found at https://orgmode.org/manual/CDLaTeX-mode.html (Section 11.5.3 of the manual). However, the link to find `cdlatex.el` and `texmathp.el` (http://www.astro.

Re: [O] org-clock-in-last bug report

On 2018-10-09, at 18:28, Nicolas Goaziou wrote: > Hello, > > Marcin Borkowski writes: > >> org-clock-in-last used to do nothing when already clocking. Now it >> clocks out and immediately in in the same task. It does that even in >> emacs -Q. >> >> Org mode version 9.1.14 (release_9.1.14-968

Re: [O] org-clock-in-last bug report

Hello, Marcin Borkowski writes: > org-clock-in-last used to do nothing when already clocking. Now it > clocks out and immediately in in the same task. It does that even in > emacs -Q. > > Org mode version 9.1.14 (release_9.1.14-968-gfdb36d) > > I'd try to debug it myself, but I'm rather in a h

Re: [O] org-clock-in-last bug report

On 2018-10-09, at 16:25, Marcin Borkowski wrote: > Hi all, > > org-clock-in-last used to do nothing when already clocking. Now it > clocks out and immediately in in the same task. It does that even in > emacs -Q. > > Org mode version 9.1.14 (release_9.1.14-968-gfdb36d) > > I'd try to debug it

[O] org-clock-in-last bug report

Hi all, org-clock-in-last used to do nothing when already clocking. Now it clocks out and immediately in in the same task. It does that even in emacs -Q. Org mode version 9.1.14 (release_9.1.14-968-gfdb36d) I'd try to debug it myself, but I'm rather in a hurry now, sorry. I looked into git log

Re: [O] BUG report [Was: computing the size of a tikz to png image during export]

2018-01-30 21:59 GMT+01:00 Nicolas Goaziou : > Hello, > > Fabrice Popineau writes: > > > You should have a look at commit 38be85124551083d269. > > It prevents evaluation of the by-backend form in parameters. > > It doesn't. > > My mistake: it optionaly prevents :-) > It prevents evaluation con

Re: [O] BUG report [Was: computing the size of a tikz to png image during export]

Hello, Fabrice Popineau writes: > You should have a look at commit 38be85124551083d269. > It prevents evaluation of the by-backend form in parameters. It doesn't. It prevents evaluation conditionally, i.e., when an optional argument is non-nil. The same argument prevents expanding Noweb refer

Re: [O] BUG report [Was: computing the size of a tikz to png image during export]

> On Jan 28, 2018, at 11:49 PM, Fabrice Popineau > wrote: > > You should have a look at commit 38be85124551083d269. > It prevents evaluation of the by-backend form in parameters. > You are right. I do not see a clean way to do what `by-backend' would have done prior to that commit. Maybe

Re: [O] BUG report [Was: computing the size of a tikz to png image during export]

2018-01-29 2:34 GMT+01:00 Berry, Charles : > > On Jan 28, 2018, at 3:24 PM, Nicolas Goaziou > wrote: > > > > Would you have an ECM? I don't know what is "the by-backend trick". > > Not a bug AFAICS. > > `by-backend' is a macro mentioned here: > > https://lists.gnu.org/archive/html/emacs-orgmode/2

Re: [O] BUG report [Was: computing the size of a tikz to png image during export]

> On Jan 28, 2018, at 3:24 PM, Nicolas Goaziou wrote: > > Would you have an ECM? I don't know what is "the by-backend trick". Not a bug AFAICS. `by-backend' is a macro mentioned here: https://lists.gnu.org/archive/html/emacs-orgmode/2013-07/msg00500.html I guess it needs to use `org-export-

Re: [O] BUG report [Was: computing the size of a tikz to png image during export]

2018-01-29 0:24 GMT+01:00 Nicolas Goaziou : > Hello, > > Fabrice Popineau writes: > > > Well, I think there is a problem with the current master > > since commit 38be85124551083d269. > > > > The problem is that the by-backend trick which were tolerated before > > does not work anymore. > > > > Te

Re: [O] BUG report [Was: computing the size of a tikz to png image during export]

Hello, Fabrice Popineau writes: > Well, I think there is a problem with the current master > since commit 38be85124551083d269. > > The problem is that the by-backend trick which were tolerated before > does not work anymore. > > Tested between Org 9.1.6 as in current emacs-26.0.91 release versus

[O] BUG report [Was: computing the size of a tikz to png image during export]

Well, I think there is a problem with the current master since commit 38be85124551083d269. The problem is that the by-backend trick which were tolerated before does not work anymore. Tested between Org 9.1.6 as in current emacs-26.0.91 release versus current Org master. More over, ignoring the n

Re: [O] bug report: + is not escaped in org-link-escape

Nicolas Goaziou twisted the bytes to say: Nicolas> Hello, Nicolas> dmg writes: >> org-link-escape only replaces space, [, ], and % >> >> but search in google/gmail is replacing + also. >> >> The simplest solution is to add 43 to org-link-escape-chars: >> >> org-link-escape-chars is

Re: [O] bug report: + is not escaped in org-link-escape

Hello, dmg writes: > org-link-escape only replaces space, [, ], and % > > but search in google/gmail is replacing + also. > > The simplest solution is to add 43 to org-link-escape-chars: > >org-link-escape-chars is a variable defined in ‘org.el’. >Its value is (32 91 93 37) > > This va

[O] bug report: + is not escaped in org-link-escape

hi everybody, I am running 9.0.10. org-link-escape only replaces space, [, ], and % but search in google/gmail is replacing + also. The simplest solution is to add 43 to org-link-escape-chars: org-link-escape-chars is a variable defined in ‘org.el’. Its value is (32 91 93 37) This var

Re: [O] org-submit-bug-report takes ages to format the message buffer

Hello, Uwe Brauer writes: > Sorry I wanted to send a bug report on a different issue but it > took/takes ages to format the corresponding message buffer using > org-submit-bug-report. > > What could I do? You could provide a profiler report with both M-x profiler-start

[O] org-submit-bug-report takes ages to format the message buffer

Hi Sorry I wanted to send a bug report on a different issue but it took/takes ages to format the corresponding message buffer using org-submit-bug-report. What could I do? Uwe Brauer

Re: [O] [Bug Report] wrong item is modified when multiple frames are open

Hello, Anders Papitto writes: > I have org version 9.0.3 (and I've been noticing this the whole time I've > used org - only just now reporting it), and this is 100% consistent for me. > > I often have two client frames open, connected to the same emacs daemon. > One frame will be displaying the

[O] [Bug Report] wrong item is modified when multiple frames are open

I have org version 9.0.3 (and I've been noticing this the whole time I've used org - only just now reporting it), and this is 100% consistent for me. I often have two client frames open, connected to the same emacs daemon. One frame will be displaying the org agenda (I'll call this Frame 1), while

Re: [O] Invalid read syntax: "?" when switching org-dates or when tying to org-submit-bug-report

Hello Nicolas, that worked perfectly. I had a strange character in that file and now it works good. Thanks, Michael Am 2017-05-08 11:52, schrieb Nicolas Goaziou: > michael.zi...@xiron.de writes: > >> When i byte-compile the file i get the following error: >> >> Compiling file >> c:/Use

Re: [O] Invalid read syntax: "?" when switching org-dates or when tying to org-submit-bug-report

michael.zi...@xiron.de writes: > When i byte-compile the file i get the following error: > > Compiling file > c:/Users/sane/AppData/Roaming/.emacs.d/elpa/org-20170502/org-clock.el at > Mon May 8 11:27:30 2017 > org-clock.el:1949:1:Error: Invalid read syntax: "?" It looks odd. Could you double-c

Re: [O] Invalid read syntax: "?" when switching org-dates or when tying to org-submit-bug-report

ce. Michael Am 2017-05-08 11:09, schrieb Nicolas Goaziou: > Hello, > > michael.zi...@xiron.de writes: > >> when i try to swicht an active timestamp via org-shitright or when i >> fire M-x org-submit-bug-report i get the following error: >> >> Debugger entered--

  1   2   3   >