all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Anders Lindgren <andlind@gmail.com>
Cc: 22392@debbugs.gnu.org, alan@idiocy.org, emacs-devel@gnu.org
Subject: bug#22392: Emacs OS X GUI doesn't set locale
Date: Wed, 27 Jan 2016 17:53:00 +0200	[thread overview]
Message-ID: <83si1jyq77.fsf__1929.51576686955$1453910020$gmane$org@gnu.org> (raw)
In-Reply-To: <CABr8ebb55SEwE2MOnKdSYm=xO6VReRU8g_dr0vN4CGMVwVYrvg@mail.gmail.com> (message from Anders Lindgren on Wed, 27 Jan 2016 07:21:41 +0100)

> Date: Wed, 27 Jan 2016 07:21:41 +0100
> From: Anders Lindgren <andlind@gmail.com>
> Cc: 22392@debbugs.gnu.org, emacs-devel <emacs-devel@gnu.org>
> 
>     > * Why a separate source file? Is there any technical reasons why this
>     > couldn't reside in, say, nsterm.m?
>     
>     No, I just wasn't sure what the deal was with including files like that
>     in emacs.c since there's quite a lot in it. If that's an acceptable way
>     to do it then I'd be happy to do so.
> 
> Ah, I see. Including "nsterm.h" from "emacs.c" sounds like a bad idea, as it
> would increase the rebuild times.

Why is that?  We already include nsterm.h in at least 2 other *.c
files, so why would a third one matter so much?

> In this case, introducing a new source file seems like the right
> choice.

I'd rather avoid a new file, especially as it's going to be very
small.

Thanks.





  parent reply	other threads:[~2016-01-27 15:53 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 ` 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         ` bug#22392: " Anders Lindgren
2016-01-26 16:58         ` Anders Lindgren
2016-01-26 23:05         ` bug#22392: " Alan Third
2016-01-26 23:05         ` Alan Third
2016-01-27 18:06           ` Paul Eggert
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-27 19:44             ` bug#22392: " Eli Zaretskii
2016-01-28 22:53             ` Alan Third
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-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
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 15:06     ` Anders Lindgren
2016-01-26 14:44   ` Eli Zaretskii
2016-01-26 22:50   ` Alan Third
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       ` Eli Zaretskii
2016-01-27 15:53       ` Eli Zaretskii [this message]
2016-01-26  7:11 ` bug#22392: " 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

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

  git send-email \
    --in-reply-to='83si1jyq77.fsf__1929.51576686955$1453910020$gmane$org@gnu.org' \
    --to=eliz@gnu.org \
    --cc=22392@debbugs.gnu.org \
    --cc=alan@idiocy.org \
    --cc=andlind@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 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.