Re: Different emacs arrangements in one session

[Dan Espen <despen@verizon.net>]

Jai Dayal <dayalsoap@gmail.com> writes:
> 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.
...fixed top post (once per customer)
> Well, I guess Frames does *kind of* what I want it to do, I was just using
> it incorrectly.
>
> They're not as disjoint as I'd like, i.e., in one frame, I can access the
> files in another.. I guess Frames really just manages window arrangements,
> and doesn't actually multiplex different emacs sessions over one server.
>
> Also part of the reason I want multiple terminals is because this code is a
> distributed system, so after I compile something and I want to test it, I
> like to be able to lauch multiple processes in different windows and see
> the output live.

I don't think you read and understood what I wrote.


-- 
Dan Espen