Mercurial > emacs
view src/README @ 57862:60f1782b5d8d
From Ulf Jasper <ulf.jasper@web.de>:
(icalendar-version): Increase to 0.08.
(icalendar--split-value): Change name of work buffer.
(icalendar--get-weekday-abbrev): Return nil on error.
(icalendar--date-to-isodate): New function.
(icalendar-convert-diary-to-ical)
(icalendar-extract-ical-from-buffer): Use only two args for
make-obsolete (XEmacs compatibility).
(icalendar-export-file, icalendar-import-file): Blank at end of prompt.
(icalendar-export-region): Doc fix. If error, return non-nil
and write errors to buffer ` *icalendar-errors*'. Use correct weekday
for weekly recurring events. Check whether date has been parsed for
ordinary events. Make weekly events start in the year 2000. DTEND is
non-inclusive, shift end date by one day if necessary (not for entries
that have date and time). Rename local let variables: oops ->
found-error, datestring -> startdatestring.
author | Glenn Morris <rgm@gnu.org> |
---|---|
date | Tue, 02 Nov 2004 01:05:27 +0000 |
parents | 7ca787d18982 |
children | 68cfc1db0d26 |
line wrap: on
line source
This directory contains the source files for the C component of GNU Emacs. Nothing in this directory is needed for using Emacs once it is built and installed, if the dumped Emacs (on Unix systems) or the Emacs executable and map files (on VMS systems) are copied elsewhere. See the files ../README and then ../INSTALL for installation instructions. Under GNU and Unix systems, the file `Makefile.in' is used as a template by the script `../configure' to produce `Makefile.c'. The same script then uses `cpp' to produce the machine-dependent `Makefile' from `Makefile.c'; `Makefile' is the file which actually controls the compilation of Emacs. Most of this should work transparently to the user; you should only need to run `../configure', and then type `make'. See the file VMSBUILD in this directory for instructions on compiling, linking and building Emacs on VMS. The files `*.com' and `temacs.opt' are used on VMS only. The files `vlimit.h', `ioclt.h' and `param.h' are stubs to allow compilation on VMS with the minimum amount of #ifdefs. `uaf.h' contains VMS uaf structure definitions. This is only needed if you define READ_SYSUAF. This should only be done for single-user systems where you are not overly concerned with security, since it either requires that you install Emacs with SYSPRV or make SYSUAF.DAT world readable. Otherwise, Emacs can determine information about the current user, but no one else.