unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Re: L10N & LC variables
Date: Sat, 27 May 2017 09:34:06 +0900	[thread overview]
Message-ID: <6F65C4B8-67D9-45DA-A77A-9D5A5C641B3F@gmail.com> (raw)
In-Reply-To: <58516957-5971-7a1f-a4e2-d276f2881046@cs.ucla.edu>


> On May 27, 2017, at 3:42, Paul Eggert <eggert@cs.ucla.edu> wrote:
> 
> On 05/26/2017 07:41 AM, Jean-Christophe Helary wrote:
>> 2005-04-14  YAMAMOTO Mitsuharu<mituharu@math.s.chiba-u.ac.jp>
>> 
>> 	* international/mule-cmds.el (set-locale-environment): On Mac OS,
>> 	use preferences AppleLocale and AppleLanguages, and variable
>> 	mac-system-locale for default locale.  On Mac OS Classic, use
>> 	mac-system-coding-system for default coding systems.
>> But there is no further references to mac-system-locale in the other changelogs
> 
> That code was removed here:
> 
> http://git.savannah.gnu.org/cgit/emacs.git/commit/?id=9e2a2647758db83b490e2993aa31cd4607305a82
> 
> in a commit dated 2008-07-27 that removed support for Carbon. From what you say, that part of the 2008 change is making life for macOS users more difficult,

Interesting. It looks like the whole macOS preference settings acquisition code was taken from Emacs in that commit, including a lisp function written in C: mac-get-preference. That was quite a radical commit...

> Presumably there is a non-Carbon way to do the equivalent of the old code, and if you or some other macOS expert would write it, that would remove this minor glitch in the default Emacs configuration on macOS.

(shell-command "defaults read -g AppleLocale") seems to do the job well, although it may not be considered super elegant.

(side note: le Elisp Reference index does not seem to have an entry for "shell-command" although "read-shell-command" that is also defined in simple.el is there.)

Jean-Christophe 


  parent reply	other threads:[~2017-05-27  0:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2F438BC0-4073-4D29-8504-1909EE1762DD@gmail.com>
2017-05-26 14:41 ` L10N & LC variables Jean-Christophe Helary
2017-05-26 14:53   ` Eli Zaretskii
2017-05-26 15:10     ` Jean-Christophe Helary
2017-05-26 15:20       ` Eli Zaretskii
2017-05-26 15:54         ` Jean-Christophe Helary
2017-05-26 17:39           ` Eli Zaretskii
2017-05-26 23:22             ` Jean-Christophe Helary
2017-05-26 18:42   ` Paul Eggert
2017-05-26 23:13     ` Jean-Christophe Helary
2017-05-27  0:38       ` Alan Third
2017-05-27  0:54         ` Jean-Christophe Helary
2017-05-27  7:33           ` Alan Third
2017-05-27  7:59             ` Eli Zaretskii
2017-05-27  9:51               ` Jean-Christophe Helary
2017-05-27  0:34     ` Jean-Christophe Helary [this message]
2017-05-27  5:25   ` Anders Lindgren

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=6F65C4B8-67D9-45DA-A77A-9D5A5C641B3F@gmail.com \
    --to=jean.christophe.helary@gmail.com \
    --cc=emacs-devel@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).