BUG REPORT: SQL Editor selects too much text after you hit return and select "one line"

From: k mac <kmac(at)loxcel(dot)com>
To: pgadmin-support(at)postgresql(dot)org
Subject: BUG REPORT: SQL Editor selects too much text after you hit return and select "one line"
Date: 2014-06-12 13:31:19
Message-ID: CAOXNhtsgRQbbptV43adekUwm7wCjafPFop_HYnVXT1J_OG13qw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

PRODUCT: pgADMIN SQL Editor

VERSION: pgADMIN version 1.18.1 (Apr 9 2014, rev: REL-1_18_1)

ISSUE: Editor selects too much text after you hit return and select "one
line".

The following example illustrates the issue:

cursor-1.png shows three lines of text in SQL Editor, with the cursor
positioned in the middle of the 1st line:

[image: Inline image 1]

cursor-2.png shows the effect of pressing the Enter / Return key:

[image: Inline image 2]

Up to this point, everything is as expected.

cursor-3.png shows the anomaly: after pressing Enter / Return, I then held
"Shift" while pressing "cursor down" ONCE, to select the second line of
text "efg". However, two lines of text were selected: "efg" and the first
four characters from line 3. I know of no other application that behaves
this way.

[image: Inline image 3]

cursor-4.png shows what I expected to have happened after pressing "Shift"
+ "cursor down" ONCE:

[image: Inline image 4]

Would you be able to make text selection behave as shown in cursor-4.png?

--
Thank you

*Kevin Macdonald*
Partner | Loxcel Geomatics
Tel: 416.904.0370
www.loxcel.com

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Oliver 2014-06-17 09:51:41 Best backup strategy for production systems
Previous Message Dave Page 2014-06-12 06:58:11 Re: PATCH: Search Objects by definitions and comments