SlickEdit Community
Archived Beta Discussions => SlickEdit 201x Beta Discussions => SlickEdit 2018 v23 Beta Discussion => Topic started by: sigmund on September 05, 2018, 09:50:12 AM
-
Steps to reproduce:
1. Open workspace "C:\Program Files\SlickEdit Pro 23.0.0 Beta3\SampleProjects\DevStudio\2015\VS2015.sln"
2. Jump to line 83: printf(...
3. Press right cursor (or run cursor-right) twice
Expected result: cursor gets moved to column 6.
Actual result: cursor gets stuck at column 5.
About SlickEdit:
SlickEdit Pro 2018 (v23.0.0.4 64-bit)
Serial number: FE38414_BETA
License type: Beta License
License expiration: 2018-10-10 02:00:00
License file: C:\ProgramData\slickedit\23\slickedit.lic
Build Date: August 29, 2018
Emulation: CUA
OS: Windows 10 x64
OS Version: 10.00.0
Memory: 36% Load, 11809MB/32648MB Physical, 13866MB/37512MB Page File, 979MB/134217727MB Virtual
Shell Information: C:\tools\JPSoft\TCMD23\tcc.exe /LD /LH
Screen Size: 1920 x 1040, 1920 x 1080
Project Type: Microsoft Visual Studio Visual C++
Language: .h (C/C++)
Encoding: Automatic
Installation Directory: C:\Program Files\SlickEdit Pro 23.0.0 Beta3\ (non-removable drive,NTFS,169668MB free)
Configuration Directory: C:\Users\VikS\Documents\My SlickEdit Config\23.0.0\ (non-removable drive,NTFS,169668MB free)
Migrated from: C:\Users\VikS\Documents\My SlickEdit Config\22.0.2\
-
I haven’t been able to reproduce this. See if you can reproduce this with a default config (vs +new <new-directory>).
-
It happens for "vs +new <new-directory>" as well, but only if the line starts with leading tab characters. If the line starts with spaces, then all is fine.
When I run "vs +new <new-directory>", then SlickEdit starts up with my normal config. Did you mean "vs +new -sc <new-directory>"? If I do this, then I cannot reproduce the problem (regardless if the line starts with tabs or spaces).
-
I did mean -sc (oops -- my bad). Please post your user.cfg.xml. Looks like we need your options in order to reproduce this.
-
There is some sensitive information in that file that I would like to clean out first (aliases, color coding symbols etc). Do you happen to know of a way to anonymize the content of that file?
If I copy user.cfg.xml to the new directory for "vs +new -sc <new-directory>", then I get the incorrect behavior, so it certainly seems to be something in this file that triggers it.
-
Nothing that does that yet but it would be handy. Single file project profiles can definitely be deleted (no source there but it does have path info). Other than that, there is path information scattered around which I don't need.
The most important profile settings I need are misc.options, misc.def_vars, and language.* profiles. It's probably an option in one of these profiles.
Another way to do this is to start with a clean config and start making changes which you use to determine which setting is doing this. If you did that, you would just tell us which setting causes this issue. If you made tons of configuration changes, this might be a pain.
-
It was quick enough to find the exact problematic setting:
<options>
<misc.def_vars n="misc.def_vars" version="1">
<p n="def_emulate_leading_tabs" v="1"/>
</misc.def_vars>
</options>
-
Thanks for finding that, reproduced it now. Fixing it for next beta drop.