Troy> I now have a few cycles to look at the portable dumper bug a Troy> little more, and figured out that (setq-default ) on an Troy> opaque type doesn't work properly after the dumper reloads Troy> it into memory. It appears to apply to Troy> SYMVAL_BOOLEAN_FORWARD variables (defined as DEFVAR_BOOLEAN) Troy> that are buffer local. Don't know yet if it's more Troy> pervasive than that. Troy> Who's the portable dump expert, and are there plans to fix Troy> this anytime soon? See Coding Projects in http://xemacs.sourceforge.net/Develop/jobs.html Troy> If not, I'd like to ask a few questions and see if I can fix Troy> it myself... but don't know if the list wants to see all Troy> that traffic, so could correspond with them offline if need Troy> be. xemacs-beta is the right list for that. Fixing these problems is highly desirable! Best regards, Adrian Troy> It may be as simple as making sure the opaque variables get Troy> into the reloc_table so they get handled by the call to Troy> pdump_reorganize_hash_table. I'm not sure yet though. Troy> dumper.c, Line 1040 is the last time the variable gets "touched" if Troy> my debugger watchpoint doesn't lie. Troy> /* Put back the opaques */ Troy> for (i=0; i<((dump_header *)pdump_start)->nb_opaquedmp; i++) Troy> { Troy> struct pdump_dumpopaqueinfo di = PDUMP_READ (p, struct Troy> pdump_dumpopaqueinfo); Troy> p += di.size; Troy> } Troy> Thanks, Troy -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org