ct6502 / vscode-idl Goto Github PK

With the VSCode Python extension running in a project that uses both Python and IDL, the Python extension will still try to activate the environment in use (in this case, my base environment).

When I open an IDL terminal from the command pallet (ctrl + shift + p), I get the following:

C:\Users\asher\ion-transport>cd C:\Users\asher\ion-transport && idl
IDL 8.8.1 (Win32 x86_64 m64).
(c) 2021, Harris Geospatial Solutions, Inc.

Licensed for use by: <me>
License: <my license>
License expires 31-Aug-2022.
IDL> C:/Users/asher/Anaconda3/Scripts/activate

C:/Users/asher/Anaconda3/Scripts/activate     
   ^
% Syntax error.
IDL> conda activate base

conda activate base     
       ^
% Syntax error.
IDL> 

Not a functionality-impairing bug, but something to be aware of that could be fixed.

I press F5 to choose IDL Debug for compiling the program, but an error occurred. It shows "You don't have an extension for debugging IDL. Should we find a IDL extension in the Markerplace?"
What's wrong with it？ If someone can help me solve this problem, I would be very grateful

Hi, I am using the vscode-idl extension for a while and love it. Yesterday the new version came out with lots of new features which I find so convenient. But the auto completion doesn't work for the variables in the file any more. Is this a bug or I didn't do it in the right way? Thanks a lot in advance.

Placeholder to add debugging into the extension.

The IDL executable name is hard-coded to idl. Can you change that to a configurable value, eg IDL_EXECUTABLE? Then
vscode-idl would work with FL and GDL, too.

Thanks,
Lajos Foldy

Hi, I have enjoyed using this extension for several months. Could I suggest two features which I think would further improve the usability of this great tool?

1. able to run or compile the pro file using the command palette (Ctrl+Shift+P), so I don't have to click the Run/Compile button in the panel every time
2. simple debug functionality which enables to insert breakpoints

Maybe a related question about debugging in IDL, I can only access the variables inside the called procedure/function but no variables outside it or in the main program. Can I ask if there is a way to resolve this?

Placeholder in case anyone else has this issue. Breakpoints do not always:

• Remove as expected. Meaning you remove them, but IDL still stops on them

• Get added as expected. Meaning that IDL does not always stop on them.

  • This has to do with some magic that the IDL Workbench does which recompiles them on the fly if it can.

Just loaded the extension to VS Code. Attempted to try a couple simple lines of code and when I hit run without debugging get looking for debug client. when I go to the extension and try to run the code from there I get a popup to start a debug session. and this is preventing the execution of a simple hello world program.

pro Hello
print, 'Hello World!'
end