From: Nicolas Goaziou <n.goaziou@gmail.com>
To: smade4@gmail.com
Cc: Org Mode List <emacs-orgmode@gnu.org>,
Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: [ANN] List improvement v.2
Date: Sun, 15 Aug 2010 13:29:18 +0200 [thread overview]
Message-ID: <87y6c86rn5.wl%n.goaziou@gmail.com> (raw)
In-Reply-To: <8739ugfem9.fsf@gmail.com>
Hello,
> Glauber Alex Dias Prado writes:
>> Carsten Dominik <carsten.dominik@gmail.com> writes:
>> 1 Error when pressing M-RET in second line after list
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>> - Example item1
>> - Exmaple item2
>>
>> With cursor position at "@", M-RET throws an error
This is now fixed.
>> 2 Incompatibility 1
>> ~~~~~~~~~~~~~~~~~~~~
>> - Example 1
>> - Ex 2
>>
>> This used to be outside of the list. The HTML exporter still treats
>> it as being outside of the list. The LaTeX exporter treats it as
>> part of the last item. If I add a second empty line, then both
>> exporters handle it well.
>>
>> So this breaks with documented properties of the lists. I guess
>> this is unavoidable because this is just how the new list definition
>> works. But it will break existing documents when exported to LaTeX
According to the new list definition, LaTeX exporter is correct here.
Now, DocBook and HTML exporters will also treat it as being part of
the last item (unless `org-empty-line-terminates-plain-lists' is t,
obviously).
>> 3 Text between two sublists
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>> - Ex1
>> - Ex2
>> - Ex2a
>> - Ex2b
>> Some text between two sublists
>> - A new list starts
>>
>> This always was an inconsistency between HTML and LaTeX export, and it
>> still is now. There seems to be no way now to do what I intend here,
>> putting some text between two lists.
I removed this inconsistency (see 2.).
Alas, what you want to achieve here isn't possible. Lists are now a
strong structural element. Think of them as mini headings. Indentation
of body means nothing in both of them. In the case of headings, only
the number of stars matters, while lists only pay attention to
indentation of bullets.
There's somewhat a workaround though, as you can indent the very first
item of a list to any column, making this possible:
- List 1, item 1
- List 1, sub item 1
Some comments after list 1 has ended
- List 2, item 1
- List 2, item 2
- List 3, item 1
While there are in fact 3 different lists, it more or less looks like
what you want to do (and it could be cleaner with
`org-empty-line-terminates-plain-lists' set to t). Please note that
trick won't survive an export.
If export matters, there are quote blocks, or verbatim, or example.
But I won't teach you all of this! ;)
> preferably not only for lists, something like:
> * some stuff
> quick intro
> ** nest 1
> stuff about nest1
> now what i dont think is possible and dont even know if it is usually
> done on latex something that belongs to some stuff and is in between
> nest 1 and 2, i find it usefull for commenting on nests(thats why
> i miss it) and looks like it is the same thing you are wishing for lists?
> My use case for this is mostly note-taking.
> ** nest 2
> stuff about nest2
> could be also usefull, if it makes sense, btw the lists are taking shape :).
You are right, this is exactly the same problem. I think there are 2
ways to handle this:
1. either indentation brings information, and there can't possibly be
a working automatic indentation (like previous list implementation)
as you can never tell for sure if current line is badly indented or
sending information on something.
2. either indentation is given by structural elements (like headings
in your example) and there's no "in between nest 1 and 2".
Since Org is about structure, option 2 is, in my opinion, clearly the
way to go.
Regards,
-- Nicolas
next prev parent reply other threads:[~2010-08-15 11:29 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 21:08 [ANN] List improvement v.2 Nicolas Goaziou
2010-07-23 7:55 ` Nicolas Goaziou
2010-07-23 16:58 ` Eric Schulte
2010-07-25 16:17 ` Nicolas Goaziou
2010-07-27 12:51 ` Scot Becker
2010-07-27 14:50 ` Daniel Martins
2010-07-27 17:49 ` Nicolas Goaziou
2010-08-15 6:26 ` Carsten Dominik
2010-08-15 8:45 ` Glauber Alex Dias Prado
2010-08-15 11:29 ` Nicolas Goaziou [this message]
2010-08-15 14:40 ` Carsten Dominik
2010-08-15 20:52 ` Glauber Alex Dias Prado
2010-08-16 7:17 ` Carsten Dominik
2010-08-15 13:21 ` Nicolas Goaziou
2010-08-15 14:07 ` Nicolas Goaziou
2010-08-17 17:24 ` Request for opinions: [ANN] List improvement v.2o Carsten Dominik
2010-08-17 17:25 ` Carsten Dominik
2010-08-17 18:02 ` Nicolas Goaziou
2010-08-18 6:53 ` Sébastien Vauban
2010-08-18 22:50 ` Daniel Martins
2010-08-18 7:38 ` Christian Moe
2010-08-18 9:09 ` Nicolas Goaziou
2010-08-18 12:39 ` Christian Moe
2010-08-20 0:56 ` Nicolas Goaziou
2010-08-21 11:29 ` Bernt Hansen
2010-08-21 14:18 ` Nicolas Goaziou
2010-08-21 14:22 ` Bernt Hansen
2010-08-27 8:24 ` [ANN] List improvement v.2 Carsten Dominik
2010-08-27 10:57 ` Bernt Hansen
2010-09-02 8:13 ` Carsten Dominik
2010-09-03 8:39 ` Eric S Fraga
2010-09-03 14:34 ` Nicolas Goaziou
2010-09-03 17:16 ` Eric S Fraga
2010-09-03 20:26 ` Nicolas Goaziou
2010-09-03 20:42 ` Eric S Fraga
2010-09-03 15:06 ` Sebastian Rose
2010-09-04 3:54 ` Matt Lundin
2010-09-04 10:24 ` Nicolas Goaziou
2010-09-04 11:36 ` Carsten Dominik
2010-09-04 12:09 ` Nicolas Goaziou
2010-09-07 11:25 ` Strange behavior of M-RET with new list improvements Anthony Lander
2010-09-07 11:46 ` Bernt Hansen
2010-09-07 12:05 ` Anthony Lander
2010-09-07 17:11 ` Nicolas Goaziou
2010-09-17 13:01 ` [Bug] Level 2 text not exported in LaTeX (well in HTML) + some comments Sébastien Vauban
2010-09-17 15:29 ` Eric S Fraga
2010-09-18 18:02 ` Nicolas Goaziou
2010-09-18 21:53 ` Eric S Fraga
2010-09-19 9:24 ` Nicolas Goaziou
2010-09-19 21:07 ` Sébastien Vauban
2010-09-20 7:54 ` Eric S Fraga
2010-09-22 11:35 ` Carsten Dominik
2010-09-22 20:21 ` Sébastien Vauban
2010-09-22 21:31 ` Nicolas Goaziou
2010-09-18 17:44 ` Nicolas Goaziou
2010-09-19 21:01 ` Sébastien Vauban
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=87y6c86rn5.wl%n.goaziou@gmail.com \
--to=n.goaziou@gmail.com \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=smade4@gmail.com \
/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).