Recent Posts91
SlickEdit® / Re: Debugging in SlickEdit
« Last post by gkl on February 10, 2025, 02:45:49 PM »Dear Clark,
3.13.
Best Regards,
George
3.13.
Best Regards,
George
Recent Posts
92
SlickEdit® / Re: copy file name to clipboard does not work outside of slickedit
« Last post by Clark on February 10, 2025, 02:41:50 PM »What specific Linux are you on? Works for me. Tried Linux Mint 21, Ubuntu 24, and Rocky 8.1
93
SlickEdit® / copy file name to clipboard does not work outside of slickedit
« Last post by losvatoslocos on February 10, 2025, 01:58:10 PM »hi all,
just noticed a strange thing with my Slickedit PRO v29.0.0.0 on Linux (still on trial).
If I do Copy Full Name To Clipboard or Copy Name To Clipboard, none of them can escape outside of the editor, in other words, I cannot paste the copied data in another app. Interestingly, if I select a text and copy it (CTRL+C), it does work and propagates to other apps. Is there anything I'm doing wrong? I thought such a trivial features should just work.
PS
If I do Edit -> List Clipboard, I always do see my filename or path added on top of the list. Weird.
just noticed a strange thing with my Slickedit PRO v29.0.0.0 on Linux (still on trial).
If I do Copy Full Name To Clipboard or Copy Name To Clipboard, none of them can escape outside of the editor, in other words, I cannot paste the copied data in another app. Interestingly, if I select a text and copy it (CTRL+C), it does work and propagates to other apps. Is there anything I'm doing wrong? I thought such a trivial features should just work.
PS
If I do Edit -> List Clipboard, I always do see my filename or path added on top of the list. Weird.
94
SlickEdit® / Re: Debugging in SlickEdit
« Last post by Clark on February 10, 2025, 01:34:13 PM »What version of Python are you using?
95
SlickEdit® / Debugging in SlickEdit
« Last post by gkl on February 10, 2025, 10:17:16 AM »Dear All,
I am in SlickEdit 28.0.1 on Windows 11 and I am trying to debug a single file Python project, i.e. a Python source file. I click on Debug and Start, get the debugging menu, but then SlickEdit says that the socket shut down (please see attached image). How can I solve this?
Best Regards,
George
I am in SlickEdit 28.0.1 on Windows 11 and I am trying to debug a single file Python project, i.e. a Python source file. I click on Debug and Start, get the debugging menu, but then SlickEdit says that the socket shut down (please see attached image). How can I solve this?
Best Regards,
George
96
SlickEdit® / Re: Execute menu option is greyed out
« Last post by gkl on February 10, 2025, 10:12:43 AM »Dear Clark,
It turns out that Mapping execution aliases was the reason, I had Python installed from the Microsoft Store and for some reason, it wasn't been picked up. I switched the alias to off and now it works. I have a separate issue with the debugger, but I will make a separate post about it.
Best Regards,
George
It turns out that Mapping execution aliases was the reason, I had Python installed from the Microsoft Store and for some reason, it wasn't been picked up. I switched the alias to off and now it works. I have a separate issue with the debugger, but I will make a separate post about it.
Best Regards,
George
97
SlickEdit® / Re: Execute menu option is greyed out
« Last post by Clark on February 09, 2025, 03:53:37 PM »If this normally has those menu items enabled, sometimes there's a delay in the menu updating. Restart SlickEdit if the menu remains incorrect.
Note that your'e not on the latest version of v28. The latest version is 28.0.2. Although, I don't expect updating to change what you are seeing here.
Note that your'e not on the latest version of v28. The latest version is 28.0.2. Although, I don't expect updating to change what you are seeing here.
98
SlickEdit® / Execute menu option is greyed out
« Last post by gkl on February 09, 2025, 03:43:23 PM »Dear All,
I am on 28.0.1 on Windows 11 and out of the blue, the Execute option under Build is greyed out. I would usually have single Python files that I will execute by going to the Build menu and selecting Execute. Now, this option is greyed out as seen in the attached image. How can I bring it back?
Best Regards,
George
I am on 28.0.1 on Windows 11 and out of the blue, the Execute option under Build is greyed out. I would usually have single Python files that I will execute by going to the Build menu and selecting Execute. Now, this option is greyed out as seen in the attached image. How can I bring it back?
Best Regards,
George
99
SlickEdit® / Re: Unable to debug on macOS
« Last post by Clark on February 07, 2025, 08:02:54 PM »glad this works for you.
v30 there will have support for CMake's new file API. It's really good. Much better and more convenient that the old cmake support. Although you will have to manually change the compiler options if you want to be able to debug on macOS. No way to automate that.
v30 there will have support for CMake's new file API. It's really good. Much better and more convenient that the old cmake support. Although you will have to manually change the compiler options if you want to be able to debug on macOS. No way to automate that.
100
SlickEdit® / Re: Unable to debug on macOS
« Last post by PaulElliott on February 07, 2025, 04:26:57 PM »This was with the clang workspace, my other projects are too complex for simple tests / built externally.
This was extremely curious. It didn't work until I started messing around with dsymutil on clang_prog, trying to ascertain what debug version it was using. At some point during this, breakpoints started catching again. I have since tried to break this by removing the files that this produces, but to no avail. For now, I will just take the win I think.
I will report back if I can find anything more on this, given many of my projects are being built externally with cmake, this is still something of an issue which won't get resolved with the hotfix either.
This was extremely curious. It didn't work until I started messing around with dsymutil on clang_prog, trying to ascertain what debug version it was using. At some point during this, breakpoints started catching again. I have since tried to break this by removing the files that this produces, but to no avail. For now, I will just take the win I think.
I will report back if I can find anything more on this, given many of my projects are being built externally with cmake, this is still something of an issue which won't get resolved with the hotfix either.