From: Eli Zaretskii <eliz@gnu.org>
To: Eric Hanchrow <eric.hanchrow@gmail.com>
Cc: 22120@debbugs.gnu.org
Subject: bug#22120: Another backtrace
Date: Sun, 13 Dec 2015 20:22:40 +0200 [thread overview]
Message-ID: <83r3iq439r.fsf@gnu.org> (raw)
In-Reply-To: <CAHZoxq9AESxNDbCc6aESkTUsE4p7Mo22FGfEj+1shLc+AaHHhg@mail.gmail.com> (message from Eric Hanchrow on Sun, 13 Dec 2015 18:19:52 +0000)
> From: Eric Hanchrow <eric.hanchrow@gmail.com>
> Date: Sun, 13 Dec 2015 18:19:52 +0000
> Cc: 22120@debbugs.gnu.org
>
> I glanced through (info "(elisp) Undo") and didn't see any sort of warning.
> Should we add one? I can certainly stick something in there myself, but doubt
> it'd be quite correct.
Let's not get ahead of ourselves: first, let's see if my guess holds
any water, and only afterwards let's worry about documenting whatever
we find.
OK?
next prev parent reply other threads:[~2015-12-13 18:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 20:19 bug#22120: 25.1.50; segfault while running circe Eric Hanchrow
2015-12-08 20:33 ` Eli Zaretskii
2015-12-08 20:36 ` Eric Hanchrow
2015-12-08 20:54 ` Eli Zaretskii
2015-12-08 21:03 ` John Wiegley
2015-12-09 15:29 ` Eric Hanchrow
[not found] ` <83h9jrbl7b.fsf@gnu.org>
2015-12-09 19:13 ` Eric Hanchrow
2015-12-08 20:36 ` John Wiegley
2015-12-08 20:38 ` Eric Hanchrow
2015-12-10 18:42 ` bug#22120: Another backtrace Eric Hanchrow
2015-12-10 19:02 ` Eli Zaretskii
2015-12-10 19:15 ` Eric Hanchrow
2015-12-10 19:30 ` Eli Zaretskii
2015-12-12 22:37 ` Eric Hanchrow
2015-12-13 15:27 ` Eli Zaretskii
2015-12-13 17:54 ` Eric Hanchrow
2015-12-13 18:04 ` Eli Zaretskii
2015-12-13 18:07 ` Eric Hanchrow
2015-12-13 18:13 ` Eli Zaretskii
2015-12-13 18:19 ` Eric Hanchrow
2015-12-13 18:22 ` Eli Zaretskii [this message]
2015-12-13 18:29 ` Eric Hanchrow
2015-12-24 3:24 ` Eric Hanchrow
2015-12-24 16:12 ` Eli Zaretskii
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=83r3iq439r.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22120@debbugs.gnu.org \
--cc=eric.hanchrow@gmail.com \
/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.