Bug: org-plain-list-ordered-item-terminator

Bug: org-plain-list-ordered-item-terminator

[Matthew Lundin]

When I set org-plain-list-ordered-item-terminator to 'paren like in
"2)"' in the customize interface, I no longer able to use plain lists in
org-mode, but instead get the following error:

,----
| org-at-item-p: Invalid regexp: "Unmatched ( or \\("
`----

In my custom settings, the setting looks like this:

,----
| [snip]                                      
| '(org-plain-list-ordered-item-terminator 41)
| [snip]
`----

Here's the backtrace:

,----
| Debugger entered--Lisp error: (error "Cannot return from the debugger in an error")
|   looking-at("\\([ 	]*\\([-+]\\|\\([0-9]+))\\)\\|[ 	]+\\*\\)\\( \\|$\\)")
|   org-at-item-p()
|   org-metaright(nil)
|   call-interactively(org-metaright nil nil)
`----

And here are my other plain list settings:

--8<---------------cut here---------------start------------->8---
(setq org-blank-before-new-entry '((heading . auto) (plain-list-item . auto)))
(setq org-empty-line-terminates-plain-lists nil)
(setq org-cycle-include-plain-lists nil)
--8<---------------cut here---------------end--------------->8---

Thanks,
Matt

Re: Bug: org-plain-list-ordered-item-terminator

[Samuel Wales]

I do not know, but I do have an idea for making it less necessary to
do.  If a plain list is not recognized unless it is indented, then
erroneous interpretation of column 0 numbers will not happen.  Of
course, they would still happen with text that is indented by
whitespace.

Re: Bug: org-plain-list-ordered-item-terminator

[Carsten Dominik]

Fixed.

However, bullet cycling also seems to have bugs when this
variable is not equal to t.

Why do you need to change the variable?

- Carsten

On Apr 26, 2009, at 3:39 AM, Matthew Lundin wrote:

> When I set org-plain-list-ordered-item-terminator to 'paren like in
> "2)"' in the customize interface, I no longer able to use plain  
> lists in
> org-mode, but instead get the following error:
>
> ,----
> | org-at-item-p: Invalid regexp: "Unmatched ( or \\("
> `----
>
> In my custom settings, the setting looks like this:
>
> ,----
> | [snip]
> | '(org-plain-list-ordered-item-terminator 41)
> | [snip]
> `----
>
> Here's the backtrace:
>
> ,----
> | Debugger entered--Lisp error: (error "Cannot return from the  
> debugger in an error")
> |   looking-at("\\([ 	]*\\([-+]\\|\\([0-9]+))\\)\\|[ 	]+\\*\\)\\( \\| 
> $\\)")
> |   org-at-item-p()
> |   org-metaright(nil)
> |   call-interactively(org-metaright nil nil)
> `----
>
> And here are my other plain list settings:
>
> --8<---------------cut here---------------start------------->8---
> (setq org-blank-before-new-entry '((heading . auto) (plain-list- 
> item . auto)))
> (setq org-empty-line-terminates-plain-lists nil)
> (setq org-cycle-include-plain-lists nil)
> --8<---------------cut here---------------end--------------->8---
>
> Thanks,
> Matt
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Bug: org-plain-list-ordered-item-terminator

[Matthew Lundin]

Hi Carsten,

Carsten Dominik <carsten.dominik@gmail.com> writes:

> Fixed.
>
> However, bullet cycling also seems to have bugs when this
> variable is not equal to t.
>
> Why do you need to change the variable?

Again, sorry for the late reply. Just for the record, I need to change
this variable for to avoid lines starting with a number/period
combination being exported as enumerated lists.

This often happens when I'm citing someting in a footnote. E.g.,

--8<---------------cut here---------------start------------->8---
[1] Author, /A Very Long Book Title that Stretches to the Line's End/, p. 
101.
--8<---------------cut here---------------end--------------->8---

The "101." above gets exported as item 1 in an ordered list if I don't
set the variable.

Best,

Matt