From: Peter Salazar <cycleofsong@gmail.com>
To: Rasmus <rasmus@gmx.us>
Cc: org-mode <emacs-orgmode@gnu.org>
Subject: Re: Valid use cases for lists?
Date: Sun, 23 Aug 2015 13:18:26 -0400 [thread overview]
Message-ID: <CAE+_6TzAqy+-Mu+oPGRJ4NJzcaReoyXwKtMqAZd6yEhG-_M6=Q@mail.gmail.com> (raw)
In-Reply-To: <87h9nsh4f6.fsf@gmx.us>
[-- Attachment #1: Type: text/plain, Size: 1187 bytes --]
Agreed, plain-text lists are definitely preferable!
On Fri, Aug 21, 2015 at 2:39 PM, Rasmus <rasmus@gmx.us> wrote:
> Peter Salazar <cycleofsong@gmail.com> writes:
>
> > Export isn't a good reason to use lists over headings, since you can
> always
> > export headings as <li> lists if you want to, e.g. by setting number of
> > heading levels in export options. This doesn't mean plain text lists
> aren't
> > useful in org, it just means you don't need them to get lists in your
> > export format.
>
> Semantically, lists are nicer.
>
> Compare this is your org file.
>
> * A very long item which you'd like to split over several lines A very
> long item which you'd like to split over several lines A very long item
> which you'd like to split over several lines A very long item which you'd
> like to split over several lines
>
> - A very long item which you'd like to split over several lines A very
> long item which you'd like to split over several lines A very long
> item which you'd like to split over several lines A very long item
> which you'd like to split over several lines
>
>
> Which one do you prefer?
>
>
> --
> With monopolies the cake is a lie!
>
>
>
[-- Attachment #2: Type: text/html, Size: 1761 bytes --]
next prev parent reply other threads:[~2015-08-23 17:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 19:32 Valid use cases for lists? Chris Patti
2015-08-19 19:55 ` Rasmus
2015-08-20 15:18 ` Mike McLean
2015-08-21 3:59 ` Peter Salazar
2015-08-21 18:39 ` Rasmus
2015-08-23 17:18 ` Peter Salazar [this message]
2015-08-19 20:00 ` Kyle Meyer
2015-08-19 21:02 ` Florian Beck
2015-08-20 14:06 ` Matt Lundin
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='CAE+_6TzAqy+-Mu+oPGRJ4NJzcaReoyXwKtMqAZd6yEhG-_M6=Q@mail.gmail.com' \
--to=cycleofsong@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
/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).