Recent Posts91
Recent Posts
92
Features and/or Improvements / Re: Request for Slickedit extension for Visual Studio Code
« Last post by rowbearto on December 20, 2025, 02:20:31 PM »I realized today that a simple feature between SlickEdit and vscode would be extremely helpful, and would take a relatively small amount of development time for SlickEdit team to implement. It could be a simple way to get the initial framework of vscode extension talking to Slickedit process.
I'd like to have a command/hotkey when my cursor is in a file in Slickedit to switch to the already running vscode with that file opened at that cursor position and put the vscode window into the foreground.
This is because I find myself with both SE and vscode opened. I am using SE for navigation, going to results from searches, going to next/prev build error, navigating with 'go to definition' and 'find references'.
But when I want the AI features I need to be editing in vscode. But I found the place I want to edit with SE and my file is open in SE now, not vscode.
So the difficulty for me is when I am navigating in SE and I find a place I want to start editing, to shift context to vscode, open the same file in the vscode editor at the same line, that is a multi-step process and is getting tedious.
If there was a way to quickly go from my file/line in SE IDE to vscode IDE then it would be very easy to start using the AI features.
In the previous messages we were discussing SE providing a REST API.
But now I am asking for SE to initiate an action to the vscode extension, not the other way around.
So would the vscode extension (for SE) require a REST API that SE could communicate with too so that SE could initiate an action?
I'd like to have a command/hotkey when my cursor is in a file in Slickedit to switch to the already running vscode with that file opened at that cursor position and put the vscode window into the foreground.
This is because I find myself with both SE and vscode opened. I am using SE for navigation, going to results from searches, going to next/prev build error, navigating with 'go to definition' and 'find references'.
But when I want the AI features I need to be editing in vscode. But I found the place I want to edit with SE and my file is open in SE now, not vscode.
So the difficulty for me is when I am navigating in SE and I find a place I want to start editing, to shift context to vscode, open the same file in the vscode editor at the same line, that is a multi-step process and is getting tedious.
If there was a way to quickly go from my file/line in SE IDE to vscode IDE then it would be very easy to start using the AI features.
In the previous messages we were discussing SE providing a REST API.
But now I am asking for SE to initiate an action to the vscode extension, not the other way around.
So would the vscode extension (for SE) require a REST API that SE could communicate with too so that SE could initiate an action?
93
Features and/or Improvements / Re: Request for Slickedit extension for Visual Studio Code
« Last post by Graeme on December 20, 2025, 12:32:32 PM »Unfortunately I have to use VS Code for the AI capabilities, SlickEdit doesn't offer AI integration.
Which AI capability in vs code do you use?
BTW - vs code has "find all references" and "go to definition" - in the Dart language at least.
94
SlickEdit® / Re: Slickedit v28 minimap is always zoomed...?
« Last post by LBCEi on December 19, 2025, 05:29:30 PM »I've been seeing the same thing for a long time (several releases, starting in 28.0.2) and reported it last May (https://community.slickedit.com/index.php/topic,19454.msg78152.html#msg78152).
Clark asked for steps to reproduce with a clean config and I was unable to make it happen with a clean config. The minimap with a clean config actually had a smaller font that I expected instead of bigger.
Clark asked for steps to reproduce with a clean config and I was unable to make it happen with a clean config. The minimap with a clean config actually had a smaller font that I expected instead of bigger.
95
Features and/or Improvements / Re: Request for Slickedit extension for Visual Studio Code
« Last post by rowbearto on December 19, 2025, 04:05:15 PM »Agree, a REST API would be really nice.
SE could still sell their normal product just as they do now.
It would be nice if SE could write the vscode extension to communicate with SE using the REST API. As customer has to pay for SlickEdit IDE anyway, Slickedit team could offer the extension for free but it would be useless unless a customer paid $$ for the Slickedit IDE the same way they do now.
SE could still sell their normal product just as they do now.
It would be nice if SE could write the vscode extension to communicate with SE using the REST API. As customer has to pay for SlickEdit IDE anyway, Slickedit team could offer the extension for free but it would be useless unless a customer paid $$ for the Slickedit IDE the same way they do now.
96
Features and/or Improvements / Re: Request for Slickedit extension for Visual Studio Code
« Last post by Dan on December 19, 2025, 03:30:38 PM »An SE extension to vscode could be achieved more quickly if the SlickEdit IDE remains running in the background and the vscode extension communicates with the SE executable.
A REST API would be cool. That would let people write an extension in any language that they want. It could just be part of SlicKEdit and all you have to do is launch it. It's just one product that way.
97
SlickEdit® / Slickedit v28 minimap is always zoomed...?
« Last post by Brandon on December 19, 2025, 03:04:56 PM »For some reason, whenever I load a file the minimap window font size is always the same as the main file.
I have to rightclick and set "Unzoom" to get it to show the correct rendering. Normally I would dig into the macro files to try and hack this ... but I'm not sure what exactly controls this behavior or why it defaults to "zoomed" the same as the code window.
As far as I can tell, things are set correctly in the Font settings (and I have tried several different fonts).
I am still on v28.0.2.0, if that matters.
I have to rightclick and set "Unzoom" to get it to show the correct rendering. Normally I would dig into the macro files to try and hack this ... but I'm not sure what exactly controls this behavior or why it defaults to "zoomed" the same as the code window.
As far as I can tell, things are set correctly in the Font settings (and I have tried several different fonts).
I am still on v28.0.2.0, if that matters.
98
Features and/or Improvements / Re: Request for Slickedit extension for Visual Studio Code
« Last post by rowbearto on December 19, 2025, 02:36:27 PM »An SE extension to vscode could be achieved more quickly if the SlickEdit IDE remains running in the background and the vscode extension communicates with the SE executable.
99
Features and/or Improvements / Request for Slickedit extension for Visual Studio Code
« Last post by rowbearto on December 19, 2025, 12:54:18 AM »Unfortunately I have to use VS Code for the AI capabilities, SlickEdit doesn't offer AI integration.
I was thinking that if SlickEdit could create a paid VS code extension I wouldn't miss the SlickEdit features I love so much. SlickEdit could also get compensated for their work and maybe open themselves to many more customers!
By having a SlickEdit extension then when vscode evolves its AI and/or other features, we automatically get them in vscode while the SlickEdit extension provides the useful SE features.
What I would want to see in such an extension:
1) BigFind and multiple search results windows, show new search results in new search tab, be able to go back to old search tabs
2) Ability to see the context in the search results window, what file/function the search result is in
3) SlickEdit tagging and indexing, examples:
3.1) would be nice to do a "push-tag" in vscode and have it use SlickEdit's code to "go to definition"
3.2) would be nice to find all references and have that displayed in a vscode window
4) Project management of SlickEdit, create slickedit projects so the tagging engine knows the files to look at, can do a BigFind search of SE workspace and SE project
5) Error parsing: When I do a build in vscode use SlickEdit back end to find the next/prev error and open the file with the error at the line#
6) Ability to go to opening brace from cursor and ability to go to the first line of the surrounding function.
Probably many more features that I'd like to see, I will add to this post as I think of them.
I was thinking that if SlickEdit could create a paid VS code extension I wouldn't miss the SlickEdit features I love so much. SlickEdit could also get compensated for their work and maybe open themselves to many more customers!
By having a SlickEdit extension then when vscode evolves its AI and/or other features, we automatically get them in vscode while the SlickEdit extension provides the useful SE features.
What I would want to see in such an extension:
1) BigFind and multiple search results windows, show new search results in new search tab, be able to go back to old search tabs
2) Ability to see the context in the search results window, what file/function the search result is in
3) SlickEdit tagging and indexing, examples:
3.1) would be nice to do a "push-tag" in vscode and have it use SlickEdit's code to "go to definition"
3.2) would be nice to find all references and have that displayed in a vscode window
4) Project management of SlickEdit, create slickedit projects so the tagging engine knows the files to look at, can do a BigFind search of SE workspace and SE project
5) Error parsing: When I do a build in vscode use SlickEdit back end to find the next/prev error and open the file with the error at the line#
6) Ability to go to opening brace from cursor and ability to go to the first line of the surrounding function.
Probably many more features that I'd like to see, I will add to this post as I think of them.
100
SlickEdit® / SE + Wayland?
« Last post by jc44 on December 17, 2025, 02:37:06 PM »Hi
Is there some reason why SE doesn't ship with a Qt Wayland plugin? Both my Pi & Ubuntu installations would probably benefit from it as the desktop is Waylnd. FWIW I can easily believe that Wayland might break things especially running with Qt5.
Thanks
John Cox
Is there some reason why SE doesn't ship with a Qt Wayland plugin? Both my Pi & Ubuntu installations would probably benefit from it as the desktop is Waylnd. FWIW I can easily believe that Wayland might break things especially running with Qt5.
Thanks
John Cox