unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 5973@debbugs.gnu.org
Subject: bug#5973: Crash in get_next_display_element
Date: Tue, 20 Apr 2010 15:36:33 +0200	[thread overview]
Message-ID: <i2yf7ccd24b1004200636m6792123au9f38aac8c9cbfa83@mail.gmail.com> (raw)
In-Reply-To: <834oj65mr5.fsf@gnu.org>

On Tue, Apr 20, 2010 at 14:31, Eli Zaretskii <eliz@gnu.org> wrote:

> Right, now I see it as well (except that, the 1st time I use C-x n n,
> I need to answer the question about it being disabled;

Yes, of course.

> the crash
> happens the next time I invoke C-x n n).

Curious. Not so in my case. I answer with <space> and the crash just happens.

    Juanma






  reply	other threads:[~2010-04-20 13:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-19 16:08 bug#5973: Crash in get_next_display_element David Reitter
     [not found] ` <handler.5973.B.12716933351499.ack@debbugs.gnu.org>
2010-04-19 16:46   ` bug#5973: Acknowledgement (Crash in get_next_display_element) David Reitter
2010-04-19 17:31     ` Eli Zaretskii
2010-04-19 17:23 ` bug#5973: Crash in get_next_display_element Eli Zaretskii
2010-04-19 17:40   ` David Reitter
2010-04-19 18:26     ` Eli Zaretskii
2010-04-19 18:39       ` David Reitter
2010-04-19 18:43         ` Eli Zaretskii
2010-04-19 22:46       ` Juanma Barranquero
2010-04-20  8:23         ` Eli Zaretskii
2010-04-20  9:19           ` Juanma Barranquero
2010-04-20  9:56             ` Eli Zaretskii
2010-04-20 10:27               ` Juanma Barranquero
2010-04-20 12:31                 ` Eli Zaretskii
2010-04-20 13:36                   ` Juanma Barranquero [this message]
2010-04-20 13:56                   ` Juanma Barranquero
2010-04-20 10:21         ` Eli Zaretskii
2010-04-20 10:33           ` Juanma Barranquero
2010-04-20 12:23             ` 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

  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=i2yf7ccd24b1004200636m6792123au9f38aac8c9cbfa83@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=5973@debbugs.gnu.org \
    --cc=eliz@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).