Am Samstag, 23. Juni 2018, 22:48:05 CEST schrieb Joseph Comfort:

On Sat, 23 Jun 2018, Mikhail Ramendik wrote:

...

Can you simply run the command directly from a shell prompt and see what happens?

My suspicion is that the edc file fails to start because of some lost prerequisite, and so shell says the file is not there.

An interesting thought, thanks. I have not fully installed the system yet -- only the initial load from the DVD iso. I need an ascii file editor [...]

this is why some basic familiarity with vi is beneficial for the average unix guy. Cheers MH -- Mathias Homann Senior Systems Engineer, IT Consultant. IT Trainer Mathias.Homann@openSUSE.org http://www.tuxonline.tech gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102

On 06/23/2018 09:11 PM, David T-G wrote:

+1 (again and again and again :-)

It really isn't hard to get to know and it Just Works. It would definitely be worth your time.

+2 If you can learn nothing more than type 'i' to enter insert/edit mode and remember to hit '<esc>' to return from input mode to command mode -- you can pretty much make things work to edit what you need. Then in command mode if you can remember :w (to write/save the file) :q (to quit) :wq (both save and quit together) :q! (to quit abandoning changes) You are good to go. openSuSE provides a good system-wide vimrc that make the arrow keys functional as well as backspace in vim. But also remember there is a difference between vim and vi (some distros install basic vi -- which by default only allows *editing* a single line at a time -- though you can *insert* as many as you like) That will get you started, then whenever you need to do anything else, either :help (with info-page like navigation, :q quit) or look whatever you need to do on the web (e.g. search 'vim what I want to do') and just slowly add tools to your vim toolbox. A few minutes with :help quickref will do a good job giving you the basics. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Greg -- ...and then Greg Freemyer said... % % On Sun, Jun 24, 2018 at 1:36 AM, David C. Rankin % > % > But also remember there is a difference between vim and vi (some distros % > install basic vi -- which by default only allows *editing* a single line at a % > time -- though you can *insert* as many as you like) % % David, I'm not that David, but you could say I play one on TV ;-) % ... % No idea what you mean by the difference between basic vi and vim. % % Basic vi is a screen editor that shows a screen full of lines and % h/j/k/l allow you to move around the screen. Yep. % % Is vim different in some fundamental way? It is "Vi IMproved". It offers a proper superset of all original vi functionality as well as supporting the various little differences of elvis, nvi, and maybe others. For the vi user, it's pretty much the same. For the experienced vim user, though, going back to vi could feel constrictive (I love me some folding, for instance). % % I use vim as a 100% vi replacement and don't know what extras it % brings to the table. You can do that, and you can even use it in plain vanilla vi mode with nothing special added (although I confess that I don't recall the flag that makes it so). I tried, honest, for all of 17 seconds to have a look at the vim help for a good list of everything, but I don't have the time to go digging. I would start with :help intro (which ability, BTW, is another example of vim that is not vi :-) and see where it takes you. Have a lot of fun ;-) % % Thanks % Greg HTH & HANW :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Le 24/06/2018 à 18:58, L A Walsh a écrit :

The one I notice the most -- original vi only allows 1-step undo.

you know, there is no "original vi". I searched for it once and found than there was a visual editor may be since the first computer, certainly since the first unix https://en.wikipedia.org/wiki/Vi jdd :-) -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Le 24/06/2018 à 21:29, David T-G a écrit :

How much more original must one be? :-)

where is the source code? can you compile it? AFAIK one can't *use* the original one :-) but I would love to try :-) jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 06/24/2018 05:38 PM, David T-G wrote:

Well, if you just grab a copy of the original BSD 1.0 and install it on probably a Vax (or even a Vax emulator these days!), you could...

I used to work with VAX 11/780 computers, though they were running VAX/VMS. https://www.flynetviewer.com/content/web-based-vax-vms-terminal-emulator?gcl...

Indeed I do miss playing around on the PDP-11 terminals where, along with a BSD Vax and those crazy new SunOS 4 machines (Sun 3/ and 4/ boxes), I first got to know UNIX...

Those could have been M33 Teletypes or perhaps "glass TTYs" such as the VT52, VT100 etc.. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Le 25/06/2018 à 16:03, Liam Proven a écrit :

On 24/06/18 23:16, jdd@dodin.org wrote:

...

where is the source code? can you compile it?

AFAIK one can't *use* the original one :-)

but I would love to try :-)

http://ex-vi.sourceforge.net/

I will try this, thanks :-), but it's a "modernized" vi :-(( jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Le 25/06/2018 à 16:48, Liam Proven a écrit :

Brace yourself for a very basic sort of experience, though.

uvi on gentoo was not to bad either (was what drived mr to this search :-)

If that's too much, try NetBSD. It's pretty old-school. :-)

done already on a sun pizzabox, pretty cool, but for a linux user many details to cope with jdd (that feel really old timer then :-) -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Le 25/06/2018 à 16:58, Liam Proven a écrit :

It was way too hardcore for me. :-D But then, to be honest, even PC-BSD, er, FreeBSD, I mean, TrueOS is a bit too hardcore...

well on 128Mb ram, 1Gb hdd in worked pretty well, but beginning with the disklabel thing... we may got to OT list now :-( jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 06/25/2018 09:42 AM, jdd@dodin.org wrote:

...

...

but I would love to try :-)

http://ex-vi.sourceforge.net/

I will try this, thanks :-), but it's a "modernized" vi :-((

jdd

Oh no.... ex (vi) is as bare bones as it gets and still be usable. This will provide all basic vi capabilities, but you have not syntax highlight, can only **edit** single lines (e.g. up/down-arrow cancels input mode), but you can insert all the text you like in one go. If you want to build the most basic vi to keep in your hip-pocket for recovery, etc, ex is the way to go. I've attached the pkgbuild file from Arch that includes a couple of helpful patches. Just untar the file, which will provide: -rw-r--r-- 1 david david 1563 Jun 3 23:19 PKGBUILD -rw-r--r-- 1 david david 368 Jun 3 23:19 fix-tubesize-short-overflow.patch -rw-r--r-- 1 david david 2031 Jun 3 23:19 navkeys.patch -rw-r--r-- 1 david david 2798 Jun 3 23:19 preserve-dir.patch You can view the PKGBUILD to grab the patch, and make options uses as well as the URL for the direct download of he source (it's just a bash script, so you can see where the 'pkgname, pkgver and pkgrel' are expanded. It's a great little editor, "The original ex/vi text editor", but it lacks the creature comforts of vim. Amazing part is the source is only 211k and the resulting package is only 165k. Very few editors will easily fit on a 1.44M floppy anymore... -- David C. Rankin, J.D.,P.E.

On 2018-06-23 23:19, Mathias Homann wrote:

Am Samstag, 23. Juni 2018, 22:48:05 CEST schrieb Joseph Comfort:

...

On Sat, 23 Jun 2018, Mikhail Ramendik wrote:

...

Can you simply run the command directly from a shell prompt and see what happens?

My suspicion is that the edc file fails to start because of some lost prerequisite, and so shell says the file is not there.

An interesting thought, thanks. I have not fully installed the system yet -- only the initial load from the DVD iso. I need an ascii file editor [...]

this is why some basic familiarity with vi is beneficial for the average unix guy.

joe is installed by default on openSUSE machines besides vi. IIRC it is in the rescue image. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)

Le 24/06/2018 à 12:23, Mikhail Ramendik a écrit :

People are responding about knowing vi, but I suspect that nano is available. Can you try starting nano? Unlike vi it is extremely easy to use. and it would give you your editing capabilities.

on kde, kate works well (no more kwrite), but vi may be the only app that open absolutely any file and the number of commands to learn is very low (i, ESC, :wq, :q, :/) do most of the job :-) and it's almost always here. But if you can, use vim, most tiny vi can be a pain jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2018-06-24 14:39, David T-G wrote:

Hi, all --

...and then jdd@dodin.org said... % % Le 24/06/2018 à 12:23, Mikhail Ramendik a écrit : % % >People are responding about knowing vi, but I suspect that nano is ... % > % on kde, kate works well (no more kwrite), but vi may be the only app

There are tons of editors out there, and some of them are even acceptable. That's not the point, though. You will find vi on every *NIX system (unless you build from scratch and choose to exclude it); when you can't count on anything else, you can count on vi (and ed, which I admit requiers being able to hold more in your head).

You should find "joe" on every openSUSE machine, even the rescue image on the install DVD. We asked many years ago for it and convinced devs to not only package vi and not rely on people having to vi by force.

% that open absolutely any file and the number of commands to learn is % very low (i, ESC, :wq, :q, :/) do most of the job :-)

I'd go so far as to say that you really should also be familiar with the hjkl cursor movement keys, since not all keyboards have those silly arrow things :-) In general, though, this is true.

Every PC (PC as in IBM PC clone descendant) has arrows. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)

what type file is it? 'file /usr/local/ED-159/edc' My guess is an unsupported binary type, or it's an script which is missing the interpreter (like your script with '#!/bin/sh', when there is no /bin/sh)

The file is a binary, compiled from C code. The first few binary characters are: <7f>ELF<01> ... It was built in 2000, and has worked ever since. I tried once to recompile it, but conventions had changed for some of the C code and it failed. I suppose that, by now, some conflicts with system libraries may have crept in, although I hope not. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Sat, 23 Jun 2018, Bernhard Voelker wrote:

Try:

ldd /usr/local/ED-159/edc

Chances are it's an x86 binary but you didn't install the 32bit libraries, e.g. glibc-32bit and friends.

Again, thank you Berry. You were right, and the script now works as expected! Just what I needed. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Thank you Barry. Some old history involved. I have made the changes. Unfortunately, the behavior is still the same. Joe On Sat, 23 Jun 2018, Bernhard Voelker wrote:

On 06/23/2018 08:10 PM, Joseph Comfort wrote:

...

#!/bin/sh # Script for EDT look-alike ED v1.5.9

eddsk=/usr/local/ED-159

$eddsk/edc $eddsk/vt200.ed $eddsk/ed.setup 0 0 -1 -u $1 $2 $3 $4 $5 $6 $7

FWIW: this is pretty poor variable quoting style - actually there's no quoting at all. This might work in some of your cases ... but to have a more robust script, please do yourself and everyone else a favor and use:

"$eddsk/edc" "$eddsk/vt200.ed" "$eddsk/ed.setup" 0 0 -1 -u "$1" "$2" "$3" "$4" "$5" "$6" "$7"

or probably even more simply:

"$eddsk/edc" "$eddsk/vt200.ed" "$eddsk/ed.setup" 0 0 -1 -u "$@"

Have a nice day, Berny

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org