3 Nov 2008 09:09
Re: Using a "saved" macro
Ulli Horlacher <framstag <at> rus.uni-stuttgart.de>
2008-11-03 08:09:12 GMT
2008-11-03 08:09:12 GMT
On Sun 2008-10-26 (21:01), Duke Normandin wrote: > though... what is the intent of "macro_save_macro"? I suppose it is code (macro.sl) that has not been finished yet. I asked this question some time ago I got some hints, so that I have now a function store_macro() which assigns the current macro to a key and saves it to $HOME/.jed/macros.sl which itself get loaded at jed startup. What still is missing is list_macros() and delete_macro(). -- -- Ullrich Horlacher Server- und Arbeitsplatzsysteme Rechenzentrum E-Mail: horlacher <at> rus.uni-stuttgart.de Universitaet Stuttgart Tel: ++49-711-685-65868 Allmandring 30 Fax: ++49-711-682357 70550 Stuttgart (Germany) WWW: http://www.rus.uni-stuttgart.de/
README.Debian-startup % explains the Debian-specific startup scheme
README.Debian.gz % Contains an appropriate warning
changelog.Debian.gz % lists the change as well
> It really shouldn't require 45+ minutes of
> sleuthing through site.sl and such to figure out that there was an
> overriding defaults.sl that was loading files from /etc/jed.d/ that was
> preventing my ~/.jedrc from loading because I had a ~/.jed directory.
Agreed. But IMO the Debian README files are the right place for this
kind of info.
> OBTW - If the debian package maintainer is around, installing jed-extras
> breaks the info reader.
Not here.
> Looks like the drop-in replacement for info.sl
RSS Feed