emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: org code and error catching
Date: Sat, 03 Jun 2023 00:44:59 +0200	[thread overview]
Message-ID: <87sfb9pjpw.fsf@web.de> (raw)
In-Reply-To: <87cz2e5mfu.fsf@localhost> (Ihor Radchenko's message of "Fri, 02 Jun 2023 07:54:13 +0000")

Ihor Radchenko <yantar92@posteo.net> 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, and I was unsure if it is truly
> safe.

I don't recall either why I originally needed backtraces for it.  There
was a reason, but I don't remember.

> I see no obvious downsides though.
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=1cb5de621

Thanks, Ihor.


      reply	other threads:[~2023-06-02 22:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-26 18:34 org code and error catching Michael Heerdegen
2023-05-12 13:28 ` Ihor Radchenko
2023-05-15  0:38   ` Michael Heerdegen
2023-05-15  7:28     ` Ihor Radchenko
2023-05-16  3:27       ` Michael Heerdegen
2023-05-16  9:33         ` Ihor Radchenko
2023-05-16 19:55           ` Michael Heerdegen
2023-05-16 20:04             ` Ihor Radchenko
2023-05-16 23:50               ` Michael Heerdegen
2023-06-01 12:12                 ` Ihor Radchenko
2023-06-02  0:41                   ` Michael Heerdegen
2023-06-02  1:12                     ` Michael Heerdegen
2023-06-02  7:54                       ` Ihor Radchenko
2023-06-02 22:44                         ` Michael Heerdegen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sfb9pjpw.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@posteo.net \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).