From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Michelbach Subject: Feature Proposal: Titled Paragraphs Date: Wed, 23 Oct 2019 15:13:09 +0200 Message-ID: <3eb58af3-c03b-4225-ec31-15321c05ceff@gmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------------E1B10D07C903DB34A05658F6" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:43294) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iNGRu-0005hx-Jc for emacs-orgmode@gnu.org; Wed, 23 Oct 2019 09:13:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iNGRt-0007T7-EJ for emacs-orgmode@gnu.org; Wed, 23 Oct 2019 09:13:14 -0400 Received: from mail-wr1-x429.google.com ([2a00:1450:4864:20::429]:32855) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iNGRt-0007Ss-6B for emacs-orgmode@gnu.org; Wed, 23 Oct 2019 09:13:13 -0400 Received: by mail-wr1-x429.google.com with SMTP id s1so13293537wro.0 for ; Wed, 23 Oct 2019 06:13:12 -0700 (PDT) Received: from ?IPv6:2a02:8071:2189:cc00:ce9b:34ca:9b3f:e9c3? ([2a02:8071:2189:cc00:ce9b:34ca:9b3f:e9c3]) by smtp.gmail.com with ESMTPSA id e17sm20113692wma.15.2019.10.23.06.13.10 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 23 Oct 2019 06:13:10 -0700 (PDT) Content-Language: en-US List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org This is a multi-part message in MIME format. --------------E1B10D07C903DB34A05658F6 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit I often write documents in org mode that are going to be exported to PDF via LaTeX and find myself writing something like \paragraph{Lorem Ipsum} Duis ac nibh cursus, elementum ipsum quis, faucibus sapien. \paragraph{Interdum} Cras volutpat, sem eu semper ultrices, risus lacus tempor erat, eu pulvinar magna arcu sit amet massa. a lot, therefore mixing very simple Latex into my org documents simply because I want titled paragraphs. This comes with the further disadvantage that there is no syntax highlighting for it while editing. This is despite the fact that org mode already has syntax for titled things. Whenever we need a description list, we write: - Lorem Ipsum :: Duis ac nibh cursus, elementum ipsum quis, faucibus sapien. - Interdum :: Cras volutpat, sem eu semper ultrices, risus lacus tempor erat, eu pulvinar magna arcu sit amet massa. I think we should be able to use the same syntax outside of lists: Lorem Ipsum :: Duis ac nibh cursus, elementum ipsum quis, faucibus sapien. Interdum :: Cras volutpat, sem eu semper ultrices, risus lacus tempor erat, eu pulvinar magna arcu sit amet massa. -- Christoph Michelbach --------------E1B10D07C903DB34A05658F6 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit I often write documents in org mode that are going to be exported to PDF via LaTeX and find myself writing something like

\paragraph{Lorem Ipsum} Duis ac nibh cursus, elementum ipsum quis, faucibus sapien.

\paragraph{Interdum} Cras volutpat, sem eu semper ultrices, risus lacus tempor erat, eu pulvinar magna arcu sit amet massa.

a lot, therefore mixing very simple Latex into my org documents simply because I want titled paragraphs. This comes with the further disadvantage that there is no syntax highlighting for it while editing.

This is despite the fact that org mode already has syntax for titled things. Whenever we need a description list, we write:

- Lorem Ipsum :: Duis ac nibh cursus, elementum ipsum quis, faucibus sapien.
- Interdum :: Cras volutpat, sem eu semper ultrices, risus lacus tempor erat, eu pulvinar magna arcu sit amet massa.

I think we should be able to use the same syntax outside of lists:

Lorem Ipsum :: Duis ac nibh cursus, elementum ipsum quis, faucibus sapien.

Interdum :: Cras volutpat, sem eu semper ultrices, risus lacus tempor erat, eu pulvinar magna arcu sit amet massa.

--
Christoph Michelbach
--------------E1B10D07C903DB34A05658F6-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Fraga, Eric" Subject: Re: Feature Proposal: Titled Paragraphs Date: Wed, 23 Oct 2019 13:24:32 +0000 Message-ID: <87o8y7sigg.fsf@ucl.ac.uk> References: <3eb58af3-c03b-4225-ec31-15321c05ceff@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:46103) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iNGcu-000149-RG for emacs-orgmode@gnu.org; Wed, 23 Oct 2019 09:24:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iNGct-0006aG-O3 for emacs-orgmode@gnu.org; Wed, 23 Oct 2019 09:24:36 -0400 Received: from mail-eopbgr30121.outbound.protection.outlook.com ([40.107.3.121]:20484 helo=EUR03-AM5-obe.outbound.protection.outlook.com) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iNGct-0006Zn-B8 for emacs-orgmode@gnu.org; Wed, 23 Oct 2019 09:24:35 -0400 In-Reply-To: <3eb58af3-c03b-4225-ec31-15321c05ceff@gmail.com> (Christoph Michelbach's message of "Wed, 23 Oct 2019 15:13:09 +0200") Content-Language: en-US List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Christoph Michelbach Cc: "emacs-orgmode@gnu.org" On Wednesday, 23 Oct 2019 at 15:13, Christoph Michelbach wrote: > I often write documents in org mode that are going to be exported to > PDF via LaTeX and find myself writing something like > > \paragraph{Lorem Ipsum} Duis ac nibh cursus, elementum ipsum quis, > faucibus sapien. [...] > I think we should be able to use the same syntax outside of lists: Why not use a further headline if you are exporting to LaTeX? In the default configuration, the 4th level heading corresponds to \paragraph in LaTeX. --=20 Eric S Fraga via Emacs 27.0.50, Org release_9.2.6-552-g8c5a78 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Michelbach Subject: Re: Feature Proposal: Titled Paragraphs Date: Wed, 23 Oct 2019 15:51:02 +0200 Message-ID: References: <3eb58af3-c03b-4225-ec31-15321c05ceff@gmail.com> <87o8y7sigg.fsf@ucl.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:50200) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iNH2Z-0005XP-P5 for emacs-orgmode@gnu.org; Wed, 23 Oct 2019 09:51:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iNH2Y-0007FB-Lw for emacs-orgmode@gnu.org; Wed, 23 Oct 2019 09:51:07 -0400 Received: from mail-wm1-x334.google.com ([2a00:1450:4864:20::334]:36125) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iNH2Y-0007EW-F3 for emacs-orgmode@gnu.org; Wed, 23 Oct 2019 09:51:06 -0400 Received: by mail-wm1-x334.google.com with SMTP id c22so10637341wmd.1 for ; Wed, 23 Oct 2019 06:51:06 -0700 (PDT) In-Reply-To: <87o8y7sigg.fsf@ucl.ac.uk> Content-Language: en-US List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: "Fraga, Eric" Cc: "emacs-orgmode@gnu.org" On 2019-10-23 15:24, Fraga, Eric wrote: > Why not use a further headline if you are exporting to LaTeX? In the > default configuration, the 4th level heading corresponds to \paragraph > in LaTeX. > 1. Because headlines and paragraphs are different things. One is used for hierarchical structuring and description, the other only for description. 2. Because that'd mean skipping hierarchical levels when using paragraphs on a high level. 3. Because headlines are collapsed by default. I realize the default can be changed but if you like hierarchical levels to be collapsed, you still have to expand paragraphs far up individually or expand all the hierarchical levels below by dobule-tabbing. -- Christoph Michelbach From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Fraga, Eric" Subject: Re: Feature Proposal: Titled Paragraphs Date: Wed, 23 Oct 2019 14:20:15 +0000 Message-ID: <87y2xbr1b5.fsf@ucl.ac.uk> References: <3eb58af3-c03b-4225-ec31-15321c05ceff@gmail.com> <87o8y7sigg.fsf@ucl.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:55273) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iNHUx-00083z-ME for emacs-orgmode@gnu.org; Wed, 23 Oct 2019 10:20:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iNHUr-0003l5-NG for emacs-orgmode@gnu.org; Wed, 23 Oct 2019 10:20:27 -0400 Received: from mail-eopbgr10138.outbound.protection.outlook.com ([40.107.1.138]:40346 helo=EUR02-HE1-obe.outbound.protection.outlook.com) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iNHUr-0003he-BB for emacs-orgmode@gnu.org; Wed, 23 Oct 2019 10:20:21 -0400 In-Reply-To: (Christoph Michelbach's message of "Wed, 23 Oct 2019 15:51:02 +0200") Content-Language: en-US List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Christoph Michelbach Cc: "emacs-orgmode@gnu.org" Hi Cristoph, okay, paragraph headings are not what you want. And lists aren't suitable either. I don't think there is any other way and I predict that adding :: syntax in arbitrary positions will not be acceptable as a development to the language but let's see what others think. I have no strong feelings either way. Just some rebuttals on your points: On Wednesday, 23 Oct 2019 at 15:51, Christoph Michelbach wrote: > 1. Because headlines and paragraphs are different things. One is used > for hierarchical structuring and description, the other only for=20 > description. Well, that's a personal view, not a strict definition. > 2. Because that'd mean skipping hierarchical levels when using > paragraphs on a high level. Org allows this just fine. I often have 4th level headings within a 1st level heading with no intervening levels. > 3. Because headlines are collapsed by default. I realize the default > can be changed but if you like hierarchical levels to be collapsed, > you still have to expand paragraphs far up individually or expand all > the hierarchical levels below by dobule-tabbing. You can set visibility on individual headlines using properties. =20 I always start my (long) documents with all headings to a certain level exposed (org-content 3) so paragraphs are hidden by default. You might find this useful. Or maybe not! ;-) --=20 Eric S Fraga via Emacs 27.0.50, Org release_9.2.6-552-g8c5a78 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dominik Schrempf Subject: Re: Feature Proposal: Titled Paragraphs Date: Wed, 23 Oct 2019 16:18:20 +0200 Message-ID: <87h83zy28j.fsf@gmail.com> References: <3eb58af3-c03b-4225-ec31-15321c05ceff@gmail.com> <87o8y7sigg.fsf@ucl.ac.uk> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:54986) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iNHT2-0006hm-IZ for emacs-orgmode@gnu.org; Wed, 23 Oct 2019 10:18:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iNHT1-0002hH-2G for emacs-orgmode@gnu.org; Wed, 23 Oct 2019 10:18:28 -0400 Received: from mail-wm1-x332.google.com ([2a00:1450:4864:20::332]:56149) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iNHT0-0002gl-AB for emacs-orgmode@gnu.org; Wed, 23 Oct 2019 10:18:26 -0400 Received: by mail-wm1-x332.google.com with SMTP id g24so12281302wmh.5 for ; Wed, 23 Oct 2019 07:18:24 -0700 (PDT) In-reply-to: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org Cc: "Fraga, Eric" Hello! I agree with this proposal. At some point I already asked if the following structure is possible: #+begin_example * Title ** Section I Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Donec hendrerit tempor tellus. Donec pretium posuere tellus. Proin quam nisl, tincidunt et, mattis eget, convallis nec, purus. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Nulla posuere. Donec vitae dolor. Nullam tristique diam non turpis. Cras placerat accumsan nulla. Nullam rutrum. Nam vestibulum accumsan nisl. Another paragraph that is not related to Section I, but doesn't deserve a section title. Another paragraph that is not related to Section I, but doesn't deserve a section title. Another paragraph that is not related to Section I, but doesn't deserve a section title. Another paragraph that is not related to Section I, but doesn't deserve a section title. #+end_example With titled paragraphs, this document structure could be achieved. All the best, Dominik Christoph Michelbach writes: > On 2019-10-23 15:24, Fraga, Eric wrote: >> Why not use a further headline if you are exporting to LaTeX? In the >> default configuration, the 4th level heading corresponds to \paragraph >> in LaTeX. >> > > 1. Because headlines and paragraphs are different things. One is used for > hierarchical structuring and description, the other only for description. > 2. Because that'd mean skipping hierarchical levels when using paragraphs on a > high level. > 3. Because headlines are collapsed by default. I realize the default can be > changed but if you like hierarchical levels to be collapsed, you still have to > expand paragraphs far up individually or expand all the hierarchical levels > below by dobule-tabbing. From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Loris Bennett" Subject: Re: Feature Proposal: Titled Paragraphs Date: Wed, 23 Oct 2019 16:55:23 +0200 Message-ID: <87ftjjtstg.fsf@hornfels.zedat.fu-berlin.de> References: <3eb58af3-c03b-4225-ec31-15321c05ceff@gmail.com> <87o8y7sigg.fsf@ucl.ac.uk> <87h83zy28j.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:33661) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iNI2z-0003hR-SL for emacs-orgmode@gnu.org; Wed, 23 Oct 2019 10:55:38 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iNI2y-0006jz-Lj for emacs-orgmode@gnu.org; Wed, 23 Oct 2019 10:55:37 -0400 Received: from 195-159-176-226.customer.powertech.no ([195.159.176.226]:47430 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iNI2y-0006gG-E0 for emacs-orgmode@gnu.org; Wed, 23 Oct 2019 10:55:36 -0400 Received: from list by blaine.gmane.org with local (Exim 4.89) (envelope-from ) id 1iNI2t-000nIi-E2 for emacs-orgmode@gnu.org; Wed, 23 Oct 2019 16:55:31 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org Hi, What would be an actual example of a "paragraph that is not related to Section I, but doesn't deserve a section title"? Cheers, Loris Dominik Schrempf writes: > Hello! > > I agree with this proposal. At some point I already asked if the following > structure is possible: > > #+begin_example > * Title > ** Section I > Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Donec hendrerit tempor > tellus. Donec pretium posuere tellus. Proin quam nisl, tincidunt et, mattis > eget, convallis nec, purus. Cum sociis natoque penatibus et magnis dis > parturient montes, nascetur ridiculus mus. Nulla posuere. Donec vitae dolor. > Nullam tristique diam non turpis. Cras placerat accumsan nulla. Nullam rutrum. > Nam vestibulum accumsan nisl. > > Another paragraph that is not related to Section I, but doesn't deserve a > section title. Another paragraph that is not related to Section I, but doesn't > deserve a section title. Another paragraph that is not related to Section I, but > doesn't deserve a section title. Another paragraph that is not related to > Section I, but doesn't deserve a section title. > #+end_example > > With titled paragraphs, this document structure could be achieved. > > All the best, > Dominik > > Christoph Michelbach writes: > >> On 2019-10-23 15:24, Fraga, Eric wrote: >>> Why not use a further headline if you are exporting to LaTeX? In the >>> default configuration, the 4th level heading corresponds to \paragraph >>> in LaTeX. >>> >> >> 1. Because headlines and paragraphs are different things. One is used for >> hierarchical structuring and description, the other only for description. >> 2. Because that'd mean skipping hierarchical levels when using paragraphs on a >> high level. >> 3. Because headlines are collapsed by default. I realize the default can be >> changed but if you like hierarchical levels to be collapsed, you still have to >> expand paragraphs far up individually or expand all the hierarchical levels >> below by dobule-tabbing. > > > -- Dr. Loris Bennett (Mr.) ZEDAT, Freie Universität Berlin Email loris.bennett@fu-berlin.de From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Feature Proposal: Titled Paragraphs Date: Wed, 23 Oct 2019 18:44:40 +0200 Message-ID: <87k18v5s3r.fsf@nicolasgoaziou.fr> References: <3eb58af3-c03b-4225-ec31-15321c05ceff@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:51722) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iNJke-0006V8-Cv for emacs-orgmode@gnu.org; Wed, 23 Oct 2019 12:44:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iNJkc-0007kq-TH for emacs-orgmode@gnu.org; Wed, 23 Oct 2019 12:44:47 -0400 Received: from relay7-d.mail.gandi.net ([217.70.183.200]:53307) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iNJkc-0007hX-NP for emacs-orgmode@gnu.org; Wed, 23 Oct 2019 12:44:46 -0400 In-Reply-To: <3eb58af3-c03b-4225-ec31-15321c05ceff@gmail.com> (Christoph Michelbach's message of "Wed, 23 Oct 2019 15:13:09 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Christoph Michelbach Cc: emacs-orgmode@gnu.org Hello, Christoph Michelbach writes: > I often write documents in org mode that are going to be exported to > PDF via LaTeX and find myself writing something like > > \paragraph{Lorem Ipsum} Duis ac nibh cursus, elementum ipsum quis, > faucibus sapien. > > \paragraph{Interdum} Cras volutpat, sem eu semper ultrices, risus > lacus tempor erat, eu pulvinar magna arcu sit amet massa. > > a lot, therefore mixing very simple Latex into my org documents simply > because I want titled paragraphs. This comes with the further > disadvantage that there is no syntax highlighting for it while > editing. There is nothing wrong with using simple LaTeX in Org files, if you intent to export to PDF. Org doesn't provide equivalents for \bigskip, or \vspace, or \hfill=E2=80=A6 Anyhow, you could use a macro, if you want to make it look more Org-ish, or try to use keywords, e.g., #+attr_latex: :title Whatever Foo... Changing the syntax is the very last thing to consider, IMO. Regards, --=20 Nicolas Goaziou From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Fraga, Eric" Subject: Re: Feature Proposal: Titled Paragraphs Date: Thu, 24 Oct 2019 05:20:22 +0000 Message-ID: <87wocuk9d6.fsf@ucl.ac.uk> References: <3eb58af3-c03b-4225-ec31-15321c05ceff@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:43443) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iNVXv-0002f3-8W for emacs-orgmode@gnu.org; Thu, 24 Oct 2019 01:20:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iNVXu-0002RV-8H for emacs-orgmode@gnu.org; Thu, 24 Oct 2019 01:20:27 -0400 Received: from mail-eopbgr150135.outbound.protection.outlook.com ([40.107.15.135]:35085 helo=EUR01-DB5-obe.outbound.protection.outlook.com) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iNVXt-0002QU-SR for emacs-orgmode@gnu.org; Thu, 24 Oct 2019 01:20:26 -0400 In-Reply-To: <3eb58af3-c03b-4225-ec31-15321c05ceff@gmail.com> (Christoph Michelbach's message of "Wed, 23 Oct 2019 15:13:09 +0200") Content-Language: en-US List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Christoph Michelbach Cc: "emacs-orgmode@gnu.org" On Wednesday, 23 Oct 2019 at 15:13, Christoph Michelbach wrote: > This comes with the further disadvantage that there is no syntax > highlighting for it while editing. I forgot to add that you could use hi-lock-mode to highlight your \paragraph statements. --=20 Eric S Fraga via Emacs 27.0.50, Org release_9.2.6-552-g8c5a78 From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?Julius_M=c3=bcller?= Subject: Re: Feature Proposal: Titled Paragraphs Date: Thu, 24 Oct 2019 09:50:17 +0200 Message-ID: <8df91ed0-912f-70f8-a4b3-b80a12bd53de@gmx.net> References: <3eb58af3-c03b-4225-ec31-15321c05ceff@gmail.com> <87o8y7sigg.fsf@ucl.ac.uk> <87h83zy28j.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:33519) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iNXt7-0006QD-AC for emacs-orgmode@gnu.org; Thu, 24 Oct 2019 03:50:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iNXt6-0001Es-27 for emacs-orgmode@gnu.org; Thu, 24 Oct 2019 03:50:29 -0400 Received: from mout.gmx.net ([212.227.15.15]:34221) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iNXt5-0001EA-KY for emacs-orgmode@gnu.org; Thu, 24 Oct 2019 03:50:28 -0400 Received: from [192.168.175.209] ([87.139.53.30]) by mail.gmx.com (mrgmx004 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MSKuA-1iYWFb0nJA-00Sf5A for ; Thu, 24 Oct 2019 09:50:23 +0200 In-Reply-To: <87h83zy28j.fsf@gmail.com> Content-Language: en-GB List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org Am 23.10.19 um 16:18 schrieb Dominik Schrempf: > I agree with this proposal. At some point I already asked if the followi= ng > structure is possible: > > #+begin_example > * Title > ** Section I > Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Donec hendreri= t tempor > tellus. Donec pretium posuere tellus. Proin quam nisl, tincidunt et, mat= tis > eget, convallis nec, purus. Cum sociis natoque penatibus et magnis dis > parturient montes, nascetur ridiculus mus. Nulla posuere. Donec vitae do= lor. > Nullam tristique diam non turpis. Cras placerat accumsan nulla. Nullam r= utrum. > Nam vestibulum accumsan nisl. > > Another paragraph that is not related to Section I, but doesn't deserve = a > section title. Another paragraph that is not related to Section I, but d= oesn't > deserve a section title. Another paragraph that is not related to Sectio= n I, but > doesn't deserve a section title. Another paragraph that is not related t= o > Section I, but doesn't deserve a section title. > #+end_example > > With titled paragraphs, this document structure could be achieved. Only if you are very restrictive about it, as you hit a fundamental problem of org markup here, a problem it shares with (La)TeX, HTML, all printed books I'm aware of, and a lot of other formats. Org and (La)TeX only markup the start of a section, not its end. Thus it would be difficult to tell your construct apart from other kind of structures. Contrary to your view, in the (La)TeX-world \paragraph is usually seen as just another hierarchical level of document structuring. It is a heading (with a weird default of not standing on a line of its own), and it does NOT solely belong to the one paragraph it starts. In fact, with your view, (La)TeX's \subparagraph macro would not make any sense at all. That means, adding \paragraph in your sense will break document structure the moment you also have nesting deeper than 3 (or 4 for book-like formats). Julius