update of jed-extra

Jörg Sommer joerg@alea.gnuu.de
Fri Jul 8 20:41:36 UTC 2005


--Y1L3PTX8QE8cb2T+
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

G. Milde schrieb am Thu 07. Jul, 09:38 (+0200):
> On  6.07.05, J=F6rg Sommer wrote:
> > G. Milde schrieb am Wed 06. Jul, 14:44 (+0200):
> > > On  5.07.05, J=F6rg Sommer wrote:
> > > > G. Milde schrieb am Tue 05. Jul, 15:36 (+0200):
>=20
> > > > > * Should we use debconf to let the administrator decide which mod=
es to
> > > > >   activate/install?
> >=20
> >      * the admin can set _Jed_Default_Emualtion in jed.conf to the one =
he
> >        wants.
> >=20
> > >      So why not in debconf?
> >=20
> > Because it's simple easy to edit jed.conf or do we talk about
> > different things?
>=20
> Yes, I got your point regarding the _Jed_Default_Emualtion an already
> changed jed.conf accordingly.
>=20
> Here we have a different problem: Which jed-extra modes should be
> activated?

none. We should not set _Jed_Default_Emulation, but we should have it
commented out in jed.conf to give the admin a hint.

> Alternatively to the exclusion_list now in make_ini, we could introduce a
> "whitelist" of modes to generate autoloads or INITIALIZATION blocks in
> ini.sl.=20

I don't know. My present thought is, should jed-extra change the
behaviour of jed or should jed look the same with and without jed-extra?
For example, should jed-extra overwrite modes in jed?

> > A way would be to disable loading of jed.conf with command line option.
>=20
> This is the "brute force" option, as it disables all other
> configurations.=20
>=20
> However, with carefully chosen/patched modes the problems should only
> occure for the experienced user that either is also an administrator or
> able to copy (and modify) jed.conf to the start of his|her .jedrc, so it
> should work (and be documented) as a last resort.

> > We should patch site.sl.
>=20
> ... and send this patch to John as well. Or even better ask John,
> as the command_line_hook is a really convoluted piece of code.

ACK.

> BTW: Emacs calls this option --no-site-file, as our configuration file is
> called jed.conf (and not running site.sl is a rather bad idea), I would
> like to call the corresponding jed argument --no-conf-file.

Or --no-etc-files

--=20
"Computer games don't affect kids. If Pacman would have affected us as
children, we would now run around in darkened rooms, munching pills and
listening to repetetive music."

--Y1L3PTX8QE8cb2T+
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iQEVAwUBQs7lAIZ13Cz2nwVYAQJn1ggAwqKVBuLKpHV/JGx5M2eqfkaP5mVBN0X/
B5NlUj+pdXnOhX7EME77UCJ2KM5PT/5nTK5eoZugZGO3sS3etj4/Gm4ER/DwBI63
dE95yAVc6ZYPnDHMbirlkXpHtPWeT9ohzB8HL1yULB8TakMqKh4D7ej2JoswgIRG
bqklvLL0GPUY4JghZg6fhHZczn6LpEVWlW6kOgVOtv/h1fF2efws0P1z659VQcJy
z/Qo+9mHXqurQgJrNJBIz6oBCJIjUBfrOuNk97KLCGpeiyuzZidpEsW/5Z7HQ2FL
vcypvjmM38mkxHYRWEGGXGaJBp997OkB9iZYpX0pWeLn4w78l0fUwA==
=qTMp
-----END PGP SIGNATURE-----

--Y1L3PTX8QE8cb2T+--




More information about the Pkg-jed-devel mailing list