Re: [Nano-devel] [Request] allow deleting a marked region without affecting the cutbuffer

[Benno Schulenberg]

Op 11-10-18 om 11:37 schreef Brand Huntsman:
> On Thu, 11 Oct 2018 11:02:27 +0200 Benno Schulenberg <address@hidden>
> wrote:
>> That second cut function (that removes something without affecting the
>> cutbuffer) should be made first -- <Del> and <Bsp> will want to use it when
>> something is marked.
> 
> I thought you said Bsp wouldn't delete regions, should it?

When <Del> deletes a region, then <Bsp> should delete it too, just like in
other editors where <Del> deletes a region.

>> Or rather: when something is soft marked (shift-selected).  Maybe we can get
>> away without an extra option: Pico doesn't know Shift-selection, so people
>> who are used to Pico will set the mark before making a selection, and in
>> that case <Del> and <Bsp> should continue to delete single characters. But
>> when something is shift-selected... they could delete the selection.
> 
> I use a mixture of mark and shift selections, because marking is easier when
> selecting more than a couple lines. Could there be an option to allow marked
> regions to use it?

No.  Either the difference between hard and soft marking causes the behavior
change, or there is an option that causes the behavior change.  Not a mixture
of both.

> The attached patches implement the nuke function and <Del> nuking selections.
> It doesn't check for mark vs shift in <Del>. Nuke is the only name I could
> come up with for the function, if anyone has a better name...

"wipe", "blot", "erase".

> do_nuke_text() could be merged into do_cut_text() but they only share a few
> lines and merging would require a fourth boolean. Should it be merged?

More than ten lines in common...  Yes, it should.

Benno

signature.asc
Description: OpenPGP digital signature