id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
2872	OMEdit - better omeditcommands.log	Adrian Pop	Adeel Asghar	"I would be really cool to be able to run omeditcommands.log by just renaming
it to .mos. Currently is not possible because you have a lot of text around
the commands you sent to omc and the answer from OMC.
{{{
getNthConnection(Modelica.Fluid.Examples.Tanks.ThreeTanks, 5) 15:58:36:932
{pipe2.port_b,tank2.ports[1], """"} 15:58:36:932
Elapsed Time :: 0 secs

getClassRestriction(Modelica.Fluid.Pipes.StaticPipe) 15:58:36:933
""model"" 15:58:36:933
Elapsed Time :: 0 secs

existClass(Modelica.Fluid.Pipes.StaticPipe) 15:58:36:933
true 15:58:36:934
Elapsed Time :: 0.001 secs

getClassRestriction(Modelica.Fluid.Vessels.OpenTank) 15:58:36:934
""model"" 15:58:36:934
Elapsed Time :: 0 secs

}}}

I suggest outputting the command you send to omc followed by {{{""; // ""}}} then the time. Also the answer you get from OMC should be in comments:

{{{
/*
OMC answered: ....
*/
}}}

This way you can run an omeditcomands.log with OMC and debug way easier.
Alternatively you could generate an extra file with just the commands you
sent to omc followed by {{{"";""}}} named omeditcommands.mos
"	enhancement	closed	high	1.9.4	OMEdit	trunk	fixed