error entering dired

error entering dired

[Michael Powe]

Hello,

After opening emacs and trying to enter dired mode, I get this message
and dired buffer will not open:

font-lock-eval-keywords: Lisp nesting exceeds `max-lisp-eval-depth'

other functionality, such as gnus and using JDE to create/edit java
source, seems to be working fine.

This was all working on my old slackware system, I just changed to
ubuntu 7.10 today, and copied over my .emacs &c to the new system.  The
old system was emacs 21 and the new one is emacs 22.

Any thoughts on what could have changed between the two versions that
would cause this behavior?

Thanks.

mp

-- 
cat: /home/powem/.signature: No such file or directory

Re: error entering dired

[Martin Fischer]

  >>>>> Michael Powe writes:
  > Date: Thu, 27 Dec 2007 13:48:47 -0500
  > 
  > Hello,
  > 
  > After opening emacs and trying to enter dired mode, I get this message
  > and dired buffer will not open:
  > 
  > font-lock-eval-keywords: Lisp nesting exceeds `max-lisp-eval-depth'
  > 
  > other functionality, such as gnus and using JDE to create/edit java
  > source, seems to be working fine.
  > 
  > This was all working on my old slackware system, I just changed to
  > ubuntu 7.10 today, and copied over my .emacs &c to the new system.  The
  > old system was emacs 21 and the new one is emacs 22.
  > 
  > Any thoughts on what could have changed between the two versions that
  > would cause this behavior?
  > 
  > Thanks.
  > 
  > mp
  > 
  > -- 
  > cat: /home/powem/.signature: No such file or directory
  > 

Hi,

my thoughts:

  - what is in your .emacs ?

  - what is in your *Message* buffer when you start emacs ?

  - what happens if you start emacs with the option --debug-init ?

Martin
-- 
parozusa at web dot de

Re: error entering dired

[Michael Powe]

>>>>> "Martin" == Martin Fischer <nospam@nospam.net> writes:

    >>>>>> Michael Powe writes:
    >> Date: Thu, 27 Dec 2007 13:48:47 -0500

    >> After opening emacs and trying to enter dired mode, I get this
    >> message and dired buffer will not open:

    >> font-lock-eval-keywords: Lisp nesting exceeds
    >> `max-lisp-eval-depth'

    >> other functionality, such as gnus and using JDE to create/edit
    >> java source, seems to be working fine.

    >> This was all working on my old slackware system, I just changed
    >> to ubuntu 7.10 today, and copied over my .emacs &c to the new
    >> system.  The old system was emacs 21 and the new one is emacs
    >> 22.

    >> Any thoughts on what could have changed between the two
    >> versions that would cause this behavior?

    Martin> my thoughts:

    Martin>   - what is in your .emacs ?

    Martin>   - what is in your *Message* buffer when you start emacs
    Martin> ?

    Martin>   - what happens if you start emacs with the option
    Martin> --debug-init ?

Hello,

Thanks for the reply.  There is quite a bit in the .emacs, actually
but no init errors are generated.  Here is the content of the
*Messages* buffer after starting with --debug-init.  Quite long,
sorry.

Thanks.

mp

("emacs" "--debug-init")
Loading 00debian-vars...
No /etc/mailname. Reverting to default...
Loading 00debian-vars...done
Loading /etc/emacs/site-start.d/50dictionaries-common.el (source)...
Loading debian-ispell...
Loading /var/cache/dictionaries-common/emacsen-ispell-default.el (source)...done
Loading debian-ispell...done
Loading /var/cache/dictionaries-common/emacsen-ispell-dicts.el (source)...done
Loading /etc/emacs/site-start.d/50dictionaries-common.el (source)...done
Loading /home/powem/share/emacs/lisp/cedet-1.0pre3/common/cedet.el (source)...
"/home/powem/share/emacs/lisp/cedet-1.0pre3/common/" added to `load-path'
Loading cl-macs...done
"/home/powem/share/emacs/lisp/cedet-1.0pre3/cogre" added to `load-path'
"/home/powem/share/emacs/lisp/cedet-1.0pre3/ede" added to `load-path'
"/home/powem/share/emacs/lisp/cedet-1.0pre3/eieio" added to `load-path'
"/home/powem/share/emacs/lisp/cedet-1.0pre3/semantic" added to `load-path'
"/home/powem/share/emacs/lisp/cedet-1.0pre3/speedbar" added to `load-path'
"/home/powem/share/emacs/lisp/cedet-1.0pre3/contrib" added to `load-path'
Setting up cedet...done
Setting up cogre...done
Setting up ede...done
Setting up eieio...done
Setting up semantic...
Loading derived...done
Loading advice...done
Loading semantic-idle...
Loading easymenu...done
Loading semantic-idle...done
Loading semanticdb...done
Setting up semantic...done
Setting up speedbar...done
Setting up cedet-contrib...done
Loading /home/powem/share/emacs/lisp/cedet-1.0pre3/common/cedet.el (source)...done
jde-java-font-lock: building names cache...empty
Loading bytecomp...done
Loading byte-opt...done
Loading /home/powem/.recentf...done
Cleaning up the recentf list...done (0 removed)
Loading /home/powem/.abbrev_defs...done
Loading ange-ftp...done
Loading time...done
Loading diary-lib...done
Preparing diary...
Loading holidays...done
Loading cal-hebrew...done
Loading cal-islam...done
Loading cal-china...done
No diary entries for Thursday, December 27, 2007
Loading /home/powem/.cc-mode...done
Loading mailcrypt...done
Loading mc-setversion...done
PGP version set to GPG.
Loading semantic-el...done
For information about the GNU Project and its goals, type C-h C-p. [2 times]
Mark set


-- 
cat: /home/powem/.signature: No such file or directory

Re: error entering dired

[Tassilo Horn]

Michael Powe <michael+gnus@trollope.org> writes:

Hi Michael,

> After opening emacs and trying to enter dired mode, I get this message
> and dired buffer will not open:
>
> font-lock-eval-keywords: Lisp nesting exceeds `max-lisp-eval-depth'

Please start a fresh emacs, do `M-x toggle-debug-on-error' and then try
to start dired.  Then poste what's in the *Backtrace* and *Messages*
buffer.

Bye,
Tassilo

Re: error entering dired

[Michael Powe]

>>>>> "Tassilo" == Tassilo Horn <tassilo@member.fsf.org> writes:

    >> After opening emacs and trying to enter dired mode, I get this
    >> message and dired buffer will not open:
    >> 
    >> font-lock-eval-keywords: Lisp nesting exceeds
    >> `max-lisp-eval-depth'

    Tassilo> Please start a fresh emacs, do `M-x
    Tassilo> toggle-debug-on-error' and then try to start dired.  Then
    Tassilo> poste what's in the *Backtrace* and *Messages* buffer.

Hello,

Below are the results of the backtrace.  Note that after I did this, i
tried to start gnus to send the information and got the same error
message when gnus started.  I then had to quit emacs and start again
to get back here.  Things to make you go 'hmm.'

Thanks.

mp

============ backtrace ==================
Debugger entered--Lisp error: (error "Lisp nesting exceeds `max-lisp-eval-depth'")
  font-lock-eval-keywords(t)
  [ ... this entry repeats 285 times ... ]
  font-lock-eval-keywords(t)
  font-lock-eval-keywords(t)
  font-lock-eval-keywords(t)
  font-lock-eval-keywords(dired-font-lock-keywords)
  font-lock-set-defaults()
  font-lock-mode-internal(t)
  font-lock-default-function(t)
  font-lock-mode()
  turn-on-font-lock()
  turn-on-font-lock-if-enabled()
  global-font-lock-mode-enable-in-buffers()
  run-hooks(after-change-major-mode-hook)
  run-mode-hooks(dired-mode-hook)
  dired-mode("~/" "-al")
  dired-internal-noselect("~/" nil)
  dired-noselect("~/" nil)
  dired("~/" nil)
  call-interactively(dired)
=========== end backtrace ==================
=========== messages =======================
("emacs")
Loading encoded-kb...done
Loading 00debian-vars...
No /etc/mailname. Reverting to default...
Loading 00debian-vars...done
Loading /etc/emacs/site-start.d/50dictionaries-common.el (source)...
Loading debian-ispell...
Loading /var/cache/dictionaries-common/emacsen-ispell-default.el (source)...done
Loading debian-ispell...done
Loading /var/cache/dictionaries-common/emacsen-ispell-dicts.el (source)...done
Loading /etc/emacs/site-start.d/50dictionaries-common.el (source)...done
Loading /home/powem/share/emacs/lisp/cedet-1.0pre3/common/cedet.el (source)...
"/home/powem/share/emacs/lisp/cedet-1.0pre3/common/" added to `load-path'
Loading cl-macs...done
"/home/powem/share/emacs/lisp/cedet-1.0pre3/cogre" added to `load-path'
"/home/powem/share/emacs/lisp/cedet-1.0pre3/ede" added to `load-path'
"/home/powem/share/emacs/lisp/cedet-1.0pre3/eieio" added to `load-path'
"/home/powem/share/emacs/lisp/cedet-1.0pre3/semantic" added to `load-path'
"/home/powem/share/emacs/lisp/cedet-1.0pre3/speedbar" added to `load-path'
"/home/powem/share/emacs/lisp/cedet-1.0pre3/contrib" added to `load-path'
Setting up cedet...done
Setting up cogre...done
Setting up ede...done
Setting up eieio...done
Setting up semantic...
Loading derived...done
Loading advice...done
Loading semantic-idle...
Loading easymenu...done
Loading semantic-idle...done
Loading semanticdb...done
Setting up semantic...done
Setting up speedbar...done
Setting up cedet-contrib...done
Loading /home/powem/share/emacs/lisp/cedet-1.0pre3/common/cedet.el (source)...done
jde-java-font-lock: building names cache...empty
Loading bytecomp...done
Loading byte-opt...done
Loading /home/powem/.recentf...done
Cleaning up the recentf list...done (0 removed)
Loading /home/powem/.abbrev_defs...done
Loading ange-ftp...done
Loading time...done
Loading diary-lib...done
Preparing diary...
Loading holidays...done
Loading cal-hebrew...done
Loading cal-islam...done
Loading cal-china...done
No diary entries for Friday, December 28, 2007
Loading /home/powem/.cc-mode...done
Loading mailcrypt...done
Loading mc-setversion...done
PGP version set to GPG.
Loading semantic-el...done
For information about the GNU Project and its goals, type C-h C-p.
Making completion list...
Loading eieio-opt...done
Debug on Error enabled globally
Loading dired...done
Loading debug...done
Entering debugger...

=========== end messages ===================

-- 
cat: /home/powem/.signature: No such file or directory

Re: error entering dired

[Sven Joachim]

On 2007-12-28 15:42 +0100, Michael Powe wrote:

> Loading /home/powem/share/emacs/lisp/cedet-1.0pre3/common/cedet.el (source)...
> "/home/powem/share/emacs/lisp/cedet-1.0pre3/common/" added to `load-path'
> Loading cl-macs...done
> "/home/powem/share/emacs/lisp/cedet-1.0pre3/cogre" added to `load-path'
> "/home/powem/share/emacs/lisp/cedet-1.0pre3/ede" added to `load-path'
> "/home/powem/share/emacs/lisp/cedet-1.0pre3/eieio" added to `load-path'
> "/home/powem/share/emacs/lisp/cedet-1.0pre3/semantic" added to `load-path'
> "/home/powem/share/emacs/lisp/cedet-1.0pre3/speedbar" added to `load-path'
> "/home/powem/share/emacs/lisp/cedet-1.0pre3/contrib" added to `load-path'

Maybe this is not related to your problem, but you definitely should not
use cedet versions prior to 1.0pre4, see [1], for instance.  Just
install the Ubuntu package and get rid of the outdated version in your
home directory.

[1] https://bugs.launchpad.net/ubuntu/+source/cedet/+bug/72867

Re: error entering dired

[Michael Powe]

>>>>> "Sven" == Sven Joachim <svenjoac@gmx.de> writes:

    Sven> On 2007-12-28 15:42 +0100, Michael Powe wrote:
    >> Loading
    >> /home/powem/share/emacs/lisp/cedet-1.0pre3/common/cedet.el
    >> (source)...
    >> "/home/powem/share/emacs/lisp/cedet-1.0pre3/common/" added to
    >> `load-path' Loading cl-macs...done
    >> "/home/powem/share/emacs/lisp/cedet-1.0pre3/cogre" added to
    >> `load-path' "/home/powem/share/emacs/lisp/cedet-1.0pre3/ede"
    >> added to `load-path'
    >> "/home/powem/share/emacs/lisp/cedet-1.0pre3/eieio" added to
    >> `load-path'
    >> "/home/powem/share/emacs/lisp/cedet-1.0pre3/semantic" added to
    >> `load-path'
    >> "/home/powem/share/emacs/lisp/cedet-1.0pre3/speedbar" added to
    >> `load-path'
    >> "/home/powem/share/emacs/lisp/cedet-1.0pre3/contrib" added to
    >> `load-path'

    Sven> Maybe this is not related to your problem, but you
    Sven> definitely should not use cedet versions prior to 1.0pre4,
    Sven> see [1], for instance.  Just install the Ubuntu package and
    Sven> get rid of the outdated version in your home directory.

    Sven> [1]
    Sven> https://bugs.launchpad.net/ubuntu/+source/cedet/+bug/72867

Thanks, I will follow up on that.  The JDE setup was copied over
verbatim from my old emacs 21 config, which was working.  JDE
configuration is very finicky and even seemingly harmless changes
(like upgrading individual packages) has been known to break it.

I'll look at the new cedet.  Thanks.

mp

-- 
cat: /home/powem/.signature: No such file or directory

Re: error entering dired

[Michael Powe]

>>>>> "Sven" == Sven Joachim <svenjoac@gmx.de> writes:

    Sven> On 2007-12-28 15:42 +0100, Michael Powe wrote:
    >> Loading
    >> /home/powem/share/emacs/lisp/cedet-1.0pre3/common/cedet.el
    >> (source)...
    >> "/home/powem/share/emacs/lisp/cedet-1.0pre3/common/" added to
    >> `load-path' Loading cl-macs...done
    >> "/home/powem/share/emacs/lisp/cedet-1.0pre3/cogre" added to
    >> `load-path' "/home/powem/share/emacs/lisp/cedet-1.0pre3/ede"
    >> added to `load-path'
    >> "/home/powem/share/emacs/lisp/cedet-1.0pre3/eieio" added to
    >> `load-path'
    >> "/home/powem/share/emacs/lisp/cedet-1.0pre3/semantic" added to
    >> `load-path'
    >> "/home/powem/share/emacs/lisp/cedet-1.0pre3/speedbar" added to
    >> `load-path'
    >> "/home/powem/share/emacs/lisp/cedet-1.0pre3/contrib" added to
    >> `load-path'

    Sven> Maybe this is not related to your problem, but you
    Sven> definitely should not use cedet versions prior to 1.0pre4,
    Sven> see [1], for instance.  Just install the Ubuntu package and
    Sven> get rid of the outdated version in your home directory.

Hello,

I followed your advice and upgraded JDE and CEDET.  It did not solve
the dired problem.  However, it did solve another peculiarity, which
was that JDE compile command would not work (seemed to freeze up) but
the JDE run application command DID work (e.g., I went to command line
and compiled java file, I could run it from emacs buffer with C-c C-v
C-r).

so, Thanks!

mp

-- 
cat: /home/powem/.signature: No such file or directory

Re: error entering dired

[martin rudalics]

 > Below are the results of the backtrace.  Note that after I did this, i
 > tried to start gnus to send the information and got the same error
 > message when gnus started.  I then had to quit emacs and start again
 > to get back here.  Things to make you go 'hmm.'

If the bug shows up with Emacs -Q please send a bug report.  Otherwise,
step by step evaluate your .emacs until the bug gets reported and post
your findings here.

Re: error entering dired

[Tassilo Horn]

Michael Powe <michael+gnus@trollope.org> writes:

Hi Michael,

> ============ backtrace ==================
> Debugger entered--Lisp error: (error "Lisp nesting exceeds `max-lisp-eval-depth'")
>   font-lock-eval-keywords(t)
>   [ ... this entry repeats 285 times ... ]
>   font-lock-eval-keywords(t)
>   font-lock-eval-keywords(t)
>   font-lock-eval-keywords(t)
>   font-lock-eval-keywords(dired-font-lock-keywords)
>   font-lock-set-defaults()
>   font-lock-mode-internal(t)
>   font-lock-default-function(t)
>   font-lock-mode()
>   turn-on-font-lock()
>   turn-on-font-lock-if-enabled()
>   global-font-lock-mode-enable-in-buffers()
>   run-hooks(after-change-major-mode-hook)
>   run-mode-hooks(dired-mode-hook)
>   dired-mode("~/" "-al")
>   dired-internal-noselect("~/" nil)
>   dired-noselect("~/" nil)
>   dired("~/" nil)
>   call-interactively(dired)
> =========== end backtrace ==================

Please check if the problem persists with "emacs -Q" and "emacs -q".  If
not, then the problem is in your ~/.emacs.  In that case please poste
all lines of it which might have something to do with font-locking.

Bye,
Tassilo
-- 
GNU Emacs is a text editor for Über-Geeks.

Re: error entering dired

[Nick Roberts]

 > Please check if the problem persists with "emacs -Q" and "emacs -q".  If
 > not, then the problem is in your ~/.emacs.  In that case please poste
 > all lines of it which might have something to do with font-locking.

Or better, split it in two and see which half causes the problem.  Then repeat
the process until you have identified the relevant expression and post that.

-- 
Nick                                           http://www.inet.net.nz/~nickrob

Re: error entering dired

[reader]

Nick Roberts <nickrob@snap.net.nz> writes:

>  > Please check if the problem persists with "emacs -Q" and "emacs -q".  If

[...]

Sorry to butt into this with a different topic but what does the
uppercase Q signify?  

emacs --help and `man emacs' show nothing using -Q (uppercase)

Re: error entering dired

[Nick Roberts]

reader@newsguy.com writes:
 > Sorry to butt into this with a different topic but what does the
 > uppercase Q signify?  
 >
 > emacs --help and `man emacs' show nothing using -Q (uppercase)

Then you must have Emacs 21 or earlier.  Emacs 22 gives:

--quick, -Q                 equivalent to -q --no-site-file --no-splash

-- 
Nick                                           http://www.inet.net.nz/~nickrob

Re: error entering dired

[reader]

Nick Roberts <nickrob@snap.net.nz> writes:

> reader@newsguy.com writes:
>  > Sorry to butt into this with a different topic but what does the
>  > uppercase Q signify?  
>  >
>  > emacs --help and `man emacs' show nothing using -Q (uppercase)
>
> Then you must have Emacs 21 or earlier.  Emacs 22 gives:
>
> --quick, -Q                 equivalent to -q --no-site-file --no-splash

There may be something jacked up in my install but I'm running 22.
It was installed by the portage tools on gentoo emacs.  Might be a bug
for the installer or something.  I have had older versions installed
way back.

(wrapped for mail)
Its a symlink to what appears to be the proper man page for 22.1
ls -l /usr/share/man/man1/emacs.1.bz2
lrwxrwxrwx [...] Dec 22 12:47 \
                /usr/share/man/man1/emacs.1.bz2 -> emacs-emacs-22.1.bz2

Re: error entering dired

[Nick Roberts]

 > There may be something jacked up in my install but I'm running 22.
 > It was installed by the portage tools on gentoo emacs.  Might be a bug
 > for the installer or something.  I have had older versions installed
 > way back.
 > 
 > (wrapped for mail)
 > Its a symlink to what appears to be the proper man page for 22.1
 > ls -l /usr/share/man/man1/emacs.1.bz2
 > lrwxrwxrwx [...] Dec 22 12:47 \
 >                 /usr/share/man/man1/emacs.1.bz2 -> emacs-emacs-22.1.bz2

It looks like a Gentoo problem.  What does it say at the end of the manpage?
I get:


GNU Emacs 22.1                   2007 April 13                        EMACS(1)


-- 
Nick                                           http://www.inet.net.nz/~nickrob

Re: error entering dired

[Tassilo Horn]

Nick Roberts <nickrob@snap.net.nz> writes:

>  > (wrapped for mail)
>  > Its a symlink to what appears to be the proper man page for 22.1
>  > ls -l /usr/share/man/man1/emacs.1.bz2
>  > lrwxrwxrwx [...] Dec 22 12:47 \
>  >                 /usr/share/man/man1/emacs.1.bz2 -> emacs-emacs-22.1.bz2
>
> It looks like a Gentoo problem.  What does it say at the end of the manpage?
> I get:
>
>
> GNU Emacs 22.1                   2007 April 13                        EMACS(1)

Gentoo has a tool called eselect-emacs that allows multiple emacs
versions being installed.  Do

  $ eselect emacs list

which will print all installed profiles and

  $ eselect emacs set <profile>

to select one.  That should make all symlink point to the right
location.

Bye,
Tassilo

Re: error entering dired

[reader]

Nick Roberts <nickrob@snap.net.nz> writes:

> It looks like a Gentoo problem.  What does it say at the end of the manpage?
> I get:

Not really, it was my own doing.  I'd built an emacs quite some time
ago on /usr/local ... I've forgotten why now... I think checking
something out about a gentoo specific file being read before
site-start.el or something like that.

Anyway those old man pages were still there but with Tasillo help I've
gotten it staightened out.

Re: error entering dired

[reader]

Tassilo Horn <tassilo@member.fsf.org> writes:

>   $ eselect emacs set <profile>
>
> to select one.  That should make all symlink point to the right
> location.

Nice tip... thanks.  I only recently started letting gentoo keep track
of emacs as all.  I wondered what those various eselect things really
did but not enough to look into it.