From: "Herbert Euler" <herberteuler@hotmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Max-specpdl-size Bug in Emacs Lisp Interpreter?
Date: Tue, 18 Apr 2006 22:07:26 +0800 [thread overview]
Message-ID: <BAY112-F3367945CC36922647DAF97DAC40@phx.gbl> (raw)
In-Reply-To: <85bquzmlv2.fsf@lola.goethe.zz>
>From: David Kastrup <dak@gnu.org>
>To: "Herbert Euler" <herberteuler@hotmail.com>
>CC: rms@gnu.org, emacs-devel@gnu.org
>Subject: Re: Max-specpdl-size Bug in Emacs Lisp Interpreter?
>Date: Tue, 18 Apr 2006 08:36:01 +0200
>
>The mailing list is not a single person, and you better get used to
>it. You can't expect everybody with an opinion on a question to read
>the list hourly for your sake.
So you minunderstood me. Of course, I didn't mean I want a reply
within an hour. I'm sorry, I didn't express it clearly.
When I posted this thread, I just wanted to confirm whether it's a bug.
Perhaps I should post it in bug-gnu-emacs, but since I was not sure about
it and most Emacs developers read threads in this list as well, I posted it
here. Did you notice the last sentence? It's "Does this imply a bug in
Emacs Lisp interpreter?" Simply "no" is also an answer. After that, most
developers had followed other threads, but didn't follow this one. And
I then replied it myself, but again got no response after another day, in
which most developers had read this mailing list again. And so on. I'm
not an Emacs developer, and also not familar with Emacs internals. I
believe Emacs developers know about it, so I subscribe this mailing list
and post. Appearntly I'm too anxious to say "no response", for I'm
not sure does there someone notice that, and thread last more than
several days definitely will be forgot.
Sincerely,
Guanpeng Xu
_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar - get it now!
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
next prev parent reply other threads:[~2006-04-18 14:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-16 7:59 Max-specpdl-size Bug in Emacs Lisp Interpreter? Herbert Euler
2006-04-17 2:40 ` Herbert Euler
2006-04-17 9:06 ` Romain Francoise
2006-04-18 1:41 ` Richard Stallman
2006-04-18 3:20 ` Herbert Euler
2006-04-18 6:36 ` David Kastrup
2006-04-18 14:07 ` Herbert Euler [this message]
2006-04-18 11:25 ` Juanma Barranquero
2006-04-18 20:50 ` Richard Stallman
2006-04-19 1:43 ` Herbert Euler
2006-04-17 17:56 ` Richard Stallman
2006-04-18 2:18 ` Herbert Euler
2006-04-18 2:22 ` Miles Bader
2006-04-18 5:44 ` Luc Teirlinck
2006-04-18 20:50 ` Richard Stallman
2006-04-18 23:34 ` Miles Bader
2006-04-18 23:43 ` David Kastrup
2006-04-19 3:07 ` Herbert Euler
2006-04-19 15:40 ` Richard Stallman
2006-04-19 2:59 ` Herbert Euler
2006-04-19 3:47 ` Luc Teirlinck
2006-04-19 4:03 ` Luc Teirlinck
2006-04-19 5:11 ` Herbert Euler
-- strict thread matches above, loose matches on Subject: below --
2006-04-18 13:51 Herbert Euler
2006-04-15 8:24 Herbert Euler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BAY112-F3367945CC36922647DAF97DAC40@phx.gbl \
--to=herberteuler@hotmail.com \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.