Re: [Nano-devel] a segfault when editing a file in stereo

[Benno Schulenberg]

On Thu, Jul 30, 2015, at 00:08, David Niklas wrote:
> It would be helpful to tell us what nano is continuing or not, 
> so as to know when to hit N or ^C.

Yes, this is unclear.  Currently N and ^C do the same
thing: nano skips the file and opens a blank buffer (or
any other specified files).  How would you like nano to
behave for these two responses?

> Also, knowing the version would be useful.

Hm? What do you mean?  When nano says a file is
already being edited, it also specifies which editor
and version is doing that.

Or are you referring to the segfault scenario?  Then
it is about all versions that know about --locking,
but specifically 2.4.1 and 2.4.2.

Benno

-- 
http://www.fastmail.com - A fast, anti-spam email service.