Strange font problem stops emacs from starting

Strange font problem stops emacs from starting

[Fabrice DELENTE]

Hello.

I have a private font that I update regularly to add new glyphs.

It is a personal version of helvetiva 12, for internal and private use
in emacs only.

Today I added a new glyph with fontforge, as I have done many times before.

But when I wnated to start emacs, it gave


$ /usr/bin/emacs -geometry 92x64+0+0 -fn "lutRS12" -q
Variable binding depth exceeds max-specpdl-size

I tried that with emacs -q, but the problem is still there.

If I don't give the '-fn "lutRS12"', or if I use the previous version
of my font, it works...

It seems as if emacs chokes on too much glyphs??

This is with

$ /usr/bin/emacs --version
GNU Emacs 22.3.1

Any hint?

Thanks!

-- 
F. Delente

Re: Strange font problem stops emacs from starting

[Peter Dyballa]

Am 08.09.2010 um 20:29 schrieb Fabrice DELENTE:

> Any hint?


The "font server" department of your X server caches fonts. Try to use  
xset (xset fp ...) to remove the path element with your font file,  
then make the X server rehash (to clean its caches), add the just  
removed path element again, and finally invoke the rehash again.

--
Greetings

   Pete

Rain is saved up in cloud banks.

Re: Strange font problem stops emacs from starting

[Fabrice DELENTE]

> The "font server" department of your X server caches fonts. Try to use  
> xset (xset fp ...) to remove the path element with your font file,  
> then make the X server rehash (to clean its caches), add the just  
> removed path element again, and finally invoke the rehash again.

Thanks, I tried it but it didn't solve my problem.

-- 
F. Delente

Re: Strange font problem stops emacs from starting

[Peter Dyballa]

Am 09.09.2010 um 12:53 schrieb Fabrice DELENTE:

> Thanks, I tried it but it didn't solve my problem.


Shutting down the X server?

--
Greetings

   Pete

When confronted with actual numbers, a mathematician is at a loss.
				– Steffen Hokland

Re: Strange font problem stops emacs from starting

[Fabrice DELENTE]

> >Thanks, I tried it but it didn't solve my problem.
> 
> 
> Shutting down the X server?

Tried that too, but it doesn't change anything. I think the problem is
really in emacs, not in X.

I have saved my font in a state that works with emacs, then modified it and
restarted emacs: I have the error.

If I immediately copy back the working font and restart emacs, it works,
without leaving the X server and even without using xset fp rehash.

Is there a way to know which variable has bindings that exceed
max-specpdl-size?

Thanks.

-- 
F. Delente

Re: Strange font problem stops emacs from starting

[Peter Dyballa]

Am 12.09.2010 um 09:11 schrieb Fabrice DELENTE:

> Is there a way to know which variable has bindings that exceed
> max-specpdl-size?


There is some indirect way:

	(setq debug-on-error t)

Inserted close to the beginning of your init file, or launching GNU  
Emacs with --debug-init, will create a *Backtrace* buffer which will  
contain the last few commands executed before the error happened, in  
reverse order, the last one on top. Maybe it helps to know this  
command and the sequence to it...

--
Greetings

   Pete

Sometimes I think the surest sign that intelligent life exists  
elsewhere in the universe is that none of it has tried to contact us.
		– Bill Watterson, in his comic strip Calvin and Hobbes

Re: Strange font problem stops emacs from starting

[Fabrice DELENTE]

I've just tried setting max-specpdl-size to 2000 instead of 1000, but the
error is still there.

-- 
F. Delente

Re: Strange font problem stops emacs from starting

[tomas]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sun, Sep 12, 2010 at 09:24:44AM +0200, Fabrice DELENTE wrote:
> I've just tried setting max-specpdl-size to 2000 instead of 1000, but the
> error is still there.

Hi,

you might try to pinpoint the problem setting "debug-on-error" to true.
You achieve this either by putting

  (setq debug-on-error t)

early in your .emacs or (even better) by adding the command line option

  --debug-init

to the emacs invocation.

You should get a stack trace leading us to the spot where this error is
detected.

Regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFMjJG1Bcgs9XrR2kYRAnPbAJ4lZQNqYZkkgXjV1gPdXQtu1/DHUwCfbEK4
s4fk4VsO8iP28HYY6XVq86k=
=2aCB
-----END PGP SIGNATURE-----