Passing filename to editor in action window (FIXED)

[Coachz]

Using an external editor (Sublime Text), I find if there are spaces in the filename it tries to open a file for each word. Is there a way Reaper can wrap it in double quotes or something to pass it the parameter for the filename ?

example: Script: edgemeal_Toggle envelope lanes for selected track.lua
Thanks !

Windows 7, Reaper 5.974rc3/x64

[nofish]

Confirmed here using VS Code as external editor.

[Coachz]

I can't even open Script: Mouse_position_dependant_actions.eel in sublime text without the same problem as op. grrrrr

[nofish]

Same thing happens when making a new script via action list's ReaScript: New... button.

[Meo-Ada Mespotine]

This looks like a simple enclosing if filename+path with quotes within Reaper would solve the problem.
It also seems like that Scripts stored in Scripts-folder might not be passed with full absolute path to Sublime/VS(the latter is speculation by me).

What happens, when creating a new script, if you type the same filename plus absolute path, enclosed in quotes. Does this work?

[Coachz]

Originally Posted by mespotine

This looks like a simple enclosing if filename+path with quotes within Reaper would solve the problem.
It also seems like that Scripts stored in Scripts-folder might not be passed with full absolute path to Sublime/VS(the latter is speculation by me).

What happens, when creating a new script, if you type the same filename plus absolute path, enclosed in quotes. Does this work?

Yeah it should be a very quick fix for the devs to make to make sure to pass the file name in quotes. I doubt that putting quotes around the creation of a new script will work

[Meo-Ada Mespotine]

It wouldn't be a fix for the problem, but if creating one script that way leads to a "valid editable" file in Sublime, it would be a confirnation of my theory, surrounding the problem.
And suggesting the way to fix it.

Can t test it myself right now, as I have no "Reaperable device" at hand

Edit: according to FoxAsteria and Breeder, this problem doesn't happen with Lua-scripts. So maybe the problem lies somewhere else :/

[Coachz]

"ztest of spaces" gets extension not supported

[nofish]

Originally Posted by mespotine

Edit: according to FoxAsteria and Breeder, this problem doesn't happen with Lua-scripts. So maybe the problem lies somewhere else :/

Does happen here also with Lua scripts.

[Sju]

Yeah happens here too whenever I try to open a script (lua or whatever, doesn't matter) using Code.exe as the editor.

[Coachz]

Fixed in v5.978+dev0515 - May 15 2019
https://forum.cockos.com/showthread.php?t=220995

[Meo-Ada Mespotine]

Nice