Recent Posts31
SlickEdit 2023 v28 Beta Discussion / Re: Git status indicators on Buffers tab
« Last post by curtiswren on September 27, 2023, 01:44:28 PM »I’m seeing it both with files in the workspace and not in the workspace
Recent Posts
32
SlickEdit 2023 v28 Beta Discussion / Re: Slickedit "lost" keyboard input
« Last post by patrick on September 27, 2023, 01:34:04 PM »Hmm, I don't think we've hit this before. Is there anything in your .slickedit/28.0.0/logs/vs.log file? If you know the time frame it happened, run "journalctl -xe" and scan back to that time period and see if you see any references to vs_exe, or anything that might be wayland/xorg related.
Are you using the default GNOME environment for Ubuntu 22? Is it the default Wayland session, or are you using the GNOME on Xorg session?
Are you using the default GNOME environment for Ubuntu 22? Is it the default Wayland session, or are you using the GNOME on Xorg session?
33
SlickEdit 2023 v28 Beta Discussion / Re: Git status indicators on Buffers tab
« Last post by Dan on September 27, 2023, 12:49:29 PM »Do you see this problem with files that aren't in the workspace? That was how I was able to reproduce it.
34
SlickEdit 2023 v28 Beta Discussion / Re: Macros sometimes don't work on other windows
« Last post by Clark on September 26, 2023, 11:05:41 PM »I can't reproduce this.
It would help if you could determine if there are some exact steps to get this to happen.
It would help if you could determine if there are some exact steps to get this to happen.
35
SlickEdit 2023 v28 Beta Discussion / Re: Git status indicators on Buffers tab
« Last post by curtiswren on September 26, 2023, 09:53:34 PM »Some of the files are in the workspace. I typically just put my library header files in the workspace using *.h in the header directories.
Yes, this is on Linux.
Thanks
Yes, this is on Linux.
Thanks
36
SlickEdit 2023 v28 Beta Discussion / Slickedit "lost" keyboard input
« Last post by astromme on September 26, 2023, 09:22:32 PM »SlickEdit Pro 2023 (v28.0.0.3 64-bit Qt5) on Ubuntu 22.04.2 LTS with multiple monitors.
Whilst I was editing away, suddenly keyboard input did nothing in Slickedit. I could click on File->Save to save my work. I opened Key Bindings and tried to enter something there, no go, nor in the Options search.
When this started, I saw "Background tagging is searching for files to tag in tag file '<one of my apps>.vtg'.
I could click to other windows and the keyboard worked fine.
I File->Exit-ed Slickedit and restarted it and the keyboard started to work again.
Whilst I was editing away, suddenly keyboard input did nothing in Slickedit. I could click on File->Save to save my work. I opened Key Bindings and tried to enter something there, no go, nor in the Options search.
When this started, I saw "Background tagging is searching for files to tag in tag file '<one of my apps>.vtg'.
I could click to other windows and the keyboard worked fine.
I File->Exit-ed Slickedit and restarted it and the keyboard started to work again.
37
SlickEdit 2023 v28 Beta Discussion / Re: Git status indicators on Buffers tab
« Last post by Dan on September 26, 2023, 08:05:38 PM »Are your files in a workspace?
If so, what is the layout like?
You are seeing this issue on Linux, correct?
If so, what is the layout like?
You are seeing this issue on Linux, correct?
38
SlickEdit 2023 v28 Beta Discussion / Macros sometimes don't work on other windows
« Last post by astromme on September 26, 2023, 06:53:57 PM »SlickEdit Pro 2023 (v28.0.0.3 64-bit Qt5) on Ubuntu 22.04.2 LTS with multiple monitors.
Sometimes when I want to screen share code, I'll split a pane, then drag the pane out into a new window. I have the following vusrmacs.e:
They're bound to Ctrl-Shift-Alt-0 and Ctrl-Shift-0. Sometimes when I try to make the font bigger with these, nothing happens. If I click around back and forth and run it in a pane in the main window showing the same file, it'll work there, then when I switch back to the separate window it'll start working there.
Sometimes when I want to screen share code, I'll split a pane, then drag the pane out into a new window. I have the following vusrmacs.e:
Code: [Select]
#include "slick.sh"
_command view_file_shared_screen() name_info(','VSARG2_MACRO|VSARG2_MARK|VSARG2_REQUIRES_EDITORCTL)
{
wfont_zoom(20);
view_line_numbers_toggle();
}
_command end_view_file_shared_screen() name_info(','VSARG2_MACRO|VSARG2_MARK|VSARG2_REQUIRES_EDITORCTL)
{
wfont_unzoom();
view_line_numbers_toggle();
}
They're bound to Ctrl-Shift-Alt-0 and Ctrl-Shift-0. Sometimes when I try to make the font bigger with these, nothing happens. If I click around back and forth and run it in a pane in the main window showing the same file, it'll work there, then when I switch back to the separate window it'll start working there.
39
SlickEdit 2023 v28 Beta Discussion / Re: ctrl+click-mutiple cursor : how do i get old mouse cursor instead of cross ?
« Last post by Dennis on September 26, 2023, 06:52:48 PM »The purpose of switching to the cross when you hold down Control is to help indicate that you are in a different mode. Currently there is no option for turning off the crosshair, however, there is an option to turn off Ctrl+Click creating multiple cursors (needed for people on laptops where you can bump the touchpad while hitting control) Tools > Options... > Editing > Cursor Movement
Do you normally use the mouse to create multiple cursors, or do you also use the keyboard shortcuts?
(Ctrl+Alt+Shift+Up/Down and Ctrl+Shift+|) I find these much easier to use than Ctrl+Click, the second one is easy to remember because vertical bar looks like a cursor.
Do you normally use the mouse to create multiple cursors, or do you also use the keyboard shortcuts?
(Ctrl+Alt+Shift+Up/Down and Ctrl+Shift+|) I find these much easier to use than Ctrl+Click, the second one is easy to remember because vertical bar looks like a cursor.
40
SlickEdit® / Re: typed characters are appearing out of order
« Last post by Chris Nisbet on September 26, 2023, 05:57:39 PM »Thanks, I'll give it a try when I get a chance. For now, what seems to have helped is to use a completely fresh config (with minimal customisation), and completely recreate my workspace. I haven't had much time to look at this in the last few days, but those changes seem to have made things a lot better. I still see a little bit of the 'stickyness', and I think I might have seen the out of order chars once or twice, but that really might have been due to operator error, so wouldn't swear to it.