From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.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 uDO9EBdijmKYcgEAbAwnHQ (envelope-from ) for ; Wed, 25 May 2022 19:06:31 +0200 Received: from aspmx1.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id sD/XEBdijmI7RQEA9RJhRA (envelope-from ) for ; Wed, 25 May 2022 19:06:31 +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 DAE7EEE1F for ; Wed, 25 May 2022 19:06:30 +0200 (CEST) Received: from localhost ([::1]:42048 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ntuSr-0001Qz-E5 for larch@yhetil.org; Wed, 25 May 2022 13:06:29 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:49504) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ntuSJ-0001QV-V0 for emacs-orgmode@gnu.org; Wed, 25 May 2022 13:05:55 -0400 Received: from ciao.gmane.io ([116.202.254.214]:34872) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ntuSI-0006VB-2z for emacs-orgmode@gnu.org; Wed, 25 May 2022 13:05:55 -0400 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1ntuSG-0009Ga-8Y for emacs-orgmode@gnu.org; Wed, 25 May 2022 19:05:52 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: emacs-orgmode@gnu.org From: Max Nikulin Subject: Re: About 'inline special blocks' Date: Thu, 26 May 2022 00:05:44 +0700 Message-ID: References: <87czg49cwq.fsf@posteo.net> <87bkvn7iqn.fsf@gmail.com> <875ylvzio8.fsf@gmail.com> <87tu9e13ha.fsf@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.1 Content-Language: en-US In-Reply-To: <87tu9e13ha.fsf@localhost> Received-SPF: pass client-ip=116.202.254.214; envelope-from=geo-emacs-orgmode@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: 28 X-Spam_score: 2.8 X-Spam_bar: ++ X-Spam_report: (2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FORGED_MUA_MOZILLA=2.309, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, NICE_REPLY_A=-0.001, NML_ADSP_CUSTOM_MED=0.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no 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" 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=1653498390; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to: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; bh=On78MkqoxrCKdiaeYA30OaGLUVdKM7etJ8+1KfuCeeE=; b=j05bCDoEEFgxUF70RHHkCrE0UOOKgGZJjMV/eTrrbwBfrJ1XlY+QfjWkowy7Inno6wabga EDsi6Ux/HTStgo7FcWIHPWhcvn19yBwkH7EjF8MQQRRj0QETaUAhM4VDol6R/bxAYXvSoe UV9SWEKy3VsuaMOh8zVakkhME+sSo7p718wwMYto1NGv9lzZRS9wO/DxkQQAkcP1o+q8Mt OXcb9di5PRUGNHmv4ciJ0Cd+ZvgrB6SSUDH3+FSZSt+25KS7yHgdj1+ge43KZJ+2V6slb7 Wx08ifmL8rds/pl5SocvBbMybNg2lxuh4lfERuvJmeuPyQf60Bh7z8eo9+9SUg== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1653498390; a=rsa-sha256; cv=none; b=paV2g5bXucNK0yIPpBKWEudybqKcKgibwFFvJT/sh/L42y0RWFmAx30CT7HFIvro6l1WG9 zLp4W0Cc4pGvVfn+oCsRPPND5KQUU5oZwxu2NIy3l7lWW/l+NK6wt6bl4NEGIwCaeanqsc CAuRUar/Ad2TTUg4hvqsg4Z4J137F2Tm5XyVgwyhmxhW3nLxrfQSidQId5qXCLTvt0Vpol LYJAa1T+xMwSBKziS/9yttBwWHWwiaAPOoPRuimNVbXYmeBIqzu05lVImJET3IKR8cK28h GP8ZMgGhX/Tf3SHo7bBCgqLZp4S+o+cOED6InFEriqGeQQH5clvYilWYPvIyhw== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=gmail.com (policy=none); 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: 2.16 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=gmail.com (policy=none); 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: DAE7EEE1F X-Spam-Score: 2.16 X-Migadu-Scanner: scn0.migadu.com X-TUID: 7k69Ybj0Xjt/ On 25/05/2022 14:22, Ihor Radchenko wrote: > Max Nikulin writes: >> On 24/05/2022 09:51, Timothy wrote: >>> >>> To me, this is another reason for comment and #+attr_X lines not to break >>> paragraphs, as then we can just re-use #+attr_X lines. > > I will raise a compatibility issue, but it is bad enough to not think > about other things. > AFAIU, the proposed change will break whole export system? How would you > represent the AST of > > First line > # comment > Second line > > Should we consider a comment as inline object? I suspect that such > change will cause unpredictable breakages all around Org and third-party > packages. I believed that comments are stripped before passing to export backend, so I did not expect any problem with inline comments. >> ---- >8 ---- >> #+macro: nofollow [[attr:(:html (:rel "nofollow noopener"))]] >> >> An {{{nofollow}}[[attr:(:html (:title "be >> careful!"))]][[http://unsafe.com][unsafe link]]. >> ---- 8< ---- > > I am not sure if I like this idea. It seems fine, but I afraid that it > will complicate parser at some point. We may want to assign such inline > properties to the following object, which is already a pain for > affiliated keywords. Certainly parser should recognize inline attributes, but I do not expect real complications here. Assigning attributes may be performed when AST is ready. Just collect attributes and put them to the following non-attribute object during breadth-first tree transversal. Attributes as the last child is a reason for a warning.