Nick Dokos <ndo...@gmail.com> writes: > Peter Davis <p...@pfdstudio.com> writes: > >> Alan Schmitt <alan.schm...@polytechnique.org> writes: >> >>> On 2015-07-29 06:18, Peter Davis <p...@pfdstudio.com> writes: >>> >>>> Thank you, Daniele. I've tried the above command line, and I get: >>>> >>>> emacsclient: can't find socket; have you started the server? >>>> To start the server in Emacs, type "M-x server-start". >>>> emacsclient: No socket or alternate editor. Please use: >>>> >>>> --socket-name >>>> --server-file (or environment variable EMACS_SERVER_FILE) >>>> --alternate-editor (or environment variable ALTERNATE_EDITOR) >>>> >>>> I have (server-start) at the top of my .emacs file, and I've restarted >>>> manually a few times, so I suspect emacsclient is failing >>>> silently somehow and that's the problem. I'll try to troubleshoot that. >>> >>> You’re probably running the emacsclient that comes by default with OS X, >>> which is probably a different version from your emacs. Here I had to >>> change the path in the extension setting to use >>> “/usr/local/bin/emacsclient” instead of the system >>> “/usr/bin/emacsclient”. >> >> Ah! There's no /usr/local/bin/emacsclient, but on my Mac, I have >> >> /Applications/Emacs.app/Contents/MacOS/bin-x86_64-10_5/emacsclient >> >> When I set the extension to use that, I get a new frame with a buffer named >> Org-capture%20for%20Firefox, but there's nothing in it >> and it doesn't seem to correspond to a file. >> >> Progress. >> > > You need to (require 'org-protocol) in your .emacs (or wherever). > And if you don't want the new frame, you can uncheck that it in the > extension's preferences.
Excellent! That works. It prepends "CAPTURE-2-" to the filename I specified in the template, but otherwise seems to work beautifully. Now to look for the Chrome version. Thanks, all! -pd
