Bug Hunting Session
Bug 53023 - AutoText (text only) embeds extra carriage return
Summary: AutoText (text only) embeds extra carriage return
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: difficultyBeginner
: 63740 77482 (view as bug list)
Depends on:
Blocks: AutoText
  Show dependency treegraph
 
Reported: 2012-08-01 01:40 UTC by Jay Valatka
Modified: 2019-07-05 21:39 UTC (History)
9 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jay Valatka 2012-08-01 01:40:06 UTC
Creating user shortcuts with AutoText seems to append a carriage return to the end of the text saved.  Removing the extra carriage return from the item through direct editing and saving it will not remove the carriage return; it just reappears upon save.

1. First create a new category or just use "My AutoText" with Edit | AutoText... | Categories...
2. Inside a document, type in a few words, like "ready to close year" _without adding a carriage return_.  Highlight the words and do a Ctrl-C (copy to clipboard).
3. Go back to Edit | AutoText... and enter a Name and Shortcut.  Click on AutoText drop-down button and select "New (text only)".

If you select "New" instead of "New (text only)", you may not see this problem.

4. Go back to document to try the shortcut you've just created.
Comment 1 Jean-Baptiste Faure 2012-09-02 08:32:31 UTC
Old bug, already there in OOo 2 : https://issues.apache.org/ooo/show_bug.cgi?id=79861
Set version accordingly : 3.3.0

Best regards. JBF
Comment 2 Joel Madero 2014-05-16 20:09:46 UTC
*** Bug 77482 has been marked as a duplicate of this bug. ***
Comment 3 a07cd040897db54e103c 2014-05-19 06:27:01 UTC
*** Bug 63740 has been marked as a duplicate of this bug. ***
Comment 4 Joel Madero 2014-05-20 05:12:08 UTC
In the future please do not add bugs to most annoying bug list without knowing what belongs on there - I am removing it from the list.

Note that other bugs on MAB list are mostly crashers, hangers, or if not, are bugs that are going to affect a large portion of our users. This bug has 4 total comments over almost 2 year period - it's really not affecting many users.

Please do not add it back to the list - it won't make it get fixed faster, it'll just make the MAB list less useful because bugs that don't belong on there will be sitting on the list.
Comment 5 a07cd040897db54e103c 2014-05-20 07:23:06 UTC
(In reply to comment #4)
> This bug has
> 4 total comments over almost 2 year period - it's really not affecting many
> users.

Did you also have a look at the "See also" section?

At least two duplicates of this bug exist (bug 63740 and bug 77482) which in total add 17 more comments. *Yourself* commented there and even marked 77482 as a duplicate of this. So dont't complain about too less users affected and comments in this certain report.

The apache bugtracker for AOO adds 11 further comments to this issue.

So we are talking about 33 comments in total about a bug that at least exists since 2007-07-21 in AOO and was taken over to LO.

> Note that other bugs on MAB list are mostly crashers, hangers, or if not,
> are bugs that are going to affect a large portion of our users

The fact, that at least two further users felt it would be worth writing a report and 33 comments about the reports make me feel believe that "large portion of our users" *are* affected. 

Furthermore i believe that a bug

  - that makes a function unusable in some cases (single phrases without formatting) 
  - that is known of for nearly *seven* years now
  - that is reported many times
  - that is easily reproducible
  - that seems easy to fix

definitely *is* "most annoying".

> Please do not add it back to the list

I won't, but your arguments are wrong.
Comment 6 QA Administrators 2015-06-08 14:41:28 UTC Comment hidden (obsolete)
Comment 7 Laurent BP 2015-06-08 16:52:09 UTC
Confirmed on Win 7 with Version: 4.4.4.1.0+
Build ID: 24c5f9979e61fde7b098af60756a4890e5713390
Locale : fr_FR
Comment 9 royerjy 2016-08-08 16:02:25 UTC
Always in LO 2.0.4. Is it so complicated to correct this bug ?
Comment 10 a07cd040897db54e103c 2016-08-10 15:30:02 UTC
just retestet with 

Version: 5.1.4.2 (x64)
Build-ID: f99d75f39f1c57ebdd7ffc5f42867c12031db97a
CPU-Threads: 2; BS-Version: Windows 6.1; UI-Render: Standard; 
Gebietsschema: de-DE (de_DE)

and the problem still exists
Comment 11 Eduardo Sanchez 2016-10-08 14:31:29 UTC
Confirmed in 5.2.1.2 under Gnu/Linux.

Please fix. The bug is extremely annoying and it's making me lose valuable time, focus, and keystrokes. Thanks!
Comment 12 Laurent BP 2017-01-22 11:20:45 UTC
An easy workaround is to use autocorrection instead of autotext
Comment 13 QA Administrators 2018-08-18 02:39:07 UTC Comment hidden (obsolete)
Comment 14 Jean-Baptiste Faure 2018-08-18 07:20:15 UTC
Still reproducible with LO 6.1.1.0.0+ built at home under Ubuntu 18.04 x86-64.

Best regards. JBF
Comment 15 Justus 2019-07-05 21:39:17 UTC
Still annoying and reproducible on Arch-Linux with LO:

- Version: 6.2.4.2.0+
- Build-ID: 6.2.4-1

Best regards
Justus