From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Elena Newsgroups: gmane.emacs.help Subject: Re: What is the best way to navigate #ifdef and #endif in C program Date: Wed, 4 Aug 2010 09:20:05 -0700 (PDT) Organization: http://groups.google.com Message-ID: <79a1eb94-9f44-4fa9-8be0-1ee6a546f1ef@f42g2000yqn.googlegroups.com> References: <53f62f81-fb10-4fb6-87ce-0eb5609d12f5@h17g2000pri.googlegroups.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1291858240 4838 80.91.229.12 (9 Dec 2010 01:30:40 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 9 Dec 2010 01:30: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 02:30: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 1PQVL8-0004lw-4L for geh-help-gnu-emacs@m.gmane.org; Thu, 09 Dec 2010 02:30:34 +0100 Original-Received: from localhost ([127.0.0.1]:44781 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PQVL7-0003kH-Gy for geh-help-gnu-emacs@m.gmane.org; Wed, 08 Dec 2010 20:30:33 -0500 Original-Path: usenet.stanford.edu!postnews.google.com!f42g2000yqn.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help, comp.unix.shell, comp.lang.c, comp.lang.lisp, comp.lang.scheme Original-Lines: 13 Original-NNTP-Posting-Host: 89.96.190.244 Original-X-Trace: posting.google.com 1280938806 28981 127.0.0.1 (4 Aug 2010 16:20:06 GMT) Original-X-Complaints-To: groups-abuse@google.com Original-NNTP-Posting-Date: Wed, 4 Aug 2010 16:20:06 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: f42g2000yqn.googlegroups.com; posting-host=89.96.190.244; posting-account=AFCLjAoAAABJAOf_HjgEEEi3ty-lG5m2 User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8,gzip(gfe) Original-Xref: usenet.stanford.edu gnu.emacs.help:180378 comp.unix.shell:246342 comp.lang.c:979406 comp.lang.lisp:290893 comp.lang.scheme:87272 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:76388 Archived-At: On Aug 4, 4:45=A0am, Fren Zeee wrote: > If there is a wrapper do nothing type function in elisp/clisp/scheme > which can have the same effect as commenting out. In Emacs Lisp, if you are looking for a way to comment out blocks of text, you are out of luck. I've read Pythonistas use multi-line strings as multi-line comments (strings are always multi-line in Emacs). If you are looking for a way to comment out blocks of code, you can do that with a macro. I remember having seen a "comment" macro inside Emacs Lisp packages kindly published by Pascal J. Bourguignon here: http://www.informatimago.com/develop/emacs/index.html