From: "Stefan-W. Hahn" <stefan.hahn@s-hahn.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 17281@debbugs.gnu.org
Subject: bug#17281: 24.4.50; emacs hangs in next-line
Date: Thu, 17 Apr 2014 09:25:23 +0200 [thread overview]
Message-ID: <20140417072523.GC23131@pille.home> (raw)
In-Reply-To: <834n1sjuo1.fsf@gnu.org>
Mail von Eli Zaretskii, Thu, 17 Apr 2014 at 10:13:02 +0300:
> > Date: Thu, 17 Apr 2014 08:10:37 +0200
> > From: "Stefan-W. Hahn" <stefan.hahn@s-hahn.de>
> >
> > In GNU Emacs 24.4.50.2 (i686-pc-linux-gnu, GTK+ Version 2.24.10)
> > of 2014-03-31 on pille
> >
> > commit 79bbb1454f3e44bf69096f03c26bb42f4930e591
>
> Thanks for the report, but please don't cite git sha1 values alone to
> specify a commit; please show the full commit log message instead. As
> long as we use bzr as the primary VCS, git sha values don't bring
> enough information to identify a commit, not without some extra work.
Sorry,
commit 79bbb1454f3e44bf69096f03c26bb42f4930e591
Author: Dmitry Antipov <dmantipov@yandex.ru>
Date: Mon Mar 31 11:13:58 2014 +0400
* search.c (Freplace_match): Use make_specified_string.
* xterm.c, w32term.c (x_set_glyph_string_gc): Use emacs_abort
to catch bogus override face of glyph strings.
>
> > Stripping this down it seems, that (next-line) is the problem.
>
> Sounds like another duplicate of 17269. Does setting cache-long-scans
> to nil solve the problem?
No it does not solve it.
With kind regards,
Stefan
--
Stefan-W. Hahn It is easy to make things.
It is hard to make things simple.
next prev parent reply other threads:[~2014-04-17 7:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 6:10 bug#17281: 24.4.50; emacs hangs in next-line Stefan-W. Hahn
2014-04-17 7:13 ` Eli Zaretskii
2014-04-17 7:25 ` Stefan-W. Hahn [this message]
2014-04-17 8:00 ` Eli Zaretskii
2014-04-17 8:29 ` Stefan-W. Hahn
2014-04-17 9:03 ` Eli Zaretskii
2014-04-17 10:16 ` Eli Zaretskii
2014-04-17 11:00 ` Stefan-W. Hahn
2014-04-17 11:25 ` Eli Zaretskii
2014-04-17 12:39 ` Stefan Monnier
2014-04-17 12:37 ` Stefan Monnier
2014-04-17 12:47 ` Eli Zaretskii
2014-04-17 13:16 ` Stefan Monnier
2014-04-17 12:56 ` Stefan-W. Hahn
2014-04-17 13:13 ` 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=20140417072523.GC23131@pille.home \
--to=stefan.hahn@s-hahn.de \
--cc=17281@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).