nano-devel
[Top][All Lists]
Advanced

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

Re: [Nano-devel] RFC: nano's justifications are poorer than those of Pic


From: Benno Schulenberg
Subject: Re: [Nano-devel] RFC: nano's justifications are poorer than those of Pico -- okay to improve?
Date: Sat, 19 May 2018 18:03:17 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0

Op 18-05-18 om 20:28 schreef David Ramsey:
> Benno Schulenberg:
>> 1) I think nano should recognize indented paragraphs also when
>> --autoindent is not given.  Okay to change?
>>
>> 2) Nano should do the same as Pico in this case: the indentation of a
>> paragraph may not change after its second line.  Okay to change?
>>
>> 3) I think nano should be improved to treat paragraphs like ne does.
>> Okay to change?
> 
> All three of these sound good to me.  Justification should work the same
> regardless of autoindent, Pico compatibility is definitely a priority,
> and justification is handy enough (under the right circumstances) that
> it should be smarter.

Thanks for responding, and confirming.

Meanwhile I understand why nano behaves the way it does under 2).  When
one has a paragraph like this:

        xx xx xx xx
    222 222 222 222
    xxxx xxxx.

and one moves to the first line and inserts some word, automatic
hard-wrapping will cause it (when autoindent is on) to look like:

        xx xx xx new
        xx
    222 222 222 222
    xxxx xxxx.

When hitting Justify, one wants it to be rewrapped like this:

        xx xx xx new
    xx 222 222 222
    222 xxxx xxxx.

But with the new rule of "no indent change after the second line"
that won't happen.  What seems to be needed, when autoindent and
automatic hard-wrapping are on (the latter won't be on when writing
code, only for prose), is that an automatic spillover from a line
should not get the indentation of the current line but of the next
line.  Then, after the insertion of "new", the text would look like:

        xx xx xx new
    xx
    222 222 222 222
    xxxx xxxx.

And ^J would correctly reformat it to the expected arrangement.

Benno

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

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