From: Gregory Heytings <gregory@heytings.org>
To: Hongyi Zhao <hongyi.zhao@gmail.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: Quickly check for differences in code and locate possible errors.
Date: Wed, 29 Mar 2023 08:34:27 +0000 [thread overview]
Message-ID: <10ececa33fab16df39e9@heytings.org> (raw)
In-Reply-To: <CAGP6POKjB+VGSti8uymJkVeY_exG86sEb7Dmf4VEqFQLiDi+JA@mail.gmail.com>
>
> Now, let's consider a further problem: if I only have the wrong version
> of the code at hand, I want to quickly locate the possible problematic
> code characters from it. Is it possible?
>
If you can unambiguously define what "possible problematic code
characters" are (and what their non-problematic counterparts are), that's
possible. I don't know enough about Mathematica to help you more, sorry.
prev parent reply other threads:[~2023-03-29 8:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 13:56 Quickly check for differences in code and locate possible errors Hongyi Zhao
2023-03-28 14:40 ` gebser
2023-03-28 15:03 ` Gregory Heytings
2023-03-29 2:04 ` Hongyi Zhao
2023-03-29 8:34 ` Gregory Heytings [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:
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=10ececa33fab16df39e9@heytings.org \
--to=gregory@heytings.org \
--cc=help-gnu-emacs@gnu.org \
--cc=hongyi.zhao@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).