[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nano-devel] how Alt+6 should behave

From: Rishabh Dave
Subject: Re: [Nano-devel] how Alt+6 should behave
Date: Sun, 7 Feb 2016 01:31:49 +0530

Patch is over source nano-2.5.1 with no previous patches done using diff under --recursive and --unified options. I tried --cut and --softwrap, they too run okay. However it isn't complete as screen doesn't scroll if marking goes beyond marking window and downwards and rightwards don't behave as we want. Cursor, on copying, falls back to a line/character below/right of the other end of marking. That is due to underlying data structures, I guess.

On Sat, Jan 30, 2016 at 8:21 PM, Benno Schulenberg <address@hidden> wrote:

  It should just copy the marked portion to the
cutbuffer, unset the mark, and leave the cursor wherever it
was at the moment that Alt+6 was pressed.  Nor should it
scroll the screen in any way.
Any way? It should scroll when marking goes out of screen otherwise how would user know how much he/she has selected? At least it would be inconvenient.

I saw this behaviour for first time: if a couple of line are marked, and if we use backspace, whole block of selected text moves back instead of deleting it. Marked text should be deleted otherwise mark is not useful there. After the applying attached patch, this effect looks literally grotesque as text after mark_begin gets deleted while paint length remains same.

Attachment: mark-end-in-currents-stead.patch
Description: Text Data

reply via email to

[Prev in Thread] Current Thread [Next in Thread]