|Subject:||Re: [Nano-devel] how Alt+6 should behave|
|Date:||Fri, 5 Feb 2016 16:53:37 +0530|
> About progress in patch,
> I achieved the effect - cursor doesn't move while selecting and copying
> text - for all movements while selecting text i.e. up, down, left and
> right. However, they are little unstable.
What do you mean with unstable? That it crashes now and then?
On Thu, Feb 4, 2016, at 18:55, Rishabh Dave wrote:
> Code in patch I sent -
> +> if.(!copy_text)
> +> ....openfile->current.=.openfile->filebot;
> Code in patch you sent -
> +> openfile->current.=.openfile->filebot;
> Could you please point me to the mistake
You see, you have a tab (represented by a >) before the if,
and I have four spaces. And before the openfile you have
a tab plus four spaces, and I just a tab. Nano's code
assumes a tab size of eight (yes, sorry, but that's how it
is). So your fragment is indented too much by four positions.
> Also highlighting text while
> selecting the effect is remaining (I have figured where is that under our
> source code) and --cut and --wrap are unstable; it will take some time. I
> wanted to send a patch to confirm things are what we want but I keep
> repeating that whitespace-mistake.
Well, for just judging whether the behaviour is the intended one,
the whitespace doesn't matter. But you wanted me to comment
|[Prev in Thread]||Current Thread||[Next in Thread]|