From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id EEZjAPD6xWEaKQAAgWs5BA (envelope-from ) for ; Fri, 24 Dec 2021 17:53:04 +0100 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id EDi8N+/6xWH2JAAA1q6Kng (envelope-from ) for ; Fri, 24 Dec 2021 16:53:03 +0000 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 B6098E8FC for ; Fri, 24 Dec 2021 17:53:03 +0100 (CET) Received: from localhost ([::1]:52216 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n0noU-0000HL-HZ for larch@yhetil.org; Fri, 24 Dec 2021 11:53:02 -0500 Received: from eggs.gnu.org ([209.51.188.92]:56680) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n0nnR-0000Gy-Rw for emacs-orgmode@gnu.org; Fri, 24 Dec 2021 11:51:57 -0500 Received: from ciao.gmane.io ([116.202.254.214]:43410) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n0nnQ-0002it-Br for emacs-orgmode@gnu.org; Fri, 24 Dec 2021 11:51:57 -0500 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1n0nnO-0006s6-06 for emacs-orgmode@gnu.org; Fri, 24 Dec 2021 17:51:54 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: emacs-orgmode@gnu.org From: Max Nikulin Subject: Re: text after sub headings? Date: Fri, 24 Dec 2021 23:51:42 +0700 Message-ID: References: <9881E3B7-A1F0-4C0F-AED6-893368A6FEA0@icloud.com> <87wnjvvzgv.fsf@posteo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 In-Reply-To: <87wnjvvzgv.fsf@posteo.net> Content-Language: en-US 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: 7 X-Spam_score: 0.7 X-Spam_bar: / X-Spam_report: (0.7 / 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.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NICE_REPLY_A=-2.133, NML_ADSP_CUSTOM_MED=0.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 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-Country: US ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1640364783; 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=E/LeGu67wLuu+wehKVRyVq/CFUQ6UncKuFuH7ndkQQw=; b=CYzVVJGqgmYka1Aji4CVDL7AmoAs1vz6AbmZshPkgfNsDeWmZMt7PioihO0BXyAUhdqVJS 2LkVVMHbeJFKRi8K5Va1uiUr1PZlJiJi3OrbWCuYkIKBfgp9DR/EkcZ+RIR7BwKID0Wm8E t9fpbNmD/w2swNR7FVvZOyxM4IkKCN4iML3yuFy7g3SOlnB9ncCi93/qpQ9aVgt0qGdX2X V6Kz8eB3gofK/lOW5no3X6JnbnwAat5mq0ox7gk1288DgON5aBSRWW9jnwASggd8NnWDXi NLsBxnOCLWQX55MszHM009mZOYjSO0Kv0HVBv/EsgYGXHLY5md7wjteqxTGQoQ== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1640364783; a=rsa-sha256; cv=none; b=hTTlA7ltYOfrxs4tyuVJXT/B+8nzgX8Rv/zre6VMWxGlQF6wlys1Q90X7zFIxBNjh9puHS xCumxMDFunD68E/rMlKRPim4Ly91N3g/+tLZ1KYxkGkw54/HQhxqFVULrRVU2bA48zOMoJ AoEan5Uur8DNMKHf+2XP0WBmuaQdVtQXEOVbysHrUlrbIoXhwDwaF3GxitG6M/nLGSzQjN d59ZHni98tD3zzbHF5Zxf8CWWB5Fev4k8BVK2WlyJ9NA9UXqAX2RUX/tRRdsak8fJyUgFi nK/f//fl7evuASXJ1dmYEY1tHLSI2C41/yHR7M6uD+ovBIgJ2ByBB1cIAcp8tg== 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: -1.46 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: B6098E8FC X-Spam-Score: -1.46 X-Migadu-Scanner: scn0.migadu.com X-TUID: y/+Wkx81jRCD On 24/12/2021 03:27, Juan Manuel Macías wrote: > Robert Nikander writes: > >> I see why this is not possible, given the text format of an org file. >> But I am curious if people think it would be useful. While considered isolated, vim feature "set foldmethod=marker" with explicit open and closed markers ("{{{" and "}}}" by default) is more flexible. There are at least 2 problems with Org: performance penalty and rather reach lightweight markup, so a lot of marker variants are busy already. > Although we feel that our structure is very clear, our publisher will > probably force us to include some kind of division into the texts marked > with "??". I mean, it's not that easy to escape from the (graphical) > levels, parts and chapters, even if it is by editorial imposition or for > not confuse our readers. We can, for example, call Part II "Interlude", > or add the first text marked with "??" after a graphic separation (some > dashes, for example: ------). Although the literary structure is > complex, its graphical representation always has limits: Text books and magazines may contain insets (side notes), sometimes even page-long ones. They present independent material that may be interesting or useful in particular context or may be just skipped when a reader is concentrated on main material. Such inset may be considered as a heading that is inserted in the middle of another section. It may have larger margins, smaller font, distinct font face, another background color, box around or just rule at some side, so readers have clear notion where it ends and main material continues. Export filter may solve the problem by treating specially marked headings as continuation of text. Aside from export, it may be notes interspersed with deeper details (debug logs, etc.) It would be nice to be able to switch between 2 reading modes: all details are collapsed to quickly skim through main steps and conclusions or all details are open (in particular subtree). Plain list items, #+begin_/#+end_ blocks may be folded, drawers may be expanded but only individually. Besides list items, deeper nested substructure may be a problem, e.g. neither of them may contain headings. Using of such construct is not perfect but mostly bearable. The following is not a feature request just some thoughts how to achieve convenient reading without heading closing syntax. In addition to current heading visibility cycle, there may be commands increasing or decreasing "zoom level" for the whole document or for the current subtree. Headings may have a "lense" property that may change zoom level when such section becomes visible (absolute value or relative adjustment in respect to parent, positive or negative). So in response to "zoom in" command some headings are unfolded, some remains collapsed. Visibility effect to some extent is similar to explicit end of subheading.