From: Andrea Corallo <acorallo@gnu.org>
To: Pranshu <pranshusharma366@gmail.com>
Cc: 71375@debbugs.gnu.org
Subject: bug#71375: 30.0.50
Date: Wed, 05 Jun 2024 05:13:07 -0400 [thread overview]
Message-ID: <yp1y17jn464.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <877cf36eu9.fsf@gmail.com> (Pranshu's message of "Wed, 05 Jun 2024 17:14:38 +1000")
Pranshu <pranshusharma366@gmail.com> writes:
> Currently in table.el, charecters such as '$' sign are escaped. This
> diff adds a variable which can control what is escaped or not. Since a
> backslash is escaped in a different way to other charecters in latex,
> the variable had to be a cons cell of a regexp and bool.
Hi Pranshu,
I think you sent this by mistake twice, I'm merging it with 71364.
Andrea
prev parent reply other threads:[~2024-06-05 9:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 7:14 bug#71375: 30.0.50 Pranshu
2024-06-05 9:13 ` Andrea Corallo [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=yp1y17jn464.fsf@fencepost.gnu.org \
--to=acorallo@gnu.org \
--cc=71375@debbugs.gnu.org \
--cc=pranshusharma366@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.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).