When using automatically closed parentheses for formulas in LO Calc, if I'm typing some formula, add the parenthesis (or get it added through the autocomplete), and immediately delete one of them (either the opening or the closing one), the other part of the parentheses is not deleted like it happens it pretty much every single IDE and programming-oriented text editor. Steps to reproduce: -Activate autoclose parenthesis and code completion (Tools -> Options -> Basic IDE -> tick "Enable code completion" and "Autoclose parenthesis"). -Start writing some formula in some cell, get it autocompleted. -From the same pointing position from which it was autocompleted, delete a parenthesis. Expected behavior: -The other parenthesis that was added automatically should also be deleted. Actual behavior: -The other parenthesis is still there after the triggering parenthesis is already deleted, even when there was nothing written in between these parentheses. Setup: LO 6.0.5.2 running on Linux (Debian buster/sid).
How can I autocomplete besides hitting Enter?
(In reply to Buovjaga from comment #1) > How can I autocomplete besides hitting Enter? No idea, I was autocompleting by hitting enter.
Aha, I was just confused by "From the same pointing position from which it was autocompleted" thinking that I need to remain in edit mode the whole time. Ok, I confirm and if you say the auto-deleting is standard IDE stuff, I believe you.
Dear david.cortes.rivera, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Comment that the bot asked for: Version: 6.2.5.2 (x64) Build ID: 1ec314fa52f458adc18c4f025c545a4e8b22c159 CPU threads: 8; OS: Windows 10.0; UI render: GL; VCL: win; Locale: en-US (en_US); UI-Language: en-GB Calc: threaded
Dear david.cortes.rivera, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still an issue. Version: 7.0.4.2 Build ID: 00(Build:2) CPU threads: 16; OS: Linux 5.10; UI render: default; VCL: kf5 Locale: en-US (en_US.UTF-8); UI: en-US Debian package version: 1:7.0.4-4 Calc: threaded
I have used a fair number of text editors and IDEs in my time and none of them have done this. When I hit backspace, I expect only the character immediately to the left of the cursor to be deleted, regardless of how it was inserted. I guess I could see adding an option for this, but it's an enhancement, not a bug.
Ah, seems I was naive in 2018 to believe this to be standard behaviour. Let's put this on UX team's table.
(In reply to Michael Warner from comment #8) > I have used a fair number of text editors and IDEs in my time and none of > them have done this. When I hit backspace, I expect only the character > immediately to the left of the cursor to be deleted, regardless of how it > was inserted. > > I guess I could see adding an option for this, but it's an enhancement, not > a bug. A couple counterexamples: sublime text, vscode, dbeaver, rstudio, spyder, jupyter (those are all the editors and IDEs that I use, not sure about others but I assume they'd behave similarly).
(In reply to david.cortes.rivera from comment #0) > Steps to reproduce: > -Activate autoclose parenthesis and code completion (Tools -> Options -> > Basic IDE -> tick "Enable code completion" and "Autoclose parenthesis"). > -Start writing some formula in some cell, get it autocompleted. > -From the same pointing position from which it was autocompleted, delete a > parenthesis. Note: you have to activate experimental features to get into Basic IDE options
I tend to agree with Michael (c8), there might be situations where you want to insert a single parenthesis but it's always duplicated and you cannot delete one. In order to revert the double parenthesis I would run Undo - however, we ignore the automatically inserted character. My take: improve Undo (different topic) and keep the current solution. Another option sounds like overkill but could solve the issue for everyone.