| Re: changing editors? [message #31241] |
Wed, 26 June 2002 17:12  |
Mark Hadfield
Messages: 783
Registered: May 1995
|
Senior Member |
|
|
"tim gunter" <tim.gunter@bioscrypt.com> wrote in message
news:f924816d.0206261524.11b07d6@posting.google.com...
> i played around some with simply opening the file in gvim, and
> editing it, but i had trouble getting IDLDE to recognize that the
> file had been modified.
That's why I open it with .edit first. The IDLDE editor detects
modified files and offers to reload them.
> i would find it _extremely_ useful. especially if i could use use
> IDL in combination with cygwin and bash to script IDL programs. i
> cant imagine it would take much development effort on RSIs part to
> release a windows command line IDL utility of some sort. they
> already provide one on UNIX platforms.
Best suggest it to them. How many millions of dollars of business do
you do with RSI?
--
Mark Hadfield "Ka puwaha te tai nei, Hoea tatou"
m.hadfield@niwa.co.nz
National Institute for Water and Atmospheric Research (NIWA)
|
|
|
|
| Re: changing editors? [message #31242 is a reply to message #31241] |
Wed, 26 June 2002 16:24  |
tim.gunter
Messages: 2
Registered: June 2002
|
Junior Member |
|
|
"Mark Hadfield" <m.hadfield@niwa.co.nz> wrote in message news:<af848b$ir6$1@newsreader.mailgate.org>...
> I use XEmacs with idlwave mode for most of my IDL editing on
> windows. What I have done is this:
emacs??? uuueeeeeewwwwwwwwww!!!
;)
> - Write a macro to open the current file in my editor and attach it
> to a handy key combination The macro command is something like
>
> spawn, 'xemacs "%f"'
>
> (Actually it's not exactly that because I have wrapped the command
> to spawn xemacs in a procedure, but you get the idea. I'm not sure
> if the quoting is right.)
>
> - Open each .pro file I want to edit in the IDLDE editor with the
> .edit executive command.
>
> - Run macro and edit file in xemacs.
>
> - When finished editing, close file and return to IDLDE. IDLDE sees
> that the file has been modified and asks whether to reload it. Say
> yes! Then compile.
i havent tried the spawn and .edit technique.
i played around some with simply opening the file in gvim, and editing
it, but i had trouble getting IDLDE to recognize that the file had
been modified. in visual studio, i am able to have a file open in
visual studio and gvim, and both do a pretty good job of recognizing
when the other has modified the file. not ideal, but acceptable.
> There's no technical reason why a console-mode IDL executable doesn't
> exist. It would be handy with (X)Emacs idlwave mode. If enough users
> hassled RSI they *could* release one, but don't hold your breath.
i would find it _extremely_ useful. especially if i could use use IDL
in combination with cygwin and bash to script IDL programs. i cant
imagine it would take much development effort on RSIs part to release
a windows command line IDL utility of some sort. they already provide
one on UNIX platforms.
> I use both Cygwin & IDL a great deal. Spawning Cygwin commands from
> IDL is straightforward. Getting information from IDL to Cygwin
> involves kludges: write a file in IDL, switch to command shell and
> read file, that sort of thing.
yes, cygwin is a godsend. one of the most useful pieces of software i
have ever had the joy of using. windows is unusable to me without it.
thanks for your suggestions, ill see what i can rig up.
--tim
|
|
|
|
| Re: changing editors? [message #31279 is a reply to message #31242] |
Mon, 24 June 2002 14:50 |
Mark Hadfield
Messages: 783
Registered: May 1995
|
Senior Member |
|
|
"tim gunter" <tim.gunter@bioscrypt.com> wrote in message
news:f924816d.0206240946.323f49b@posting.google.com...
> I'm running IDL 5.4 on Windows 2k. I have been trying to figure out
> if there is a way to change from the default IDL editor to a
> different one, such as gvim.
No there isn't.
I use XEmacs with idlwave mode for most of my IDL editing on
windows. What I have done is this:
- Write a macro to open the current file in my editor and attach it
to a handy key combination The macro command is something like
spawn, 'xemacs "%f"'
(Actually it's not exactly that because I have wrapped the command
to spawn xemacs in a procedure, but you get the idea. I'm not sure
if the quoting is right.)
- Open each .pro file I want to edit in the IDLDE editor with the
.edit executive command.
- Run macro and edit file in xemacs.
- When finished editing, close file and return to IDLDE. IDLDE sees
that the file has been modified and asks whether to reload it. Say
yes! Then compile.
It's messy, but it works as long as you don't make changes in both
editors at once.
> Also it appears there is no way to run IDL from the command line
> under windows, is there any way to do so?
No. At least, you can launch IDLDE from a command line if you want,
but it's the same window-mode application as you get from clicking on
the shortcut. There's no console-mode IDL.
There's no technical reason why a console-mode IDL executable doesn't
exist. It would be handy with (X)Emacs idlwave mode. If enough users
hassled RSI they *could* release one, but don't hold your breath.
> Any help on getting IDL to work better with command line utils (in
> particular cygwin) would be helpful.
I use both Cygwin & IDL a great deal. Spawning Cygwin commands from
IDL is straightforward. Getting information from IDL to Cygwin
involves kludges: write a file in IDL, switch to command shell and
read file, that sort of thing.
--
Mark Hadfield "Ka puwaha te tai nei, Hoea tatou"
m.hadfield@niwa.co.nz
National Institute for Water and Atmospheric Research (NIWA)
>
|
|
|
|
|
|
| Re: changing editors? [message #31387 is a reply to message #31242] |
Tue, 09 July 2002 15:14 |
condor
Messages: 35
Registered: January 2002
|
Member |
|
|
tim.gunter@bioscrypt.com (tim gunter) wrote in message news:<f924816d.0206261524.11b07d6@posting.google.com>...
> [...]
> i would find it _extremely_ useful. especially if i could use use IDL
> in combination with cygwin and bash to script IDL programs.
and
> yes, cygwin is a godsend. one of the most useful pieces of software i
> have ever had the joy of using. windows is unusable to me without it.
So this is most probably a stupid question, but why not chuck windows
and use one of the approximately zillion Linux flavors out there? You
seem to be using your win-box mostly as a u*x box anyways, so why not
just go that one last step?
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
