Thanks Era for looking into this.

The answer is "yes": If i start with
-q (or --no-init-file) it comes up
exactly the same.

So i don't think the fault is the
~/.emacs.

The *Messages* buffer has this in it:
   ("emacs")
   Loading encoded-kb...done
   command-line: Symbol's value as variable is void: on
independent of how emacs is started.

(I've also tried --debug-init, but i don't
even get to the ~/.emacs it looks like.)

Even if we don't get a fix we'd appreciate
any ideas for investigation.

dan


era wrote:
> I'm not sure I understand.  If you start up emacs with emacs -q, do you
> still get this error?
> 
> I'm setting the Status of this bug report to Incomplete to mark it as
> pending on a reply from you.  It can be set back to New once you supply
> the requested information.  Thank you.
> 
> ** Changed in: emacs22 (Ubuntu)
>        Status: New => Incomplete
>

-- 
Symbol's value as variable is void: on
https://bugs.launchpad.net/bugs/583133
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to