Recent Posts

Pages: [1] 2 3 ... 10
1
SlickEdit® / Adding markdown languages to align with standards
« Last post by spongyryno on February 08, 2026, 08:04:48 PM »
SlickEdit will show me the correct color coding for CMD/BAT script code inside markdown if I call it "Batch":

Code: [Select]
# This is a markdown title

Works in SlickEdit, but not GitHub, VSCode, etc.:

```Batch
REM this is a comment
echo "Hello World %USERNAME%"
```

However, GitHub, VSCode, and other markdown viewers don't honor this.

Similarly, GitHub, VSCode, and other markdown viewers all support "CMD" and "BAT", but SlickEdit does not:

Code: [Select]
# This is a markdown title

Works in GitHub, VCode, and others, but not SlickEdit:

```BAT
REM this is a comment
echo "Hello World %USERNAME%"
```

Works in GitHub, VCode, and others, but not SlickEdit:

```CMD
REM this is a comment
echo "Hello World %USERNAME%"
```

Is there any way I can configure SlickEdit to treat "CMD" or "BAT" the same as "Batch"?
2
I don't think there is an option for excluding files from being tagged but still be added to the project.
3
SlickEdit® / Re: Slickedit v28 minimap is always zoomed...?
« Last post by kniped1 on February 04, 2026, 07:51:06 PM »
I have been seeing this since I upgraded from Slickedit v27 to Slickedit v30 with hotfix 2. I was hoping someone of the forums had a fix, but I guess not.
4
Hi there  :)

I want to set up my project to recursively add files as a wildcard to a project, e.g. all *.c files but even though they are added to the project so that I can open and view them, I do not want certain directories to be tagged.

I know there's an option to exclude files or directories from the Wildcard Properties but then they are not added to the project. Also, I have to repeat the exclude pattern for each wildcard, e.g. *.c, *.h, *.cpp, *.hpp, etc.

I am looking for a workspace / project wide option to ignore specific directories from being tagged even though they are added to the project.

Thanks in advance,
Pieter
5
SlickEdit® / Re: SE keeps docking tool windows that have been previously undocked
« Last post by joecar on January 30, 2026, 06:15:50 PM »
Deleting *.vpwhist* kind of works (still occurs on a project or two)...

but it is tedious when I have 15+ workspaces.
6
SlickEdit® / Re: SE keeps docking tool windows that have been previously undocked
« Last post by joecar on January 30, 2026, 05:57:28 PM »
Deleting vrestore.xml is not a good idea since you lose your configured panes, toolbars, buttons, etc.

I don't see vrestore.slk so I don't know what happens when you delete this.
7
SlickEdit® / Re: SE keeps docking tool windows that have been previously undocked
« Last post by joecar on January 30, 2026, 05:55:11 PM »
Also does it when opening a different workspace.
8
SlickEdit® / Re: SE keeps docking tool windows that have been previously undocked
« Last post by joecar on January 30, 2026, 05:23:11 PM »
v30 with hotfix 2 applied, same thing happening again...
9
Try restarting but I don't think that will help. I'm guessing the filename can't be found because it is missing path information or it has a relative path but not to the current directory. If this isn't the case, email your user.cfg.xml to support and include a text file with compiler error output that matches the problematic error messages.
10
SlickEdit® / Re: V30 license
« Last post by Clark on January 30, 2026, 01:38:35 PM »
@clark
https://www.slickedit.com/shop still shows text for how to upgrade to v29 instead of v30

Thanks. Updated
Pages: [1] 2 3 ... 10