Mercurial > emacs

comparison etc/PROBLEMS @ 38175:8976a1349254

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
More about long file names and the MSDOS port.
author Eli Zaretskii <eliz@gnu.org>
date Sun, 24 Jun 2001 13:16:33 +0000
parents f4830f2d181b
children c96885865dda
comparison
equal deleted inserted replaced
38174:c91c4f77f5fb 38175:8976a1349254
1488 compilation are not the same. See the MSDOG section of INSTALL for 1488 compilation are not the same. See the MSDOG section of INSTALL for
1489 the explanation of how to avoid this problem. 1489 the explanation of how to avoid this problem.
1490 1490
1491 * Emacs compiled for MSDOS cannot find some Lisp files, or other 1491 * Emacs compiled for MSDOS cannot find some Lisp files, or other
1492 run-time support files, when long filename support is enabled. 1492 run-time support files, when long filename support is enabled.
1493 (Usually, this problem will manifest itself when Emacs exits 1493
1494 Usually, this problem will manifest itself when Emacs exits
1494 immediately after flashing the startup screen, because it cannot find 1495 immediately after flashing the startup screen, because it cannot find
1495 the Lisp files it needs to load at startup. Redirect Emacs stdout 1496 the Lisp files it needs to load at startup. Redirect Emacs stdout
1496 and stderr to a file to see the error message printed by Emacs.) 1497 and stderr to a file to see the error message printed by Emacs.
1498
1499 Another manifestation of this problem is that Emacs is unable to load
1500 the support for editing program sources in languages such as C and
1501 Lisp.
1497 1502
1498 This can happen if the Emacs distribution was unzipped without LFN 1503 This can happen if the Emacs distribution was unzipped without LFN
1499 support, thus causing long filenames to be truncated to the first 6 1504 support, thus causing long filenames to be truncated to the first 6
1500 characters and a numeric tail that Windows 95 normally attaches to it. 1505 characters and a numeric tail that Windows 95 normally attaches to it.
1501 You should unzip the files again with a utility that supports long 1506 You should unzip the files again with a utility that supports long
1502 filenames (such as djtar from DJGPP or InfoZip's UnZip program 1507 filenames (such as djtar from DJGPP or InfoZip's UnZip program
1503 compiled with DJGPP v2). The MSDOG section of the file INSTALL 1508 compiled with DJGPP v2). The MSDOG section of the file INSTALL
1504 explains this issue in more detail. 1509 explains this issue in more detail.
1510
1511 Another possible reason for such failures is that Emacs compiled for
1512 MSDOS is used on Windows NT, where long file names are not supported
1513 by this version of Emacs, but the distribution was unpacked by an
1514 unzip program that preserved the long file names instead of truncating
1515 them to DOS 8+3 limits. To be useful on NT, the MSDOS port of Emacs
1516 must be unzipped by a DOS utility, so that long file names are
1517 properly truncated.
1505 1518
1506 * Emacs compiled with DJGPP complains at startup: 1519 * Emacs compiled with DJGPP complains at startup:
1507 1520
1508 "Wrong type of argument: internal-facep, msdos-menu-active-face" 1521 "Wrong type of argument: internal-facep, msdos-menu-active-face"
1509 1522