Mail Archives: djgpp/1997/10/07/08:38:35
On Tue, 7 Oct 1997, Davin Pearson wrote:
> I have both Eli Zaretskii's Emacs and Geoff Voelker's Emacs running
Please, it is not MY Emacs. I only compiled it for DJGPP and made a
few patches there. Richard Stallman is the author and the principal
maintainer of GNU Emacs.
> under Windows 95 but for some reason Eli's emacs now refuses to load.
> (This sort of annoying problem has happened to me before)
> Instead of loading, displays the following error message for about
> 3/50 ths of a second, before obliterating it with the command line.
>
> Cannot open load file: case-table
This is described in the file PROBLEMS. You either don't set LFN=y in
the environment, or you unzipped the distribution with an unzip
program that doesn't support long filenames (in which case
`lisp/case-table.elc' got truncated to `lisp/case-tab.elc', which is
not the same under LFN=y).
> So it seems that Eli should search the sources of his Emacs and
> replace occurences of \n with \r\n in the above string and other
> similar ones.
\n is not the reason that the message disappears. When Emacs exits,
it restores the screen contents as they were before Emacs was invoked,
and that's when the message is erased.
You can redirect Emacs's output to a file, and then you will see all
the messages intact:
redir -o emacs.log -eo emacs ...
After Emacs exits, look at the file `emacs.log'.
> With Win95-Emacs, which otherwise works fine, I have also come across
> some puzzling differences between running my makefile from the shell
> prompt and from inside Emacs (M-x compile). Could an experienced user
> explain the reason for the difference in behaviour? (I am using Win95
> Emacs)
Wrong news group, sorry. I have no idea how the Windows 95 version
runs child programs, and I doubt if anybody who reads this news group
does. It is a tricky issue to get correctly (I know how hard DJGPP's
library and the DOS-specific Emacs code have to work to do it right).
FYI: your Makefile produces *identical* results in all 3 cases when I
use DJGPP's port of Emacs.
Also, please make sure you have the latest version of NTEmacs
(19.34.6) installed. I hear they corrected quite a few bugs related
to running child programs in the last release.
> Another unrelated problem is that when I type the command: etags *.el
> on the bash command line, I get a bizarre error like:
>
> asm-mo: no such file or directory
>
> , but when I type the command: etags '*.el' it churns away and
> correctly produces the tags file. My understanding of this is that
> single quotes on the argument protects the argument from wildcard
> expansion from bash, so that the wildcard expansion is done inside the
> etags command.
Right.
> My guess as to why: etags *.el doesn't work is that there are so many
> files in the directory that it overflows the command line and causes
> etags to get confused.
>
> Trying out the command: etags *.el with the COMMAND.COM works fine,
> which seems to confirm the theory that bash is overflowing the command
> line.
>
> Is bash limited to 126-character command lines like COMMAND.COM?
Are you using the DJGPP port of Bash? If so, it is not limited to 126
characters. I have just tried "etags *.el" on my machine under Bash,
and it worked.
> If not, what is its limit?
the limit is 16K bytes minus the size of your environment (more, if
you stubedit bash.exe and enlarge its transfer buffer size beyond the
default 16KB). This is further explained in section 16.4 of the DJGPP
FAQ list.
- Raw text -