Author Topic: can not enter a semicolon in the C / C ++ code part  (Read 2697 times)

kkarino

  • Community Member
  • Posts: 23
  • Hero Points: 2
can not enter a semicolon in the C / C ++ code part
« on: March 01, 2018, 02:04:32 PM »
I can not enter a semicolon in the C / C ++ code part.
However, I can enter it in the comment section.

Windows10 Japanese version.

SlickEdit Pro 2017 (v22.0.2.1 64-bit)

Serial number:
Licensed number of users: Single user
License file: C:\ProgramData\slickedit\22\slickedit.lic

Build Date: February 12, 2018
Emulation: Vim

OS: Windows 10 x64
OS Version: 10.00.0 
Memory: 56% Load, 4663MB/8191MB Physical, 16970MB/19967MB Page File, 633MB/134217727MB Virtual
Shell Information: C:\WINDOWS\system32\cmd.exe /q
Screen Size: 2560 x 1080, 2560 x 1440

Project Type: Single file project - Other
Language: No file open
Encoding: No file open

Installation Directory: D:\SlickEdit Pro 22.0.2\ (non-removable drive,NTFS,33703MB free)
Configuration Directory: L:\temp\22.0.2\ (non-removable drive,NTFS,90652MB free)

« Last Edit: March 01, 2018, 02:08:44 PM by kkarino »

Dennis

  • Senior Community Member
  • Posts: 3960
  • Hero Points: 517
Re: can not enter a semicolon in the C / C ++ code part
« Reply #1 on: March 01, 2018, 04:29:22 PM »
This is fixed in hotfix 1.  (The problem was related to having an unusual set of syntax expansion options, aka, syntax expansion on, but insert braces immediately turned off).

Little known fact about SlickEdit syntax expansion.  If you type "if;", it will expand to "if (^) ^;".

Normally people who turn off the option to insert braces immedately do so because they want statements to expand to "if ( ^ ) ^" because they frequently do one line statements, so they do not want to delete the braces for one liners.  However, if they got in the habit of typing "if;" when they want a one-line if, and "if<space>" when they want a statement with braces, then you get the best of both worlds.

Semicolon expansion works for other statements also (while, for, return, continue, break).
« Last Edit: March 01, 2018, 04:35:34 PM by Dennis »

hs2

  • Senior Community Member
  • Posts: 2761
  • Hero Points: 292
Re: can not enter a semicolon in the C / C ++ code part
« Reply #2 on: March 01, 2018, 06:22:51 PM »
Nice easter egg - thanks for letting us know Dennis :)
HS2

kkarino

  • Community Member
  • Posts: 23
  • Hero Points: 2
Re: can not enter a semicolon in the C / C ++ code part
« Reply #3 on: March 01, 2018, 08:28:43 PM »
Dennis, Thank you for the quick answer.  :)

Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2897
  • Hero Points: 153
Re: can not enter a semicolon in the C / C ++ code part
« Reply #4 on: March 02, 2018, 12:09:46 PM »
Nice easter egg - thanks for letting us know Dennis :)
HS2

If you haven't tried it, the "Beautify line on when reindent" option on each languages General tab is amazing.  It beautifies the current line when you press tab.

hs2

  • Senior Community Member
  • Posts: 2761
  • Hero Points: 292
Re: can not enter a semicolon in the C / C ++ code part
« Reply #5 on: March 02, 2018, 12:31:41 PM »
Oh yes - that's awesome, too !
When it comes to typing I'm pretty lazy and use quite a lot of those automagic ;D
HS2

Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2897
  • Hero Points: 153
Re: can not enter a semicolon in the C / C ++ code part
« Reply #6 on: March 02, 2018, 12:37:16 PM »
I threw that in just because you said "Easter Egg" and I wasn't sure how many people knew about that.  There is a video about it. I love all of our beautify while typing features, but asked for that one because I kept deleting and retyping semicolons to get things beautified.  When Patrick said "what if we put it on Tab?" it was like a lightning bolt.  It is one of my favorite new features in 2017.

We used to have an actual easter egg.  There was a certain message box that whose title read "Danger Will Robinson! Danger! Danger!".  It came up very rarely and not too many people caught on.  I'm 99% certain it's gone now, just because that part of the editor has been reworked.