From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id CEv4BC3mEGO1rwAAbAwnHQ (envelope-from ) for ; Thu, 01 Sep 2022 19:04:45 +0200 Received: from aspmx1.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id 4HzVBC3mEGO8nwAAauVa8A (envelope-from ) for ; Thu, 01 Sep 2022 19:04:45 +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 891EAE809 for ; Thu, 1 Sep 2022 19:04:44 +0200 (CEST) Received: from localhost ([::1]:34830 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oTncQ-0000NF-Nt for larch@yhetil.org; Thu, 01 Sep 2022 13:04:42 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:36470) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oTnFE-0003fw-SN for emacs-orgmode@gnu.org; Thu, 01 Sep 2022 12:40:46 -0400 Received: from mout02.posteo.de ([185.67.36.66]:54789) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oTnFC-0003x4-K5 for emacs-orgmode@gnu.org; Thu, 01 Sep 2022 12:40:44 -0400 Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id B0110240107 for ; Thu, 1 Sep 2022 18:40:39 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.eu; s=2017; t=1662050439; bh=Ti8w5OEiHmCLWLBrWCTv+FKWGAbZhk5B4eCQ14wpIO0=; h=Date:Subject:To:From:Cc:From; b=Sr0Fs/WLOZxdMtzhZ/GmSYAcBlbkazN8EMNTiKcui9rI6PQPLEdU9osVZeTBbXYnc W45eV6u3+Vj8Gc0j58/WCyK7tS/YSeUZj4DJg1njczKdJtp8D5d19c2Jsr6NQ098c+ g9dEqpTTxaYkucx6cDVD2t1BOQmHBRCr/UkrrbRgfFc8pVC7wUWN37R7UPYS5CZPDQ 4O0rfIAGsZPjU2KJNRnfs5/khkKFfndW61qcDQRgyU66qG5eAA6P2W5Lkgu6IsORUV VMKb58Wr5yOI+OCqwsTY7GdyJjdAVI1klWP24mKPNWoJ615MLZHC3EA8aqRWtAWypB GU6rpeJDclgtQ== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4MJRcP3zPKz6tpm; Thu, 1 Sep 2022 18:40:37 +0200 (CEST) Message-ID: <30d5a0be-4651-3f41-8b53-91acd4a86ca5@posteo.eu> Date: Thu, 1 Sep 2022 16:40:36 +0000 MIME-Version: 1.0 Subject: Re: Support for tagging (special) blocks Content-Language: fr To: Ihor Radchenko References: <8735dbbuku.fsf@gmail.com> <87ler3oc4u.fsf@localhost> From: =?UTF-8?Q?S=c3=a9bastien_Miquel?= Cc: emacs-orgmode In-Reply-To: <87ler3oc4u.fsf@localhost> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Received-SPF: pass client-ip=185.67.36.66; envelope-from=sebastien.miquel@posteo.eu; 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_H2=-0.001, 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-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: , Reply-To: sebastien.miquel@posteo.eu Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Migadu-Flow: FLOW_IN X-Migadu-To: larch@yhetil.org X-Migadu-Country: US ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1662051884; h=from:from:sender:sender:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=VcmpHpiLJfdsCThvPrq8VP4sQoj0hhpHRY0XpB1SDxE=; b=Vl4ie8upOKQhrohaRLVGrtCJUbvJ8tjbPofYnw0LrF0cEEVEOP89fbbVaqjB9VpARcPxcm AKKBe5qUy2X1nrOtrya+oe4YGgY2SlFNFdq70aVCpIeHDVRgyqJSlsoD0in8F4QMy1LUfP OHzcoYZY4UbzBuczVCrK7hiB3ry12zbl7xWYZbWNDXOGdG0sBWdE+7O/rNF97zj2jw6Dww GmEBxISUVeAWa/qBgaeMhrXaGzUce219xyHzau4yBrLNY/MXqpYESa30x25EAs1kJBwOV1 JxSh2IhlW5Vx381gk5ZXZFf4tqXruDPfjiCoHq4zRlMGoRoCmgI8C3wXWhGmWg== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1662051884; a=rsa-sha256; cv=none; b=AxTVer7lZ7qrm8CFwoatWWFEvq1d96oI32iqw3O2RGCzQduL0V6oQ0FA88Du9qIzm1ThMp 6ZvgiLj9NOqEoSWdP7ummBNK+sUdW5DdCNxhZ5tRoOFKnnVSElBMp4mzy0N5PFHtm6q1/O bua4bTtIErhBGmEHf35sI3jayeN3sfb40HjfKL4C9mVi1BkYPx5Wz+Hu7w8jacRjoEHnZp +nEXnxoqyPYa6tdWrLLuS4KPqPSy0urOnFS8531JaBTiMES9YbPd5ZBa/yQyT2Q4kd9HLm 70z9HPlOfdNTbcYTu+hYiUw+xTnFXI3mrk3JtVq5KsEGjZDcJywiB0eyTWVkpw== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.eu header.s=2017 header.b="Sr0Fs/WL"; dmarc=pass (policy=none) header.from=posteo.eu; 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" X-Migadu-Spam-Score: -3.98 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.eu header.s=2017 header.b="Sr0Fs/WL"; dmarc=pass (policy=none) header.from=posteo.eu; 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" X-Migadu-Queue-Id: 891EAE809 X-Spam-Score: -3.98 X-Migadu-Scanner: scn1.migadu.com X-TUID: ldDJG2ibKJrg Hi, Ihor Radchenko writes: > They do not. Tags are only considered inside headlines. Trying to allow > tags outside headlines will require major changes across the whole Org > codebase and will still make things incompatible with third party > packages, like org-ql. Not to mention the whole new concept for block > syntax. Tags on block do not need to have the same support as headlines tags. I'm not suggesting they should interact with the agenda or whatnot. Support could be behind a user option, and consist only of say easy tag edition, and `#+exclude_tags:` support. With that scope, the implementation should be fairly simple. As for third party packages, it is up to them whether to extend their features to tagged blocks ; in some case it might not make sense. > If one wants to add "tags" or other keywords associated with blocks or > other Org elements, the right tool to use is affiliated keywords. But > note that Org search infrastructure is tailored towards searching > headlines. Two inconvenients with using affiliated keywords. 1. There would be no uniform treatment with headline tags. In my use, I have the same tags on headline and blocks, and I filter the export according to them with #+exclude_tags. 2. They waste too much space. Say I have some 20 short exercices (represented by special blocks). Since I dot not display the #+end_ line, each of them takes 2 or 3 lines in my screen. If I want to tag those using affiliated keywords that makes for a 50% or 33% size increase, with very poor readability. On a slightly related note, I find it quite unfortunate that one presently cannot make use of the #+begin_ line of special blocks to set some kind of optional title instead of using #+name or #+attr_latex. That's a lot of wasted real estate. -- Sébastien Miquel