Re: [O] (org-table-next-row) and # - bug or feature?

2013-04-05 Thread Bastien
Hi Thorsten,

Thorsten Jolitz tjol...@gmail.com writes:

 The problem is actually in these two lines of 'org-table-insert-row':

 ,-
 | (if (string-match ^[ \t]*| *[#$] *| line)
 |(setq new (replace-match (match-string 0 line) t t new)))
 `-

 looks as if its intentional, but for me this behaviour still seems
 buggy. 

Yes, I don't know why cells with # and $ should be copied when
creating a new row.  I'm copying Carsten so he might explain, or
remove this quirk if needed.

Thanks for reporting this,

-- 
 Bastien



[O] (org-table-next-row) and # - bug or feature?

2013-03-21 Thread Thorsten Jolitz

Hi List, 

is this a bug or a feature:

in all 4 following examples point is in cell 1x1 when calling 

,---
| M-x org-table-next-row
`---

| A | B |
|   |   |

| 1 | 2 |
|   |   |

| \ | / |
|   |   |

but 

| # | b |
| # |   |


For me at least it breaks a program that looks if e.g. cell 1x1 is
empty, and if it isn't, calls 'org-table-next-row' and then inserts in
new empty cell 2x1.

As it happens, # is among the characters my program tries to insert and
thus it enters an endless loop, since everytime it calls
'org-table-next-row', the new cell in the next-row/same-column will be
filled with # too, and never be empty.

I can't think of a situation where this behaviour could be useful. Its
probably a bug related to the use of '#' as 'comment-start' char in
Org-mode. 

-- 
cheers,
Thorsten





Re: [O] (org-table-next-row) and # - bug or feature?

2013-03-21 Thread Thorsten Jolitz
Thorsten Jolitz tjol...@gmail.com writes:

[following up to my own post]

 in all 4 following examples point is in cell 1x1 when calling 

 ,---
 | M-x org-table-next-row
 `---

 | A | B |
 |   |   |

 | 1 | 2 |
 |   |   |

 | \ | / |
 |   |   |

 but 

 | # | b |
 | # |   |


The problem is actually in these two lines of 'org-table-insert-row':

,-
| (if (string-match ^[ \t]*| *[#$] *| line)
|(setq new (replace-match (match-string 0 line) t t new)))
`-

looks as if its intentional, but for me this behaviour still seems
buggy. 

-- 
cheers,
Thorsten