> > David Frey <[EMAIL PROTECTED]> writes:
> > >>TOPIC 4: editor/pager policy
> > > What is the benefit of /usr/bin/sensible-{editor,pager}?
> > > Why don't we just default to EDITOR=/usr/bin/vi and PAGER=/usr/bin/more
> > > if both variables are unset? (auch, don't beat me)
> >
> > That might enable us to get rid of /usr/bin/{editor,pager} though it's an
> > inferior solution to what we're doing at the moment. It won't enable us to
> > get rid of /usr/bin/sensible-{editor,pager} which are for progams that don't
> > understand EDITOR and PAGER.
>
> Not exactly.
>
> The files /usr/bin/{editor,pager} will be managed through alternatives.
> Since alternatives can be changed by the sysadmin only, we allow the user
> to define EDITOR and PAGER to override this.
>
> That's why we need "sensible-{editor,pager}". These are two simply shell
> scripts that test if EDITOR/PAGER is set and launches either that program,
> or /usr/bin/{editor,pager}.
Im still confused. What do /usr/bin/{editor,pager} do then?
Are they hard links to vi and more? Or equivalently trivial shell scripts
of the form:
#!/bin/sh
/usr/bin/vi
Thanks for your patience,
David
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
