Open rocksolidity opened 3 years ago
Are there emacs on osx user here? You should check how the envvar changes and how you should manage when emacs launched from shell or from finder.
Are there emacs on osx user here? You should check how the envvar changes and how you should manage when emacs launched from shell or from finder.
Thanks for this feedback. I have been trying to find out more details about how macOS implements the open
command but no luck as yet. I have been working on other things so have left this for now. I actually have Emacs also installed as an App using homebrew so maybe I should try and figure out how to use one or the other. The problem is that I need to have an App that in Apple's framework in order for me to be able to launch from the Finder by double clicking. I cannot specify a binary as far as I know but maybe some Automator option might work and I can launch Emacs using Roswell. I will keep trying and if I figure out a solution I will post it here. I am managing by having a running Emacs all the time (launched from the Terminal). Then it seems as though I can launch with the Application. There is an emacsclient
binary in the App but not an actual emacs
binary.
Please note that this issue was submitted some time ago by someone else (and I viewed the detailed interactions a short while ago) but it was not fully resolved (at least not for my case). I think it only refers to macOS and in my experience only one specific situation is affected as I will explain below but first I include the necessary details for posting here.
Environment
Entry in .emacs file
I initially inserted only the last two lines as the tutorial suggests, but I also tried using a suggestion from one person on the forum to including
/usr/local/bin
in theexec-path
.How to reproduce the issue
My issue only occurs if I double click on a file icon in the Finder. I get an error when Emacs opens and the following is in my Warnings buffer. (I have Emacs assigned as the default application for .lisp, .asd and .org files for example.
I do not get this error when I launch emacs using Roswell or by
emacs <filename>
or even byopen <filename>
from the Terminal.It could be a problem with the launching options from macOS but I would really like to find a solution because in many contexts when looking over files in different directories and making some editing changes I prefer to launch Emacs with a double click.
IN CASE I HAVE A RUNNING EMACS PROCESS THEN I DO NOT GET THE ERROR! This confuses me and perhaps it is an Emacs issue too - but I am submitting it here because I have never experienced this before with any other program in 12 years actively using OS X. It is only after installing Roswell yesterday that I have had problems and I would really like to know how to trouble shoot it because I feel it is a good tool for me in the long term for many reasons. Already I have found installing some of the less frequently used Lisps made very easy for me by using Roswell.
This is my first post here and I hope that I have followed the guidelines. I will be happy to edit or add more info as needed. Many thanks.
Rama Lakshmanan