| Re: idlde: Linux vs. Windows [message #36323] |
Tue, 09 September 2003 20:49  |
JD Smith
Messages: 850
Registered: December 1999
|
Senior Member |
|
|
On Tue, 09 Sep 2003 20:10:40 -0700, Craig Markwardt wrote:
> odell@aos.wisc.edu (Chris ODell) writes:
>> So tell me, what is an idl programmer in linux to do? What do you guys
>> do (I'm thinking of Craig Marquardt, Liam Gumley, David Fanning, etc)?
>> All use
>> emacs plus the simple idl command line interface? Or something else?
>
> Hi Chris, I use emacs, but then again I always used emacs. I use
> idlwave for the formatting. Generally I have an emacs window and a
> terminal window side by side: edit in emacs, run and debug in the
> terminal. Nothing fancy.
>
When I started using IDLWAVE, I was in exactly the same boat. I'd always
used Emacs, so it was natural to continue doing so. I had also always run
IDL in an xterm, and the concept of running it *inside* of Emacs was
entirely anathema. A few things changed my mind. It's incredibly
natural. I can use all my favorite editing tricks right on the command
line. I can grab bits of old commands or output and assemble new commands
on the fly. But once you let the IDLWAVE buffers start talking to the IDL
Shell, a whole new world of power is opened up. I won't recount all the
details, since David has (im)memorialized most of them on his site in one
of my posts (looks for something about sliced bread). I will say this:
just fire up the shell sometime -- C-c C-s. Use it for a few minutes.
Kill it with C-d and go back to your familiar xterm... no bid deal, no
problems. Everything is still in place. Try it again in a few days. Try
the completion... just hit Tab as you go. A few days or weeks later, try
getting routine info on a routine as you go (C-c ?). Baby steps.
JD
|
|
|
|
|
|
| Re: idlde: Linux vs. Windows [message #36325 is a reply to message #36324] |
Tue, 09 September 2003 18:37  |
R.Bauer
Messages: 1424
Registered: November 1998
|
Senior Member |
|
|
Chris ODell wrote:
> I have just switched jobs, and in the process have been forced to
> migrate from Windows to Linux. I have a lot of programming in the
> windows IDLDE and really love it. Color coding, lots of preferences
> available (like getting the silly project manager off the desktop),
> etc. I see (in previous threads) that there are some weird technical
> reasons why idlde in Linux totally bites.
>
> So tell me, what is an idl programmer in linux to do? What do you
> guys do (I'm thinking of Craig Marquardt, Liam Gumley, David Fanning,
> etc)? All use
> emacs plus the simple idl command line interface? Or something else?
>
> I realize I am new to programming IDL under linux, so I am figuring
> people out there have come up with a nice system (equal in
> functionality to the windows idlde i hope!) for linux idl
> programming/debugging/running. Just curious what it is.
>
> BTW, i am now running Linux RedHat 9 with IDL 6.0.
>
> Cheers,
> Chris O'Dell
Dear Chris,
I believe you have followed the previous thread: "Syntaxis highlighting in
IDL 6." If not you should do so.
I just want to say, it depends always on your experience. Sometimes I just
need only a simple editor e.g. vi.
If I need to debug a greater package I am using emacs (idlpvwave) or idlde.
emacs has a lot of benefits. You could format the code, You always see the
structure of the code (which "(" belongs to which ")" ) etc.
Reimar
--
Forschungszentrum Juelich
email: R.Bauer@fz-juelich.de
http://www.fz-juelich.de/icg/icg-i/
============================================================ ======
a IDL library at ForschungsZentrum Juelich
http://www.fz-juelich.de/icg/icg-i/idl_icglib/idl_lib_intro. html
|
|
|
|
| Re: idlde: Linux vs. Windows [message #36412 is a reply to message #36323] |
Wed, 10 September 2003 09:04 |
odell
Messages: 6
Registered: September 2003
|
Junior Member |
|
|
Thanks everyone for the comments. I was really used to the nice
functionality in the windows IDLDE -- not just syntax highlighting,
but the variable window which shows everything that is in memory (main
level, system vars, etc), and having lots of windows open at once,
also along with the buttons/menus for compiling and debugging. I'm
totally new to emacs, so its advantages aren't very apparent yet.
But, I tried to bite to the bullet and get IDLWAVE going on my emacs
(xemacs to be precise). No go -- it complained about some # character
thing when I did
Ctrl-c Ctrl-s. I also tried it with regular emacs; it gave me a
different error, but still wouldn't open the idlwave shell. bummer.
maybe it's b/c i'm using idl 6.0? or maybe rh9 is just buggy. i miss
windows, never thought i'd say that!
Chris
JD Smith <jdsmith@as.arizona.edu> wrote in message news:<pan.2003.09.09.20.49.24.825284.30642@as.arizona.edu>...
> On Tue, 09 Sep 2003 20:10:40 -0700, Craig Markwardt wrote:
>
>
>> odell@aos.wisc.edu (Chris ODell) writes:
>>> So tell me, what is an idl programmer in linux to do? What do you guys
>>> do (I'm thinking of Craig Marquardt, Liam Gumley, David Fanning, etc)?
>>> All use
>>> emacs plus the simple idl command line interface? Or something else?
>>
>> Hi Chris, I use emacs, but then again I always used emacs. I use
>> idlwave for the formatting. Generally I have an emacs window and a
>> terminal window side by side: edit in emacs, run and debug in the
>> terminal. Nothing fancy.
>>
>
> When I started using IDLWAVE, I was in exactly the same boat. I'd always
> used Emacs, so it was natural to continue doing so. I had also always run
> IDL in an xterm, and the concept of running it *inside* of Emacs was
> entirely anathema. A few things changed my mind. It's incredibly
> natural. I can use all my favorite editing tricks right on the command
> line. I can grab bits of old commands or output and assemble new commands
> on the fly. But once you let the IDLWAVE buffers start talking to the IDL
> Shell, a whole new world of power is opened up. I won't recount all the
> details, since David has (im)memorialized most of them on his site in one
> of my posts (looks for something about sliced bread). I will say this:
> just fire up the shell sometime -- C-c C-s. Use it for a few minutes.
> Kill it with C-d and go back to your familiar xterm... no bid deal, no
> problems. Everything is still in place. Try it again in a few days. Try
> the completion... just hit Tab as you go. A few days or weeks later, try
> getting routine info on a routine as you go (C-c ?). Baby steps.
>
> JD
|
|
|
|
| Re: idlde: Linux vs. Windows [message #36418 is a reply to message #36323] |
Wed, 10 September 2003 07:03 |
savoie
Messages: 68
Registered: September 1996
|
Member |
|
|
Add me to the choir. I've always used emacs and using it with the idlwave is
just a natural extension. But of course, I use emacs as my mail/news reader
and shell too. It's pretty much my operating system and when I have to go
work on a windows machine I feel like someone has cut off all of my fingers
and I have to edit with my nose. But like JD said, just give it a try. You
don't even have to do anything fancy if you start up the idlwave shell it's
just like having an xterm until you start learning little tricks. Pretty
soon, you can't imagine how anyone could work any other way.
Matt
JD Smith <jdsmith@as.arizona.edu> writes:
> On Tue, 09 Sep 2003 20:10:40 -0700, Craig Markwardt wrote:
>> odell@aos.wisc.edu (Chris ODell) writes:
>>> So tell me, what is an idl programmer in linux to do? What do you guys
>>> do (I'm thinking of Craig Marquardt, Liam Gumley, David Fanning, etc)?
>>> All use
>>> emacs plus the simple idl command line interface? Or something else?
--
Matthew Savoie - Scientific Programmer
National Snow and Ice Data Center
(303) 735-0785 http://nsidc.org
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
