Re: Different emacs arrangements in one session

[Jai Dayal <dayalsoap@gmail.com>]

Since you tried to be pedantic and not actually answer my question, explain
this:

I have code on machine 1. I make a change, compile it, and then git commit
it.

On machine 2 and also on machine 3, I have to git pull, and then compile.

Then I have to launch the codes that test it. Machine 1 runs something,
machine 2 runs something, machine 3 runs something, etc.

That's why I like having multiple terminals in my emacs session; in one
frame I have all of my code buffers. In the other frame, I have all of my
terminals (ssh'd into machine 2, machine 3 and one for machine 1). From
there, I can launch the respective codes, git pull, and compile.

You can't do that with M-x compile.

So basically, you tried to be pedantic, and were *wrong* with your stupid
suggestion.


On Fri, Jan 24, 2014 at 6:09 PM, Dan Espen <despen@verizon.net> wrote:

> Jai Dayal <dayalsoap@gmail.com> writes:
>
> > Hi,
> >
> >   I use Emacs primarily for development over SSH into a remote server. I
> > generally have several terminal sessions, many buffers of code, etc.
>  Often
> > times, I want the window arrangement for my ansi-term buffers to be
> > different than my code buffers.
> >
> > For example, Perhaps, I have my code buffers split into quarters, and
> then
> > I want to switch to one of my ansi-terms to compile the code. As it
> stands
> > now, that ansi-term will just take up one of my quarter screens, when I
> > want this to be my full screen.
> >
> > Any idea how to do this? I've looked at frames, but it doesn't seem to
> > quite work right?
> >
> > It should be noted, that on the remote server, I generally do emacs
> > --daemon and then emacsclient -c -nw
> >
> > this way, my environment persists across different logins.
> >
> > Any idea how I can accomplish the above?
>
> No not really.
>
> But switching to a terminal session to do a compile might not be the
> best way to use Emacs.  I do all my work in a similar ssh'd Emacs
> and save huge amounts of time driving all my compiling _and testing_
> using M-x compile.
>
> There are a lot of benefits to working this way.
> You'll never compile without saving your file first,
> Emacs can use the compiler messages to access lines in error,
> and if multiple files need compiling before a test
> the makefile takes care of all that.
>
> Oh, also, the window configuration is managed by M-x compile.
>
> --
> Dan Espen
>