Old Question: How to Print From XCode With Line Numbers

Wow. I'm rather surprised, since I saw comments that showed the XCode developers have known for a good while this is a requested feature.

Does anyone know why this has never been added? I'd think it'd be a much requested and very useful feature.

I just tried -- I got an error page telling me to file a bug report!

I meant I had read comments by the developers of XCode from years ago with them making comments that made it clear they knew that it was a much desired feature.

I'll file a report. Right now I'm on XCode 3. I'll probably be upgrading soon. I'm coding in Perl without an extensive IDE and just switched over to XCode from some Linux programs I had been using with MacPorts.

Okay, got it to print line numbers. It's a bit kludgey, but I tried printing to a PDF I could check in Preview and it is printing out line numbers.

It wasn't easy and I'll definitely file a bug report on this when I can get that page to work.

I wish you had responded before I marked this ans answered, since that is a good answer about how to do it.

Is there a way, with Enscript, to specify the colors so they match what I use in XCode? Switching between one style and another confuses me.

Thanks for the heads up on versions 3 and 4. The project I'm working on now is almost all Perl (but will include Python later) for a Linux system. While I don't have to build anything, I'd hate to lose syntax highlighting. (Why on Earth would they REMOVE features like highlighting for other languages? Or is it just a matter of copying over the proper definition files?)

If XCode is moving in that direciton, I may have to find another editor to use. What amazes me is that after trying 10-12 editors over the past week, and just looking at what I would think are standard features (line numbering in the editor and for printing, syntax highlighting for the same, code folding, being able to control font or printout size, and how it handles finding or showing start and end braces/brackets/parenthesis), I'm amazed that even text editors that cost as much as $100 lack a number of these basic features.

I have a solution that works for now. I wrote a user script in Perl that reads through the file and adds line numbers with spaces at the start of each line. Then I can print it. After printing, I can either use UNDO to remove the line numbers or use the same script to remove them.

After I get comments and stuff in there, I'll post it on my blog site with my other projects and put a linke here, in a spearate topic about printing with line numbers.

If Apple is removing the user scripts from XCode 4 and is changing things so I either don't have syntax highlighting for Perl or have to have it in a project or something similar, than that tells me that OS X is going the same way IOS is going: Restrict everything and make everyone do it in our languages and our way.

As much as I love working on an iMac, that's getting too restrictive for an IDE. I use Eclipse for Java, but it feels klunky and really wanted to use something else for Perl (and later Python) and sometimes C++.

I don't need a lot for an IDE. I ran my business for almost a decade using just a text editor that had the editor on top, a file list on the side, and a console in the bottom part of the window. A text editor with the features I need is what's important.

If XCode is removing more and more features, including powerful features, then when I have a break between this section and the next on this project, I'm going to be evaluating IDEs and text editors for something that won't cut me off at the knees.

Sorry to sound harsh. I'm thankful for the help from people here, but I'm frustrated that Apple is acting like Big Brother and removing words in the language of developers, like BB did with Newspeak.

I'm self-taught and never even used anything that most would qualify as an IDE until I had been programming for a number of years and my business was well past the startup phase. Most of what I do is with scripting languages, althought I will, in the future, be using more C++, and I do sometimes use Java. I don't need a heavy duty IDE.

But on the part about restrictions, yes, Apple does things their way. That's okay. But their way is not my way and it's unlikely I'll ever be at a point where I'm developing for just OS X. After I finish my current project, I'll be working more on video editing and programming will be just a hobby for me when I have time or need a project for a particular purpose.

In the past I've looked over open source programs, commercial programs, programs that came with a particular OS and others along those lines.

In this case, I'm more concerned about a text editor that has the features I need than many of the other features IDEs provide. (And, in the past, when I had to deal with building something, I did my own scripts and found I worked just as well running al that from the command line as I did from within an IDE.)

So it's not a love or hate feeling, but, as you pointed out, Apple doesn't try to be all things to all people, and if they're trimming features and focusing more on their model of development, and it's diverging from my needs, then that's fine. They'll do well. I'm just looking for the best environment that fits my needs.