Re: [Nano-devel] DOS/Mac text conversion

[Dwayne Rightler]

Yuck... At first glance I thought the patch would be easy, now that you
mention multiple buffers I realized that all the buffers share the writing
format...  that could get hairy.  You'd have to have the write format for
each buffer stored in a structure somewhere.  I don't even want to think
about how much code that would touch.

-Dwayne

Chris Allegretta said:
> On Fri, Oct 01, 2004 at 11:34:30AM -0400, Bill Soudan wrote:
>> On Fri, 2004-10-01 at 11:02, Dwayne Rightler wrote:
>> > I don't know what shell you use, but for bash you could always do
>> > something like:
>> >
>> > alias nano-dos='nano -D'
>> >
>> > That would solve your problem as long as you could remember to use the
>> > nano-dos command instead of nano when editing win32 text files.
>>
>> heh, that's irritating, and yes I will forget.  Why not just fix the
>> editor so that it does what I know I expect as a user:  save the text
>> file in the same format it was read in from?  As a reference, vi and
>> emacs do this.
>
> Yes.  However, last time I used it (which is now a LONG time ago), Pico
> did not do this.  It saves all files as Unix format by default, and I
> don't believe there's any option to change how it is saved.  Has any
> used Pico recently who would know if this is still the case?
>
> Since we're already doing this better, it just becomes a question of
> whether we save in the file's format by default (and hence not need
> --noconvert).  I'm fine with that, what do you think DLR?  How do we
> handle multiple file buffers?  Yuck, I cant think about this right now
> :)
>
> Chris A
> --
> Chris Allegretta      http://www.asty.org
>
> v1sw7CUPhw5ln6pr5ck4ma7u7LSIw0m5g/l7DRa27s5MRr3e6t5NLMb6TDp3en7g6M
> hackerkey.com
> _______________________________________________
> Nano-devel mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/nano-devel
>