From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Aaron W. Hsu Newsgroups: gmane.emacs.help 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 Message-ID: References: <53f62f81-fb10-4fb6-87ce-0eb5609d12f5@h17g2000pri.googlegroups.com> NNTP-Posting-Host: lo.gmane.org X-Trace: dough.gmane.org 1291929280 2072 80.91.229.12 (9 Dec 2010 21:14:40 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 9 Dec 2010 21:14:40 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Thu Dec 09 22:14:36 2010 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1PQnor-0007YL-Vj for geh-help-gnu-emacs@m.gmane.org; Thu, 09 Dec 2010 22:14:30 +0100 Original-Received: from localhost ([127.0.0.1]:37757 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PQnZd-0000Su-6a for geh-help-gnu-emacs@m.gmane.org; Thu, 09 Dec 2010 15:58:45 -0500 Original-Path: usenet.stanford.edu!news.glorb.com!news2.glorb.com!news.glorb.com!Xl.tags.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local2.nntp.dca.giganews.com!news.giganews.com.POSTED!not-for-mail Original-NNTP-Posting-Date: Thu, 05 Aug 2010 23:59:13 -0500 Original-Newsgroups: gnu.emacs.help, comp.unix.shell, comp.lang.c, comp.lang.lisp, comp.lang.scheme User-Agent: nn/6.7.3 Original-Lines: 47 X-Usenet-Provider: http://www.giganews.com Original-X-Trace: sv3-FoPRBQP81GC8lAlISxgmXoQlQnT+QmRynASoJLKirwHVAIpJqfMhx1uadWYYSRmiRim/kTmnbWBHZko!QdIX+TG5BhH7Mjg6ueFRKIOPtiRVHfwL75yU2IbyyE3QmvM4TyE+qHHJ4hH0TPb1+WXCOg+SYCi/ Original-X-Complaints-To: abuse@giganews.com X-DMCA-Notifications: http://www.giganews.com/info/dmca.html X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.40 Original-Xref: usenet.stanford.edu gnu.emacs.help:180438 comp.unix.shell:246371 comp.lang.c:979565 comp.lang.lisp:290966 comp.lang.scheme:87286 X-Mailman-Approved-At: Thu, 09 Dec 2010 15:39:42 -0500 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:77072 Archived-At: Fren Zeee 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