Mudlet - Forum

One feature I would like to see is having the line numbers able to show up in the editor window. This would help you quickly find the line when you see an error in your script which gives you the line number.

Line numbers are shown in the status bar of the editor.

They are, but that's not nearly so handy as having them displayed along the left of the window. Many coders (myself included) are simply used to seeing them there.

Heiko wrote:Line numbers are shown in the status bar of the editor.

The point is to quickly go to the line number when you see the error in the status window. If I had a script with let's say 500 lines of code and the status window says go to line 300 it would take me a long time to find exactly where I am having issues.

Darmir wrote:

Heiko wrote:Line numbers are shown in the status bar of the editor.

The point is to quickly go to the line number when you see the error in the status window. If I had a script with let's say 500 lines of code and the status window says go to line 300 it would take me a long time to find exactly where I am having issues.

I always miss VIM when I have to do any coding outside of it. One of the many features I love: keyboard shortcut to go straight to a line number.

tsuujin wrote:

Darmir wrote:

Heiko wrote:Line numbers are shown in the status bar of the editor.

The point is to quickly go to the line number when you see the error in the status window. If I had a script with let's say 500 lines of code and the status window says go to line 300 it would take me a long time to find exactly where I am having issues.

I always miss VIM when I have to do any coding outside of it. One of the many features I love: keyboard shortcut to go straight to a line number.

Me too. I learned how to write perl and korn shell in VIM.

Darmir wrote:

Heiko wrote:Line numbers are shown in the status bar of the editor.

The point is to quickly go to the line number when you see the error in the status window. If I had a script with let's say 500 lines of code and the status window says go to line 300 it would take me a long time to find exactly where I am having issues.

A word of advice, coming from experience: If your script contains files (even a single one) with 500 lines in it, you may want to consider writing it outside of Mudlet and using require() to load the script. I would think just about any IDE is a better development environment than direct Mudlet when working on something of that scope.

Personally, I use the Scite that came with Lua For Windows.

Okay I never would have a script with 500 lines either but that is just an example.

Oneymus wrote:

Darmir wrote:

Heiko wrote:Line numbers are shown in the status bar of the editor.

The point is to quickly go to the line number when you see the error in the status window. If I had a script with let's say 500 lines of code and the status window says go to line 300 it would take me a long time to find exactly where I am having issues.

A word of advice, coming from experience: If your script contains files (even a single one) with 500 lines in it, you may want to consider writing it outside of Mudlet and using require() to load the script. I would think just about any IDE is a better development environment than direct Mudlet when working on something of that scope.

Personally, I use the Scite that came with Lua For Windows.

The issue I have with require() or dofile() is:

require() :
If I unload or nil out the package, the functions it loaded are NOT unloaded. Thus I have to go through and manually nil out each function and then reload/require the package again to get the UPDATED functions there.

dofile() :
Running mudlet for a while and loading/reloading the main script alot, eventually you'll run into an error that 'too many file handles are open' or some such. This requires you to completely logoff/close mudlet and then reopen in order to get around it or reload the script.

I see no issues with large scripts in Mudlet itself. Mudlet may not offer all the functionalities of a dedicated script editor, but it works well enough for my purposes, and I find it more comfortable to have everything in one place than having to toggle to other programs/files to edit some of my scripts. The core script of my curing system has well over 500 lines.