https://bugs.documentfoundation.org/show_bug.cgi?id=64028
--- Comment #8 from William Friedman <[email protected]> --- I opened a duplicate bug report/enhancement request today, more than 10 years after the original request. While it is true that both Google Sheets and Excel evince this behavior, it is also true that users have been trying to work around it for years (re: Excel, see: https://stackoverflow.com/questions/29122940/keeping-the-formatting-of-the-cut-cells-preserved and https://www.reddit.com/r/excel/comments/3dkbk3/how_can_i_cut_and_paste_text_from_a_cell_but_keep/; re: Google Sheets, see: https://www.reddit.com/r/googlesheets/comments/jpf7tv/moving_data_without_losing_formatting_in_columns/). I wish I understood the origins of this behavior in the spreadsheet world. It seems so counter-intuitive to how cut behavior works generally (remove the data, leave the source formatting) that there must be a reason that it was implemented this way the first time. What surprises me is the dismissive reactions to the suggestion that this behavior is undesirable to some users in some (many? most?) use cases, and the apparent lack of interest in providing what appears to be a small customization enhancement. This is all the more surprising given the extensive dialog box offered for deleting a cell. Why should "cut" be treated with absolute uniformity when "delete", a component action of "cut", is extensively customizable? I hope that a developer some day concurs that a customizable cut command would raise Calc's usefulness in the experience of some unknown but non-zero number of spreadsheet users. Thank you in advance to that developer! -- You are receiving this mail because: You are the assignee for the bug.
