bkyk8rc3zvpnsf5inmcqq4n3k98cv6hj-my-site-hyper-literate-git.test.suzanne.soy-0.0.1

Unnamed repository; edit this file 'description' to name the repository.
Log | Files | Refs | README | LICENSE

commit db7729e6c4a0a11adcb6f5ecc4dd19e195e3af26
parent 027d80e352d23eea1563319031b6c9d8312712d0
Author: Eli Barzilay <eli@barzilay.org>
Date:   Mon, 13 Jun 2011 16:47:27 -0400

Revise this comment

original commit: 80f0d57cdd46a4b3226dc5af64bd8e72edaba3dd

Diffstat:
Mcollects/scribblings/scribble/reader.scrbl | 8+++++---
1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/collects/scribblings/scribble/reader.scrbl b/collects/scribblings/scribble/reader.scrbl @@ -323,8 +323,10 @@ following spaces (or tabs) are part of the comment (similar to blah} }===| -Tip: if you're editing in a Racket-aware editor (like DrRacket or -Emacs), it is useful to comment out blocks like this: +Tip: if you use an editor in some Scheme mode without support for +@"@"-forms, balanced comments can be confusing, since the open brace +looks commented out, and the closing one isn't. In such cases it is +useful to ``comment'' out the closing brace too: @verbatim[#:indent 2]|==={ @;{ @@ -333,7 +335,7 @@ Emacs), it is useful to comment out blocks like this: }===| so the editor does not treat the file as having unbalanced -parenthesis. +parentheses. If only the @nonterm{cmd} part of an @"@"-form is specified, then the result is the command part only, without an extra set of parenthesis.