Branches
Comments
[»]
ty
by Echtor2oo3 - Apr 6th 2007 09:12:57
Nice thanks.. i love it :)
--
(°v°)
[reply]
[top]
[»]
excellent performance on very large files
by csaveanu - Mar 13th 2007 15:33:05
Congratulations for the nano developers! A long time nano user for small
tasks, I discovered today the syntax highlighting abilities and all the
features that can be activated with the .nanorc file. This is simply
amazing. Nano also saved my day when it allowed me to edit a very large
text file that neither SciTE (an excellent editor by itself, that I use
for writing code since it does auto-complete in a very useful way) nor
powerful vim (in the user-friendly Cream incarnation) wanted to handle
gracefully.
Having auto-completion would push nano at the top of the text editors list
for me. It is almost there with all the features and its no-nonsense
interface. Thank you very much.
Cosmin
[reply]
[top]
[»]
Replace Capability Question
by StarDragonII - Apr 6th 2005 17:41:42
Hello,
Just wondering is there capability to do replacements with special
characters such as newlines, and EOF? Kinda like doing s/^/ / in vi.
[reply]
[top]
[»]
Scroll with cursor still broken
by shancock - Nov 27th 2004 14:07:21
The bug: - When at the very bottom of the edit window, do_wrap goes berserk
and
puts the cursor somewhere bad; subsequent keystrokes crash the
program
(14) [FIXED, mostly]
is still present for me and is a show stopper. This problem makes the
editor unusable. While it does not crash for me, the screen is so jumbled
that one has to exit and start over being careful to use only page up and
down untill reaching the point of edit, then resume with page up and down.
Big pain. Sometimes even page up and down foul the screen.
This is present in both the stable and development versions. It occurs on
all my linux boxes - Fedora Core 2 and 3, SuSE 9.1 and 9.2 and SLES 9.
[reply]
[top]
[»]
Re: Scroll with cursor still broken
by Chris Allegretta - Nov 27th 2004 15:18:29
> The bug: - When at the very bottom of
> the edit window, do_wrap goes berserk
> and
> puts the cursor somewhere bad;
> subsequent keystrokes crash the program
> (14) [FIXED, mostly]
>
> is still present for me and is a show
> stopper. This problem makes the editor
> unusable. While it does not crash for
> me, the screen is so jumbled that one
> has to exit and start over being careful
> to use only page up and down untill
> reaching the point of edit, then resume
> with page up and down. Big pain.
> Sometimes even page up and down foul the
> screen.
>
> This is present in both the stable and
> development versions. It occurs on all
> my linux boxes - Fedora Core 2 and 3,
> SuSE 9.1 and 9.2 and SLES 9.
Please consider emailing the development team about this, or filing a bug
report. The Savannah page for nano is at
http://savannah.gnu.org/projects/nano.
[reply]
[top]
[»]
cut'n'paste
by spiritlover - Nov 1st 2002 01:17:56
I can't paste into nano, tho I can with pico.
Any solution available, and/or has anyone else
had this same problem?
thanks
[reply]
[top]
[»]
Re: cut'n'paste
by Chris Allegretta - Nov 1st 2002 16:26:53
> I can't paste into nano, tho I can with
> pico.
> Any solution available, and/or has
> anyone else
> had this same problem?
> thanks
Hello,
I'm assuming you mean paste from X window? nano should not be interfering
with your normal X mouse actions...I'm curious, what version of nano are
you using, and with what distribuion of Linux/*BSD/WIndows/etc? Also,
what terminal program are you running nano in? Thanks much.
[reply]
[top]
[»]
Re: cut'n'paste
by spiritlover - Nov 21st 2002 16:20:32
>
> % I can't paste into nano, tho I can
> with % % pico.
> I'm assuming you mean paste from X
> window? nano should not be interfering
> with your normal X mouse actions...I'm
> curious, what version of nano are you
> using, and with what distribuion of
> Linux/*BSD/WIndows/etc? Also, what
> terminal program are you running nano
> in? Thanks much.
Yeah...it's rather weird, apparently it's only in certain contexts.
Cuz I have had the problem go either way...I'm rather confused, cuz this
time I tried it and nano would do it but not pico. But last time it was
the other way 'round.
It's GNU nano version 1.0.0 (compiled 23:01:44, Oct 27 2002)
Compiled options:
on a slackware 8.1 system. Which actually has multiple other problems but
none of them have to do with terminals or text-editors. ;)
I usually use eterm or aterm (aterm is to eterm what nano is to pico ;)
).
I'm not absolute certain anymore which one is the problem, nano or pico.
I'm thinking nano was the one I had the prob with originally so what just
happened was messed up. *shrug*
sl
[reply]
[top]
[»]
Pico Clone
by Elik - Aug 4th 2000 05:27:57
Excellent clone. It have same functionality as the regular Pico without
the pesky Pine program and all the baggage that came with it.
Excellent editor to give to newbie shell account holders who want to
use text editor but want pico, not Vi like us power trippers.
[reply]
[top]
[»]
Re: Pico Clone
by R.L. - Feb 1st 2001 08:58:47
> Excellent clone. It have same
> functionality as the regular Pico
> without the pesky Pine program and all
> the baggage that came with it.
>
> Excellent editor to give to newbie
> shell account holders who want to use
> text editor but want pico, not Vi like
> us power trippers.
There are enough situations in which lighter, tinier tools are the most
practical ones, eventually. (And: not just for the newbies only.) Nano is
a fast, understatement, 80/20 editor. (A la pico, yes ... it works, e.g.,
beautifully with pine and mutt.) I am impressed too. Indeed, I have
switched from pico to nano. (Last but not least, it's free.)
[reply]
[top]
[»]
?!?
by richman - Jul 30th 2000 16:59:40
This looks just like Pico. Truly this is a good editor. I'm impressed.
Toga! Toga! Toga!
[reply]
[top]
[»]
very good work, but...
by lim3gr3en - Feb 20th 2001 03:53:55
I use nano very often because it's really light.
I'm still waiting for some improvements, such as
the possibility to run shell commands directly
from nano. Also the italian translation is not
really excellent: some labels in the menu are too
long, so they are cut in a bad way.
Nonetheless, very good job!
[reply]
[top]
|
