[BUG/Suggestion]Replace \ with \\ when using built-in path variables in Inline Lua

[death.crafter]

I was trying to take an path as an argument for a lua function and I wanted to use [#ROOTCONFIGPATH]. But lua doesn't read single \. So if it is possible to repalce single \ by double \\ of built-in path variables before sending it to lua would be good. I know the work around but it would be good if it's done automatically.

[death.crafter]

I was trying to take an path as an argument for a lua function and I wanted to use [#ROOTCONFIGPATH]. But lua doesn't read single \. So if it is possible to repalce single \ by double \\ of built-in path variables before sending it to lua would be good. I know the work around but it would be good if it's done automatically.

I just wanted to bring it to the front. Is this possible?

[jsmorley]

I just wanted to bring it to the front. Is this possible?

I'm just not sure I agree with it. Yes, there are times when you pass a string to Lua and the nature of the function you use it in sees it as an "expression" that will treat the \ character as an escape, but there are just as many times, probably a lot more, when it doesn't, and forcing in \\ would break things. It's not hard to deal with really, and I'm not sure there is a one-size-fits-all answer to this.

If you have Lua like this:

Code: Select all

function readFile(arg)

	file = io.open(arg)
	fileTxt = file:read('*all')
	file:close()
	
	return fileTxt

end

It will work perfect well with a call like [&LuaMeasure:readFile('#CURRENTPATH#myFile.txt')]. Forcing \\ into the resolution of #CURRENTPATH# before sending it to Lua would break this.

[death.crafter]

I'm just not sure I agree with it. Yes, there are times when you pass a string to Lua and the nature of the function you use it in sees it as an "expression" that will treat the \ character as an escape, but there are just as many times, probably a lot more, when it doesn't, and forcing in \\ would break things. It's not hard to deal with really, and I'm not sure there is a one-size-fits-all answer to this.

If you have Lua like this:

Code: Select all

function readFile(arg)

	file = io.open(arg)
	fileTxt = file:read('*all')
	file:close()
	
	SKIN:Bang('!SetOption', 'MeterFile', 'Text', fileTxt)

end

It will work perfect well with a call like [&LuaMeasure:readFile('#CURRENTPATH#myFile.txt')]. Forcing \\ into the resolution of #CURRENTPATH# before sending it to Lua would break this.

Ahh I see. Actually if you look at my skin here, I have to use inline lua to take paths and configs. This is fine Ig. Thanks for the reply.