From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ihor Radchenko Newsgroups: gmane.emacs.devel Subject: Re: cond* Date: Wed, 03 Jan 2024 15:48:35 +0000 Message-ID: <87il4a76zw.fsf@localhost> References: <87frzuae9n.fsf@posteo.net> <871qbatqc8.fsf@posteo.net> <87wmsz7lzn.fsf@posteo.net> <87edf1m7lq.fsf@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33055"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Jan 03 16:46:29 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 1rL3Rs-0008Ox-Om for ged-emacs-devel@m.gmane-mx.org; Wed, 03 Jan 2024 16:46:28 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rL3R0-0008Lz-LE; Wed, 03 Jan 2024 10:45:34 -0500 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 1rL3Qz-0008Hz-2V for emacs-devel@gnu.org; Wed, 03 Jan 2024 10:45:33 -0500 Original-Received: from mout02.posteo.de ([185.67.36.66]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rL3Qt-0000uA-A9 for emacs-devel@gnu.org; Wed, 03 Jan 2024 10:45:32 -0500 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id C650B240103 for ; Wed, 3 Jan 2024 16:45:24 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1704296724; bh=4N/vPuWlLuSpGz1PgYzwiby767/2cTA6YJIVs2dfKIU=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version: Content-Transfer-Encoding:From; b=TvVhwF1yOWu89vNqDT7j/rNwrJiihnKLX81gGqTQ6M399+nHYl7aHsZjnPOUe3+4x ZpxndDWxO2qLjwytovVQg0uwnpcBoOaupPV3JJPHCxoxZkHz8wheMZGMqAXRU0bGx2 PDQiESgdSny+1ee3iNAcNyAieIXbOnCY4eqlb/NI7X+RRCQBt2OJHibMSKmt2Wqf12 llaNSIltEMpbpJEpKuiGPFf09lbEgumDT4UG7YINYd46OjVrAnT76rG45Tug3Vswa4 zXg6PSId+1lJ7Kxe6ftGrejcQHxauqfPbZHVhAH2dOCGL75m94VPclhqodSky8CYpT ja33YFg4iLAXA== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4T4vF0158fz9rxB; Wed, 3 Jan 2024 16:45:23 +0100 (CET) In-Reply-To: Received-SPF: pass client-ip=185.67.36.66; envelope-from=yantar92@posteo.net; helo=mout02.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=unavailable 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:314499 Archived-At: Richard Stallman writes: > > In addition to the usual =E2=80=98rx=E2=80=99 syntax, RX-EXPR...= can contain the > > following constructs: > > > =E2=80=98(let REF RX-EXPR...)=E2=80=99 > > Bind the symbol REF to a submatch that matches RX-EXPR.... > > REF is bound in BODY-FORMS to the string of the submatch or > > =E2=80=98nil=E2=80=99, but can also be used in =E2=80=98bac= kref=E2=80=99. > > I don't understand that description. I don't see what this construct > would look like inside of an (rx ...) pattern, let alone what it would > mean. > > Can you show me a complete pattern example using (rx...) and this, and > explain it? Sure. Consider the following `rx' form that matches lines like "#+begin: something": (rx line-start (0+ (any " \t")) "#+BEGIN:" (0+ (any " \t")) ;; matches "something" (1+ word)) This is equivalent to "^[ ]*#\\+BEGIN:[ ]*[[:word:]]+" Now, consider that we need to extract "something" from the match if the match succeeds: (pcase " #+begin: something" ((rx line-start (0+ (any " \t")) "#+BEGIN:" (0+ (any " \t")) ;; matches "something" ;; (let VAR ) binds VAR to sub-expression match. (let matched-value (1+ word))) (format "We just matched \"%s\"" matched-value))) ; =3D> "We just matche= d \"something\"" --=20 Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at