Suppose I have some autotext entry with a certain shortcut (e.g. ---). If I type in that shortcut and press F3, it should be replaced with the autotext entry (well, that and the gratuitous newline, see bug 53023). However, if, before the shortcut, I have a parenthesis character rather than a space (or nothing), - F3 will not be match my shortcut and I'll get an error message.
I can't confirm it with Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 51fb84829afbc1c0957fd1a489085613ad199f1a CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL Example:(DT + F3 inserts dummy text behind parenthesis
(In reply to Dieter from comment #1) > Example:(DT + F3 inserts dummy text behind parenthesis Try it with a shortcut of three minus signs please.
I confirm it with shortcut "---" So it's not a general problem with shortcuts but with special one (Assumption: If you combine letters and non-letters LO will ony trest letters as shortcut. If you combine non-letters LO will treat all characters as a shortsut). Version: 7.3.2.1 (x64) / LibreOffice Community Build ID: 0b2e59a88b7e225b655db87910f97dca7aef27aa CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL
Just adding some motivation: I use some non-letter shortcuts to insert characters without keyboard keys, e.g. --- for em-dash, -> for right-arrow etc. This could theoretically be achieved with autocorrect, but one might want fine-grained control, or otherwise need to avoid autocorrect.
I understand the use case, but I also think, that autocorrect is the more appropriate solution.
Confirmed that AutoText will use the closest string of non-space characters that's only composed of either alphanumeric characters _or_ special characters. Note that using Ctrl + Shift + Left arrow will also select the full ")---". OOo 3.3 would also catch the full ")---", so marking as inherited. Mike, after your work on bug 126589, what are your thoughts? Deciding what constitute a boundary or not in a series of non-alphanum will always be debatable[1], so the only way out as I understand it is to: (a) keep adding characters to the string and checking if it matches a shortcut until it does or it reaches a space or alphanum character. Sounds like a pretty bad hack, but could work? Alternatively: (b) Stop accepting some boundary characters in new shortcuts (which ones? and would break existing shortcuts, so not workable.) (c) Won't fix. [1] What happens if I want my shortcut to be ")))" ? It's currently accepted in the shortcut field.
Dear Eyal Rozenberg, 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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Bug still manifests with: Version: 26.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: bc58a54d513702bc07906627dce073f05d7978fd CPU threads: 4; OS: Linux 6.12; UI render: default; VCL: gtk3 Locale: en-IL (en_IL); UI: en-US