Re: Different emacs arrangements in one session

[Richard Riley <rileyrg@gmail.com>]

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