[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Local elisp library files and variable corruption

From: Tom
Subject: Re: Local elisp library files and variable corruption
Date: Sun, 26 Jun 2016 05:29:26 +0000 (UTC)
User-agent: Loom/3.14 (http://gmane.org/)

Eli Zaretskii <eliz <at> gnu.org> writes:
> > 
> >         The variable `after-init-hook' then appears to be corrupted:
> > 
> > after-init-hook is a variable defined in ‘startup.el’.
> > Its value is (#[0 "\305\211\235\203\306\"\301\307!\210\210
\205(\n\205 \205 \310 ?\311 \210\312\211)\207"
> >      [command-line-args desktop-save-mode desktop-restore-frames
> inhibit-startup-screen "--no-desktop" delete 0 daemonp desktop-read t]
> >      4]
> >  x-wm-set-size-hint)
> Why do you say this is corrupted?  It looks like bytecode to me.

Wouldn't it be better if describe-variable didn't just dump the bytecode
there with octal sequences and stuff, confusing users who don't know
what that is? 

If it can detect a bytecoded value then it could say the value is
bytecoded and there could be a button or something to show the actual
bytecode if somebody wants to see it.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]