nano-devel
[Top][All Lists]
Advanced

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

[Nano-devel] nano 2.0.5pre1 is out


From: David Ramsey
Subject: [Nano-devel] nano 2.0.5pre1 is out
Date: Wed, 18 Apr 2007 16:33:19 -0400

It's available here:

http://www.nano-editor.org/dist/test/nano-2.0.5pre1.tar.gz

I've found some rather severe bugs in nano lately, and this should
address them all.  Specifically:

* saving in a directory starting with a tilde that isn't a user's home
directory will segfault if that directory's name isn't contained in some
user's home directory (this was apparently broken sometime during 1.3.x)

* saving in a directory starting with a tilde that isn't a user's home
directory will save in the wrong home directory if that directory's name
is contained in some user's home directory; for example, saving in "~d"
will save it in the first user entry beginning with "d", which is
"daemon" on my system (this is also in the 1.2.x branch, but better
hidden as it doesn't tell you where it's trying to save the file if
there's an error)

Note that these first two bugs were first mentioned here:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=419353

* "include" directives in nanorc files weren't properly checked to see
if the user was trying to open a directory or a block device (this is a
cut-and-paste error from the code in do_rcfile())

* files that are opened aren't tilde-expanded, so nano will think you
have a new file if you specify "~user/file.txt" on the command line
(with the quotes around it)

* a few more problems with warning the user if a file to be saved is
going to overwrite another, or if its name is going to be changed; most
notably, saving a file with no name over an existing file name will not
produce a warning, and saving in a directory starting with a tilde that
isn't the user's home directory (when the name to be saved under is
different from that of the original file) will not produce a warning

* the Cancel key is now properly handled; this is so that if you run
Putty with TERM set to "putty", Ctrl-C is interpreted properly (since
the terminfo file for "putty" marks Ctrl-C as the equivalent of the
Cancel key)

All these fixes have been applied to the 2.1 branch as well.

I would like to get these fixes out in a release very soon, so please
test, especially with tilde notation and overwriting/renaming files if
you can.

Thanks in advance.


reply via email to

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