XJed is a superset of jed
Mon, 27 Jun 2005 16:00:01 +0200
On 27.06.05, Rafael Laboissiere wrote:
> * G. Milde <firstname.lastname@example.org> [2005-06-27 09:43]:
> My wording above was not clear.
I think I got it, but still differ in my opinion (see below).
> Let me try again :
> If the executable /usr/bin/jed is under the alternatives scheme control,
> then the system administrator can choose /usr/bin/jed to be either the
> console (/usr/bin/jed.real) or the X version (/usr/bin/jed.xjed).
Clear. `jed` resolves to either real jed or xjed behaving as jed.
> Once this alternative is set, then the system administrator needs only to
> add the alternative /usr/bin/jed (which is an alternative itself) to
> /usr/bin/editor. There is no need to add /usr/bin/xjed to the
> /usr/bin/editor alternatives.
The administrator/user might want to choose "editor" to point to
either a console editor (/usr/bin/jed), or
a X-capable editor (/usr/bin/xjed)
Example: I am writing this with xjed, called from mutt. With the above
choice, I could set /usr/bin/editor to xjed and in .muttrc the editor to
Other people might not want different behaviour of `editor` depending on the
presence of DISPLAY, so they would prefer jed as choice for `editor`.