A "traditional" vi for puppy 3.00 ( & 4.20)
A "traditional" vi for puppy 3.00 ( & 4.20)
I've been irritated by e3vi since I first found puppy, but only recently became annoyed enough to look out a replacement.
vim is just too big (23MB) and is overengineered for my wants and needs.
I found source code for the "traditional" vi here, and a suitable termcap that will make it workhere (thanks to
this thread)
It compiled without trouble (I'm not a programmer at all btw) under Puppy 3.00 with devx_300, and I packaged it up with dir2pet etc.
Installed, it comes in at about 500K, and it drives nicely for simple tasks.
I hope someone else will find it as useful (and beautiful) as I.
paul
EDIT (05 05 2008) The termcap link given above now seems to be broken, but forum user carolus has found this one:
http://fts.ifac.cnr.it/cgi-bin/dwww?typ ... termcap.gz
vim is just too big (23MB) and is overengineered for my wants and needs.
I found source code for the "traditional" vi here, and a suitable termcap that will make it workhere (thanks to
this thread)
It compiled without trouble (I'm not a programmer at all btw) under Puppy 3.00 with devx_300, and I packaged it up with dir2pet etc.
Installed, it comes in at about 500K, and it drives nicely for simple tasks.
I hope someone else will find it as useful (and beautiful) as I.
paul
EDIT (05 05 2008) The termcap link given above now seems to be broken, but forum user carolus has found this one:
http://fts.ifac.cnr.it/cgi-bin/dwww?typ ... termcap.gz
- Attachments
-
- ex-050325-i486.pet
- Simple dotpet for trad vi
- (126.59 KiB) Downloaded 923 times
Last edited by paulh177 on Thu 16 Apr 2009, 18:31, edited 1 time in total.
vi for puppy 4.00
Thanks so much, paul. I registered just to thank you.
Works, so far, flawlessly in v4.0 (2.6.21.7), ram only install (live cd from HD).
Though I've been a great puppy admirer and user for about 3 years, now, perhaps I'm still a newbie at getting information. It took me close to an hour to find your download: specifically a pre-compiled vi that was pupget/petget package that works for recent versions.
I wish we could somehow bump up this link for others that might be interested.
Without causing a heated vi discussion, I wonder if we could get this included in the next release of official petGet files unleashed. At least it would be available, then, via the installer.
Again, thanks so very much. My pro-pup-ductivity increases thanks to you.
BTW, I don't know much about termcap, but it ran without hitch in rxvt. I'd be glad to make any quick tests for this on my live-boot.
Works, so far, flawlessly in v4.0 (2.6.21.7), ram only install (live cd from HD).
Though I've been a great puppy admirer and user for about 3 years, now, perhaps I'm still a newbie at getting information. It took me close to an hour to find your download: specifically a pre-compiled vi that was pupget/petget package that works for recent versions.
I wish we could somehow bump up this link for others that might be interested.
Without causing a heated vi discussion, I wonder if we could get this included in the next release of official petGet files unleashed. At least it would be available, then, via the installer.
Again, thanks so very much. My pro-pup-ductivity increases thanks to you.
BTW, I don't know much about termcap, but it ran without hitch in rxvt. I'd be glad to make any quick tests for this on my live-boot.
Many thanks - my sanity is saved :D
Paul
Like you e3 had irritated me ever since I started using Puppy - all of a month - but I'd never got irritated enough to do anything about it.
A couple of days ago it finally do and I asked if there was a vi lookalike for Puppy.
The search at http://wellminded.com/puppy/pupsearch.html revealed your thread and I jumped at the chance of a better vi.
Five minutes work of downloading and installing and all I can say is THANKS it is instantly better than e3vi.
Thanks from very happy bunny
Kelly
Like you e3 had irritated me ever since I started using Puppy - all of a month - but I'd never got irritated enough to do anything about it.
A couple of days ago it finally do and I asked if there was a vi lookalike for Puppy.
The search at http://wellminded.com/puppy/pupsearch.html revealed your thread and I jumped at the chance of a better vi.
Five minutes work of downloading and installing and all I can say is THANKS it is instantly better than e3vi.
Thanks from very happy bunny
Kelly
got it from debian
http://packages.debian.org/unstable/editors/elvis-tiny
depends on ncurses but isn't such a mess with termcap
good luck,
Sven
http://packages.debian.org/unstable/editors/elvis-tiny
depends on ncurses but isn't such a mess with termcap
good luck,
Sven
- Attachments
-
- elvis-tiny-1.4.pet
- minimal vi like editor
- (85.04 KiB) Downloaded 801 times
Here's the debian link:
http://packages.qa.debian.org/e/elvis-tiny.html
It's also in T2:
http://www.t2-project.org/packages/elvis-tiny.html
http://packages.qa.debian.org/e/elvis-tiny.html
It's also in T2:
http://www.t2-project.org/packages/elvis-tiny.html
-
- Posts: 12
- Joined: Sun 12 Apr 2009, 20:10
Found it. Thanks.
Ignore my request for more info. I was assuming some sort of dedicated pet package search, but a plain ol' forum search was enough.
Thanks again for giving me a real vi!
Thanks again for giving me a real vi!
I've now compiled this under Puppy 4.2.
The .pet includes and installs a suitable termcap, and the main executable has been stripped.
I haven't performed any regression tests
The .pet includes and installs a suitable termcap, and the main executable has been stripped.
I haven't performed any regression tests
- Attachments
-
- ex-050325-i486.pet
- A simple "traditonal" vi compiled under Puppy 4.20
- (128.32 KiB) Downloaded 684 times
"xterm: unknown terminal type"
Hi,
Sorry to bump an old thread but my post subject relates significantly to this thread's subject ...
I am in the process of switching from 4.2 to 4.3.1. The old "xterm: unknown terminal type" issue is surfacing again (http://www.murga-linux.com/puppy/viewtopic.php?t=28767).
I have tested both versions of the ex-050325 pet and installing termcap manually as per the instruction in the OP (and I still have and used the original termcap file from the very first version of the OP) - nothing works: the issue is persistent. The remedies of the other above mentioned thread do not work either.
Does anybody have any ideas?
Off-Topic: Happy New Year
cklammer
Sorry to bump an old thread but my post subject relates significantly to this thread's subject ...
I am in the process of switching from 4.2 to 4.3.1. The old "xterm: unknown terminal type" issue is surfacing again (http://www.murga-linux.com/puppy/viewtopic.php?t=28767).
I have tested both versions of the ex-050325 pet and installing termcap manually as per the instruction in the OP (and I still have and used the original termcap file from the very first version of the OP) - nothing works: the issue is persistent. The remedies of the other above mentioned thread do not work either.
Does anybody have any ideas?
Off-Topic: Happy New Year
cklammer
It destroys "/usr/local/bin/defaulttexteditor". Original content is:Sven wrote:got it from debian
http://packages.debian.org/unstable/editors/elvis-tiny
depends on ncurses but isn't such a mess with termcap
good luck,
Sven
Code: Select all
#!/bin/sh
exec xterm -e elvis ""
Code: Select all
#!/bin/sh
exec xterm -e elvis "$@"
I am using 4.31 and tested this on a vanilla 4.31 (booted with pfix=ram)
cklammer
Re: "xterm: unknown terminal type"
If you open a terminal and do a "set" or "env", what do you see?cklammer wrote: I am in the process of switching from 4.2 to 4.3.1. The old "xterm: unknown terminal type" issue is surfacing again (http://www.murga-linux.com/puppy/viewtopic.php?t=28767).
I have tested both versions of the ex-050325 pet and installing termcap manually as per the instruction in the OP (and I still have and used the original termcap file from the very first version of the OP) - nothing works: the issue is persistent. The remedies of the other above mentioned thread do not work either.
Does anybody have any ideas?
*nix boxes expect to see a "TERM=<whatever>" string in the environment, where <whatever> identifies what you are using as a terminal. The identifier maps to a name in the termcap file, where the entry that defines that terminal and how to talk to it will hopefully be found.
It sounds like either
a) The TERM variable isn't defined, or
b) The value it's set to isn't in termcap, or
c) the termcap file isn't where the system expects to find it.
On Puppy 4.12, here, termcap is in /etc/termcap, and TERM=xterm
The version of vi offered by the OP works fine.
______
Dennis