unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Hongyi Zhao <hongyi.zhao@gmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: Convert some Latex expressions in Emacs.
Date: Tue, 17 May 2022 11:44:22 +0800	[thread overview]
Message-ID: <CAGP6POJx_psqM+n-fBa743QURGRotfi_RsAgiiQCaNyogUkVWQ@mail.gmail.com> (raw)
In-Reply-To: <87zgjg2676.fsf@web.de>

On Tue, May 17, 2022 at 11:23 AM Michael Heerdegen
<michael_heerdegen@web.de> wrote:
>
> Hongyi Zhao <hongyi.zhao@gmail.com> writes:
>
> > I roughly browse the relevant introduction here [1]. It seems that all
> > Emacs Lisp based regex patterns are more complicated and tedious than
> > other languages, e.g., python, wolfram, and so on.
> >
> > [1] https://elpa.gnu.org/packages/peg.html
>
> No, that's something different (and a bit more powerful).  Didn't want
> to confuse you.

I rechecked the description here [1], and still can't find any
difference. Why do you say they are different?

[1] https://www.emacswiki.org/emacs/peg.el

>
> When you do want to use regexps - what's the problem?  You have
> incremental regexp based query-replace, symbolic regexps with `rx',
> nearly anything one can dream of.
>
> Michael.
>
>



  parent reply	other threads:[~2022-05-17  3:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16  3:25 Convert some Latex expressions in Emacs Hongyi Zhao
2022-05-16  4:49 ` Emanuel Berg
2022-05-17  0:02 ` Michael Heerdegen
2022-05-17  2:12   ` Hongyi Zhao
2022-05-17  2:22     ` Emanuel Berg
2022-05-17  3:23     ` Michael Heerdegen
2022-05-17  3:38       ` Michael Heerdegen
2022-05-17  3:44       ` Hongyi Zhao [this message]
2022-05-17  4:46         ` Emanuel Berg
2022-05-18  0:25           ` Hongyi Zhao
2022-05-17 23:45         ` Michael Heerdegen
2022-05-18  0:23           ` Hongyi Zhao

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=CAGP6POJx_psqM+n-fBa743QURGRotfi_RsAgiiQCaNyogUkVWQ@mail.gmail.com \
    --to=hongyi.zhao@gmail.com \
    --cc=help-gnu-emacs@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.
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).