From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.migadu.com ([2001:41d0:306:2d92::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id mGTJB7v+6mQTpwAAauVa8A:P1 (envelope-from ) for ; Sun, 27 Aug 2023 09:43:55 +0200 Received: from aspmx1.migadu.com ([2001:41d0:306:2d92::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id mGTJB7v+6mQTpwAAauVa8A (envelope-from ) for ; Sun, 27 Aug 2023 09:43:55 +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 E13B15C13C for ; Sun, 27 Aug 2023 09:43:54 +0200 (CEST) Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=Z204Z+OS; 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=1693122235; 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=noEgB9+SSsH3+7lRFrXs0iBoHbkcAYO0nbHxeFBOXbQ=; b=qN2X4LoOgkfDBvSz7dmLGsV+LOQmHfuoSmpaYZAnDyNfqXD16JnBQFN4Mx6/ebAdBqthmq M7sPBnzIaYf9zxGWT9t6C29HKU6mhz4SjGiLJtIlIq48oJ23PTgouY1nbD2F0C9cUs4Vro c/SeAqZeyeTCuP4tnjFWSgeIEGIi7wPJ/n+bAdX3yC5JykPwAZN81BZroH9rXorf9kqcuS CDGbT5auM1YCqughevZkKZP5t+wBP6CPwM4utqhHRKKg+sOseycjKA4/WvRgbdCER/4Fw7 zUGlERVbN6l+cqzCept6Fq71H6ji3zn40tPDKVradXjSgo02gE8HNsAY7sDc4w== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=Z204Z+OS; 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=1693122235; a=rsa-sha256; cv=none; b=K9NtNmATShjrlMMvwOiv2R//+0FVJ9pQg58MexED/o3QM8wRI2BX6AQFpQrITlXDZ4rrvb YN1SEY3Oe7jZLNu6QwKOmukxnN9FTfwNq6yuc9ZAJcMyO49vYZgT+JBQtxAfhPRzdE0Bdd K0ZIpZwjw5MdMN/JXjj5v6K+Zq+nnPl2pZDe1uWUPq/mzdvYPTFAr1dOvLc+0ThkRSsFt+ S2k/BUewjTCuvXDEujkwcRXdBkTMZCpK0s8BB/8ou05PQ7Bm08YhbLdIkAmN8MhI/U8Tsq GVKP/pJLa0aHx+AQA4M4g+1EQOd4QL+4oezG3edvTALD6nwM5FVAqCPWID8WDw== Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qaAQV-0001Pj-55; Sun, 27 Aug 2023 03:43:15 -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 1qaAQL-0001Ns-Tz for emacs-orgmode@gnu.org; Sun, 27 Aug 2023 03:43:07 -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 1qaAQI-0001Fu-U2 for emacs-orgmode@gnu.org; Sun, 27 Aug 2023 03:43:05 -0400 Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 1DC8C240104 for ; Sun, 27 Aug 2023 09:42:59 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1693122179; bh=Bie10EMRza3yE5bUZTgAdyvIGaH3La8iBYpYUTuhwPE=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=Z204Z+OSfCg5q4y9dIGuZOu+8Ql+/vhWjb8igWk9JB1W5DKFGtkX0U2wcYvxb+Gs+ eerQXs+ws4TKprNUkYTcZ/OjxAZgGTAfeNnRrV5jmK0o6Dkukl+0fm2yCZZy9fuPYV ugsvvOjDXguDKq89CrbWROnHS2nXXXezqgu4/QqE89Ts0T5QgTS1IZ3+ISCIvcKAUx BNd7ULTIt3G0SUh9hyhevZk6Cq9XweRSgzE7N0T8WE82TE8+vt3Ftn4jbE4enTxVUo 4VtcsWGGFCyIJAm1C0bFaR/NoYhbjiFi4njwvpNTK/Q7A7ntxZz+7EF2jbu8qjugBG 1Nt3myEJ+ebBw== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4RYQdt36vJz6tvq; Sun, 27 Aug 2023 09:42:58 +0200 (CEST) From: Ihor Radchenko To: Samuel Loury Cc: Jens Schmidt , 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: <878r9xez7m.fsf@gmail.com> 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> Date: Sun, 27 Aug 2023 07:43:25 +0000 Message-ID: <874jklhqw2.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-Country: US X-Migadu-Flow: FLOW_IN X-Migadu-Scanner: mx2.migadu.com X-Migadu-Spam-Score: -7.90 X-Spam-Score: -7.90 X-Migadu-Queue-Id: E13B15C13C X-TUID: DT5QQRkSOGRN Samuel Loury writes: > IMHO, "-tag&-todo=TODO" is totally ok. I even imagine we could say that > & and | are forbidden to say anything else than AND and OR and people > would be ok with that. Actually, explicit & or | might be an easier way to not worry about escaping things. Except escaping & or | themselves. It might be the preferred way to put into the manual. > IOW, I wonder of the time and effort to deal with optional & is worth > it. WDYT? We cannot remove the optionality of &, because doing so will break existing user setups. But we can certainly change our recommendations in the manual. Though pure tag matcher makes more sense with implicit &: +tag1-tag2+tag3... vs +tag1&-tag2&+tag3 Especially in the interactive agenda filters. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at