Mercurial > hg > xemacs-beta
comparison README.packages @ 2420:ad56e5a6d09f
[xemacs-hg @ 2004-12-06 03:46:06 by ben]
(none)
README.packages: Document use of --package-prefix.
Fix error in specifying standard package location.
make-docfile.c: Use QXE_PATH_MAX.
info.el: Correct doc string giving example package path.
menubar-items.el: Move Prefix Rectangle command up one level.
xemacs/packages.texi: Add long form of Lisp Reference Manual to links.
Add links pointing to Lisp Reference Manual for more detailed
package discussion.
lispref/range-tables.texi: Document range-table changes.
internals/internals.texi: Update history section.
elhash.c, elhash.h, profile.c: Create inchash_eq() to allow direct incrementing of hash-table
entry. Use in profile.c to try to reduce profiling overhead.
Increase initial size of profile hash tables to reduce profiling
overhead.
buffer.c, device-msw.c, dialog-msw.c, dired-msw.c, editfns.c, event-msw.c, events.c, glyphs-msw.c, keymap.c, objects-msw.c, process-nt.c, syswindows.h, text.c, text.h, unexnt.c: Rename xetcs* -> qxetcs* for consistency with qxestr*.
Rename ei*_c(_*) -> ei*_ascii(_*) since they work with ASCII-only
strings not "C strings", whatever those are. This is the last
place where "c" was incorrectly being used for "ascii".
dialog-msw.c, dumper.c, event-msw.c, fileio.c, glyphs-gtk.c, glyphs-x.c, nt.c, process-nt.c, realpath.c, sysdep.c, sysfile.h, unexcw.c, unexnext.c, unexnt.c: Try to avoid differences in systems that do or do not include
final null byte in PATH_MAX. Create PATH_MAX_INTERNAL and
PATH_MAX_EXTERNAL and use them everywhere. Rewrite code in
dumper.c to avoid use of PATH_MAX. When necessary in nt.c,
use _MAX_PATH instead of MAX_PATH to be consistent with
other places.
text.c: Code to short-circuit when binary or Unicode was not working
due to EOL wrapping. Fix this code to work when either no
EOL autodetection or no CR's or LF's in the text.
lisp.h, rangetab.c, rangetab.h, regex.c, search.c: Implement different types of ranges (open/closed start and end).
Change default to be start-closed, end-open.
author | ben |
---|---|
date | Mon, 06 Dec 2004 03:46:07 +0000 |
parents | 712931b4b71d |
children |
comparison
equal
deleted
inserted
replaced
2419:9d2ccd3f9049 | 2420:ad56e5a6d09f |
---|---|
30 A. You can grab all the packages at once like you used to with old | 30 A. You can grab all the packages at once like you used to with old |
31 XEmacs versions, skip to the 'Sumo Tarball' section below. | 31 XEmacs versions, skip to the 'Sumo Tarball' section below. |
32 | 32 |
33 Q. How do I tell XEmacs where to find the packages? | 33 Q. How do I tell XEmacs where to find the packages? |
34 | 34 |
35 A. Normally, you put the packages under $prefix/lib/packages, where | 35 A. Normally, you put the packages under $prefix/lib/xemacs, where |
36 $prefix is specified using the `--prefix' parameter to `configure'. | 36 $prefix is specified using the `--prefix' parameter to `configure'. |
37 (See `Package hierarchies' below). However, if you have the packages | 37 (See `Package hierarchies' below). However, if you have the packages |
38 somewhere else (e.g. you're a developer and are compiling the packages | 38 somewhere else (e.g. you're a developer and are compiling the packages |
39 yourself, and want your own private copy of everything), use the | 39 yourself, and want your own private copy of everything), use the |
40 `--package-path' parameter, something like this: | 40 `--package-prefix' parameter to `configure' to specify the directory prefix |
41 | 41 under which you have placed the `xemacs-packages' and (if MULE support |
42 configure --package-path="~/.xemacs::/src/xemacs/site-packages:/src/xemacs/xemacs-packages:/src/xemacs/mule-packages" ... | 42 exists) `mule-packages' directories. |
43 | 43 |
44 Q. After installing, I want XEmacs to do `foo', but when I invoke it | 44 Q. After installing, I want XEmacs to do `foo', but when I invoke it |
45 (or click the toolbar button or select the menu item), nothing (or | 45 (or click the toolbar button or select the menu item), nothing (or |
46 an error) happens, and it used to work. | 46 an error) happens, and it used to work. |
47 | 47 |
95 If your packages are located in the above directories, XEmacs will | 95 If your packages are located in the above directories, XEmacs will |
96 automatically find them at startup; however, if you have your packages | 96 automatically find them at startup; however, if you have your packages |
97 somewhere else (e.g. you're a developer and are compiling the packages | 97 somewhere else (e.g. you're a developer and are compiling the packages |
98 yourself, and want your own private copy of everything), you can tell | 98 yourself, and want your own private copy of everything), you can tell |
99 XEmacs specifically where to look for the packages by using the | 99 XEmacs specifically where to look for the packages by using the |
100 `--package-path' parameter to the 'configure' script. Normally, it looks | 100 `--package-prefix' parameter to 'configure' to specify the directory prefix |
101 like this: | 101 under which you have placed the `xemacs-packages' and (if MULE support |
102 | 102 exists) `mule-packages' directories. |
103 configure --package-path="~/.xemacs::/src/xemacs/site-packages:/src/xemacs/xemacs-packages:/src/xemacs/mule-packages" ... | |
104 | 103 |
105 See `configure.usage' for more info about the format of this parameter. | 104 See `configure.usage' for more info about the format of this parameter. |
106 | 105 |
107 * Where to get the packages | 106 * Where to get the packages |
108 --------------------------- | 107 --------------------------- |