in reply to Re^7: Backdating strict
in thread Backdating strict

> I have always had great success by simply running the script at a terminal and letting perl point out the errors.

You never tried flymake-mode, right? :)

And why do you run it in a terminal instead of a compilation buffer?

Cheers Rolf
(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery

Replies are listed 'Best First'.
Re^9: Backdating strict
by jcb (Parson) on Nov 19, 2020 at 02:09 UTC

    Simple; the main reason I run X is to have dozens of xterms and Emacs frames scattered across my numerous virtual desktops with the occasional graphical application. Emacs is a better editor, but xterm is a better terminal. :)

      The benefit of an IDE comes from the "integration".

      Like automatically jumping to errors found in the STDERR output. This facilitates development a lot.

      Your line of arguments are classical with VI zealots, ( I don't need feature XY integrated I can always use Unix) and from that perspective VI is probably the better editor.

      Anyway, I don't intend to convince you. :)

      Cheers Rolf
      (addicted to the Perl Programming Language :)
      Wikisyntax for the Monastery

        I actually use both Emacs and vim. Emacs is a vastly superior programmer's editor, but vim has a much shorter start-up time, so it works better for quick edit jobs.

        In this case, it's more X11 than Unix; I would almost certainly be learning to use Emacs compile mode if I did not have the ability to have both xterms and Emacs frames on the screen at once. As it is, I just turn on line and column display in the modeline and scroll.

      Check out vterm if you're using a recent emacs with loadable module support. Anecdotal but I've noticed differences (I still do most normal work in iTerm but the things I do do within emacs straight seem peppier).

      The cake is a lie.
      The cake is a lie.
      The cake is a lie.

      What follows is a totally irrelevant post in this thread, sorry.

      I do the same but I use micro-emacs and can't stand tabbed terminals. I like to take my time scrolling the page of errors and jumping to the offending line in another terminal. It's like a zen exercise. I start thinking subconciously the problem in these few seconds between switching contexts and that helps me.

      I have to admit that when I had to use it, Android Studio feels like flying a JumboJet. I press a button and the drinks cart comes out. A lot of these I could make with a Makefile and scripts, e.g. to upload the app to the emulator etc. And I would prefer it that way.

      I often wonder what productivity does the IDE offer? The one it comes to mind is autocompleting method names in classes, checking arguments etc. that's cool as it saves me time to look up the docs. But what company would deny paying their developers an extra hour per day for reading documentation? And instead get them an IDE to save money? Oh yes: Fools Inc.!

      Of all the free code out there I avoid like the plague those integrated with Xcode and VisualStudio. I just don't bother with these (anymore).

      So, I would use an IDE if it guarantees that compiled code can be achieved also via the command line without that IDE.

      And another thought, there is so much effort put into graphical editors, let's say Android Studio's UI builder (in olden times it was Access db). It's almost impossible to be able to explain or get help from a text-based forum. I consider heroes those answering those queries with a ton of screenshots and phrases like Menu->X->Y->Z click, drag, left-holder, etc. Instead there is a perfectly sane XML-based UI language there. The point here is that "Menu->X->Y .." is the lowest form of knowledge.

      So, what I am trying to say is that IDE is cool but they start innocent and before you know it, you depend so much on it you can't escape it. Hello IDEs, welcome and join the queue. So many of you battling for my soul.

      bw, bliako

        The good thing about emacs is that it's not an IDE but an IDE Construction Set.

        you can scale it down to plain vi (i.e. not vim) level or full blown jumbo.

        I even use it on termux/android to hack scripts within a terminal emulation, i.e. plain text.

        The drawback of this openness is the complexity of recombining different solutions.

        Cheers Rolf
        (addicted to the Perl Programming Language :)
        Wikisyntax for the Monastery

        Personally I'm a fan of jumbo jets and drinks carts. Much happier traveling first class that way than pushing myself along on a scooter with different sized square wheels and promising myself I'll knock some of the edges off the wheels some day when I get enough time out from pushing myself along.

        Optimising for fewest key strokes only makes sense transmitting to Pluto or beyond