emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alan L Tyree <alantyree@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [html] non-lists showing up as lists
Date: Mon, 03 Jun 2013 09:05:57 +1000	[thread overview]
Message-ID: <51ABCFD5.7040208@gmail.com> (raw)
In-Reply-To: <87r4gkjio7.fsf@pierrot.dokosmarshall.org>

On 03/06/13 07:40, Nick Dokos wrote:
> Alan L Tyree <alantyree@gmail.com> writes:
>
>> So: my problem is that somehow the '137.' got at the head of a line. I
>> have no idea how that happened. I inserted references in this document
>> using reftex, so I suppose that is one source to investigate.
>>
>> The other source is, no doubt, cut and paste.
>>
>> In a 60+ page document, I had four or five of these, so it is a very
>> annoying problem.
>>
>> In view of this, should I explore further about the source of these or
>> try out the patch you sent?
>>
>
> If the problematic lines existed in the file that you pasted into an org
> file, then there is nothing that org can do of course. The thing to do
> is to check the file *before* you "import" it into org. Here's a simple
> awk script to catch the two cases of plain and numbered lists:
>
> --8<---------------cut here---------------start------------->8---
> #! /usr/bin/gawk -f
>
> /^ *- /         {printf("Line %d: plain list element: %s\n", NR, $0);}
> /^ *[0-9]+\. /	{printf("Line %d: numbered list element: %s\n", NR, $0);}
> --8<---------------cut here---------------end--------------->8---
>
> Catching more cases and integrating the script into your workflow (and
> fixing any bugs) is left as an exercise.
>
Indeed, an exercise which I have already done in the form of a lisp 
function to catch the nasty little numbers at the beginning of lines.

For the earlier exporter, I used this to insert non-printing spaces, 
export, then remove non-printing space. Far from elegant :-).

I still like the suggestion that there should be an option so that lists 
cannot begin at the beginning of a line. Like Samuel earlier in this 
thread, I always indent lists.

Thanks for you consideration of all this, Nicolas. I need to identify 
where the offending lines are coming from.

Cheers,
Alan



-- 
Alan L Tyree                    http://www2.austlii.edu.au/~alan
Tel:  04 2748 6206		sip:172385@iptel.org

  reply	other threads:[~2013-06-02 23:05 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-31 16:54 [html] non-lists showing up as lists Samuel Wales
2013-05-31 17:01 ` Nicolas Goaziou
2013-05-31 20:39   ` Alan L Tyree
2013-06-01  6:39     ` Nicolas Goaziou
2013-06-01 19:35       ` Alan L Tyree
2013-06-02  7:57         ` Nicolas Goaziou
2013-06-02  9:12           ` Nicolas Goaziou
2013-06-02 20:24           ` Alan L Tyree
2013-06-02 21:40             ` Nick Dokos
2013-06-02 23:05               ` Alan L Tyree [this message]
2013-06-03  2:17                 ` Nick Dokos
2013-06-03  4:29                   ` Alan L Tyree
2013-06-03  5:40                     ` Samuel Wales
2013-06-03  5:45                       ` Alan L Tyree
2013-06-03  7:52                         ` Carsten Dominik
2013-06-03 19:59                           ` Alan L Tyree
2013-06-06 16:37                       ` Bernt Hansen
2013-06-06 17:25                         ` Samuel Wales
2013-06-01 20:10     ` Samuel Wales
2013-06-01 20:18       ` Samuel Wales
2013-06-01 22:58         ` Alan L Tyree
  -- strict thread matches above, loose matches on Subject: below --
2013-06-03  9:54 Michael Strey
2013-06-03 10:05 ` Carsten Dominik
2013-06-03 16:28   ` Samuel Wales
2013-06-04 10:02     ` Bastien
2013-06-04 17:49       ` Samuel Wales
2013-06-06 10:26 Michael Strey

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=51ABCFD5.7040208@gmail.com \
    --to=alantyree@gmail.com \
    --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).