IDL

Bundles.IDL History

Show minor edits - Show changes to markup

January 19, 2013, at 23:04 UTC by Infininight - Remove Spam
Changed lines 68-73 from:

EthanGutmann Memutihkan Ketiak

Surat Pengunduran Diri

Saksuk

to:
July 27, 2009, at 09:32 UTC by ZM -
Added line 48:
  • add the IDL bundle to TM's svn repository
August 08, 2006, at 04:20 UTC by Ethan Gutmann -
Added line 9:
  • Code completion for builtin routines (just hit escape)
Changed lines 20-29 from:
  • passes commands back and forth with a persistent IDL session!
  • pseudo commandline interface to IDL builtin
  • compiling
  • display IDL help
  • debugging keyboard shortcuts
  • numerous other useful shortcuts

OUT OF DATE Basic documentation is available courtesy of TextMate's builtin keyboard shortcut generation... but now I can't figure out how to do it again, did something move between releases?

to:
  • passes commands back and forth with a persistent IDL session!
  • pseudo commandline interface to IDL builtin
  • compiling
  • display IDL help
  • debugging keyboard shortcuts
  • numerous other useful shortcuts
Changed lines 31-35 from:
  • does not use " to escape " or ' to escape '
• sort of fixed by allowing an end of line to close a string. This appears to be how IDL treats it anyway as ''' does stay open until the end of the line (even in a compiled program)
  • does not highlight or fold function and procedures
• sort of fixed. Folding works now and if you set your preferences to highlight declaration.function.idl it will be highlighted... but for some reason it highlights the next line too.
to:
  • issues with highlighting local function/procedure names and parameters
Changed line 35 from:
  • code completion - tab to complete local and builtin function/procedure names with default parameters
to:
  • code completion - tab to complete local and builtin function/procedure names with default parameters currently esc completes builtin function
Changed lines 50-52 from:

Still fixing up small issues here and there. At some points I'd like to sit down and learn ruby so I can do some more serious hacking on code completion of various items. I've been meaning to learn it anyway, and Why's (poignant) Guide to Ruby has been a great start so far.

to:

Not sure if I'm going to bother righting more detailed code completion, the builtin completion (after supplying a list of completions) is pretty good. I might see about adding default parameters for them though.

Changed lines 53-54 from:

The above of course begs to have a simple plugin that displays all current IDL variables and their values... and maybe highlights the current position in the code... and errors... oh the possibilities... all of a sudden this becomes a full fledged IDE, esp. if we can get more code completion working

to:

It would be great to have a simple plugin that displays all current IDL variables and their values... and maybe highlights the current position in the code... and errors... I might get to some of this...

June 07, 2006, at 06:11 UTC by Ethan Gutmann -
Changed lines 4-5 from:

Current interface (esp keybindings) is likely to change as I use it and figure out what conflicts with what.

to:

Current interface (esp keybindings) is likely to change as people use it and figure out what conflicts with what.

Changed lines 17-23 from:
to:
  • passes commands back and forth with a persistent IDL session!
  • pseudo commandline interface to IDL builtin
  • compiling
  • display IDL help
  • debugging keyboard shortcuts
  • numerous other useful shortcuts
Added line 27:
  • documentation needs to be written
Changed lines 33-36 from:
to:
  • code completion - tab to complete local variable names, local and builtin function/procedure names
  • support for IDL objects
  • review IDLWAVE mode for other useful features to add
Changed lines 38-40 from:
  • pass commands to IDL
  • read variables from IDL
to:
  • more interaction!
  • view help for current variable
Added lines 47-48:

yeehaw, we can keep a persistent IDL session running and pass commands information back and forth. numerous simple features in the bundle take advantage of this, basically just low hanging fruit. much more to come I hope.

Changed lines 50-55 from:

I wonder if it is possible to keep a persistent IDL process open in the background and send commands to it. I'm not sure how IDLWAVE does this with emacs, I think emacs has its own shell... I suppose It could be done with a separate program just passing information back and forth... or as a textmate plugin... All I want to do is start a process, pass strings to it as standard in, and read strings output by it.

The above may be easy to do using tail, I should have a working command set for this available soon!

The above of course begs to have a simple plugin that displays all current IDL variables and their values... and maybe highlights the current position in the code... and errors... oh the possibilities... all of a sudden this becomes a full fledged IDE.

to:

Seems to work at the moment, but I'm not sure.

The above of course begs to have a simple plugin that displays all current IDL variables and their values... and maybe highlights the current position in the code... and errors... oh the possibilities... all of a sudden this becomes a full fledged IDE, esp. if we can get more code completion working


Maintainers :

EthanGutmann

June 05, 2006, at 22:00 UTC by Ethan Gutmann -
Added lines 1-42:

IDL Bundle Overview

Warning:

Current interface (esp keybindings) is likely to change as I use it and figure out what conflicts with what.

Current features :

  • Syntax Highlighting : Keywords, builtin routines, system variables, system commands
  • Folding
  • Indenting (mostly)
  • Recognizes a program's function names and parameters
  • IDL documentation search :
- open IDL's builtin HTML help libraries
- search IDL's builtin HTML help libraries
- run DOC_LIBRARY to build help files
  • tab completion for common control forms
  • new program template

BUGS :

  • does not use " to escape " or ' to escape ' (e.g. ''' leaves the quotation open)

To Do :

add features you would like to see here...

Interaction with IDL

  • pass commands to IDL
  • read variables from IDL

fix bugs...


A few recent thoughts on the IDL bundle development :

I would also like to read the ENVIRONMENT variables the user has set up when they open a new terminal window. that way I can find their installation of IDL (both for compilation and searching help). Currently it reads the RSI_DIR environment variable, but I'm not sure it will if the default user shell is tcsh... or if they use the GUI to launch IDL??

I wonder if it is possible to keep a persistent IDL process open in the background and send commands to it. I'm not sure how IDLWAVE does this with emacs, I think emacs has its own shell... I suppose It could be done with a separate program just passing information back and forth... or as a textmate plugin... All I want to do is start a process, pass strings to it as standard in, and read strings output by it.

The above may be easy to do using tail, I should have a working command set for this available soon!

The above of course begs to have a simple plugin that displays all current IDL variables and their values... and maybe highlights the current position in the code... and errors... oh the possibilities... all of a sudden this becomes a full fledged IDE.