Re: ae as default editor?
On Mon, 23 Sep 1996, James A. Robinson wrote: > Well, I imagine if one takes that idea further, one would say that ae > is the editor on the base disk because it is easier to use. Plus it's very small. > I think the real reason goes back to the fact that experienced users > can set their EDITOR variable, or handle ae. That's why I made ae the default editor for vipw. That and the fact that otherwise, vipw on the base disks won't work. And for those of you who think I should rename vipw to aepw or editpw or emacspw or that I should look at the first strlen()-2 letters and try to call that, I saw: Pbtl! Guy
Re: ae as default editor?
> However, I remember a discussion that, I believe, lead to this decision; > I can't remember all the discussions that have gone on here, there so very very many. ;-) > IIRC, it was the same idea that made ae (wrongly) essential - "all other > editors can be removed, so ae is a better fallback than vi". Well, I imagine if one takes that idea further, one would say that ae is the editor on the base disk because it is easier to use. Because it is on the base disk it has "recommended" status. And so on. I think the real reason goes back to the fact that experienced users can set their EDITOR variable, or handle ae. New users won't be able to handle something like vi, so we shouldn't dump them in it unless they call vi themselves. Jim -- Jim Robinson <[EMAIL PROTECTED]> - http://www.simons-rock.edu/~jimr/ Simon's Rock College.
Re: ae as default editor?
Martin> Why is ae the default editor for vipw/vigr even on a completely Martin> installed system? It's not a default, it's a fallback which is used when you have not set the EDITOR variable. Just try $ EDITOR=vi vigr -- Dirk Eddelb"uttel http://qed.econ.queensu.ca/~edd
Re: ae as default editor?
> Why is ae the default editor for vipw/vigr even on a completely > installed system? > > Doesn't VI-gr/pw suggest that a VI clone is executed? I can > understand to use ae as a fallback editor, but not as the main one Probably it is setup for the same reason ae is the default editor on the base disk. A new user, somebody who has only known DOS, WindowsX, or MacOS will probably be completely unable to deal with vi, but will probably be able to handle ae. Because these new users might be told to use vipw or vigr to edit the passwd or group file, it is better to stick them into a "friendly" editor. More experienced users will be able to set their EDITOR variable to call the correct editor (A more experienced user will also be able to get the job done in ae if need be). Jim -- Jim Robinson <[EMAIL PROTECTED]> - http://www.simons-rock.edu/~jimr/ Simon's Rock College.
ae as default editor?
Good morning folks, Why is ae the default editor for vipw/vigr even on a completely installed system? Doesn't VI-gr/pw suggest that a VI clone is executed? I can understand to use ae as a fallback editor, but not as the main one # dpkg -l passwd Desired=Unknown/Install/Remove/Purge | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ NameVersionDescription +++-===-==- ii passwd 1.0-5 Change password data. Regards, Joey -- / Martin Schulze * [EMAIL PROTECTED] * 26129 Oldenburg / / http://home.pages.de/~joey/ / Ich glaube nur der Statistik, die ich selbst gefälscht habe! /
