caldwell / build-emacs Goto Github PK

hi there

thanks for your work, have you ever think about to build with XWidget support ? i think it's really cool and useful feature on emacs 25.1

Thanks

It would be good to apply the full-screen patch, it works with 24.2 HEAD.

https://raw.github.com/gist/1746342/702dfe9e2dd79fddd536aa90d561efdeec2ba716

The emacs shell script for calling Emacs.app from the Terminal is really handy. Could the script have an auto-install option, like Aquamacs provides?

I see some variables in the binary containing "/Users/david". (I am not david.)

For example, load-path contains

"/Users/david/src/emacs-dev/ftp-versions/emacs-24.3/nextstep/Emacs.app/Contents/Resources/share/emacs/24.3/site-lisp"

And, exec-path contains

"/Users/david/Xcode-10.7_4.5.2/Xcode.app/Contents/Developer/usr/bin"

It would be good to remove these artifacts, if possible.

Just curious if there were any plans to support libxml2 and eww. Thanks!!

I just updated to the new Emacs 25.2 and get a reproducible crash when I invoke gnutls related commands (I use gnus with SSL connections to my IMAP and NNTP servers). The same setup works without problems with the previous Emacs 25.1.1.

I can reproduce the crash using the following invokation (Emacs.app copied to ~/Applications):

~/Applications/Emacs.app/Contents/MacOS/Emacs -Q -q -l tls.el

where tls.el contains the following code:

(require 'gnutls)
(open-gnutls-stream "tls" "tls-buffer" "google.com" "https")

The error message in my shell is Fatal error 4: Illegal instructionAbort trap: 6
There is also a popup to send the crash output to Apple.

Now for the fun part: this happens only on my Mac mini (mid 2010) running 10.12.4 Sierra. The same Emacs runs fine on my MacBook Air (mid 2012) also running 10.12.4 Sierra.

I downloaded the dmg file twice but that did not change anything.

A wild guess: the Mac mini has a Core 2 Duo CPU while the MacBook has a Core i5. Maybe the gnutls library has been compiled with optimisations or an instruction that is not available on the Core 2 Duo?

Great stuff! Would you consider building your Emacsen --with-imagemagick?

Thanks

Running M-x xwidget-webkit-browse-url using Emacs 25.1 results in the following error:

user-error: Your Emacs was not compiled with xwidgets support

It would be good if we were able to compile with xwidgets support.

The default load-path upon installing on a Macbook Pro running OS X 10.9.5 includes many subdirectories under /User/build, which does not exist on this system. In particular, one of these has the only reference to an emacs/24.4/ subdirectory, the site-lisp one.

I have not searched the whole list of load-list, but I do know that recentf-mode.elc, *which came in /usr/share/emacs/22.1/lisp in the version of emacs that comes with OS X), is not being loaded: I get an error message when I require either this or protobuf-mode from my .emacs file while loading Emacs (instead of the /usr/bin/emacs that came with the system).

When Emacs is active when logging of or restarting, and OSX is logging in again Emacs hangs, using 100% CPU. I've tested this with clean .emacs{,.d}

Used the Macports version on Mavericks, if this is not the place to report this or more info is needed, please let me know.

Hi,

I downloaded Emacs-24.3-universal-10.6.8.dmg today, and am running it on Mountain Lion, but Emacs' title bar doesn't have the two-arrow fullscreen button in the upper-right. Am I missing something obvious?

Thanks,
Ted

I'm using version 25.1 (9.0) from emacsformacosx.com and getting the below error when running emacs for the first time on a new machine and accessing the marmalade repo. But, I do NOT get an error when accessing it from, for example Chrome browser, curl, etc.

This makes me wonder if there is some sort of root cert list embedded in emacs that is out of date?

( This seems related, but wanted to check here first, since this is where the app was packaged: http://emacs.stackexchange.com/questions/18045/how-can-i-retrieve-an-https-url-on-mac-os-x-without-warnings-about-an-untrusted )

---- Network Security Manager ----
Certificate information
Issued by: COMODO RSA Domain Validation Secure Server CA
Issued to: Domain Control Validated
Hostname: marmalade-repo.org
Public key: RSA, signature: RSA-SHA256
Protocol: TLS1.2, key: ECDHE-RSA, cipher: AES-256-GCM, mac: AEAD
Security level: Medium
Valid: From 2015-07-12 to 2018-07-11

The TLS connection to marmalade-repo.org:443 is insecure for the
following reasons:

the certificate was signed by an unknown and therefore untrusted authority
certificate could not be verified

I just downloaded and installed v24.5.1. When I do a search and don't find anything, I get a strange visual artifact in the middle of the emacs window:

Any idea what this is / how to fix it?

If you run /Applications/Emacs.app/Contents/MacOS/Emacs in Terminal.app, Emacs successfully runs, but it steals control of the terminal until you quit Emacs.

As a mitigation, users can append the shell option & to run it as a background process, but this still results in a behind-the-scenes leash on Emacs: If you quit Terminal.app, it kills Emacs as well.

The Windows port of Emacs offers runemacs.exe, a useful command line script that accepts an optional file or directory to edit, and launches without leashing to the calling terminal. Could Emacs for Mac OS X get something similar?

As described here.

This is a follow-up question to the one at "Is /usr/bin/etags severely out of date in Yosemite?"

The Emacs in question is from http://emacsformacosx.com/ (GNU Emacs 24.4.1 (x86_64-apple-darwin13.4.0, NS apple-appkit-1265.21) of 2014-10-20 on builder10-9.porkrind.org).

If I start Emacs from the dock, then I don't see in PATH:

/Applications/Emacs.app/Contents/MacOS/bin-x86_64-10_9:/Applications/Emacs.app/Contents/MacOS/libexec-x86_64-10_9

If I use the script described at http://emacsformacosx.com/tips then I do see the above entries in PATH. But even in this case, /usr/bin comes first in PATH. To use the etags found in /Applications/Emacs.app/Contents/MacOS/bin-x86_64-10_9 I have to give it precedence in some manner. I typically want to run etags in a shell script that is started in the Emacs shell buffer.

Why don't I see these PATH entries when I start Emacs from the OS X dock (I'm using OS X Yosemite)?

At /Applications/Emacs.app/Contents/MacOS/Emacs I read:

Emacs.app sticks Emacs.app/Contents/MacOS/{bin,libexec} on the end of
the PATH when it starts, so if we stick our own architecture dependent
paths on the end of the PATH then they will override Emacs's paths
while not affecting any user paths.

This looks like an OS X bug coupled with different undefined behavior in Ruby and Emacs.

The root cause is that when launching Emacs from Finder, OS X is passing the PATH environment variable to the process twice! I wrote a test case and submitted it to Apple's bug reporter (id 19801095). Here's my test case:

#!/bin/bash

mkdir -p /tmp/test.app/Contents/MacOS/

cat > /tmp/test.app/Contents/MacOS/test <<EOF
#!/usr/bin/env ruby
\$stdout.reopen('/tmp/test.app.log', "w")
ENV.each_pair {|k,v| puts "#{k}=#{v}" if k == 'PATH' }
EOF
chmod +x /tmp/test.app/Contents/MacOS/test

launchctl setenv PATH "Extra PATH"
open -W /tmp/test.app
cat /tmp/test.app.log
launchctl unsetenv PATH

If you save that and then run it from the Terminal then it will print:

PATH=/usr/bin:/bin:/usr/sbin:/sbin
PATH=/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
PATH=Extra PATH

This only happens on 10.10. 10.9 will only print one PATH.

So that is the root cause. What's actually happening? The Emacs from http://emacsformacosx.com uses a Ruby launcher script so that it can ship a binary that runs optimally on OS X installs from 10.6 to 10.10. This launcher script manipulates the PATH:

ENV['PATH'] += ':' + File.join(base_dir,     "bin-#{arch_version}") +
               ':' + File.join(base_dir, "libexec-#{arch_version}")

So ENV['PATH'] only manipulates the first instance of PATH in the list. When Emacs launches, it only pays attention to the last instance of PATH. Which on is right? Well, POSIX talks about this case in the spec:

If more than one string in an environment of a process has the same name, the consequences are undefined.

That means that neither of these programs are technically in the wrong.

Ok, so why does it behave differently from Terminal? That's because something is filtering out the duplicate PATHs in the environment when you are running from Terminal. I suspect bash. But it could also be Terminal.app. Either way, there's only one PATH in the environment and so the Ruby launcher and Emacs communicate correctly.

So what's the solution then? I think the Ruby launcher needs to change to deal with this, since it appears to be the default behavior in 10.10. That's a shame, since it's just more cruft. Luckily (as you can see from the above test script), Ruby can get to both PATHs so it can filter out everything but the last instance which would make it work the same way Emacs works.

If I use EFMOX for more than a few minutes (just letting it sit there and chill) it will eventually start lagging and become almost completely unresponsive within an hour or less.

Is this a known issue? Can anyone reproduce this?

Edit: I think it's due to Emacs 24, I don't recall this happening on 23. I will test to verify.

Hi all,

Apologies if this is not an emacsforosx issue (and I don't think it is but more like an OS X issue) but here's my problem:

I run most stuff in terminals. For the emacs version that I have with Maverick (version 22) I can just run emacs in a terminal and runs /usr/bin/emacs and doesn't start a new window (ie., like having an `-nw' argument).

Now I've installed the latest version of emacsforosx and the app runs nicely. However, I'd really like to use that version from my terminals. If I run /Applications/Emacs.app/Contents/MacOS/Emacs -nw then all is fine and dandy.

However, if I would like to fire up a file /Applications/Emacs.app/Contents/MacOS/Emacs -nw test then the emacs app looks for the file in my home directory regardless of where I'm currently at. If I run the same command without the -nw argument I get the same result except that a new emacs window is started.

I tried to make an alias

alias eee= open -a /Applications/Emacs.app/Contents/MacOS/Emacs -nw

but that throws an error and

alias eee= open -a /Applications/Emacs.app/Contents/MacOS/Emacs

finds the file in the current directory when I use it but starts an emacs window.

Is there a command line version I can call instead of the app?

I'm on using this version of your emacs:

GNU Emacs 24.4.1 (x86_64-apple-darwin13.4.0, NS apple-appkit-1265.21) of 2014-10-20 on builder10-9.porkrind.org

When I start emacs, I loose the environment variables set in .bashrc and .bash_profile

Is this by design or did I screw something up. I discovered this by placing a binary in a non-standard location and then attempted to run the compile function. In particular, in doing development with the go language, the binary is in /usr/local/go/bin and it expects a default GOPATH variable set. Running items from the shell within emacs works because I added a init_bash.sh script in .emacs.d, but that fix doesn't help subprocesses.

If I click on the packaged app icon, the GOPATH is not set and my PATH doesn't include /usr/local/go/bin - If i manually run one of the executables in the MacOS folder under the Emacs package, the path is set correctly, but a new terminal window is left open.

I'm trying to use Emacs 24.4 (2014-10-20) on my Powerbook.

When I start Emacs I get a

Application Specific Information:
* Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '* -[EmacsImage drawInRect:fromRect:operation:fraction:respectFlipped:hints:]: unrecognized selector sent to instance 0x7229970'

Thread 0 Crashed:
0 libSystem.B.dylib 0x903589f0 __kill + 12
1 Emacs-powerpc-10_4 0x000a6d70 terminate_due_to_signal + 176
2 Emacs-powerpc-10_4 0x000c55c4 emacs_abort + 20
3 Emacs-powerpc-10_4 0x00199fec ns_term_shutdown + 156
4 Emacs-powerpc-10_4 0x000a5a14 shut_down_emacs + 324
5 Emacs-powerpc-10_4 0x000a6d40 terminate_due_to_signal + 128
6 Emacs-powerpc-10_4 0x000c56b0 handle_fatal_signal + 16
7 Emacs-powerpc-10_4 0x000c5b80 deliver_fatal_thread_signal + 144

Axel

Most modern Mac applications remember their last size and position.

Putting aside whether this is a good idea, is this something under control of the Mac OS X build? I've had a hard time figuring out where the responsibility lies.

Personally, it would be nice to have as an option.

Closing frame while in fullscreen crashes emacs GUI. The steps are:

1. open emacs for osx and make it fullscreen
2. make new frame ctrl-x 5 2 '(make-frame-command)'
3. delete frame ctrl-x 5 0

emacs crashes :(

NOTE: only reproduces on fullscreen mode. I have a macbook pro mid 2012 (10.11 (15A284)).

I've been running the Emacs 24.4 pretests as they come out.

Today I tried to install 24.3.92 from emacsforosx.com, but when I start it, nothing visible happens, and the following error message is logged in Console.app:

/Applications/Emacsen/Emacs.app/Contents/MacOS/Emacs:13: syntax error, unexpected '.', expecting $end
        .select { |v| v[:arch] == arch && v[:version] <= version }
         ^

I'm guessing there's some syntax here not supported in 10.6.8's default Ruby (1.8.7)?

I know it works on my work machine, which is on OS 10.9.

When starting Emacs by double-clicking, the directory where "aspell" is located (/usr/local/bin) is not in the exec path. This cause ispell to fail to find the aspell executable, see ispell-program-name for details.

When started from the command-line, however, it is.

I don't know if this is a "emacsforosx" problem or a problem with Emacs itself, feel free to report this upstream if you think it's appropriate.

-- Anders

http://emacsformacosx.com/about says that nightlies are built from http://git.savannah.gnu.org/cgit/emacs.git/ - the implication of the word "public" being that it is cloned over an unauthenticated transport, and so could be corrupted in transit to you by an attacker. Or do you have an SSH key registered with Savannah? Ideally, you should be cloning the repository from an SSH account (a dedicated account, not your account, with no other SSH access to anything, of course) so that you can at least verify the SSH key.

This is especially important as these binaries are codesigned; if they are built automatically and the code is retrieved via a plaintext transport, it doesn't seem there's any way to verify the code is authentic.

I'd like to launch emacs under X11 when I'm ssh'd into the machine and DISPLAY is set correctly (for example, xterm works). However, it doesn't do so and even when I specify display directly (with -d, as described in the --help message), it just runs in the terminal or pops up on my Mac's screen (depending on which executable I use). Am I doing something wrong? Or do I need to build my own version of Emacs with the X11 support as well as the native windowing support?

Emacs for Mac OS X 24.3 takes a long time to start up, sometimes a few minutes. Homebrew Emacs and Aquamacs start up much faster.

When a file containing some characters is opened, emacs crashes with the dump below. In this case I'm trying to open a file containing just one LEFT SINGLE QUOTATION MARK character (http://www.fileformat.info/info/unicode/char/2018/index.htm) but there are many characters that have the same issue. I

This does not happen in the terminal version of emacs and other builds. I'm not sure if it's related to this particular build script configuration or to the codebase, so I'm posting it here.

Process:         Emacs-10.7 [68595]
Path:            /Applications/Emacs-24.3.app/Contents/MacOS/Emacs-10.7
Identifier:      org.gnu.Emacs
Version:         Version 24.3 (9.0)
Code Type:       X86-64 (Native)
Parent Process:  launchd [249]

Date/Time:       2013-09-04 23:04:35.231 -0300
OS Version:      Mac OS X 10.7.5 (11G63)
Report Version:  9

Interval Since Last Report:          25486580 sec
Crashes Since Last Report:           145
Per-App Interval Since Last Report:  3124062 sec
Per-App Crashes Since Last Report:   12
Anonymous UUID:                      0DC53222-9BCC-4E09-A510-A05B54580CF4

Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Exception Type:  EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000

VM Regions Near 0:
--> 
    __TEXT                 0000000100000000-00000001001f4000 [ 2000K] r-x/rwx SM=COW  /Applications/Emacs-24.3.app/Contents/MacOS/Emacs-10.7

Application Specific Information:
objc[68595]: garbage collection is OFF

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib          0x00007fff9136382a __kill + 10
1   Emacs-10.7                      0x000000010009da59 terminate_due_to_signal + 153
2   Emacs-10.7                      0x00000001000ba463 emacs_abort + 19
3   Emacs-10.7                      0x000000010018b49d ns_term_shutdown + 125
4   Emacs-10.7                      0x000000010009e0c1 shut_down_emacs + 305
5   Emacs-10.7                      0x000000010009da1b terminate_due_to_signal + 91
6   Emacs-10.7                      0x00000001000ba956 deliver_fatal_thread_signal + 134
7   libsystem_c.dylib               0x00007fff962a7cfa _sigtramp + 26
8   com.apple.CoreFoundation        0x00007fff9aa363c2 CFStringGetLength + 18
9   com.apple.CoreFoundation        0x00007fff9aa4d9e9 CFStringCompareWithOptionsAndLocale + 73
10  com.apple.CoreText              0x00007fff9b35f6fe CompareLocalizedDescriptorsByTraitsAndPrecedence(void const*, void const*, void*, bool) + 209
11  com.apple.CoreFoundation        0x00007fff9aa6efa5 __CFSimpleMergeSort + 85
12  com.apple.CoreFoundation        0x00007fff9aa6f083 __CFSimpleMergeSort + 307
13  com.apple.CoreFoundation        0x00007fff9aa6f067 __CFSimpleMergeSort + 279
14  com.apple.CoreFoundation        0x00007fff9aa6f067 __CFSimpleMergeSort + 279
15  com.apple.CoreFoundation        0x00007fff9aa6f067 __CFSimpleMergeSort + 279
16  com.apple.CoreFoundation        0x00007fff9aa6f083 __CFSimpleMergeSort + 307
17  com.apple.CoreFoundation        0x00007fff9aa6f067 __CFSimpleMergeSort + 279
18  com.apple.CoreFoundation        0x00007fff9aa6f067 __CFSimpleMergeSort + 279
19  com.apple.CoreFoundation        0x00007fff9aa6f067 __CFSimpleMergeSort + 279
20  com.apple.CoreFoundation        0x00007fff9aa6eef6 CFSortIndexes + 1446
21  com.apple.CoreFoundation        0x00007fff9aa41e33 CFQSortArray + 275
22  com.apple.CoreFoundation        0x00007fff9aa41bb8 CFArraySortValues + 1080
23  com.apple.CoreText              0x00007fff9b389ab0 TDescriptorSource::GetAllDescriptors(bool, long (*)(void const*, void const*, void*)) const + 136
24  com.apple.CoreText              0x00007fff9b3564d3 TDescriptor::CreateMatchingDescriptors(__CFSet const*, unsigned long) const + 163
25  com.apple.AppKit                0x00007fff935b02b5 -[NSCTFontDescriptor matchingFontDescriptorsWithMandatoryKeys:] + 12
26  Emacs-10.7                      0x000000010019e547 ns_findfonts + 1719
27  Emacs-10.7                      0x000000010012a7df font_list_entities + 655
28  Emacs-10.7                      0x000000010012c63a font_find_for_lface + 1978
29  Emacs-10.7                      0x0000000100173dc7 fontset_find_font + 1991
30  Emacs-10.7                      0x0000000100174057 fontset_font + 311
31  Emacs-10.7                      0x0000000100174438 face_for_char + 264
32  Emacs-10.7                      0x00000001000324d5 get_next_display_element + 2565
33  Emacs-10.7                      0x000000010003a476 display_line + 5750
34  Emacs-10.7                      0x000000010004169f try_window + 175
35  Emacs-10.7                      0x000000010004ab86 redisplay_window + 15942
36  Emacs-10.7                      0x0000000100036446 redisplay_window_0 + 38
37  Emacs-10.7                      0x0000000100118cc3 internal_condition_case_1 + 307
38  Emacs-10.7                      0x00000001000363fc redisplay_windows + 140
39  Emacs-10.7                      0x000000010004288d redisplay_internal + 4061
40  Emacs-10.7                      0x00000001000ad7d9 read_char + 7961
41  Emacs-10.7                      0x00000001000b061f read_key_sequence + 7535
42  Emacs-10.7                      0x00000001000b2098 command_loop_1 + 5128
43  Emacs-10.7                      0x0000000100118e19 internal_condition_case + 297
44  Emacs-10.7                      0x00000001000b0c6e command_loop_2 + 62
45  Emacs-10.7                      0x0000000100118f15 internal_catch + 213
46  Emacs-10.7                      0x00000001000b26a0 recursive_edit_1 + 240
47  Emacs-10.7                      0x00000001000a309d Frecursive_edit + 237
48  Emacs-10.7                      0x000000010009ff2c main + 5932
49  Emacs-10.7                      0x00000001000020e4 start + 52

It appears that the full-screen patch from #4 has made its way into trunk.

As described by @bbatsov:

http://batsov.com/articles/2012/12/09/emacs-24-dot-3-introduces-native-osx-full-screen-support/

Thank you for making the best Emacs for OS X distribution out there!

I was just trying to edit and preview a svg file, and it didn't
work. I did a little digging, and it seems like this version of emacs
is compiled without SVG.

• Is this true, or am I misunderstanding something?
• Could we compile with SVG?

Emacs for Mac OS X is an excellent editor choice for Mac developers. Could we add Emacs to the Mac App Store? This could encourage more users to use Emacs.

The interpreter #!/usr/bin/ruby may not always available,
so can U change it to #!/usr/bin/env ruby

I set up emacsclient as described on the website, when I now open a new file either by using the Finder or by the Terminal I always get a new (Mac OS X) window. How can I open files in the existing window that Emacs created on startup?

When using the scroll bar or touchpad gestures, scrolling appears jarring. Could we smooth it out, the way other text editors look?

I use TAB to indent Markdown code blocks. This works in GUI mode, but when I press TAB in terminal -nw mode, nothing happens.

This is because the 'Emacs' ruby script uses its own invocation name in dir listing, which may be different. Can be fixed by changing line to:

file_version_finding_glob = "#{File.join(File.dirname($0), 'Emacs')}-*"
versions = Hash[*Dir[file_version_finding_glob].map { |file| [ numify(file.sub(/^.*-(.+)$/, '\1')), file] }.flatten]

If I remember I'll submit a PR for this, but atm I just wanted to record the problem and fix here

The current visual bell for OS-X emacs is annoying (at least to me), there's a patch to make it nicer: https://gist.github.com/1907807

(Also see also: http://old.nabble.com/visible-bell-patch-for-Mac-OS-X-td27389547.html)

The discussion seems to indicate that there were some issues discovered (I didn't notice any in daily use for a while using the gist), so I was wondering if you'd tested it at all or see any value incorporating the patch.

Hi, not sure if this is a regression from previous emacsforosx.com releases, but the built-in emacs "vc" package doesn't work with git directories.

$ /Applications/Emacs.app/Contents/MacOS/Emacs --version
GNU Emacs 24.5.1
$ /Applications/Emacs.app/Contents/MacOS/Emacs -q ~/IdeaProjects/mygitproject/

When I run "vc-dir" it doesn't recognize my directory as being git, it seems to assume "svn" then reports an error:

svn: E155007: '/Users/.../IdeaProjects/mygitproject' is not a working copy

Any idea what might be wrong? I don't see this problem with built-in OS X emacs 22.1, vc-dir works (at least sort of) and displays a message like No files locked under /Users/.../IdeaProjects/mygitproject/.

Control+Option+Command F: Emacs goes full screen.
Command+Tab: Switch from Emacs to other application, e.g. Finder.
Command+Tab: Expected to switch back to Emacs, but in practice, nothing happens.

The following has details

bbatsov/projectile#600

It would be nice if, like in Windows, the GnuTLS libraries were opportunistically used on OS X or if they were bundled with the binary.

@caldwell I think I brought this up in private e-mail a while ago but can't find it. Well, if I can help make this happen, please let me know. I personally use GnuTLS from Homebrew and compile my own Emacs because this build script doesn't support it, but would love to switch to a more integrated binary that I can test both as an Emacs developer and a user.

Emacs for Mac OS X v24.5.1, installed via Homebrew.

Steps to reproduce:

1. Change the font size, either via the Set default font menu item or M-x customize-face.
2. Move up a couple of lines with the directional keys

When the font size changes, it appears to zoom the window, followed by graphical issues when it has to redraw the window.

When I run /Applications/Emacs.app/Contents/MacOS/Emacs, that is, with no arguments, it segfaults.

I'm using Emacs for Mac OS X, 24.3.

When I run /Applications/Emacs.app/Contents/MacOS/Emacs from Terminal.app, the Emacs window launches behind the terminal. Like other GUI programs, Emacs should be launching its window in front of other windows.

I've created an icon for Emacs which matches the appearance of OS X Yosemite.
(https://github.com/cg433n/emacs-yosemite-icon)

Is there any way to include it in the build process?

According to this article, the "--srgb" flag is needed for proper rendering: http://emacsredux.com/blog/2013/08/21/color-themes-redux/

I haven't looked through the build scripts but thought I'd point it out for someone who is more familiar with them.

When trying to start 24.2 on my PowerPC system, I get this:

Process:         Emacs [568]
Path:            /Applications/Emacs.app/Contents/MacOS/Emacs
Identifier:      org.gnu.Emacs
Version:         ??? (???)
Code Type:       PPC (Native)
Parent Process:  launchd [85]

Interval Since Last Report:          1118995 sec
Crashes Since Last Report:           14
Per-App Interval Since Last Report:  0 sec
Per-App Crashes Since Last Report:   8

Date/Time:       2012-09-27 18:10:20.345 -0400
OS Version:      Mac OS X 10.5.8 (9L31a)
Report Version:  6
Anonymous UUID:  36EB611E-3CB9-4BCE-8E45-518B75664A8B

Exception Type:  EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000001, 0x000000008fe0105c
Crashed Thread:  0

Dyld Error Message:
  Library not loaded: /usr/lib/libxml2.2.dylib
  Referenced from: /Applications/Emacs.app/Contents/MacOS/Emacs
  Reason: Incompatible library version: Emacs requires version 10.0.0 or later, but libxml2.2.dylib provides version 9.0.0

I'm not sure what could have caused this: do newer OS X SDKs include PPC builds of libraries that are ABI-incompatible with actual PPC macs?

Some languages like Arabic or Persian, needs some sorts of font shaping, because they are not actually fixed-width and most of the time the letters should join together in a word. Linux Distros like Debian, Ubuntu and others compile Emacs with libotf and libm17n to get this ability. in OS X, bidirectional display works great but letters are not display correctly. is it possible for emacsformacosx.com to build Emacs with support of these libraries?

Emacs 24.2 (9.0) on Mac OSX 10.8.2

I see strange problems with what I naively call the video buffering.

First thing I immediately notice is the first line of any file I'm editing is hidden beneath the window title bar.

If I scroll the buffer, I start seeing artifacts from the title bar in the buffer itself.

I attach a screenshot as I'm sure the above is horribly unclear.

[Edited to fix attached image, typos.]

I installed emacs 25.1.1 using brew cask install emacs. All went well (I can run it by launching from the finder) until I tried to create a symlink to run emacs from the command line. I tried

ln -s /Applications/Emacs.app/Contents/MacOS/Emacs /usr/local/bin/emacs

and when I run it I get a popup that says This application will not run on your computer. Sorry!

I discovered that when run from the finder it actually uses Emacs-x86_64-10_9 (I'm on Yosemite) so I tried

ln -s /Applications/Emacs.app/Contents/MacOS/Emacs-x86_64-10_9 /usr/local/bin/emacs

and I get:

Warning: arch-dependent data dir '/Users/build/workspace/Emacs-Multi-Build/label/mavericks/emacs-source/nextstep/Emacs.app/Contents/MacOS/libexec/': No such file or directory
Warning: arch-independent data dir '/Users/build/workspace/Emacs-Multi-Build/label/mavericks/emacs-source/nextstep/Emacs.app/Contents/Resources/etc/': No such file or directory
Warning: Lisp directory '/Users/build/workspace/Emacs-Multi-Build/label/mavericks/emacs-source/nextstep/Emacs.app/Contents/Resources/lisp': No such file or directory
Error: charsets directory not found:
/Users/build/workspace/Emacs-Multi-Build/label/mavericks/emacs-source/nextstep/Emacs.app/Contents/Resources/etc/charsets
Emacs will not function correctly without the character map files.
Please check your installation!

What is the secret?

thanks

Looks like the ENV.to_h fails. This affect older Mac OS X versions where /usr/bin/ruby is Ruby 1.8.