From: Sebastian Urban <mrsebastianurban@gmail.com>
To: eliz@gnu.org
Cc: 37325@debbugs.gnu.org
Subject: bug#37325: About 'latex-insert/close-block' in 'latex-mode'
Date: Thu, 28 May 2020 17:58:22 +0200 [thread overview]
Message-ID: <5ceb5090-b235-d54b-6501-3eae0cb5ddf0@gmail.com> (raw)
In-Reply-To: <e6065af7-259e-9175-866c-474a9b1b781c@gmail.com>
A reminder. At least documentation change (point 3.) could be done.
I already sent separate e-mail with DIFF.
S. U.
prev parent reply other threads:[~2020-05-28 15:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 17:31 bug#37325: About 'latex-insert/close-block' in 'latex-mode' Sebastian Urban
2019-09-07 10:16 ` Eli Zaretskii
2019-09-07 19:15 ` Sebastian Urban
2019-09-08 17:08 ` Eli Zaretskii
2020-04-23 12:29 ` Sebastian Urban
2020-05-04 14:48 ` Sebastian Urban
2020-07-12 19:15 ` Sebastian Urban
2022-01-28 16:28 ` Lars Ingebrigtsen
2022-01-28 16:12 ` Lars Ingebrigtsen
2020-05-28 15:58 ` Sebastian Urban [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=5ceb5090-b235-d54b-6501-3eae0cb5ddf0@gmail.com \
--to=mrsebastianurban@gmail.com \
--cc=37325@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).