Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado
Gianguido Cianci writes: > Is it possible to have two idl shells in the same emacs? I am using a > multiprocessor machine and do most of my work interactively, so it > would be nice to be able to do that. You might want to sign up as one of the beta testers for FastDL, which was mentioned in this newsgroup earlier today. I had a chance to fool around with that several months ago and I was extremely impressed. IDL tasks can easily be farmed out to specific processors on your machine, or to other processors in a network. You can have as many IDL "tasks" going on as many processors as you like. Very slick and very easy to do from the IDL command line. Cheers, David -- David Fanning, Ph.D. Fanning Software Consulting, Inc. Coyote's Guide to IDL Programming: http://www.dfanning.com/ Sepore ma de ni thui. (Opata Indian saying, meaning "Perhaps thou speakest truth.")
Yes I am thinking about it, looks very nice.... is this your way of saying it can't be done in idlwave? G David Fanning wrote: > Gianguido Cianci writes: > >> Is it possible to have two idl shells in the same emacs? I am using a >> multiprocessor machine and do most of my work interactively, so it >> would be nice to be able to do that. > > You might want to sign up as one of the beta testers > for FastDL, which was mentioned in this newsgroup > earlier today. I had a chance to fool around with that > several months ago and I was extremely impressed. > IDL tasks can easily be farmed out to specific > processors on your machine, or to other processors > in a network. You can have as many IDL "tasks" going > on as many processors as you like. Very slick and > very easy to do from the IDL command line. > > Cheers, > > David > -- > David Fanning, Ph.D. > Fanning Software Consulting, Inc. > Coyote's Guide to IDL Programming: http://www.dfanning.com/ > Sepore ma de ni thui. > (Opata Indian saying, meaning "Perhaps thou speakest truth.")
Gianguido Cianci writes: > Yes I am thinking about it, looks very nice.... is this your way of > saying it can't be done in idlwave? No, no. As far as I know *everything* can be done in IDLWAVE. But I just let JD handle everything in that realm. :-) Cheers, David P.S. Let's just say I tried to learn how to use IDLWAVE several months ago and I got, uh, stuck. I just couldn't think and type at the same time. Too frustrating. Maybe if I had grown up with it...Maybe it was too much like learning French for my trip to Africa. But if JD is back from Hawaii, I'm sure he will fill you in. -- David Fanning, Ph.D. Fanning Software Consulting, Inc. Coyote's Guide to IDL Programming: http://www.dfanning.com/ Sepore ma de ni thui. (Opata Indian saying, meaning "Perhaps thou speakest truth.")
On Thu, 31 Aug 2006 14:06:06 -0600, David Fanning wrote: > No, no. As far as I know *everything* can be done in > IDLWAVE. But I just let JD handle everything in that > realm. :-) Actually, in this case the answer is "not easily". IDLWAVE knows of and keeps track of a single IDL shell process at a time. You can obviously run two different Emacs sessions and have a shell in each. Let's say you're compiling a file (C-c C-d C-c). Which shell should it compile in? That's just one example of many where having more than one shell would be somewhat problematic. You might like this tip regarding starting a "fast" IDL shell in Emacs without first loading a .pro file into a buffer: ============================================================ ============== IDLWAVE Tip of the Month: Do you love IDLWAVE for editing source and debugging, but often find yourself pulling up an XTerm IDL for quick calculations, not wanting the full IDLWAVE source buffer editing mode? Wouldn't you love to have all the same completion, on-line help and routine info features you've come to love during full-blown editing sessions? Get a quick IDLWAVE IDL Shell, without any buffer, using: emacs --geometry 80x36 --eval "(idlwave-shell 'quick)" I have this bound to a button in my launcher panel. Never be without IDLWAVE again. ============================================================ ============== I might also suggest looking at the IDL-IDL bridge. This lets the primary IDL session manage sub-sessions, to which some work can be farmed out. It comes with IDL 6.3. JD
Hi JD, thanks for your help. 'C-c C-d C-c' followed by a number identifying the session could solve the problem you mention. Also 'C-c C-d C-c a' could compile in all (idle) sessions.... if my recompiled code is better, then why not have it available to all sesions.... JD Smith wrote: > On Thu, 31 Aug 2006 14:06:06 -0600, David Fanning wrote: > >> No, no. As far as I know *everything* can be done in >> IDLWAVE. But I just let JD handle everything in that >> realm. :-) > > Actually, in this case the answer is "not easily". IDLWAVE knows of and > keeps track of a single IDL shell process at a time. You can obviously > run two different Emacs sessions and have a shell in each. Let's say > you're compiling a file (C-c C-d C-c). Which shell should it compile in? > That's just one example of many where having more than one shell would be > somewhat problematic. > Yes I do like it! > You might like this tip regarding starting a "fast" IDL shell in Emacs > without first loading a .pro file into a buffer: > > ============================================================ ============== > IDLWAVE Tip of the Month: > > Do you love IDLWAVE for editing source and debugging, but often find > yourself pulling up an XTerm IDL for quick calculations, not wanting the > full IDLWAVE source buffer editing mode? Wouldn't you love to have all > the same completion, on-line help and routine info features you've come > to love during full-blown editing sessions? Get a quick IDLWAVE IDL > Shell, without any buffer, using: > > emacs --geometry 80x36 --eval "(idlwave-shell 'quick)" > > I have this bound to a button in my launcher panel. Never be without > IDLWAVE again. > ============================================================ ============== As far as IDL-IDL bridbe, it seems to involve objects... I have never gone that deep into IDL and use it mainly as a command line image analysis system... no gui, no objects... it does look interesting however, and if I can figure out how to use it interactively from the commandline then I will definetly give it a shot. > I might also suggest looking at the IDL-IDL bridge. This lets the > primary IDL session manage sub-sessions, to which some work can be > farmed out. It comes with IDL 6.3. > > JD Thanks again, Gianguido