Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • 1) Per platform, whatever is the default, installed editor for that platform; i.e. whatever vi comes with each unix/linux, notepad on windows, tpu (in edt mode :-) on vms, etc;

    1a) On windows, esp. older versions where notepad is morally broken (eg 32k limit, etc), and systems I will spend a lot of time on (eg primary workstations) I also generally have either PFE or ConText installed along with vim;

    2+3) Tough to answer directly, given #1, but...

    2) If my plan for a given system included installing an editor for personal use, probably vim just because I've spend about 10 years in various flavors of vi (I get tired of forgetting that h, j, k, l do not work in notepad :-);

    3) Default presence is the key. I end up with a lot of systems that need some minor tweak 2-3 times per year, it's not worth installing an editor just for that. I end up on a lot of systems that have vendor support, and working around the absence of "my custom stuff" isn't fun. I'd need the ability to bare metal disaster recover, I in the event I was doing this for real I'd not want to lose time installing (and compiling?) my own editor. Your mileage will most certainly vary.

    I feel pretty much the same way about shells, IDEs, etc. I want/need to be able to function in the default toolset for the system. Not a hard and fast rule, just a guideline. One of the nicer things the last few years is the number of boxen that include some version of perl by default... it saves on exception making.