From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:403:4789::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id qBvmKNbf8mS1RAAA9RJhRA:P1 (envelope-from ) for ; Sat, 02 Sep 2023 09:10:14 +0200 Received: from aspmx1.migadu.com ([2001:41d0:403:4789::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id qBvmKNbf8mS1RAAA9RJhRA (envelope-from ) for ; Sat, 02 Sep 2023 09:10:14 +0200 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 2B94E3FD4B for ; Sat, 2 Sep 2023 09:10:14 +0200 (CEST) Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=Fvzfgv2Y; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=posteo.net ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1693638614; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=2yTlWGSdYzQyuAB4gFDf4sZ3ZVxYwRiRQa/EaQFdZys=; b=E8p1f9jXW3PagFPKQZA0B6NjVJWGVTqbFM5ZOE8ve/Nwa1YFOU3hdGi3GRZmt57RG0QafA O4OT1So/Cf/pE08W//4ccTdu+k5DGp75l/aNFo+FUsyhIJ8zHu9SlVOh8csR3l8rI6YAH0 CiGZE+3/S1rGgDUbb3U4ni4ynMawOZTyimSQMLbjtaf+gZZPdqcfOzgnWefo+z56EzuWSc crVii4MxzC4iG/QX7NkOYXV4ny4tZH1RV+E29eZdIwyHOlPc4+lgr0iKLtm5wR5/XaPcBI TdmvVtzp4A19cZQpXkgH55khRwxodca8wLYrkdUMn/YJ7EgBjC0sj2f+3iEhbA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=Fvzfgv2Y; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=posteo.net ARC-Seal: i=1; s=key1; d=yhetil.org; t=1693638614; a=rsa-sha256; cv=none; b=htfbYbq8DPZduV8RhhTOo4oJ4eefOp6I+eRgGATKFDLd3ZaH+MnO2xpeuVEtTVWx4uW8Mj eq/IPhZzjlzJGo/NqDvUZkpfk8T6rdsGzyeX7AVm+Nl73AWaBakeWMJ1XEcHCSQZVp86Dw CtpoALZmUHUAb5QUCslXsHn6Zm7lBJTT6LeeUwlt5+rFY8Dv6f+LC8SvpiKqgWPToT3Fmu XOdnF4obrYpwzNU4JC2SxEv7UQHCyNs7E+ukEhnvv6v2/vjx8qAKVnSYpUSR1dNKdoOwMQ Y/eRpNgnofBm9MYrc8I589o1BY1boG4uds8sX4aJ13o9orS6JKwKsdOVWVSDwQ== Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qcKlO-0005tc-FZ; Sat, 02 Sep 2023 03:09:46 -0400 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 1qcKlN-0005tP-Ed for emacs-orgmode@gnu.org; Sat, 02 Sep 2023 03:09:45 -0400 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 1qcKlL-0004hj-0u for emacs-orgmode@gnu.org; Sat, 02 Sep 2023 03:09:45 -0400 Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id BCFBD240101 for ; Sat, 2 Sep 2023 09:09:41 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1693638581; bh=qibsvVFWGvSn/uWHVfdSyDLy5XGCAYnXVj0TDsFMYaY=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=Fvzfgv2YpBnvvK/m3U2Hz2ZEOXua2Jp8TxTwDIDrsJXR5xQbeTam0HKVRSkpidAf2 gv2l5hip9WBL2m84p/KJYrCkjujrZZQMe4EitH+q5e3WBlQRJX96cfw5EzDRuCRugm nfJ1yWSks+EeVInNmvguCRGmfkdTKMdkYHnfPTM8C8b656wdHJTrtGRFj0a87h/hZl V9jyy8j0lWVa6Z7oPEj2JO9BfCMJ3dv1qhZ358HIuaVVoau7MHJRW08RfxO8WmgVUM OQW/egimK4OHdHfcgBs8Ns/xWumr+N1rZ5IaJ2pl0d8u1aJULO9rAYm1AXBkBVhOfc eduf5FQylTDQQ== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4Rd5cj0wL4z6txg; Sat, 2 Sep 2023 09:09:40 +0200 (CEST) From: Ihor Radchenko To: Jens Schmidt Cc: Samuel Loury , emacs-orgmode@gnu.org Subject: Re: [RFC] Quoting property names in tag/property matches [Was: [BUG?] Matching tags: & operator no more implicit between tags and special property] In-Reply-To: <2937cbf6-4ee7-0bdc-b585-d74c9d80883b@vodafonemail.de> References: <87h6oq2nu1.fsf@gmail.com> <877cpm6oe3.fsf@localhost> <811c9bda-cea4-c0d6-30b4-53ebdb432ab6@vodafonemail.de> <748acab1-eaf4-fdd3-13a6-26e6229de613@vodafonemail.de> <87o7iw7v4q.fsf@localhost> <98f4101b-7281-2793-ca30-7086c4f10c5d@vodafonemail.de> <87sf86w1k8.fsf@localhost> <6a7888b5-1b4c-9a59-8a8e-e27c9d8b50cb@vodafonemail.de> <87h6omj9nx.fsf@localhost> <87edjqj8mk.fsf@localhost> <878r9xez7m.fsf@gmail.com> <874jklhqw2.fsf@localhost> <2937cbf6-4ee7-0bdc-b585-d74c9d80883b@vodafonemail.de> Date: Sat, 02 Sep 2023 07:10:12 +0000 Message-ID: <87bkelhwyz.fsf@localhost> MIME-Version: 1.0 Content-Type: text/plain 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 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Spam-Score: -6.43 X-Spam-Score: -6.43 X-Migadu-Queue-Id: 2B94E3FD4B X-Migadu-Scanner: mx1.migadu.com X-TUID: Y6YUy7fK3QVP Jens Schmidt writes: > TL;DR: > > - I think we cannot make "&" mandatory because of backward compatibility. Sorry for the confusion. I did not mean that "&" should be mandatory, just that "&" might make it easier to avoid a need to escape things. So, it could be used _instead_ of escaping. > - Even if we made "&" mandatory, it would not really solve the quoting > problem, since the parser is rather hacky and other quoting and > context issues would still be there. But at this point you are more familiar with that parser than I am, so my idea does not seem to be viable. > This all calls for a proper parser, based on peg or bovine or whatever. > Hopefully that parser would still keep backward compatibility, but > that's probably wishful thinking. Backward compatibility will be easy - just leave the current code when old query version is detected. We should better focus on the new syntax in future and leave the current syntax as compatibility layer that will be eventually deprecated. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at