Bug: org-table-wrap-region incorrectly places the wrapped region [9.4 (9.4-elpaplus @ /home/marko/.emacs.d/elpa/org-plus-contrib-20200914/)]

Bug: org-table-wrap-region incorrectly places the wrapped region [9.4 (9.4-elpaplus @ /home/marko/.emacs.d/elpa/org-plus-contrib-20200914/)]

[Marko Schuetz-Schmuck]

[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]

Emacs  : GNU Emacs 27.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.22, cairo version 1.17.3)
 of 2020-08-28
Package: Org mode version 9.4 (9.4-elpaplus @ /home/marko/.emacs.d/elpa/org-plus-contrib-20200914/)

I'm using multi-line fields in org tables. When I wrap such a field
there are unexpected results:

Marking the region from the 'I' of "Includes" to the space just left of
the right bottom column border and calling org-table-wrap-region

| Includes all aspects of    |
| information about          |
| proposed project.          |

wraps correctly to

| Includes all aspects |
| of information about |
| proposed project.    |

But when I mark the same region in this table

|----------------------------|
| Includes all aspects of    |
| information about          |
| proposed project.          |

it results in an error message "Not in table data field".

Initially I observed such unexpected behaviors with more complex
situations where the field was in a column further to the right. But it
seems it's the same problem.

Best regards,

Marko

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 224 bytes --]

Re: Bug: org-table-wrap-region incorrectly places the wrapped region [9.4 (9.4-elpaplus @ /home/marko/.emacs.d/elpa/org-plus-contrib-20200914/)]

[Jeremie Juste]

Hello Marko,

Thanks for reporting. Unexpected behavior of (org-table-wrap-region)
confirmed.

works fine with 
> | Includes all aspects of    |
> | information about          |
> | proposed project.          |


Error: user-error: Not in table data field
with header line
> |----------------------------|
> | Includes all aspects of    |
> | information about          |
> | proposed project.          |

Best regards
Jeremie

Org mode version 9.4
GNU Emacs 28.0.50 



Marko Schuetz-Schmuck <marko.schutz@upr.edu> writes:

> Emacs  : GNU Emacs 27.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.22, cairo version 1.17.3)
>  of 2020-08-28
> Package: Org mode version 9.4 (9.4-elpaplus @ /home/marko/.emacs.d/elpa/org-plus-contrib-20200914/)
>
> I'm using multi-line fields in org tables. When I wrap such a field
> there are unexpected results:
>
> Marking the region from the 'I' of "Includes" to the space just left of
> the right bottom column border and calling org-table-wrap-region
>
> | Includes all aspects of    |
> | information about          |
> | proposed project.          |
>
> wraps correctly to
>
> | Includes all aspects |
> | of information about |
> | proposed project.    |
>
> But when I mark the same region in this table
>
> |----------------------------|
> | Includes all aspects of    |
> | information about          |
> | proposed project.          |
>
> it results in an error message "Not in table data field".
>
> Initially I observed such unexpected behaviors with more complex
> situations where the field was in a column further to the right. But it
> seems it's the same problem.
>
> Best regards,
>
> Marko

Re: Bug: org-table-wrap-region incorrectly places the wrapped region [9.4 (9.4-elpaplus @ /home/marko/.emacs.d/elpa/org-plus-contrib-20200914/)]

[Bastien]

Hi Marko,

Marko Schuetz-Schmuck <marko.schutz@upr.edu> writes:

> Marking the region from the 'I' of "Includes" to the space just left of
> the right bottom column border and calling org-table-wrap-region
>
> | Includes all aspects of    |
> | information about          |
> | proposed project.          |
>
> wraps correctly to
>
> | Includes all aspects |
> | of information about |
> | proposed project.    |
>
> But when I mark the same region in this table
>
> |----------------------------|
> | Includes all aspects of    |
> | information about          |
> | proposed project.          |
>
> it results in an error message "Not in table data field".

Fixed in maint with commit eedbe286e, thanks again for reporting this.

-- 
 Bastien