Date: prev next · Thread: first prev next last
August 2016 Archives by date, by thread · List index


https://bugs.documentfoundation.org/show_bug.cgi?id=100777

--- Comment #14 from Cor Nouws <cno@nouenoff.nl> ---
(In reply to Heiko Tietze from comment #13)

Not the best argument as both approaches have the same behavior after the
first action. 

It's convincing for me ;)

I believe the consideration was what happens when the cursor
is placed only a few characters away from the paragraph beginning. 

yeah.. then it's odd. tweak the algorithm and add an expert config to set the
number of characters :D

Word and
all other text editors jump one character to the left, LibO the full
previous paragraph. Inconsistency is bad.

I can't understand why a different behavior with different key combination is
inconsistency.

I started a survey on G+
https://plus.google.com/u/0/107566594492891737454/posts/5hy7FY5Pe83 (and so
far surprisingly many people expect the LibO behavior).

Thanks - not sure if the sole expectation is the best ground for a discussion
on the best behavior, but after all, when I'm honest: a single up/down more or
less can't bother me (the ctrl-key is pressed ~continuously anyway  ;) )

(So I'll rest may case. Unless of course others call me to support their view.)

(Sorry Hieko, not intending to nag you, but sometimes these things happen ;) )

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.