From: Richard Copley <rcopley@gmail.com>
To: Michael Maurer <maurer.michael@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: custom function getting initialized randomly
Date: Mon, 27 Mar 2023 16:06:38 +0100 [thread overview]
Message-ID: <CAPM58ohPY1vv9-w+kH+sFMSvLm1ZYCj=M7pf1zJeQs6h55TvNw@mail.gmail.com> (raw)
In-Reply-To: <CAH-0+bBkfHAddf91ZguQ_9hUXzGnhbMQto4ikphw+9GbZw4WDA@mail.gmail.com>
On Mon, 27 Mar 2023 at 15:56, Michael Maurer <maurer.michael@gmail.com> wrote:
> Would wrapping the body of the function in (ignore errors ..) be an ok
> solution as far as cheap hacks go, or is it too sketchy?
Your call, but I would try wrapping it in (when kill-ring ...) before
going that far.
next prev parent reply other threads:[~2023-03-27 15:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 8:22 custom function getting initialized randomly Michael Maurer
2023-03-27 13:56 ` Richard Copley
2023-03-27 14:56 ` Michael Maurer
2023-03-27 15:06 ` Richard Copley [this message]
2023-03-27 15:20 ` tomas
2023-03-27 15:30 ` Michael Maurer
2023-03-27 15:52 ` tomas
-- strict thread matches above, loose matches on Subject: below --
2023-03-27 8:29 Michael Maurer
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPM58ohPY1vv9-w+kH+sFMSvLm1ZYCj=M7pf1zJeQs6h55TvNw@mail.gmail.com' \
--to=rcopley@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=maurer.michael@gmail.com \
/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.
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).