Re: [Nano-devel] what is --nofollow good for?

[Mike Frysinger]

On 28 Jan 2016 10:01, Benno Schulenberg wrote:
> On Wed, Jan 27, 2016, at 21:23, Chris Allegretta wrote:
> > Someone was complaining about the behavior changing, so I'd added that
> > feature.  If it's really been broken that long then by all means, it
> > should go.
> > 
> > On Wed, Jan 27, 2016 at 3:17 PM, Benno Schulenberg
> > <address@hidden> wrote:
> > > This hasn't been working for a long time: it didn't work in 2.2.6,
> > > not in 2.2.2, not in 2.1.5, not in 2.0.9,  not in 1.0.5, and not
> > > in 1.0.1 either.
> 
> Eeeww.  I tested wrong -- I ran nano instead of ./nano.  :|
> 
> It did work in 1.0.1 and 1.0.5, and probably still a bit later.
> But it definitely stopped working in 1.3.1 (January 2004).
> I haven't tested further back -- in versions before 2.0.8
> src/files.c has to be fixed before it will compile.
> 
> So this hasn't been working for at least twelve years.
> (And why should it?  If they want the symlink gone, they
> can simply delete it beforehand.  Why should nano do the
> work for them?)  I will remove -l, --nofollow.

because when you try to edit files in dirs that others have access to,
you want to make sure a save operation does not get redirected to a
place you did not intend.  simply saying "if there's a symlink, you
should delete it first" doesn't help.
-mike

signature.asc
Description: Digital signature