From: Carsten Dominik <carsten.dominik@gmail.com>
To: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Release 7.02
Date: Fri, 29 Oct 2010 13:48:35 +0200 [thread overview]
Message-ID: <4DCCE1BD-EA36-4EFC-8DFC-3F44186DA15F@gmail.com> (raw)
In-Reply-To: <80eib9p6wp.fsf@mundaneum.com>
On Oct 29, 2010, at 1:36 PM, Sébastien Vauban wrote:
> Hi Carsten,
>
> Carsten Dominik wrote:
>> On Oct 29, 2010, at 10:30 AM, Sébastien Vauban wrote:
>>> Carsten Dominik wrote:
>>>> Due to changes made to lists, it is no longer possible to have a
>>>> sublist,
>>>> some text and then another sublist while still in the same top-
>>>> level list
>>>> item, like in the following situation:
>>>>
>>>> - Some list
>>>> + A first sublist
>>>> + of two elements
>>>>
>>>> A text belonging to the top-level list
>>>>
>>>> + Then another sublist
>>>> + and a second element in it
>>>> - End of main list
>>>
>>> Basically, it means that this entry for this entry (about Org
>>> Babel) from
>>> an old file of mine (update this morning) does not publish anymore
>>> the same
>>> way:
>>>
>>> --8<---------------cut here---------------start------------->8---
>>> * How to view the results
>>>
>>> - =C-c C-v C-v= (or =C-c C-v v=) -- View the expanded body of a
>>> code block.
>>>
>>> - =C-c C-v C-z= -- Switch to the *session* of the current code
>>> block (first,
>>> you need to add =:session= to it).
>>>
>>> Use =C-u C-c C-v C-z= to bring up the session with the input
>>> variable
>>> pre-loaded.
>>>
>>> =C-c C-v z= (=org-babel-switch-to-session-with-code=) is a variant
>>> of =C-c
>>> C-v C-z= (=org-babel-switch-to-session=): instead of switching to
>>> the
>>> session buffer, it splits the window between:
>>>
>>> + the session buffer, and
>>> + a language major-mode edit buffer for the code block in question.
>>>
>>> This can be convenient for using language major mode for
>>> interacting with
>>> the session buffer.
>>> --8<---------------cut here---------------end--------------->8---
>>>
>>> The last sentence is *not* considered part of the second element
>>> of the
>>> first list.
>>>
>>> Although I've seen similar constructs in many, many documents,
>>> does anyone
>>> know enough rules of style to tell me if this is a wrong way to
>>> write
>>> things down? Or, does some possibility still exist to support this
>>> seamlessly?
>>
>> It is not that this would be bad style. In fact I do miss this kind
>> of
>> structure as well, and accepting loosing it was the biggest
>> argument against
>> Nicolas' change.
>
> Does that mean that we must admit this will stay like that forever,
> or will
> one try to look and see if it's possible to make that extension?
I am not against it if it can be done in a clean way that is in
keeping with the structure and philosophy Nicolas has implemented.
I think this will mean that we would not use just indentation to
define this,
but some explicit piece of syntax.
Patches and discussions about this will always be welcome, no need to
close any door for good.
>
>
>> However, the trade was for much greater stability and consistency
>> of plain
>> lists, Nicolas has done some great work here. Another issue was
>> that the
>> LaTeX exporter never had any support for these structures, so that
>> was
>> inconsistent for a long time.
>
> I know that Bastien told he would fix it when he would have time.
> So, that did
> not seem to be an impossible wish.
Trust me, it is not something I can do in a day or two, or I would
have done it a long time ago. I don't know why Bastien has never done
it. bastien, did you ever try?
- Carsten
next prev parent reply other threads:[~2010-10-29 11:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-29 6:49 Release 7.02 Carsten Dominik
2010-10-29 8:30 ` Sébastien Vauban
2010-10-29 9:26 ` Carsten Dominik
2010-10-29 11:36 ` Sébastien Vauban
2010-10-29 11:48 ` Carsten Dominik [this message]
2010-10-29 16:20 ` Nicolas Goaziou
2010-10-29 9:28 ` Carsten Dominik
2010-10-29 12:42 ` Eric S Fraga
2010-10-29 13:07 ` Łukasz Stelmach
2010-10-29 12:59 ` Łukasz Stelmach
2010-10-29 14:42 ` Bastien
2010-10-29 14:02 ` Jambunathan K
2010-10-29 14:31 ` Carsten Dominik
2010-10-29 14:52 ` Eric Schulte
2010-10-29 17:50 ` Jeff Horn
2010-10-29 18:03 ` Erik Iverson
2010-10-29 18:20 ` Jeff Horn
2010-10-29 18:23 ` Erik Iverson
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=4DCCE1BD-EA36-4EFC-8DFC-3F44186DA15F@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=wxhgmqzgwmuf@spammotel.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).