More information.
xemacs-21.2-b36.tar.gz built on RedHat 6.2 Linux with --pdump=yes
exhibits the same problem.
So it doesn't seem to be germaine to the win32 port of pdump, but
is more at the core of pdump I would suspect.
I did set a trace-style breakpoint on indent_tabs_mode, and found that
(on win32) it gets set once in the following place when the pdump loads.
But
it never again gets set throughout the lifetime of the XEmacs session.
dumper.c, Line 1040:
/* Put back the opaques */
for (i=0; i<((dump_header *)pdump_start)->nb_opaquedmp; i++)
{
struct pdump_dumpopaqueinfo di = PDUMP_READ (p, struct
pdump_dumpopaqueinfo);
> memcpy (di.data, p, di.size);
p += di.size;
}
Don't know what that means for sure, I suppose I could crawl in and learn
how the portable dumper works... if time permits.
If I compile without pdump, every time I (setq indent-tabs-mode ...), I get
a
breakpoint on watch at the following location. Never did get here when
running with pdump enabled though. It's almost like once the pdump data
gets loaded, XEmacs "forgets" how to set indent_tabs_mode. Suspect that's
true of other DEVFAR's too, in which case this is a much bigger problem than
just indent-to not working.
symbols.c, Line 1259:
case SYMVAL_BOOLEAN_FORWARD:
if (magicfun)
magicfun (sym, &newval, Qnil, 0);
*((int *) symbol_value_forward_forward (fwd))
> = !NILP (newval);
return;
-----Original Message-----
From: Troy Noble [mailto:troy.noble＠channelpoint.com]
Sent: Sunday, October 22, 2000 7:32 PM
To: 'sperber(a)informatik.uni-tuebingen.de'; Adrian Aichner
Cc: Troy Noble; 'xemacs-beta(a)xemacs.org'; 'xemacs-nt(a)xemacs.org'
Subject: RE: (setq indent-tabs-mode nil) not working in 21.2b36 on NT?
>>>>> "APA" == Adrian Aichner <adrian(a)xemacs.org> writes:
>>>>> "sperber" == sperber(a)informatik.uni-tuebingen.de
<sperber(a)informatik.uni-tuebingen.de> writes:
sperber> Sure sounds like the pdump bug we've known about for ages. Of
course,
sperber> we need to know if you're using pdump to be sure.
Mike,
It does indeed appear to be a problem with pdump. Once I enabled
USE_PORTABLE_DUMPER=1
The one I compiled started exhibiting the same behavior as the 21.2b36
binary
I downloaded off the net. If I breakpoint at src/indent.c line 317, the
debugger reports indent_tabs_mode = 1, even though describe-variable
indent-tabs-mode indicates the value is "nil".
That is indeed consistent with the behavior I'm seeing (it is
incorrectly inserting tabs instead of spaces).
APA> we need a lot more info. That's how problems can get solved: facts.
Adrian,
Apologies for not providing more information. I've not contributed bug
reports to xemacs list before, so am kinda new at this.
APA> How did you get the sources (CVS or tarballs)?
I used the xemacs-21.2-b36.tar.gz tarball. This same problem has been
reported
since b34, so I know it's somewhat long-standing. If the pdump bug has
been around a long time, that would explain it.
APA> So you did a Windows native build, right?
Yes, win32 native GUI... no X support... using MSVC 5.0, not cygwin.
APA> Please send us your xemacs/nt/config.inc file then.
My nt/config.inc included below. I took a pretty simple-minded approach and
put all the .h and .lib files for all the aux libraries in the same
directory.
Seemed to work OK.
APA> Did you use the portable dumper option (we can tell from config.inc)?
Not originally. And my .exe worked fine But once I followed Mike's
suggestion
and turned use of pdump on, the problem re-appeared with the version I
compiled
too.
I would be willing to troubleshoot further if someone could point the way,
but as I said.. I'm kinda new at this, so not sure how much progress I'd
make.
APA> These are just a few simple question on the way to solve the mystery.
Thanks for the feedback. Where should I go from here?
Troy
nt/config.inc:
--------------------------------- snip
