From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Spike Ilacqua Newsgroups: gmane.emacs.help Subject: modify-syntax-entry with single and two character comments Date: Wed, 27 Oct 2004 11:55:22 -0600 Organization: Posted via Supernews, http://www.supernews.com Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Message-ID: <10nvo8bjdmul85@corp.supernews.com> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1098899861 21190 80.91.229.6 (27 Oct 2004 17:57:41 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 27 Oct 2004 17:57:41 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Oct 27 19:57:33 2004 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1CMs3A-0007j1-00 for ; Wed, 27 Oct 2004 19:57:32 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CMsAv-0003eB-CJ for geh-help-gnu-emacs@m.gmane.org; Wed, 27 Oct 2004 14:05:33 -0400 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!sn-xit-02!sn-xit-12!sn-xit-06!sn-post-01!supernews.com!corp.supernews.com!not-for-mail Original-Newsgroups: gnu.emacs.help User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en Original-X-Complaints-To: abuse@supernews.com Original-Lines: 32 Original-Xref: shelby.stanford.edu gnu.emacs.help:126130 Original-To: help-gnu-emacs@gnu.org 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: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.help:21510 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:21510 I'm trying to build a syntax table for a language that as two comment modes. "|" starts a single line comment, and works like "#" in Perl. "|* ... *|" can contain a comment and may be multiple lines, basically the same a C's "/* ... */". I've tried a number of variations and the closest I get is: (modify-syntax-entry ?\n ">" st) (modify-syntax-entry ?\| "<1b4b" st) (modify-syntax-entry ?\* ".2b3b" st) which works for "|* ... *|" and recognizes "|" as the start of a comment but doesn't see a newline as the end of a comment that starts with "|". This on the other hand: (modify-syntax-entry ?\n ">b" st) (modify-syntax-entry ?\| "Spike