From: Alan L Tyree <alantyree@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [html] non-lists showing up as lists
Date: Tue, 04 Jun 2013 05:59:13 +1000 [thread overview]
Message-ID: <87ehcjc6em.fsf@breezy.my.home> (raw)
In-Reply-To: <D298A8A2-72DE-43B1-8F35-ED6BDFA9E3CD@gmail.com>
Carsten Dominik writes:
> Hi everyone.
>
> As far as I can see, the filling code is already pretty smart about this issue. The question is then: What else can we do about it.
>
After doing some analysis of my problems last night, I agree that
filling is not the issue. All of the instances that I have found in my
own files are the result of pasting in from another file (case law plain
text database or a web page).
> Possibilities:
> 1. We could change the parser to ignore lists where the first
> item does not start with `1.' or `a)'. But this would
> be a pretty serious change.
>
> 2. We could implement a good function that could find problematic
> cases, so that they can be fixed by hand. This is basically
> what Nick proposed - only it would be implemented in Lisp.
>
> 3. We could implement a function that finds and fixes such issues.
> It would basically scan the buffer and find lists that have
> only a single item, not starting with 1, and change the wrapping
> to fix it.
>
> In any case, some hand work would be involved.
> I think we cannot fix this problem in full generality. The reason
> is simply that Org is a plain text format and has to be heuristic about
> parsing. There will always be edge cases like this.
I agree with this, Carsten. As to the choices, it seems to me that the
only real choices here are between 2 or 3.
I can't imagine ever needing a list with a single item, but there might
be a single list item in a partially completed manuscript, so I guess an
"automatic" fix should offer the user the option to leave each instance
alone.
For my purposes, either 2 or 3 would be more than satisfactory.
Cheers,
Alan
>
> Anyone volunteering to write a command that will
> check the buffer and warn about it? Maybe it could be
> implemented as org-find-next-funny-list-start, so that
> it could be used to search through the whole buffer.
>
> - Carsten
>
>
> On 3 jun. 2013, at 07:45, Alan L Tyree <alantyree@gmail.com> wrote:
>
>> On 03/06/13 15:40, Samuel Wales wrote:
>>> I don't recall whether I said I had a filling problem.
>>>
>>> Filling is a red herring for my use case.
>>>
>>> My point is that regardless of filling, it would be a good idea to be
>>> stricter about what a list is, for the reasons I listed. In my use
>>> case.
>>>
>>> Samuel
>>>
>> You're right - you said "filling and yanking" in your first post.
>>
>> As I said to Nick, I don't know if my problems stem from filling or not. Just know there are problems and I will track them down when I have a little time.
>>
>> Cheers,
>> Alan
>>
>> --
>> Alan L Tyree http://www2.austlii.edu.au/~alan
>> Tel: 04 2748 6206 sip:172385@iptel.org
>>
>>
--
Alan L Tyree http://www2.austlii.edu.au/~alan
Tel: 04 2748 6206 sip:172385@iptel.org
next prev parent reply other threads:[~2013-06-03 19:58 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
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 [this message]
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=87ehcjc6em.fsf@breezy.my.home \
--to=alantyree@gmail.com \
--cc=carsten.dominik@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).