From: | "J(dot)F(dot) Oster" <jinfroster(at)mail(dot)ru> |
---|---|
To: | Sanket Mehta <sanket(dot)mehta(at)enterprisedb(dot)com> |
Cc: | Dave Page <dpage(at)pgadmin(dot)org>, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>, Ashesh Vashi <ashesh(dot)vashi(at)enterprisedb(dot)com> |
Subject: | Re: PATCH: Clear undo/redo history when a file is opened in Query editor |
Date: | 2014-10-28 16:08:48 |
Message-ID: | 16910200208.20141028190848@mail.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Hello Sanket,
SM> As per my understanding below is the bug scenario.
Yes,
- open any file in sql editor..
- perform some modifications to file so that Undo is possible.
- now open a second file in same editor and try Undo. It will show
you previous file content again.═
- do Save.
Now contents of the second file is replaced on disk with contents of
the previous file.
SM> On Mon, Oct 27, 2014 at 4:14 PM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
SM> Ashesh, can you review/commit this please?
SM> On Fri, Oct 24, 2014 at 8:35 PM, J.F. Oster <jinfroster(at)mail(dot)ru> wrote:
>> Hello!
>>
>> A user may occasionaly assign content of a previously edited file into
>> a next file opened in the same Query window, by calling Undo and Save.
>>
>> Simple non-MDI text editors (for example, notepad.exe) prevent an
>> issue by clearing undo/redo history, so should we do.
>> Please see the attached patch.
>>
--
Best regards,
J.F.
From | Date | Subject | |
---|---|---|---|
Next Message | J.F. Oster | 2014-10-28 16:28:13 | Re: pgAdmin III commit: Beautify the query shown in the SQL pane for the fu |
Previous Message | inspector morse | 2014-10-28 15:54:02 | Re: PATCH: Stored procedure large parameter list |