Re: org code and error catching

2023-06-02 Thread Michael Heerdegen
Ihor Radchenko writes: > > Though, I think you didn't change the occurrence that this thread > > started with - `org-eval'. Does changing this one cause problems? > > Tests are passing. > I originally skipped it because it did not look useful from a brief > glance to have full backtraces there,

Re: org code and error catching

2023-06-02 Thread Ihor Radchenko
Michael Heerdegen writes: > Michael Heerdegen writes: > >> I reviewed it shortly - looks appropriate. > > Though, I think you didn't change the occurrence that this thread > started with - `org-eval'. Does changing this one cause problems? Tests are passing. I originally skipped it because it

Re: org code and error catching

2023-06-01 Thread Michael Heerdegen
Michael Heerdegen writes: > I reviewed it shortly - looks appropriate. Though, I think you didn't change the occurrence that this thread started with - `org-eval'. Does changing this one cause problems? Michael.

Re: org code and error catching

2023-06-01 Thread Michael Heerdegen
Ihor Radchenko writes: > I changed instances that appear to be safe. > https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=5b4eebfab I reviewed it shortly - looks appropriate. Thank you very much! Michael.

Re: org code and error catching

2023-06-01 Thread Ihor Radchenko
Michael Heerdegen writes: >> As for condition-case-unless-debug, may you create a patch? >> But please do not replace everything blindly - I know for sure that at >> least some `condition-case' clauses are there on purpose. > > I nearly never had a closer look at the org-mode code (other than >

Re: org code and error catching

2023-05-16 Thread Michael Heerdegen
Ihor Radchenko writes: > As for condition-case-unless-debug, may you create a patch? > But please do not replace everything blindly - I know for sure that at > least some `condition-case' clauses are there on purpose. I nearly never had a closer look at the org-mode code (other than blindly).

Re: org code and error catching

2023-05-16 Thread Ihor Radchenko
Michael Heerdegen writes: > Ihor Radchenko writes: > >> What are those? >> I do not have anything failing on my side. > > See the attached file. I had been using an up-to-date Emacs master build. Ah. Different locale (LANG). It is

Re: org code and error catching

2023-05-16 Thread Michael Heerdegen
Ihor Radchenko writes: > What are those? > I do not have anything failing on my side. See the attached file. I had been using an up-to-date Emacs master build. Michael. <>

Re: org code and error catching

2023-05-16 Thread Ihor Radchenko
Michael Heerdegen writes: > Hmm - mine gave a different result: I cloned the org-mode archive from > https://git.savannah.gnu.org/git/emacs/org-mode.git, called "make" and > ran the tests as described in the "testing/README". That gave 6 failing > tests. What are those? I do not have anything

Re: org code and error catching

2023-05-15 Thread Michael Heerdegen
Ihor Radchenko writes: > In my attempts, the tests started failing for no obvious reason. > Just from changing `condition-case' to `condition-case-unless-debug'. > > Though I did not investigate if it happened for every atomic change. Hmm - mine gave a different result: I cloned the org-mode

Re: org code and error catching

2023-05-15 Thread Ihor Radchenko
Michael Heerdegen writes: > Ihor Radchenko writes: > >> This is a good idea, except that `condition-case-unless-debug' has >> non-obvious side effects that interfere with ERT (Org testing system). > > What side effects are these? In my attempts, the tests started failing for no obvious reason.

Re: org code and error catching

2023-05-14 Thread Michael Heerdegen
Ihor Radchenko writes: > This is a good idea, except that `condition-case-unless-debug' has > non-obvious side effects that interfere with ERT (Org testing system). What side effects are these? Thx, Michael.

Re: org code and error catching

2023-05-12 Thread Ihor Radchenko
Michael Heerdegen writes: > I had a hard time to debug some problem with the expansion of some > capture template because org catched the error even when I had set > `debug-on-error'. Would it be possible to make some functions, > e.g. `org-eval' in my case (probably some more?), use >

org code and error catching

2020-10-26 Thread Michael Heerdegen
Hello, I had a hard time to debug some problem with the expansion of some capture template because org catched the error even when I had set `debug-on-error'. Would it be possible to make some functions, e.g. `org-eval' in my case (probably some more?), use `condition-case-unless-debug' instead