emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: c.buhtz@posteo.jp
To: emacs-orgmode@gnu.org
Subject: Re: Multiline list entries / Is auto-fill-mode in org(roam) usual?
Date: Sun, 03 Apr 2022 21:02:57 +0000	[thread overview]
Message-ID: <c21cd34ca6537f9359a42fb973cb6b2d@posteo.de> (raw)
In-Reply-To: <a17b319b742dae07277f03be5ea09400@posteo.de>

I found org-export-as-html and tested this

- one
   eins
ens

This as html is

<ul class="org-ul">
<li>one
eins</li>
</ul>
<p>
ens
</p>


Am 03.04.2022 22:28 schrieb c.buhtz@posteo.jp:
> Hello togehter,
> 
> is it usual to have auto-fill-mode (automatic new-line after n
> characters) turned on in org or org-roam (including fill-column set
> e.g. to 80)?
> Or let me ask from another point of view: Is it usual to have
> multiline list entries?
> 
> - first list entry
> - second list entry with more then 80 chars/columns two with Lorem 
> ipsum dolor
> sit amet, consetetur sadipscing elitr
> - third entry
> 
> Without auto-fill-mode it would look like this, without any linebreak
> in an entry:
> 
> - first list entry
> - second list entry with more then 80 chars/columns two with Lorem
> ipsum dolor sit amet, consetetur sadipscing elitr
> - third entry
> 
> I know that org is not markdown but I tried some markdown editors to
> test it. They still recognize the linebreak in my first example and
> rendered it "correct" as a 3 item list.
> I checked the syntax docu [1] about it but I couldn't find a hint or
> didn't understand.
> 
> Do I understand it correct that the end of a list is marked by an empty 
> line?
> 
> [1] -- 
> <https://orgmode.org/worg/dev/org-syntax.html#Plain_Lists_and_Items>


  reply	other threads:[~2022-04-03 21:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-03 20:28 Multiline list entries / Is auto-fill-mode in org(roam) usual? c.buhtz
2022-04-03 21:02 ` c.buhtz [this message]
2022-04-04 13:25   ` c.buhtz
2022-04-04 15:49     ` Tim Cross
2022-04-04 18:13       ` c.buhtz
2022-04-05  1:02         ` Tim Cross
2022-04-04  3:42 ` Kaushal Modi
2022-04-04  4:06   ` Ihor Radchenko
2022-04-04  4:26     ` Kaushal Modi
2022-04-04  7:16     ` c.buhtz
2022-04-04  7:44       ` Ihor Radchenko
     [not found]         ` <9ab81ac1c7c4a2e26187cf50ee8f3000@posteo.de>
2022-04-04 12:31           ` Remove old WORG page with Org Syntax (draft) in favour of new syntax page by Timothy (was: Multiline list entries / Is auto-fill-mode in org(roam) usual?) Ihor Radchenko
2022-04-04 16:08             ` Remove old WORG page with Org Syntax (draft) in favour of new syntax page by Timothy Nicolas Goaziou
2022-04-04 17:06               ` Timothy
2022-04-05  6:24                 ` Ihor Radchenko
2022-04-05  6:56                   ` Timothy
2022-04-05  7:26                     ` Ihor Radchenko
2022-04-05  7:46                       ` Timothy
2022-04-04 14:32       ` Multiline list entries / Is auto-fill-mode in org(roam) usual? c.buhtz
2022-04-04 15:02         ` Kaushal Modi
2022-04-04 15:54         ` Tim Cross

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c21cd34ca6537f9359a42fb973cb6b2d@posteo.de \
    --to=c.buhtz@posteo.jp \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).