From: Henning Hraban Ramm <hraban@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Check brackets and parentheses
Date: Fri, 6 Jul 2012 09:17:34 +0200 [thread overview]
Message-ID: <CAPm68ZgphzZgUh4TvRXAM_+pT25cK9=wbfF4v_8nybfPu3Wm+w@mail.gmail.com> (raw)
In-Reply-To: <64C3576E-DF3A-470B-82C9-295690C44AB8@gmail.com>
2012/7/5 Gilbert Houtekamer <gilbert.houtekamer@gmail.com>:
> Hi,
>
> I sometimes find myself looking for misplaced and missing brackets for a long time, as context may given errors about a completely different location.
>
> For example this one took me a while
> \goto{\url[localhost20381}[url(localhost20381)]
>
> (missing ] after this localhost20381).
>
> Is there a SciTE or Notepad++ or command line script that anyone wrote to help with this? It can be more or less sophisticated, but I found that missing / mismatched { [ ] } give the most confusing errors.
A lot of (most?) programming editors do paren checking, at least in
that they show which paren matches the one the cursor is on.
Maybe you can simply switch it on/off per language in your editor?
(It’s been a while since I tried SciTE...)
Greetlings, Hraban
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2012-07-06 7:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 18:40 Gilbert Houtekamer
2012-07-06 7:17 ` Henning Hraban Ramm [this message]
2012-07-06 7:21 ` Hans Hagen
2012-07-06 7:38 ` Pontus Lurcock
2012-07-06 12:37 ` Hongwen Qiu
2012-07-06 14:24 ` Pontus Lurcock
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPm68ZgphzZgUh4TvRXAM_+pT25cK9=wbfF4v_8nybfPu3Wm+w@mail.gmail.com' \
--to=hraban@fiee.net \
--cc=ntg-context@ntg.nl \
/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 NNTP newsgroup(s).