Work Emacs At Home

[eljobe]

Connecting To A Running Emacs Via SSH
If you are one of those readers of my blog who really likes hearing about how my life is going, but you don't really care about interesting technical problems, please pardon the rest of this post.

Comments

[erikharrison]

This actually doesn't make any sense to me. I'm not an emacs user[*], but why oh why does specifying the X display to emacs when you invoke it make emacs hunky dory with attaching to ANY display?

A quick check of man emacs doesn't clarify either. Of course, if it works for you, then I suppose it doesn't matter why. If you ask me the real solution is for the underlying toolkits to support display switching. Then you could do something like:

$ display-switch `pidof emacs` localhost:10.0

-Erik

* Anymore. I used to use emacs but now I use a combination of Geany/joe/Mousepad. And I never really mastered emacs.

[eljobe]

Hmm. Maybe I need to clarify this in the above instructions. It is not the fact that you are specifying a Display to emacs upon initial invocation that allows it to open new frames on other displays. It is the fact that you are starting emacs in a shell which was invoked with an ssh tunnel already created back to the display you want to open the new frame on

[erikharrison]

Oh yeah. I musta skimmed that part of the instructions. Blah. So you're starting emacs with DISPLAY=10.0 and then specifying the work machines 0.0 on the command line. Makes sense.

It occurs to me that if you were willing to use emacs in a terminal, screen would be a better fit all around.

[ckillian]

I am definitely a big fan of screen. The especially nice thing about screen is that you can save not only buffers, but also terminal output, running commands, etc.

Of course, I too was once an Emacs user, but have since decided I much prefer using Vi to Emacs. And what's especially nice is that Vi is especially well suited to running in a terminal.

Pepper -- now that you're a Google employee, will you be switching to Blogger?