The 80's called and they want linenumbering back

@Tim Parnell: you say in <https://xojo.com/issue/47532>

[quote]Line numbers would be more helpful if they switched sides with the breakpoints / “-” symbols.
ie, line numbers next to code.[/quote]

This isn’t exactly clear. Why would this be helpful?

(To me) the line numbers are more relevant to the code than the cute little bug or dot indicators.
The line numbering in VisualStudio is set up that way, and Xcode (kind-of) is as well.

Objective reasoning:

  • It groups clickable interface together, placing the clickable area of the gutter near the Navigator which is also a mouse-based control. Code editor is reading/writing, and the line numbers are read-only.
  • It looks like other environments, and will help ease conversions for new users.

Personal reasoning:

  • When quickly looking for a bug, breakpoint, or bookmark (without using the bottom pane) the spacing helps the icons jump out and get noticed.
  • When working with longer blocks of code I subconsciously retain the general line numbering of the area I’m working with when I need to pop away so I can get back to them quickly.
  • Visually it’s just more appealing.

I literally zip around the IDE all day moving quickly through many different spots in a project. Opening the bottom pane to find breakpoints or bookmarks just slows me down. It’s nice that line numbers were finally implemented, but I wish they had asked for input from people who use line numbering in other environments before solidifying anything.

A larger notice during beta would have also meant that bugs like <https://xojo.com/issue/47525> and <https://xojo.com/issue/47526> wouldn’t have made it to release.

Just to add noise, I code more in Xojo than any other environment, and when I do code outside Xojo it tends to be text files on linux. Something like bash, python, perl, javascript, etc.

The first time I saw the line numbers my first reaction was why aren’t they on the right and the breakpoint hashes on the left.

I’m not sure I care that much either way, but it did strike me as a little bit odd or out of place for some reason. Why exactly I don’t know. I don’t use line numbers that much, but maybe it’s just enough to condition me to liking the line numbers right next to the code.

@Norman Palardy [quote]3 lines of code and its done[/quote]

Hard to believe there is this much discussion over a feature that you can use or not use and that only took 3 lines of code.

[quote=323897:@william plunkett]Hard to believe there is this much discussion over a feature that you can use or not use and that only took 3 lines of code.

[/quote]
It took a lot more than that to implement I’m sure. But it would only take three lines of code to make it not work/display anymore

Working on projects where there are 100Ks of lines of code…

Almost all my apps are deployed into secure environments, meaning that I don’t even get to see my applications running in production, let alone be able to go in and poke around to see what is the matter.

Line numbering is important to me because I have no chance of fixing something unless I know on which line the error was thrown.

Pretty sure thats not on the table here.

[quote]The line number HAS ALWAYS BEEN present in the status area
So you could always say “oh look at line 3” and you had to mouse over the line and watch the status area to know when you were on that line
The ONLY difference is WHERE it is - thats it[/quote]

and therefore its EDITOR/COMPILE time helpful , not ‘an error occurred on a customer machine’ helpful.

@James Dooley: there is still this old feature request open <https://xojo.com/issue/15331> (More information for exceptions needed) . As far as I remember Joe said that this might be possible with LLVM.

[quote=323710:@brian franco]Not me! I like to open my httpd.conf file in VI and count lines with the cursor until I get to line 587 that the error log told me there was a misconfiguration. :stuck_out_tongue:

:stuck_out_tongue: actually I turn the line numbers on in VI[/quote]

Actually I am using mcedit, not vi :slight_smile:

In the case of PHP it is a compiler evaluated constant as opposed to runtime evaluated constant (quote from PHP help page):

Makes troubleshooting so much easier.

[ESC] :set number

[quote=323710:@brian franco]I like to open my httpd.conf file in VI and count lines with the cursor until I get to line 587 that the error log told me there was a misconfiguration. :stuck_out_tongue:
actually I turn the line numbers on in VI[/quote]
why not jump to line 587?

:587

or

vi +587 /path/to/httpd.conf

[quote=324084:@Jürg Otter][ESC] :set number

why not jump to line 587?

:587

or

vi +587 /path/to/httpd.conf

I’m not that advanced yet :stuck_out_tongue: