From pico to nano - OpenSource clone with more commands
Sven Guckes
called "nano". Please help its development by testing and coding!
See also:
From Pico to Nano
or
The Slightly Bigger Editor
http://www.linuxgazette.com/issue50/guckes.html
I am looking forward to some dicusssion. :-)
Sven [Let's *rock*!]
--
Sven Guckes gucke...@math.fu-berlin.de | NANO - like PICO, but
NANO http://www.math.fu-berlin.de/~guckes/nano/ | with search&replace,
NANO homepage: http://go.to/nano-editor | GotoLine, spellcheck,
NANO nano-...@go.to (Chris Allegretta) | I18N, and OpenSource!
Aaron S. Hawley
> For those of you who like pico - there is now an OpenSource clone
> called "nano".
pico is not OpenSource, no shit, i did not know that.
aaron
Eduardo Chappa L.
:)
:) > For those of you who like pico - there is now an OpenSource clone
:) > called "nano".
:)
:) pico is not OpenSource, no shit, i did not know that.
:)
Pico is open source, the statement is about nano as an open source editor,
not as pico as a closed source editor.
--
Eduardo
http://www.math.washington.edu/~chappa/pine/
Paul Fox
: :) > called "nano".
: :)
: :) pico is not OpenSource, no shit, i did not know that.
: :)
: Pico is open source, the statement is about nano as an open source editor,
: not as pico as a closed source editor.
the following text appears on the web page that sven pointed to, in
a review he wrote on nano:
However, the source code for Pico is closely linked to the
source code of Pine; therefore you cannot download Pico on its
own - you have to donwload the source of the complete
newsreader to install the little editor. Worse: Although
Pine is freely available you should now this:
Pine and Pico are not "OpenSource"
sven -- would you care to explain?
paul
=---------------------
paul fox, pgf-...@foxharp.boston.ma.us
Jeffrey Goldberg
> > For those of you who like pico - there is now an OpenSource clone
> > called "nano".
> pico is not OpenSource, no shit, i did not know that.
Oh, no! Not again.
Pico and Pine, the last time I looked, are about as close as possible to
being Open Source without actually being Open Source. Some argue that
they are Open Source. The dispute -- which I don't think that anyone has
anything new to say about -- has to do with restrictions on redistributing
modified versions of the software. The UW license, the last time I read
it, prohibits redistribution of modified versions. This has been the
sticking point of a feud which I would prefer not to see reopened.
In every other respect, Pine and Pico are clearly Open Source and have
those benefits.
I would ask that anyone who even considers reopening the discussion please
look in the news archives for things like "pine opensource" "free
pine" "fir" and particularly follow the postings by Mark Stallman and MRC.
After you've caught up with that discussion, I hope you will agree that
there is nothing to be gained by reopening.
I've directed follow-ups to poster, to stop this from surfacing again.
-j
--
Jeffrey Goldberg +44 (0)1234 750 111 x 2826
Cranfield Computer Centre FAX 751 814
J.Gol...@Cranfield.ac.uk http://WWW.Cranfield.ac.uk/public/cc/cc047/
Relativism is the triumph of authority over truth, convention over justice.
Joseph H Allen
Jeffrey Goldberg <J.Gol...@Cranfield.ac.uk> wrote:
>Pico and Pine, the last time I looked, are about as close as possible to
>being Open Source without actually being Open Source. Some argue that
>they are Open Source. The dispute -- which I don't think that anyone has
>anything new to say about -- has to do with restrictions on redistributing
>modified versions of the software. The UW license, the last time I read
>it, prohibits redistribution of modified versions. This has been the
>sticking point of a feud which I would prefer not to see reopened.
How very rude since Pico is based on micro-emacs, which is perhaps a little
too open sourced (public domain, not GPL). This is a good reason to
copyleft your freeware.
--
/* jha...@world.std.com (192.74.137.5) */ /* Joseph H. Allen */
int a[1817];main(z,p,q,r){for(p=80;q+p-80;p-=2*a[p])for(z=9;z--;)q=3&(r=time(0)
+r*57)/7,q=q?q-1?q-2?1-p%79?-1:0:p%79-77?1:0:p<1659?79:0:p>158?-79:0,q?!a[p+q*2
]?a[p+=a[p+=q]=q]=q:0:0;for(;q++-1817;)printf(q%79?"%c":"%c\n"," #"[!a[q-1]]);}
arv...@mail.ece.umn.edu
/* jha...@world.std.com (192.74.137.5) */ /* Joseph H. Allen */
int a[1817];main(z,p,q,r){for(p=80;q+p-80;p-=2*a[p])for(z=9;z--;)q=3&(r=time(0)
+r*57)/7,q=q?q-1?q-2?1-p%79?-1:0:p%79-77?1:0:p<1659?79:0:p>158?-79:0,q?!a[p+q*2
]?a[p+=a[p+=q]=q]=q:0:0;for(;q++-1817;)printf(q%79?"%c":"%c\n"," #"[!a[q-1]]);}
Hi Joseph,
just what exactly is your signature supposed to do? I initially
thought that it was printing your name in block ascii, then thought
it was a maze, but my eyes started to hurt after looking at it for
some time :)
requisite editor content to keep this thread not-off-topic for the
group : I read this in vi!
Arvind
--
main(int in,char *inn[]) {((in=='+'-'+'+'/'/'/')&&strcpy(inn['-'-'-'],")(Bswj\
oe!L/!Lbsboejlbs!\n\n\n\n!bswjoeAnbjm/fdf/vno/fev)in);")&&main('/'/'/'+'/'/'/'
,inn))||(!!in&&(inn['-'-'-'][in]==0x29)&&!!'('&&putchar(012)&&exit(')'-')'))||
('/'/'/'&&putchar(inn['-'-'-' ][ in]-'/'/'/'+'+'-'+')&&main(in+'/'/'/',inn));}
Sven Guckes
> > Pine and Pico are not "OpenSource"
> >sven -- would you care to explain?
Well, Christopher here gives a good explanation:
* Christopher Browne <cbbr...@news.hex.net>:
> Read: <http://www.washington.edu/pine/overview/legal.html>
> which describes the legal terms surrounding the
> distribution of Pine and Pico, and then read:
> <http://www.opensource.org/osd.html>
> which describes the distribution terms of open-source software.
> They differ, and not compatibly.
Indeed!
You might argue that the difference is small, but
I have dealt with too many delta and epsilons [*]
to know that a difference is a difference.
So - has anyone of you guys installed nano yet?
Sven
[*] "epsila" if you like.
Sven Guckes
> :) http://www.linuxgazette.com/issue50/guckes.html :
> :) The new commands are in the second column - GotoLine and Replace.
> Do you mean "new" as in pico does not have this and nano does? or you mean
> new as in last version of nano did not have this and this one have?
I actually meant "pico does not have a GotoLine command".
> Pico has those two commands already available. ^W^T is the first
> one and the other one has to be enabled from the command line.
I cannot see this command in pico-3.5 ...
> --
> Eduardo
> http://www.math.washington.edu/~chappa/pine/
... but I can see on your page that you have a
patch for pico which implements GotoLine as "^W^T".
So - does pico/pine now ship with your patches?
Sven
Pat Pridgen
> So - has anyone of you guys installed nano yet?
I was going to give it a try, but...it wants a greater glibc than I
have. I'm running RedHat 5.2. The same problem I have with a couple of
other programs.
--
Pat - La Grande,OR. - ppridgen <at> greencis <dot> net
http://www.greencis.net/~ppridgen
Linux - OS/2 dual Boot. Win What?
Sven Guckes
> > So - has anyone of you guys installed nano yet?
> I was going to give it a try, but...it wants a greater
> glibc than I have. I'm running RedHat 5.2. The same
> problem I have with a couple of other programs.
Sounds like you should upgrade then. :-)
Sven [all in favor of "greater libs"]
--
nano 0.8.1 New Buffer
^O Write Out ^_ Goto Line ^R Read File ^Y Prev Page ^K Cut Text ^C Cur Pos
^X Exit ^\ Replace ^W Where Is ^V Next Page ^U Uncut Txt ^T To Spell
Michael Dingler
> too open sourced (public domain, not GPL). This is a good reason to
> copyleft your freeware.
Well, I don't think this exact case would be a reason for copy-lefting.
After all, the difference between uemacs and pico isn't that
sensational,
so you didn't "lose" much 'cause of the "restrictive" licensing.
...Michael...
Eduardo Chappa L.
:)
:) > Pico has those two commands already available. ^W^T is the first
:) > one and the other one has to be enabled from the command line.
:)
:) I cannot see this command in pico-3.5 ...
:)
Yes indeed there is no such command in version 3.5. You can only find it
from version 3.7, which is the current version distributed with pine4.21.
I think that this command should have been made availabe a long time
ago. It's good that nano has it from the beginning.
--
Eduardo
http://www.math.washington.edu/~chappa/personal.html
Aaron S. Hawley
> It's good that nano has it (search & replace) from the beginning.
i wonder why pico doesn't, (to keep it simple, or does it slow down the
program?)
/a
Sven Guckes
> from version 3.7, which is the current version distributed with pine4.21.
So I just downloaded the current pico binary for SUN:
ftp://ftp.cac.washington.edu/pine/unix-bin/pico-bin.sun
and I find that indeed this is pico-3.7 and the command
CTRL-W offers a "GotoLine" with CTRL-T:
Search :
^G Get Help ^Y FirstLine ^T LineNumber^O End of Par
^C Cancel ^V LastLine ^W Start of P
So - why wasn't this mentioned in the annoucement to pine-4.21?
http://www.washington.edu/pine/changes/4.20-to-4.21.html
Is there some secret announcement page for pico that I am missing?
Btw, pico refuses to run under "screen" when TERM=screen:
Unknown terminal type screen!
I suppose this is because there is no entry in /etc/termcap.
Should the admin update the /etc/termcap?
> I think that this command should have been made availabe a
> long time ago. It's good that nano has it from the beginning.
Amen!
Red Wine
>How very rude since Pico is based on micro-emacs, which is perhaps a little
>too open sourced (public domain, not GPL). This is a good reason to
>copyleft your freeware.
Oh jhallen! Here you are... ;-)
And joe, how is it? That nice editor, you remember?
Is 2.8 a perfect version number?
--
Bye by Red | BHP on a FreeBSD box E-mail: ME7...@mclink.it
|---------------------------------------------------------------
| grep [Ll]ove Western_Civilization.txt > Desperate_Love.txt
| rm Western_Civilization.txt && echo '(Mr. Nobody)'
Sven Guckes
> Oh jhallen! Here you are... ;-)
> And joe, how is it? That nice editor, you remember?
> Is 2.8 a perfect version number?
The next release could be 4.96 - or 8.128.
But 33.55.03.36 looks screwed, doesn't it?
Sven
Christopher Browne
>* Paul Fox:
>> > Pine and Pico are not "OpenSource"
>> >sven -- would you care to explain?
>
>Well, Christopher here gives a good explanation:
>
>* Christopher Browne <cbbr...@news.hex.net>:
>> Read: <http://www.washington.edu/pine/overview/legal.html>
>> which describes the legal terms surrounding the
>> distribution of Pine and Pico, and then read:
>> <http://www.opensource.org/osd.html>
>> which describes the distribution terms of open-source software.
>> They differ, and not compatibly.
>
>Indeed!
>
>You might argue that the difference is small, but
>I have dealt with too many delta and epsilons [*]
>to know that a difference is a difference.
In mathematics, you only need *one example* to disprove a would-be
theorem. While lawyering isn't exactly the same, the principle still
holds: If all the terms agree except one, that one disagreement can be
enough to establish incompatibility.
>So - has anyone of you guys installed nano yet?
It's in Debian/unstable now; I've not bothered with it, as I tend to
keep an Xemacs process running perpetually, and do everything inside
that.
--
"MSDOS didn't get as bad as it is overnight -- it took over ten years
of careful development." -- <dmeg...@aix1.uottawa.ca>
cbbr...@ntlug.org- <http://www.hex.net/~cbbrowne/lsf.html>
Eduardo Chappa L.
:) Btw, pico refuses to run under "screen" when TERM=screen:
:) Unknown terminal type screen!
:) I suppose this is because there is no entry in /etc/termcap.
:) Should the admin update the /etc/termcap?
:)
From the code you can see that the chek is done in function
tcapterminalinfo, in the file pico_os.c. You can read there that the check
is being done using the function tgetent. From "man tgetent" you can read
that:
DESCRIPTION
These routines are obsolete and should not be used in new applications.
The routines are included in the Curses library as a conversion aid for
applications originally designed to use the termcap file. The routines
include the same parameters as used with the termcap file but their
operations are emulated by using the terminfo database.
The tgetent routine looks up the termcap entry for name.
--
Eduardo
http://www.math.washington.edu/~chappa/pine/
Rebeka Thomas
<Pine.OSF.4.21.00020...@goedel1.math.washington.edu>, Eduardo
Chappa L. wrote:
>*** Sven Guckes (guc...@math.fu-berlin.de) wrote on Feb 4, 2000:
>
>:) Btw, pico refuses to run under "screen" when TERM=screen:
>:) Unknown terminal type screen!
>:) I suppose this is because there is no entry in /etc/termcap.
>:) Should the admin update the /etc/termcap?
>:)
Or you can just export TERM=Vt10#, where # is one of 0, 2. Screen does VT102
emulation.
T.E.Dickey
screen emulates vt320 (a superset of vt102).
but the $TERM value outside screen has to be correct, or screen won't work.
--
Thomas E. Dickey
dic...@clark.net
http://www.clark.net/pub/dickey
NoneSuch
None