| 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
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
