unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: 12392@debbugs.gnu.org
Subject: bug#12392: 24.2; emacs-gtk misinterprets floating-point numbers under certain locales on openSUSE 12.2
Date: Mon, 10 Sep 2012 19:37:18 +0200	[thread overview]
Message-ID: <5FFEA863-8B9D-498B-BD6E-F62D4FDB1A25@swipnet.se> (raw)
In-Reply-To: <87ehmboay1.fsf@Rainer.invalid>


9 sep 2012 kl. 10:30 skrev Achim Gratz <Stromeko@nexgo.de>:

> Achim Gratz writes:
>> Steps to reproduce:
>> 
>> 1. Start "LC_NUMERIC=de_DE.UTF-8 emacs-gtk -Q"
>> 2. Type "0.25" in *scratch* buffer, then "C-j"
>> 
>> The input evaluates to "0.0" rather than "0.25".
>> 
>> The input is correctly interpreted when setting LC_NUMERIC=C.
> 
> I've just finished a Gtk-3 build: same issue, so Gtk version itself
> doesn't seem to be a factor.
> 
> 

I suspect glibc have changed, because Emacs does

  setlocale (LC_NUMERIC, "C");

when it starts up, so your setting should not matter.

I suggest you try to file a bugreport to OpenSuse.

	Jan D.







  reply	other threads:[~2012-09-10 17:37 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-09  7:37 bug#12392: 24.2; emacs-gtk misinterprets floating-point numbers under certain locales on openSUSE 12.2 Achim Gratz
2012-09-09  7:43 ` Achim Gratz
2012-09-09  8:09 ` Achim Gratz
2012-09-09  8:30 ` Achim Gratz
2012-09-10 17:37   ` Jan Djärv [this message]
2012-09-10 19:00     ` Achim Gratz
2012-09-13  8:20 ` bug#12392: " Paul Eggert
2012-09-13 17:59   ` Achim Gratz
2012-09-14 15:58   ` Achim Gratz
2012-09-21  9:59   ` Holger Arnold
2012-09-22  6:19     ` Achim Gratz
2012-09-22 14:38       ` Holger Arnold
2012-09-22 15:08         ` Andreas Schwab
2012-09-22 15:49           ` Holger Arnold
2012-09-22 16:07             ` Eli Zaretskii
2012-09-22 17:04               ` Holger Arnold
2012-09-22 17:19                 ` Jan Djärv
2012-09-22 17:22                   ` Jan Djärv
2012-09-22 16:54             ` Jan Djärv
2012-09-22 16:55               ` Jan Djärv
2012-09-22 17:00                 ` Holger Arnold
2012-09-23 10:04                   ` Jan Djärv
2012-09-23 17:27                 ` Achim Gratz
2012-09-23 19:58                   ` Holger Arnold
2012-09-22 16:56               ` Holger Arnold
2012-09-22 16:02         ` Eli Zaretskii
2012-09-22 16:38           ` Holger Arnold
2012-09-22 16:41             ` Eli Zaretskii
2012-09-22 16:54               ` Holger Arnold
2012-09-22 17:10                 ` Eli Zaretskii
2012-09-22 17:18                   ` Holger Arnold
2012-09-22 19:02                     ` Eli Zaretskii
2012-09-22 19:44                       ` Holger Arnold
2012-09-22 16:36         ` Achim Gratz
2012-10-07 10:57           ` Holger Arnold
2012-09-21 20:08   ` Holger Arnold

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=5FFEA863-8B9D-498B-BD6E-F62D4FDB1A25@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=12392@debbugs.gnu.org \
    --cc=Stromeko@nexgo.de \
    /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).