Oh, I think I see the conceptual problem. Some languages like BASIC and Python provide two environments. One where you type a line of code in and then that line of code runs immediately and the result is displayed right away. The other environment is where you type in the program using a text editor and then run the complete program all at once. That is the way that your Perl developmemt will work.

I do most of my work on Windows, so I am not the best for advice on Unix. However, I know from when I used to have a Sun workstation, that something similar to what I do on Windows is possible on Unix. I'll describe what I do so you can see what the goal is.

I use Textpad as my program editor for Perl development on Windows. I think Notepad++ has similar features. I have a single "Perl go button" that saves all open files, runs the Perl program in the active editor window and captures STDOUT and STDERR to another editor screen. I've written a lot of code with this simple arrangement.

Many editors, mine included have fancy features that do syntax highlighting, etc. I turned all that stuff off because I find it annoying. However since the editor is designed to write software, it knows about indenting and that is very useful. If the current line has an indent of say, 4, a carriage return brings the cursor back to that same indent level on the next line.

There are things called "Integrated Development Environments" or IDE. I don't use one for Perl, but I do for Java. That's because Java is so verbose that I need a program to help me spew out all of the required boilerplate! Perl is very much more "to the point".

Anyway, I suggest one goal for a simple environment is to make the cycle: "edit, run program, look at output" very easy and fast. You can go a long ways with that. I can't remember the last time I used the Perl Debugger. It is so easy for me to add a "print" statement using Data::Dumper that I just don't need it often. I just hit one "F key" and poof! I am looking at the program's output.