From: Stefan Monnier <monnier@iro.umontreal.ca>
To: covici@ccs.covici.com
Cc: emacs-devel@gnu.org
Subject: Re: emacs 23.1 and vm
Date: Sun, 09 Aug 2009 22:36:18 -0400 [thread overview]
Message-ID: <jwvskg04cqk.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <19071.9059.415476.629333@ccs.covici.com> (John covici's message of "Sun, 9 Aug 2009 15:28:35 -0400")
> Next time it happens, I can do that, but as I recall I got a lot of
> hex characters in the trace possibly because of .elc files?
hex characters basically mean we get less info, but it's still better
than nothing, so post them here.
Stefan
next prev parent reply other threads:[~2009-08-10 2:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-09 10:14 emacs 23.1 and vm John covici
2009-08-09 15:43 ` Chong Yidong
2009-08-09 19:28 ` John covici
2009-08-09 19:40 ` Eli Zaretskii
2009-08-09 20:00 ` John covici
2009-08-10 2:36 ` Stefan Monnier [this message]
2009-08-10 8:27 ` John covici
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvskg04cqk.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=covici@ccs.covici.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).