Different emacs arrangements in one session

Different emacs arrangements in one session

[Jai Dayal]

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?

Thanks much,
Jai

Re: Different emacs arrangements in one session

[Dan Espen]

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

Re: Different emacs arrangements in one session

[Jai Dayal]

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.

Jai


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
>

Re: Different emacs arrangements in one session

[Dan Espen]

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

Re: Different emacs arrangements in one session

[Jai Dayal]

Yes, I read your post just fine. You're talking about strictly compiling.
I'm pointing out that I do more than just compile when i switch to a
terminal. Since it's a distributed system, I also have to re-compile
multiple projects and libraries that link to it as well.

I guess you really didn't answer my question at all, to be honest, but
instead assumed you knew what I needed?


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

> 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
>

Re: Different emacs arrangements in one session

[Dan Espen]

Jai Dayal <dayalsoap@gmail.com> writes:

> Yes, I read your post just fine. You're talking about strictly compiling.
> I'm pointing out that I do more than just compile when i switch to a
> terminal. Since it's a distributed system, I also have to re-compile
> multiple projects and libraries that link to it as well.

Well, all I can say
> I guess you really didn't answer my question at all, to be honest, but
> instead assumed you knew what I needed?
is that I compile and test
>
> On Fri, Jan 24, 2014 at 8:54 PM, Dan Espen <despen@verizon.net> wrote:
distributed systems

>> Jai Dayal <dayalsoap@gmail.com> writes:
>> > On Fri, Jan 24, 2014 at 6:09 PM, Dan Espen <despen@verizon.net> wrote:
using Makefiles and one
>> >> Jai Dayal <dayalsoap@gmail.com> writes:
copy of Emacs every day.
>> >> > Hi,
And I don't have any issues about window arrangement.
I'm not talking about strictly compiling.
Compiling AND testing.
>> >> >   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
>>

-- 
Dan Espen

Re: Different emacs arrangements in one session

[Jai Dayal]

Nope. Sorry, not buying it, especially since the codes are compiled and
executed on different physical machines and communicate over a WAN.

Again, your solution isn't really a solution the my question, at all.

You basically said "well, if you were doing something else, you could do it
this way, therefor, your way is wrong!"




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

> Jai Dayal <dayalsoap@gmail.com> writes:
>
> > Yes, I read your post just fine. You're talking about strictly compiling.
> > I'm pointing out that I do more than just compile when i switch to a
> > terminal. Since it's a distributed system, I also have to re-compile
> > multiple projects and libraries that link to it as well.
>
> Well, all I can say
> > I guess you really didn't answer my question at all, to be honest, but
> > instead assumed you knew what I needed?
> is that I compile and test
> >
> > On Fri, Jan 24, 2014 at 8:54 PM, Dan Espen <despen@verizon.net> wrote:
> distributed systems
>
> >> Jai Dayal <dayalsoap@gmail.com> writes:
> >> > On Fri, Jan 24, 2014 at 6:09 PM, Dan Espen <despen@verizon.net>
> wrote:
> using Makefiles and one
> >> >> Jai Dayal <dayalsoap@gmail.com> writes:
> copy of Emacs every day.
> >> >> > Hi,
> And I don't have any issues about window arrangement.
> I'm not talking about strictly compiling.
> Compiling AND testing.
> >> >> >   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
> >>
>
> --
> Dan Espen
>

Re: Different emacs arrangements in one session

[Rusi]

On Saturday, January 25, 2014 3:59:06 AM UTC+5:30, Jai Dayal wrote:
> 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.

Ive heard that people find gnu screen useful for this -- no experience myself

Re: Different emacs arrangements in one session

[Jai Dayal]

Yes. Screen and Tmux are good for this. I was using Tmux before asking on
here. I just wondered of there was a way to do it solely inside emacs.
Frames is pretty close, now that I'm using them correctly.


On Fri, Jan 24, 2014 at 9:53 PM, Rusi <rustompmody@gmail.com> wrote:

> On Saturday, January 25, 2014 3:59:06 AM UTC+5:30, Jai Dayal wrote:
> > 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.
>
> Ive heard that people find gnu screen useful for this -- no experience
> myself
>

Re: Different emacs arrangements in one session

[N. Jackson]

Jai Dayal <dayalsoap@gmail.com> writes:

> 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'm no expert on Emacs and it's not clear (to me) exactly what behaviour
you're looking for, but I understand you to be saying that you want to
have the buffers visible from one frame be different from the buffers
visible from another frame.

You can do this simply by running seperate instances of Emacs.

Or, if you are using Emacs server, I believe you can run mulitple
servers by giving them different names.

For details see:

M-: (info "(emacs) Emacs Server")

N.

Re: Different emacs arrangements in one session

[Jai Dayal]

Yes, but if I do it via separate emacs instances, I can't actually copy and
paste things from one to the other solely in emacs.

I use emacs on a server over ssh, and I just use it through the terminal..
no x windows or anything.

Frames are working just fine, the problem is frame state is not saved
across emacs sessions. Apparently, this feature is native to 24.4, but I
can't find anything reasonable for 24.3.


On Fri, Jan 31, 2014 at 9:11 PM, N. Jackson <nljlistbox2@gmail.com> wrote:

> Jai Dayal <dayalsoap@gmail.com> writes:
>
> > 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'm no expert on Emacs and it's not clear (to me) exactly what behaviour
> you're looking for, but I understand you to be saying that you want to
> have the buffers visible from one frame be different from the buffers
> visible from another frame.
>
> You can do this simply by running seperate instances of Emacs.
>
> Or, if you are using Emacs server, I believe you can run mulitple
> servers by giving them different names.
>
> For details see:
>
> M-: (info "(emacs) Emacs Server")
>
> N.
>

Re: Different emacs arrangements in one session

[Jai Dayal]

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
>

Re: Different emacs arrangements in one session

[Dan Espen]

Jai Dayal <dayalsoap@gmail.com> writes:

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

Still top posting?

> 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.

I see.

Because you can't figure out how to run compiles and tests on remote
machines then it's impossible.
I wonder how I've been doing it all this time...

You know, I saw your post and I pictured all these windows and jumping
around and all that stuff, and I thought, gee, I don't have that
problem,  I think I might be able to help...

Good luck.

-- 
Dan Espen

Re: Different emacs arrangements in one session

[Jai Dayal]

I don't know what "top posting" is.

See, again, you're still stuck on "compiling" (which is really only 1/3 of
the workflow). Even still, remote-compile-host doesn't work because in
order to get to the remote hosts, you need an RSA token, and the last time
I tried that route, remote-compile didn't understand that security feature.


Jumping around windows isn't bad at all since it can all be done via frames
and keyboards.


On Fri, Jan 31, 2014 at 11:50 PM, Dan Espen <despen@verizon.net> wrote:

> Jai Dayal <dayalsoap@gmail.com> writes:
>
> > Since you tried to be pedantic and not actually answer my question,
> explain
> > this:
>
> Still top posting?
>
> > 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.
>
> I see.
>
> Because you can't figure out how to run compiles and tests on remote
> machines then it's impossible.
> I wonder how I've been doing it all this time...
>
> You know, I saw your post and I pictured all these windows and jumping
> around and all that stuff, and I thought, gee, I don't have that
> problem,  I think I might be able to help...
>
> Good luck.
>
> --
> Dan Espen
>

Re: Different emacs arrangements in one session

[Jai Dayal]

The problem is that this is a persistent problem amongst computer
scientists and software engineers. They try to opine on small little
details that actually never address the problem at hand. I asked a very
specific question, and instead of getting an answer to that question, an
assumption of "I know you're doing it wrong because I do it this way" was
made and then the question never gets answered.



On Fri, Jan 31, 2014 at 11:50 PM, Dan Espen <despen@verizon.net> wrote:

> Jai Dayal <dayalsoap@gmail.com> writes:
>
> > Since you tried to be pedantic and not actually answer my question,
> explain
> > this:
>
> Still top posting?
>
> > 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.
>
> I see.
>
> Because you can't figure out how to run compiles and tests on remote
> machines then it's impossible.
> I wonder how I've been doing it all this time...
>
> You know, I saw your post and I pictured all these windows and jumping
> around and all that stuff, and I thought, gee, I don't have that
> problem,  I think I might be able to help...
>
> Good luck.
>
> --
> Dan Espen
>

Re: Different emacs arrangements in one session

[Glyn Millington]

Jai Dayal <dayalsoap@gmail.com> writes:

> I don't know what "top posting" is.

Top-posting is replying at the top of your post, rather than down below,
that is below the material to which you are responding, which keeps the
post-then-response sequence intact and makes it easier to follow the
thread. 


> Jumping around windows isn't bad at all since it can all be done via
> frames and keyboards.

Have a look here, where there are various packages which allow to switch
between named window configurations.  Whether they will work remotely,
and whether they preserve data across sessions I have no idea. 

http://www.emacswiki.org/emacs/WinRing



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

Nobody here is paid to respond to you.  Many people here are certainly
more technically competent than I am and possibly even more so than you.
A little patience helps. As do clearer and more comprehensive explanations
of what you are seeking.


atb

Glyn

Re: Different emacs arrangements in one session

[Richard Riley]

Jai Dayal <dayalsoap@gmail.com> writes:

> I don't know what "top posting" is.

Its posting a reply with your bit at the top and not properly embedded
relative to the text you're replying to. It's generally frowned on for a
good reason : the reader can have no idea of what you're replying to without
scrolling down and trying to figure out which bit of the original post
you replied to is actually relevant. It's a "standard" to not top post
for a reason - I would recommend adopting it or a lot of good people
with a lot to offer will ignore your posts.

>
> See, again, you're still stuck on "compiling" (which is really only
> 1/3 of

See what? See? ;)

> the workflow). Even still, remote-compile-host doesn't work because in
> order to get to the remote hosts, you need an RSA token, and the last time
> I tried that route, remote-compile didn't understand that security feature.
>
> Jumping around windows isn't bad at all since it can all be done via frames
> and keyboards.
>
> On Fri, Jan 31, 2014 at 11:50 PM, Dan Espen <despen@verizon.net> wrote:
>
>> Jai Dayal <dayalsoap@gmail.com> writes:
>>
>> > Since you tried to be pedantic and not actually answer my question,
>> explain
>> > this:
>>
>> Still top posting?
>>
>> > 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.
>>
>> I see.
>>
>> Because you can't figure out how to run compiles and tests on remote
>> machines then it's impossible.
>> I wonder how I've been doing it all this time...
>>
>> You know, I saw your post and I pictured all these windows and jumping
>> around and all that stuff, and I thought, gee, I don't have that
>> problem,  I think I might be able to help...
>>
>> Good luck.
>>
>> --
>> Dan Espen
>>
>

-- 
Sent using Emacs/Gnus from home ...