From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: [html] non-lists showing up as lists Date: Sun, 02 Jun 2013 22:17:40 -0400 Message-ID: <87mwr8j5tn.fsf@pierrot.dokosmarshall.org> References: <874ndj13u5.fsf@gmail.com> <51A90A6A.5090105@gmail.com> <87a9na1gi9.fsf@gmail.com> <87d2s58w0g.fsf@breezy.my.home> <87ppw5vtb2.fsf@gmail.com> <87fvx0clbx.fsf@breezy.my.home> <87r4gkjio7.fsf@pierrot.dokosmarshall.org> <51ABCFD5.7040208@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36055) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UjKLO-0004vU-4Z for emacs-orgmode@gnu.org; Sun, 02 Jun 2013 22:18:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UjKLI-0005wP-Va for emacs-orgmode@gnu.org; Sun, 02 Jun 2013 22:17:58 -0400 Received: from plane.gmane.org ([80.91.229.3]:53288) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UjKLI-0005wL-Oj for emacs-orgmode@gnu.org; Sun, 02 Jun 2013 22:17:52 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1UjKLI-0001b1-8U for emacs-orgmode@gnu.org; Mon, 03 Jun 2013 04:17:52 +0200 Received: from pool-108-7-96-134.bstnma.fios.verizon.net ([108.7.96.134]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 03 Jun 2013 04:17:52 +0200 Received: from ndokos by pool-108-7-96-134.bstnma.fios.verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 03 Jun 2013 04:17:52 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Alan L Tyree writes: > 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 :-). > Wouldn't it be better to fix the file once and for all? After all, if you do that and then paste it into the org file, then refilling is *never* going to create the problem (assuming that there is no bug in the filling code of course: if there is, then it has to get fixed.) I may have misunderstood but I took the question to be the following: if I get an arbitrary file from somewhere, and I want to make an org document out of it, can I paste it in? The answer is "yes, but...": there might be problems. Checking the file with a script shows the problems, then you go in and fix them (by hand if necessary: four or five instances of the problem in 60+ pages seems insignificant, assuming that you *know* that the problem is there.) > 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. > Who's to guarantee that the file you are pasting in does not have indented dashes or numbers at the beginning of some lines? Wouldn't that cause the same problem? -- Nick