| Streamlining LDT [message #873502] |
Fri, 18 May 2012 07:34  |
Eclipse User |
|
|
|
Is there any way to fix these problems:
1. Combine the debugging. I have to select the debug configuration to run. Clicking on the debug does not work(gives an error). I have to click the external tools configuration to run(and match it up with what I want to do). Would be nice to have a key like 'F5' start debugging and 'F5' start non-debugging. (then they could switch over to step control afterwards or change step. I'm used to F9 and F10)
2. I have to close the source file that was opened durring debugging. It is a read only copy of what is already opened. For example, if I debug "Mytest.lua" then I get another window like "D:/workspace/Mytest.lua".
3. Fix debugger.lua so that it skips over itself if the remote debugger is not found instead of throwing a warning. This will allow me to not have to have to external tool configurations.
4. Possibly show the global variables, but local to the file, as local variables in the inspector(that way I don't have to go hunt them).
5. Possibly more options in the settings to configure various properties.
6. Do not show(or ability to turn off) escaped character in inspector. Just seems excessive to see things like \\"C:\\\\program files\\\\\" (when the string is simply "C:\\program files\\"
I'm not sure how much of this stuff is due to eclipse as I'm new to it.
[Updated on: Fri, 18 May 2012 08:08] by Moderator |
|
|
|
|
| Re: Streamlining LDT [message #873548 is a reply to message #873502] |
Fri, 18 May 2012 10:03  |
| Eclipse User |
|
|
|
Sorry for textual links: I cant put links on messages yet 
uiy uiy wrote on Fri, 18 May 2012 07:34
1. Combine the debugging. I have to select the debug configuration to run. Clicking on the debug does not work(gives an error). I have to click the external tools configuration to run(and match it up with what I want to do). Would be nice to have a key like 'F5' start debugging and 'F5' start non-debugging. (then they could switch over to step control afterwards or change step. I'm used to F9 and F10)
I don't use external tools so I can't help you on this one, sorry.
uiy uiy wrote on Fri, 18 May 2012 07:34
2. I have to close the source file that was opened durring debugging. It is a read only copy of what is already opened. For example, if I debug "Mytest.lua" then I get another window like "D:/workspace/Mytest.lua".
This is due to path mapping that failed somehow. The default option (local resolution) requires that the files are phisically the same. (see wiki.eclipse.org/Koneki/LDT/User_Guide/Concepts/Debugger#Source_Mapping for more informations)
uiy uiy wrote on Fri, 18 May 2012 07:34
3. Fix debugger.lua so that it skips over itself if the remote debugger is not found instead of throwing a warning. This will allow me to not have to have to external tool configurations.
Yes it could be a good improvement. Your fix does the job but you better break the loop instead of returning directly (the code after the loop does some cleanup, allowing some objects to be collected). An even better improvement could be to remove debug hook to remove debugger performance overhead.
uiy uiy wrote on Fri, 18 May 2012 07:34
4. Possibly show the global variables, but local to the file, as local variables in the inspector(that way I don't have to go hunt them).
If I understand correctly, you want to be able to see which of your local variables leaked to global namespace because of a forgotten "local"? I think this job is more for static analysis tools than debuggers (you may be interested by this little script: github.com/hjelmeland/globals).
uiy uiy wrote on Fri, 18 May 2012 07:34
5. Possibly more options in the settings to configure various properties.
Which properties would you like to see?
uiy uiy wrote on Fri, 18 May 2012 07:34
6. Do not show(or ability to turn off) escaped character in inspector. Just seems excessive to see things like \\"C:\\\\program files\\\\\" (when the string is simply "C:\\program files\\"
This notation is intended mimic Lua notation for strings to show that the variable is a string. Also because when you edit then you type full Lua expressions (e.g. { answer = 42 } is evaluated as table and not as string).
But indeed, the backslashes are doubled and shouldn't be in edit mode, it is a bug (I just opened a new bug on tracker). Thanks for report.
|
|
|
|
|
| Re: Streamlining LDT [message #873655 is a reply to message #873571] |
Fri, 18 May 2012 15:17 |
| Eclipse User |
|
|
|
Yes, I saw some... It's not as bad as I made it out but would be nice for a bit more control. The ability to control whitespaces is pretty important IMO. There many more options than I thought as many are under the general tab and for some reason I never looked in there ;/
Some options I would be interested in
Backspace should be greedy or at least move one tab back
Indentation should always be at a multiple of a tab (the first character of a line should always fall on an indentation level)
Indentation highlighting(lines or whole indentation region) (not a big deal but can be visually useful)
For example, it would be nice to have the spacebar treated as the tab key on a new line(this forces tab based indentation).
The last edit location is a very nice feature but only seems to remember the last place. Would be nice to have about 10 places(obviously there can be syncing issues but it would be nice to be able to move forward and backwards so small changes in several places could easily be revisited)
I think I missed a few settings as the layout is a bit different from vs. I'm sure some of the stuff I'm interested in is there already but I'll just have to spend some time with it.
|
|
|
Powered by
FUDForum. Page generated in 0.03898 seconds
Home
You have a decent amount of configurable editing settings related to the formatter (inc. white space management), the syntax coloring, the code templates, ...