Uwe> Hello Uwe> Who is now responsible for appt.el Hi Uwe, here's how to find out: M-x locate-library RET appt RET M-x show-message-log Library is file c:\Program Files\XEmacs\xemacs-packages\lisp\calendar\appt.elc Ah, it's part of the calendar package. If you have that installed you can also do this: (package-get-package-provider 'appt) (calendar "1.19") This finds the maintainer: (package-get-info-prop (car (package-get-info-find-package package-get-base 'calendar)) 'maintainer) "XEmacs Development Team <xemacs-beta(a)xemacs.org&gt;&quot; You could also use M-x pui-list-packages and i runs the command pui-display-info on the calendar package line to find that information. So, in short, xemacs-beta is the right crowd to ask for this package. Send your bug reports via M-x report-xemacs-bug and your patches to xemacs-patches. Hope this helps, Adrian Uwe> I think I found some bugs, and a small add-on. Uwe> Thanks Uwe> Uwe Brauer -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/

SY> |--==> "APA" == Adrian Aichner <adrian(a)xemacs.org&gt; writes: Uwe> Hello Uwe> Who is now responsible for appt.el APA> Hi Uwe, APA> here's how to find out: APA> M-x locate-library RET appt RET APA> M-x show-message-log APA> Library is file c:\Program Files\XEmacs\xemacs-packages\lisp\calendar\appt.elc APA> Ah, it's part of the calendar package. APA> If you have that installed you can also do this: APA> (package-get-package-provider 'appt) APA> (calendar "1.19") SY> That will work even if the package isn't installed. And the SY> function is interactive so you could M-x SY> package-get-package-provider RET appt RET Ah great! Thanks APA> This finds the maintainer: APA> (package-get-info-prop APA> (car (package-get-info-find-package package-get-base 'calendar)) APA> 'maintainer) APA> "XEmacs Development Team <xemacs-beta(a)xemacs.org&gt;&quot; SY> In my directory in the xemacs-builds CVS module there is pkg-build.el, SY> It does the work of rolling packages which wouldn't be of interest to SY> many people, but it also has... SY> ,----[ C-h f pkg-get-info RET ] SY> | `pkg-get-info' is an interactive compiled Lisp function SY> | -- loaded from "pkg-build" SY> | (pkg-get-info PACKAGE INFORMATION &optional REMOTE) SY> | SY> | Documentation: SY> | Get information about a package. SY> | SY> | Argument PACKAGE is the name of an XEmacs package (a symbol). It SY> | must be a valid package, ie, a member of either `pkg-std-packages' or SY> | `pkg-mule-packages'. SY> | SY> | Argument INFORMATION is a symbol that can be any one of: SY> | SY> | standards-version Package system version (not used). SY> | version Version of the XEmacs package. SY> | author-version The upstream version of the package. SY> | date The date the package was last modified. SY> | build-date The date the package was last built. SY> | maintainer The maintainer of the package. SY> | distribution Will always be "xemacs" (not used). SY> | priority "low", "medium", or "high" (not used). SY> | category Either "standard" or "mule". SY> | dump Is the package dumped (not used). SY> | description A description of the package. SY> | filename The filename of the binary tarball of the package. SY> | md5sum The md5sum of filename. SY> | size The size in bytes of filename. SY> | provides A list of symbols that this package provides. SY> | requires A list of packages that this package requires. SY> | type Can be either "regular" or "single-file". SY> | SY> | If optional argument REMOTE is non-nil use a package list from a SY> | remote site. For this to work `package-get-remote' must be non-nil. SY> | SY> | If this function is called interactively it will display INFORMATION SY> | in the minibuffer. SY> `---- SY> Maybe I should put this function into core, it is quite handy. That would be handy. yes. APA> You could also use APA> M-x pui-list-packages APA> and APA> i runs the command pui-display-info APA> on the calendar package line APA> to find that information. SY> Or just move your rat over the line and rea Ah, missed that. I'm a bit scared of my rat and my scratchpad sometimes acts up. -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/