7 ms·

> There are other options, like Aquamacs, which are supposed to make Emacs more "Mac-like", but they're problematic in the long run because they're set up so di

> There are other options, like Aquamacs, which are supposed to make Emacs more "Mac-like", but they're problematic in the long run because they're set up so differently from standard Emacs that it's difficult to use the Emacs manual or follow along with tutorials. Having used emacs on linux, windows and now mac I disagree with this - though aquamacs introduces some (annoying, to me) functionality, you can simply turn these off and it works just like emacs in any other environment. I have found aquamacs works better with ansi-term + with full-screen functionality than vanilla emacs, and I use both these functions enough to not want to go back.

tazjin 13y ago
When you say vanilla emacs, do you include the Cocoa version? (http://emacsformacosx.com/ http://emacsformacosx.com/) I'm using that many hours every day and have zero problems. Regarding fullscreen, if you use a recent build both native and non-native fullscreen are supported.
- blueblob 13y ago
  +1 so funny, vanilla=cocoa...
  - tazjin 13y ago
    I don't understand your reply. It is quite possible that somebody doesn't know that the Cocoa wrapper is a part of upstream emacs, which is why I asked.
    - blueblob 13y ago
      I meant that I found it humorous that Cocoa (chocolate) was being described as "vanilla" on the platform. Purely language, not anything to do with the wrapper.
- singular 13y ago
  Yes, I tried the cocoa version and that's what I'm referring to. I recall having real issues in particular with ansi-term not having the environment correctly set + simply not being able to resolve that. I'm pretty sure I had other issues too, but I can't remember them. To be fair, I've not tried the cocoa version or any other for some time, so things may have changed. However, I still think OP's point was unfair on aquamacs - other than some (annoying!) quirks regarding autofonts and tabs (I instantly turn those off), it's no different than emacs anywhere else, in my experience.
  - intranation 13y ago
    PATH, exec-path etc. are mangled because of the way OSX loads environment variables. Here's an Emacs package that fixes that: https://github.com/purcell/exec-path-from-shell https://github.com/purcell/exec-path-from-shell

tazjin 13y ago

When you say vanilla emacs, do you include the Cocoa version? (http://emacsformacosx.com/ http://emacsformacosx.com/) I'm using that many hours every day and have zero problems. Regarding fullscreen, if you use a recent build both native and non-native fullscreen are supported.

blueblob 13y ago
+1 so funny, vanilla=cocoa...
- tazjin 13y ago
  I don't understand your reply. It is quite possible that somebody doesn't know that the Cocoa wrapper is a part of upstream emacs, which is why I asked.
  - blueblob 13y ago
    I meant that I found it humorous that Cocoa (chocolate) was being described as "vanilla" on the platform. Purely language, not anything to do with the wrapper.
singular 13y ago
Yes, I tried the cocoa version and that's what I'm referring to. I recall having real issues in particular with ansi-term not having the environment correctly set + simply not being able to resolve that. I'm pretty sure I had other issues too, but I can't remember them. To be fair, I've not tried the cocoa version or any other for some time, so things may have changed. However, I still think OP's point was unfair on aquamacs - other than some (annoying!) quirks regarding autofonts and tabs (I instantly turn those off), it's no different than emacs anywhere else, in my experience.
- intranation 13y ago
  PATH, exec-path etc. are mangled because of the way OSX loads environment variables. Here's an Emacs package that fixes that: https://github.com/purcell/exec-path-from-shell https://github.com/purcell/exec-path-from-shell