SoylentNews

• Re:vi vs emacs is overRe:vi vs emacs is over (Score: 2) by stretch611 on Saturday March 26 2022, @04:34AM (6 children)

  by stretch611 (6199) on Saturday March 26 2022, @04:34AM (#1232275)

  I use nano. BUT... Only for configuration files while in a CLI. Anything else and I use a fully loaded editor like Sublime Text.

  I did learn to use vi, but only used it when required or absolutely nothing else is available. (I never used emacs)

  I also learned how to use EDLIN, so I win on the geek level of crotchety old greybeard.

  So nano vs. vi vs. emacs vs. edlin... Just say no to all.

  --
  Now with 5 covid vaccine shots/boosters altering my DNA :P

  Parent

  Starting Score:	1		point
  Karma-Bonus Modifier		+1
  Total Score:		2

• Re:vi vs emacs is overRe:vi vs emacs is over (Score: 1) by pTamok on Tuesday March 29 2022, @11:27AM (2 children)

  by pTamok (3042) on Tuesday March 29 2022, @11:27AM (#1233196)

  EDLIN? Why not sed? (Says the TECO user)

  It has been observed that a TECO command sequence more closely resembles transmission line noise than readable text. One of the more entertaining games to play with TECO is to type your name in as a command line and try to guess what it does. Just about any possible typing error while talking with TECO will probably destroy your program, or even worse - introduce subtle and mysterious bugs in a once working subroutine.

  From Wikipedia:TECO (text editor) [wikipedia.org]

  Parent

  • Re:TECORe:TECO (Score: 2) by KritonK on Saturday April 02 2022, @11:13AM (1 child)

    by KritonK (465) on Saturday April 02 2022, @11:13AM (#1234328)

    I've used TECO for a few months in my first job as a computer programmer. Back then, it was the best editor they had. No, I didn't destroy any documents with it, and my name didn't do anything in TECO. (Of course I checked, but I don't think "k" was a TECO command!) A few months later, they got EDT [wikipedia.org], a full screen editor, after an OS upgrade, and line-based editors, such as TECO, were abandoned. I became proficient in EDT, and even wrote a set of EDT emulation macros for vi, when I started using Unix.

    Parent

    • Re:TECO(Score: 1) by pTamok on Saturday April 02 2022, @12:21PM

      by pTamok (3042) on Saturday April 02 2022, @12:21PM (#1234331)

      I moved on to using TPU [wikipedia.org]/EVE [wikipedia.org], including some programmatic stuff where call handlers could edit case-logs, able to view the entire log, but only able to append to the end of it while still using the familiar text editor they were used to using. I liked EVE.

      Parent

• Re:vi vs emacs is overRe:vi vs emacs is over (Score: 2, Insightful) by pTamok on Tuesday March 29 2022, @11:32AM (2 children)

  by pTamok (3042) on Tuesday March 29 2022, @11:32AM (#1233197)

  Oh, and I'll agree about vi. I learned just enough to get into mode, make the necessary changes, write out the new file and exit. I know it is far more capable and has a rich set of commands, but it's never been something I've spent time learning. I tend to use nano, and vi only if nano is not available on the (usually) SoC/embedded system I'm working on and needing to make configuration file changes.

  Parent

  • Re:vi vs emacs is over(Score: 1) by pTamok on Tuesday March 29 2022, @11:34AM

    by pTamok (3042) on Tuesday March 29 2022, @11:34AM (#1233199)

    That should read "...get into [insert] mode..."

    [Adding some extra text to batter my way through the lameness filter...]

    Parent

  • Re:vi vs emacs is over(Score: 2) by maxwell demon on Wednesday March 30 2022, @06:27AM

    by maxwell demon (1608) on Wednesday March 30 2022, @06:27AM (#1233441) Journal

    I think vi is great for things like commit messages or other minimal edits. For everything else I use Emacs (actually, XEmacs).

    --
    The Tao of math: The numbers you can count are not the real numbers.

    Parent