From: Aaron W. Hsu <arcfide@sacrideo.us>
To: help-gnu-emacs@gnu.org
Subject: Re: [OT] Re: What is the best way to navigate #ifdef and #endif in C program
Date: Thu, 05 Aug 2010 23:59:13 -0500 [thread overview]
Message-ID: <BOOdnSnuJLY8C8bRnZ2dnUVZ_syonZ2d@giganews.com> (raw)
In-Reply-To: c28b51a6-38c7-4009-be60-0a8c1b014705@f42g2000yqn.googlegroups.com
Fren Zeee <frenzeee@gmail.com> writes:
>My question to CLISP/ELISP/scheme people is
>If there is a wrapper do nothing type function in elisp/clisp/scheme
>which can have the same effect as commenting out.
>This is because I dont like to do comment-region/uncomment-region in
>emacs.
>These three lispy languages dont seem to have comment block construct
>like C ie /* and */
Actually, there are a lot of them in common use. Here are the one's I
use regularly, and you can check with your implementation to see if it
provides them:
#| |# block comments
#; Expression comments
I find the expression comments to be very useful. Basically, it let's
you comment out the next expression, such as this:
(if (test)
#;(bad
nothing
or another)
(good thing)
(other thing))
Now, some people don't like it because it plays with their Emacs
commenting modes. Since I don't use Emacs, this doesn't bother me. ;-)
On the other hand, the workaround if you don't want to hack your Scheme
highlighting is to do something like this instead:
(if (test)
#;
(bad
nothing
or another)
(good thing)
(other thing))
This will keep the highlighting mostly in check and still do the same
thing.
Aaron W. Hsu
next prev parent reply other threads:[~2010-08-06 4:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 0:31 What is the best way to navigate #ifdef and #endif in C program Daniel (Youngwhan)
2010-08-04 4:45 ` [OT] " Fren Zeee
2010-08-04 10:27 ` Pascal J. Bourguignon
2010-08-04 10:38 ` Alessio Stalla
2010-08-04 11:57 ` Pascal J. Bourguignon
2010-08-04 14:37 ` Elena
2010-08-04 14:59 ` Arzobispo Andante
2010-08-04 15:09 ` Peter Keller
2010-08-04 15:35 ` Peter Keller
2010-08-05 19:04 ` Elena
2010-08-05 21:10 ` Peter Keller
2010-08-05 23:46 ` Pascal J. Bourguignon
[not found] ` <8c27aoFij2U1@mid.individual.net>
2010-08-06 11:17 ` Elena
2010-08-06 13:55 ` Pascal J. Bourguignon
2010-08-04 16:20 ` Elena
2010-08-04 16:23 ` Elena
2010-08-05 18:00 ` Emmy Noether
2010-08-06 4:59 ` Aaron W. Hsu [this message]
2010-08-05 17:30 ` Johan Bockgård
2010-08-06 17:03 ` Alan Mackenzie
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=BOOdnSnuJLY8C8bRnZ2dnUVZ_syonZ2d@giganews.com \
--to=arcfide@sacrideo.us \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.