From: Tassilo Horn <thorn@fastmail.fm>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 9375@debbugs.gnu.org
Subject: bug#9375: emacs -Q --eval '(imagemagick-register-types)' on console makes emacs loop
Date: Fri, 26 Aug 2011 21:43:21 +0200 [thread overview]
Message-ID: <87sjooyn52.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <4E57EC90.7030006@cs.ucla.edu> (Paul Eggert's message of "Fri, 26 Aug 2011 11:57:20 -0700")
Paul Eggert <eggert@cs.ucla.edu> writes:
Hi Paul,
> Just as another data point,
> I don't observe the problem on my host (Fedora 14 x86-64)
> with the current trunk version, bzr 105581.
Yes, it seems someone has already fixed the issue. With today's emacs,
the problem is gone.
Bye,
Tassilo
prev parent reply other threads:[~2011-08-26 19:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 18:56 bug#9375: 24.0.50; emacs -Q --eval '(imagemagick-register-types)' on console makes emacs loop Tassilo Horn
2011-08-26 18:57 ` bug#9375: " Paul Eggert
2011-08-26 19:43 ` Tassilo Horn [this message]
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=87sjooyn52.fsf@thinkpad.tsdh.de \
--to=thorn@fastmail.fm \
--cc=9375@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
/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).