From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Scheme Mode and Regular Expression Literals Date: Thu, 14 Mar 2024 09:34:10 -0400 Message-ID: References: <87sf105cw1.fsf@niceume.com> <86edcdb40m.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="37392"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: Eli Zaretskii , Toshi Umehara , jcubic@onet.pl, emacs-devel@gnu.org To: Mattias =?windows-1252?Q?Engdeg=E5rd?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Mar 14 14:35:08 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1rklEi-0009TR-Dg for ged-emacs-devel@m.gmane-mx.org; Thu, 14 Mar 2024 14:35:08 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rklDu-0000sd-Tm; Thu, 14 Mar 2024 09:34:18 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rklDs-0000s4-Va for emacs-devel@gnu.org; Thu, 14 Mar 2024 09:34:16 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rklDr-0008G1-47; Thu, 14 Mar 2024 09:34:16 -0400 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 452B410004C; Thu, 14 Mar 2024 09:34:12 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1710423251; bh=K3ZFTWh7JtHfa4r1d5mr9gP3Op5s8lnFXKh8sz9tHCQ=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=PjDC07pdObJdNiBZxmM7qJ4gE6ym1qgjEP+y15APIxAjk+oWfyENvKhSLkH5gWmoT 68SIwbCjZ1sJgI2Pr8zJbzGEV0CkDenSRYYtA0e1lb8ohcjhdkKdb/7x8qE8lhdEIB UZHp+KU8bXlXlXoKJQaeLMwvgav8HtY1954nM5qGyCbOaETWnomI0BOXJh7IsYpTha Ukr//3yVbUoO3OJpCd5bVpys6rwVfkl49JpCdNG659RfGhghWrr2sO7ekLKNyc22it UE1B6DmBYwdgHViaN9A1yGSyRgzbNFFwL1uXNlVNkf4CUjsF0EhC8TfCmv3HSQNUmW ZN9SazPW+Zp3g== Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 47E4C100046; Thu, 14 Mar 2024 09:34:11 -0400 (EDT) Original-Received: from pastel (unknown [216.154.27.181]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 0E6201201E7; Thu, 14 Mar 2024 09:34:11 -0400 (EDT) In-Reply-To: ("Mattias =?windows-1252?Q?Engdeg=E5rd=22's?= message of "Thu, 14 Mar 2024 12:38:53 +0100") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:317047 Archived-At: > ((rx (group "#") "/" > (* (| (: "\\" nonl) > (not (in "\n/\\")))) > (group "/")) > (1 "|") > (2 "|")) > > instead? > > The Gauche documentation isn't entirely clear on how literal newlines are lexed inside this construct. > If newlines can be part of regexp literals, remove the \n from the third line. > If backslashed newlines are allowed, change `nonl` to `anychar`. If they can span several lines then matching the whole #/.../ with a regexp is definitely the wrong approach. If not, that rule can be made to work but it has to check that the leading #/ is not inside a string or comment. The more robust approach is to match only #/ here and then use a function which checks the resulting `syntax-ppss` to handle the rest of the regexp. See `octave-syntax-propertize-function` for an example of the structure where we use the regexp "\\(?:^\\|[[({,; ]\\)\\('\\)" to match the beginning of a quoted string, and then use `octave-syntax-propertize-sqs` to process its contents (and use that as well at the beginning of the function in case `syntax-propertize` is called with start in the middle of such a string (or in our case, regexp)). Stefan