Problem with Nano 1.3.12

Problem with Nano 1.3.12

[John J. Boyer]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown-8bit, Size: 534 bytes --]

My new Redhat Entrrprise System has nano 1.3.12. When I do a search and
replace instead of moving the cursor to the text to be replaced, as
older versions   of nano did, it is apparently highlighting it. I've
read the man page, but I can't find out how to restore the previous mode
of operation. Is this possible? If not, can I get a previous version.

Thanks,
John

-- 
John J. boyer; President, Chief Software Developer
JJB Software, Inc.
http://www.jjb-software.com
Madison, WI USA
Developing software for people with disabilities

Re: Problem with Nano 1.3.12

[Geoff Shang]

Hi,

I've never seen Nano 1.3.12.  Under Debian Etch I have Nano 2.0.2 and I 
think it behaves like yours does (though I've not really tested it). 
There's nothing in /etc/nanorc that would seem to allow you to change this 
behaviour, as far as I can see.

Geoff.

Re: Problem with Nano 1.3.12

[Tony Baechler]

Hi,

What if you make a symlink called pico?  This is supposed to restore 
previous Pico behavior but I'm not sure what that means.

Geoff Shang wrote:
> I've never seen Nano 1.3.12.  Under Debian Etch I have Nano 2.0.2 and 
> I think it behaves like yours does (though I've not really tested it). 
> There's nothing in /etc/nanorc that would seem to allow you to change 
> this behaviour, as far as I can see.
>
> Geoff.
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>

Re: Problem with Nano 1.3.12

[Geoff Shang]

Tony Baechler wrote:

> What if you make a symlink called pico?  This is supposed to restore previous 
> Pico behavior but I'm not sure what that means.

Presumably some differences between default Nano behaviour and how pico 
behaves are reverted.

But as far as the cursor movement for replace is concerned, this makes no 
difference as the real Pico seems not to have search and replace (even 
though it seems to be available in the Pine message composer).

Geoff.