"If" typing Shortcut MacOS

[Robert_Livingston]

I cannot get this to work. MacOS Sequoia; Xojo 2025 r1.

Am I typing this wrong? Or misreading this. Does it work for others?

[Scott_C]

@Robert_Livingston

Does it work for others?

I love this little feature and have been using it for a while.

But I do just Shift+Return (no ⌘). That’s just the way it’s always been for me on macOS.

Not sure why the documentation says otherwise.

[StefanA]

It works with Opt + Shift + Return or only Shift + Return.

[Christian_Wheel]

Had no idea this feature existed. Thanks for creating this thread and calling attention to it. Great little timesaver!

[Tim_Parnell]

I always hated this shortcut because I’ve never intentionally used it, you can’t disable it, and I have a standard for closing if statements.

[Arnaud_N]

I have the opposite experience. Wanting and trying to use this feature a lot, but there are too many times where it won’t work, like when having a “select case” statement around the “if” block, the IDE often closes the “if” with an “end select”, even though there’s already an “end select” below.

I’m also angry when I want to close a loop while I’m at a single “if” line and the IDE prefers to convert the single line to a block rather than closing the loop, like here:

for i as Integer=0 to 1
  if true then MessageBox "Test" 'Cursor here

Pressing shift-return will produce this:

for i as Integer=0 to 1
  if true then 
    MessageBox "Test"
  end if

While I wanted this:

for i as Integer=0 to 1
  if true then MessageBox "Test"
Next

So, because I’m using shift-return a lot, I’m often needing to undo and type the end of loop manually; I’d prefer the IDE to detect an inline “if” and recognise it’s a valid statement not needing to be reformatted.

[Scott_C]

@Arnaud_N

I’d prefer the IDE to detect an inline “if” and recognise it’s a valid statement not needing to be reformatted.

Whereas, for those of us who dislike inline If statements, I find this handy when reformatting free code acquired here on the forum or a public repo.

So it becomes a feature, not a bug

@Arnaud_N

but there are too many times where it won’t work

Agreed. But I’ve found if you move the cursor to the right location (like one line below what you don’t want changed, or where the Select or If should end), then it’ll work. Then, in most case it’ll close the correct statement, whether a comment line, a Select Case or For loops.

[Greg_O]

FWIW, the IDE doesn’t look downward in your code when trying to figure out what the correct end block needs to be, only up. So the fact that “there’s already an End Select below the cursor” is not even considered.

I do understand that it has trouble with if statements inside select blocks. I run into that from time to time as well.