<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Writer Table Split Merged Cell - Enhancement request "Undo merge"" href="https://bugs.documentfoundation.org/show_bug.cgi?id=101123#c16">Comment # 16</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Writer Table Split Merged Cell - Enhancement request "Undo merge"" href="https://bugs.documentfoundation.org/show_bug.cgi?id=101123">bug 101123</a> from <a class="email" href="mailto:Heinrich.Hartl@email.de" title="Heinrich Hartl <Heinrich.Hartl@email.de>"> Heinrich Hartl</a> <pre>Hallo Heiko, I could imagine that "unmerge" is invoked with either cells selected (may be entire table or a single eventually merged cell or whatever subset of the table) or with the cursor in a cell. That case should be treated same as if that cell was selected. The command given by "unmerge" then would be to recreate i.e. make visible all the covered cells in the selected domain. There is no ambiguity. In all the examples I dissected columns were never deleted by merge. So I can answer why not 20 cells - there are 6 columns! Even if columns were deleted above definition of the command semantic is clear. Recreate an eventually lost entire (empty) column can be done by insert column analogous to insert row. So it is not about undoing respective recreating what may have existed before but to make visible the row/column structure and make sure that in some selected range there is no merged cell nor a covered cell thus re-exposing all parts to standard editing. To raise a valid argument about what might be possible or not I suggest to raise it with an example. Dissecting may in many cases provide a clear answer!</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>