Comments on: Response to Aquamacs gripes http://atomized.org/2008/08/response-to-aquamacs-gripes/ Fragmenting reality. Tue, 31 Aug 2010 23:25:35 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Ian http://atomized.org/2008/08/response-to-aquamacs-gripes/comment-page-1/#comment-106152 Ian Wed, 12 Nov 2008 04:18:48 +0000 http://atomized.org/?p=305#comment-106152 It’s not. I want ⌘ to work normally in OS X apps, and be Meta in Emacs. It’s not. I want ⌘ to work normally in OS X apps, and be Meta in Emacs.

]]> By: Leonardo Santagada http://atomized.org/2008/08/response-to-aquamacs-gripes/comment-page-1/#comment-105739 Leonardo Santagada Fri, 07 Nov 2008 02:33:59 +0000 http://atomized.org/?p=305#comment-105739 you can change option and command on the keyboard config in system preferences... so all your apps would have it changed not only aquamacs... if thats really what you want. you can change option and command on the keyboard config in system preferences… so all your apps would have it changed not only aquamacs… if thats really what you want.

]]> By: Ian http://atomized.org/2008/08/response-to-aquamacs-gripes/comment-page-1/#comment-95462 Ian Fri, 15 Aug 2008 21:39:48 +0000 http://atomized.org/?p=305#comment-95462 @Lawrence Yeah, definitely does not work in Aquamacs 1.4 or better. @Lawrence Yeah, definitely does not work in Aquamacs 1.4 or better.

]]> By: Lawrence Mitchell http://atomized.org/2008/08/response-to-aquamacs-gripes/comment-page-1/#comment-95450 Lawrence Mitchell Fri, 15 Aug 2008 19:01:01 +0000 http://atomized.org/?p=305#comment-95450 Well, not sure. WFM in GNU Emacs 23.0.60.1 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of 2008-07-24. So maybe there is something aquamacs-specific going on. ~/foo.txt should be enterable as: /ssh:remotehost:.emacs///~/foo.txt I think. Well, not sure. WFM in GNU Emacs 23.0.60.1 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of 2008-07-24. So maybe there is something aquamacs-specific going on.

~/foo.txt should be enterable as:

/ssh:remotehost:.emacs///~/foo.txt

I think.

]]> By: Ian http://atomized.org/2008/08/response-to-aquamacs-gripes/comment-page-1/#comment-95442 Ian Fri, 15 Aug 2008 17:58:12 +0000 http://atomized.org/?p=305#comment-95442 @Lawrence, Lame as that is, it would be fine if it, you know, worked. If I use two slashes, I get an error: “Not a tramp file name: /tmp”. Furthermore, the feature where I can open an absolute path on the remote host doesn’t work; If I’m looking at a remote file and I enter “/tmp”, I get the same error. Tramp tries to open “/ssh:user@host:/default/directory//tmp” rather than “/ssh:user@host:/tmp” And how would you enter a path such as “~/foo.txt”? @Lawrence, Lame as that is, it would be fine if it, you know, worked. If I use two slashes, I get an error: “Not a tramp file name: /tmp”. Furthermore, the feature where I can open an absolute path on the remote host doesn’t work; If I’m looking at a remote file and I enter “/tmp”, I get the same error. Tramp tries to open “/ssh:user@host:/default/directory//tmp” rather than “/ssh:user@host:/tmp”

And how would you enter a path such as “~/foo.txt”?

]]> By: Lawrence Mitchell http://atomized.org/2008/08/response-to-aquamacs-gripes/comment-page-1/#comment-95440 Lawrence Mitchell Fri, 15 Aug 2008 17:45:16 +0000 http://atomized.org/?p=305#comment-95440 And a followup. The find-file issue appears to be a feature. If you want to access a completely new path if the current working directory is a tramp path, you need to prefix it with // so: /ssh:remotehost:~/.emacs///tmp/foo finds the file /tmp/foo on localhost. Whereas /ssh:remotehost:~/.emacs//tmp/foo finds the file /tmp/foo on remotehost. And a followup. The find-file issue appears to be a feature. If you want to access a completely new path if the current working directory is a tramp path, you need to prefix it with // so:

/ssh:remotehost:~/.emacs///tmp/foo

finds the file /tmp/foo on localhost. Whereas

/ssh:remotehost:~/.emacs//tmp/foo

finds the file /tmp/foo on remotehost.

]]> By: Lawrence Mitchell http://atomized.org/2008/08/response-to-aquamacs-gripes/comment-page-1/#comment-95437 Lawrence Mitchell Fri, 15 Aug 2008 17:38:33 +0000 http://atomized.org/?p=305#comment-95437 > This may be my inner curmudgeon at work; lisp-mode used to do this, but perhaps that has changed to emacs-lisp-mode. lisp-mode has never been for emacs lisp editing. That C-x C-e worked to evaluate emacs lisp forms in such a mode was a side-effect of emacs not hooking into a lisp interpreter (and hence the local mode not shadowing the global `eval-last-sexp' binding). Slime does this latter and thus C-x C-e tries to evaluate the form in a common lisp sub-process. If that hasn't been set up, then you get a "not connected" error. Lawrence > This may be my inner curmudgeon at work; lisp-mode used to do this, but perhaps that has changed to emacs-lisp-mode.

lisp-mode has never been for emacs lisp editing. That C-x C-e worked to evaluate emacs lisp forms in such a mode was a side-effect of emacs not hooking into a lisp interpreter (and hence the local mode not shadowing the global `eval-last-sexp’ binding). Slime does this latter and thus C-x C-e tries to evaluate the form in a common lisp sub-process. If that hasn’t been set up, then you get a “not connected” error.
Lawrence

]]>