all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Random832 <random832@fastmail.com>
Cc: 22392@debbugs.gnu.org
Subject: bug#22392: Emacs OS X GUI doesn't set locale
Date: Fri, 05 Feb 2016 09:32:45 +0200	[thread overview]
Message-ID: <83r3grvcgy.fsf@gnu.org> (raw)
In-Reply-To: <m2si17iqb7.fsf@fastmail.com> (message from Random832 on Fri, 05 Feb 2016 02:12:12 -0500)

> From: Random832 <random832@fastmail.com>
> Date: Fri, 05 Feb 2016 02:12:12 -0500
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > By contrast, OS X is (AFAIK) a BSD-ish system, so I expect much more
> > programs to change their behavior when LANG is set to something that
> > suits Emacs, but is not necessarily "right" for the rest of the
> > system.
> 
> Why wouldn't it be right for the rest of the system?

I don't know.  Why don't those programs do that today?

> Keep in mind that 99% of the time the only programs that are going
> to be executing "BSD-ish" programs are going to be terminal
> emulators, which also set LANG.

If you are saying those programs all have bugs, then I find it hard to
believe, and anyway, it isn't Emacs's job to fix bugs all over the
system.

However, if enough use cases will be reported which show that indeed
many programs invoked by Emacs work better with that setting in the
environment, I will change my mind.  No such examples materialized
yet, AFAIR.





  reply	other threads:[~2016-02-05  7:32 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25 22:18 Emacs OS X GUI doesn't set locale Alan Third
2016-01-26  7:11 ` bug#22392: " Anders Lindgren
2016-01-26  7:11 ` Anders Lindgren
2016-01-26 14:44   ` Eli Zaretskii
2016-01-26 15:06     ` Anders Lindgren
2016-01-26 15:14       ` bug#22392: " Eli Zaretskii
2016-01-26 15:14       ` Eli Zaretskii
2016-01-26 16:58         ` Anders Lindgren
2016-01-26 16:58         ` bug#22392: " Anders Lindgren
2016-01-26 23:05         ` Alan Third
2016-01-27 18:06           ` Paul Eggert
2016-01-27 19:44             ` bug#22392: " Eli Zaretskii
2016-01-27 19:44             ` Eli Zaretskii
2016-01-27 22:27               ` bug#22392: " Paul Eggert
2016-01-27 22:27               ` Paul Eggert
2016-01-28 22:53             ` Alan Third
2016-02-01  5:03               ` Anders Lindgren
2016-02-01 17:48                 ` bug#22392: " Alan Third
2016-02-01 17:48                 ` Alan Third
2016-02-01 18:57                 ` Eli Zaretskii
2016-02-01 18:57                 ` bug#22392: " Eli Zaretskii
2016-02-10 23:57                 ` Alan Third
2016-02-11  2:37                   ` Paul Eggert
2016-02-01  5:03               ` Anders Lindgren
2016-01-28 22:53             ` Alan Third
2016-01-27 18:06           ` Paul Eggert
2016-01-17 14:27             ` bug#22392: 25.0.50; NS Emacs run from " Alan Third
2016-01-17 22:38               ` Random832
2016-01-18 21:12                 ` Alan Third
2016-01-18 22:09                   ` Random832
2016-01-18 23:11                     ` Alan Third
2016-01-19 15:55                       ` Eli Zaretskii
2016-01-19 16:03                     ` Eli Zaretskii
2016-01-30  6:13               ` bug#22392: Emacs " Random832
2016-02-05  7:12               ` Random832
2016-02-05  7:32                 ` Eli Zaretskii [this message]
2016-02-05  7:36                   ` Random832
2016-02-05  9:21                     ` Eli Zaretskii
2016-02-05 17:28                       ` Random832
2016-02-05 19:46                         ` Eli Zaretskii
2016-01-26 23:05         ` Alan Third
2016-01-26 15:06     ` Anders Lindgren
2016-01-26 14:44   ` Eli Zaretskii
2016-01-26 22:50   ` Alan Third
2016-01-27  6:21     ` bug#22392: " Anders Lindgren
2016-01-27  6:21     ` Anders Lindgren
2016-01-27 15:53       ` bug#22392: " Eli Zaretskii
2016-01-27 15:53       ` Eli Zaretskii
2016-01-26 22:50   ` bug#22392: " Alan Third

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83r3grvcgy.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=22392@debbugs.gnu.org \
    --cc=random832@fastmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.