unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Joe Wells <jbw@csb.bu.edu>
To: gnu-emacs-bug@moderators.isc.org
Subject: Re: strange Emacs 22.1 failure due to utf-8-compose-scripts when --no-window-system used
Date: 10 Jul 2007 17:21:56 -0400	[thread overview]
Message-ID: <xnjps30x8cr.fsf@csb.bu.edu> (raw)
In-Reply-To: mailman.2921.1183318164.32220.bug-gnu-emacs@gnu.org

Can anyone else reproduce the problem I describe below?

Joe

Joe Wells <jbw@macs.hw.ac.uk> writes:

> Dear Emacs gurus
> Run the script below to see an interesting failure.  These 3
> ingredients are needed:
>
> 1. The environment variable LC_CTYPE (or probably LANG or LC_ALL, but
>    I haven't checked those variables) must be set (probably to a UTF-8
>    locale, but I haven't checked any locales other than "C" (no bug)
>    and "en_US.UTF-8" (bug)).
> 2. The --no-window-system command-line argument must be used.
> 3. The variable utf-8-compose-scripts must be set.
>
> At this point, various things start failing strangely.  The script
> demonstrates one of the failures.
>
> I hope this helps.
>
> Joe
>
> ----------------------------------------------------------------------
> #!/bin/sh
> #
> export LC_CTYPE=en_US.UTF-8
> emacs --no-window-system --quick --eval '(setq utf-8-compose-scripts t)' --load "lao-util"
> #
> # You will now see an error message like this one (replace XYZZY by
> # the appropriate path for your system):
> #
> # utf-8-post-read-conversion: Recursive load: "XYZZY/share/emacs/22.1/lisp/language/lao-util.elc", "XYZZY/share/emacs/22.1/lisp/emacs-lisp/regexp-opt.elc", "XYZZY/share/emacs/22.1/lisp/language/lao-util.elc", "XYZZY/share/emacs/22.1/lisp/language/lao-util.elc", "/home/jbw/local2/share/emacs/22.1/lisp/emacs-lisp/regexp-opt.elc", "XYZZY/share/emacs/22.1/lisp/language/lao-util.elc", "XYZZY/share/emacs/22.1/lisp/language/lao-util.elc"
> #
> # In fact, lots of things will fail with this error message after this point.
> ----------------------------------------------------------------------
>
> In GNU Emacs 22.1.1 (i686-pc-linux-gnu, GTK+ Version 2.8.20)
>  of 2007-06-27 on artemis
> Windowing system distributor `The X.Org Foundation', version 11.0.70000000
> configured using `configure  '--prefix=/home/jbw/local2' '--enable-debug' '--disable-nls' '--with-x-toolkit=gtk' 'CFLAGS=-O0 -g3 -ggdb''
>
> Important settings:
>   value of $LC_ALL: nil
>   value of $LC_COLLATE: nil
>   value of $LC_CTYPE: en_US.UTF-8
>   value of $LC_MESSAGES: nil
>   value of $LC_MONETARY: nil
>   value of $LC_NUMERIC: nil
>   value of $LC_TIME: jbw
>   value of $LANG: nil
>   locale-coding-system: utf-8
>   default-enable-multibyte-characters: t

       reply	other threads:[~2007-07-10 21:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.2921.1183318164.32220.bug-gnu-emacs@gnu.org>
2007-07-10 21:21 ` Joe Wells [this message]
2007-07-01  3:01 strange Emacs 22.1 failure due to utf-8-compose-scripts when --no-window-system used Joe Wells

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=xnjps30x8cr.fsf@csb.bu.edu \
    --to=jbw@csb.bu.edu \
    --cc=gnu-emacs-bug@moderators.isc.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).