[Top][All Lists]

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

[Octave-bug-tracker] [bug #57861] GUI editor should save text files with

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #57861] GUI editor should save text files with an implied final newline character
Date: Wed, 19 Feb 2020 15:54:37 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.87 Safari/537.36


                 Summary: GUI editor should save text files with an implied
final newline character
                 Project: GNU Octave
            Submitted by: mtmiller
            Submitted on: Wed 19 Feb 2020 12:54:35 PM PST
                Category: GUI
                Severity: 1 - Wish
                Priority: 5 - Normal
              Item Group: Feature Request
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
                 Release: dev
         Discussion Lock: Any
        Operating System: Any



Unix files are line oriented, and it's expected that every line ends in a
newline character. The last byte of every file should be a newline character.

The GUI editor does not follow this standard, and instead only writes newline
characters when a line is followed by another line.

The standard Unix file behavior can only be achieved currently by pressing an
extra Enter at the end of the file to insert a fake extra line at the end.

The editor should always write a newline at the end of files when saving, or
at the very least offer a setting to choose the behavior, with the default
being the standard to end files with newlines.

This would help new contributors edit and write m-file functions for
submission to Octave, since this is part of our coding style guide.


Reply to this item at:


  Message sent via Savannah

reply via email to

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