emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: org code and error catching
Date: Thu, 01 Jun 2023 12:12:37 +0000	[thread overview]
Message-ID: <87pm6fwfd6.fsf@localhost> (raw)
In-Reply-To: <878rdnq1iy.fsf@web.de>

Michael Heerdegen <michael_heerdegen@web.de> 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).  I would prefer to help differently (like reviewing a patch),
> honestly, unless there is really no one more appropriate to find.

I changed instances that appear to be safe.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=5b4eebfab

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


  reply	other threads:[~2023-06-01 12:09 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 [this message]
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

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  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=87pm6fwfd6.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=michael_heerdegen@web.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).