From: Hongyi Zhao <hongyi.zhao@gmail.com>
To: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Finding and fixing the missing brackets for tcl script with Emacs.
Date: Thu, 14 Jan 2021 18:30:20 +0800 [thread overview]
Message-ID: <CAGP6POKAig+mfwHTeBpX5F_5Z4K=WCqAkKEux9CzVex42AFW9w@mail.gmail.com> (raw)
See the following TCL script snippet:
---
set sendcmds [lmap l [split [string trim $sendcmds] \n] {
if {[regexp {^\s*#} $l} continue
string trim $l
}]
---
In the above code snippets, two close brackets are missed. But finding
and fixing this sort of error manually is indeed a tedious and
laborious job. Can Emacs help me find the right spot and fix the
problem quickly for this scenario?
Best,
--
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Polytechnic University of Science and Technology engineering
NO. 552 North Gangtie Road, Xingtai, China
next reply other threads:[~2021-01-14 10:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 10:30 Hongyi Zhao [this message]
2021-01-14 11:22 ` Finding and fixing the missing brackets for tcl script with Emacs tomas
2021-01-14 13:34 ` 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='CAGP6POKAig+mfwHTeBpX5F_5Z4K=WCqAkKEux9CzVex42AFW9w@mail.gmail.com' \
--to=hongyi.zhao@gmail.com \
--cc=help-gnu-emacs@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.
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).