Re: Microsoft Introduces New Command-Line Text Editor

Liste des GroupesRevenir à ol advocacy 
Sujet : Re: Microsoft Introduces New Command-Line Text Editor
De : vallor (at) *nospam* cultnix.org (vallor)
Groupes : comp.os.linux.advocacy alt.comp.os.windows-11
Date : 21. May 2025, 04:08:13
Autres entêtes
Message-ID : <m94uctFctjhU1@mid.individual.net>
References : 1 2 3 4
User-Agent : Pan/0.162 (Hmm4; 7b109588; Linux-6.14.7)
On Wed, 21 May 2025 02:22:45 -0000 (UTC), pH <wNOSPAMp@gmail.org> wrote in
<100jddl$2kse5$1@dont-email.me>:

On 2025-05-20, Jeff Barnett <jbb@notatt.com> wrote:
On 5/20/2025 1:25 PM, rbowman wrote:
On Tue, 20 May 2025 07:54:59 -0000 (UTC), Lawrence D'Oliveiro wrote:
 
     Microsoft also wanted to avoid the “how do I exit vim?” meme, so
     it built its own text editor instead of relying on other
     available options.
 
I'll admit I wondered how to exit vim, or the original vi to be
specific,
but that was 45 years or so ago.
In the early 1980s (approximately when you were trapped in the vim
maze)
an excited colleague told me I just had to try out some new version of
EMACS running on our PDP10 farm at ISI - I had been using some other
editor. I was having some fun figuring out a few simple commands; then
I tried to exit: ctr x, ctr q, etc. After 15 minutes I screamed for
help. I avoided EMACS after that until a few years latter when I was
using the grown up adult version integrated into the Symbolics Lisp
Machine's development environment. Life had changed for the good.
 
I'd install "joe" since I'm a WordStar fan.
 
From the joe manpage....
 
syntax
       joe [global-options] [ [local-options] filename ]...
       jstar [global-options] [ [local-options] filename ]...
       jmacs [global-options] [ [local-options] filename ]...
       rjoe [global-options] [ [local-options] filename ]...
       jpico [global-options] [ [local-options] filename ]...
 
Description
       JOE  is  a powerful console screen editor. It has a "mode-less"
       user in‐ terface which is similar to many user-friendly PC
       editors. Users of  Mi‐ cro-Pro´s WordStar or Borland´s "Turbo"
       languages will feel at home. JOE is  a full featured UNIX
       screen-editor though, and has many features for editing programs
       and text.
 
       JOE also emulates several other editors. JSTAR is a close
       imitation  of WordStar  with  many "JOE" extensions. JPICO is a
       close imitation of the Pine mailing system´s PICO editor, but
       with many extensions and improve‐
       ments. JMACS is a GNU-EMACS imitation. RJOE is a restricted
       version  of JOE,  which  allows  you to edit only the files
       specified on the command line.
 
       Although JOE is actually five different editors, it still
       requires  only one  executable, but one with five different
       names. The name of the edi‐ tor with an "rc" appended gives the
       name of JOE´s  initialization  file, which determines the
       personality of the editor.
 
---------------------------------------------------------------
 
It does not seem to have vi(m) in there....oh well.
 
pH in Aptos

I, too, am a fan of joe.  Have used it since 1992, when it came with
the MCC Interim distribution of Linux.

Since most of the people using our student-access system were familiar
with BBS editors, joe was the default editor on our system.

(I can use vi, but I like to say I use it to edit the Makefile so I can
build joe. ;) )

Oh:  And it's in Cygwin, so no reason not to use joe on Windows.

--
-v System76 Thelio Mega v1.1 x86_64 NVIDIA RTX 3090 Ti
   OS: Linux 6.14.7 Release: Mint 22.1 Mem: 258G
   "Editing is a rewording activity."

Date Sujet#  Auteur
20 May 25 * Microsoft Introduces New Command-Line Text Editor50Lawrence D'Oliveiro
20 May 25 +* Re: Microsoft Introduces New Command-Line Text Editor3Alan K.
21 May 25 i`* Re: Microsoft Introduces New Command-Line Text Editor2Lawrence D'Oliveiro
21 May 25 i `- Re: Microsoft Introduces New Command-Line Text Editor1rbowman
20 May 25 +* Re: Microsoft Introduces New Command-Line Text Editor3Chris Ahlstrom
20 May 25 i+- Re: Microsoft Introduces New Command-Line Text Editor1Chris Ahlstrom
20 May 25 i`- Re: Microsoft Introduces New Command-Line Text Editor1Carlos E. R.
20 May 25 +* Re: Microsoft Introduces New Command-Line Text Editor21rbowman
20 May 25 i+* Re: Microsoft Introduces New Command-Line Text Editor15Jeff Barnett
21 May 25 ii+- Re: Microsoft Introduces New Command-Line Text Editor1Lawrence D'Oliveiro
21 May 25 ii+* Re: Microsoft Introduces New Command-Line Text Editor2pH
21 May 25 iii`- Re: Microsoft Introduces New Command-Line Text Editor1vallor
21 May 25 ii+- Re: Microsoft Introduces New Command-Line Text Editor1rbowman
21 May 25 ii+* Re: Microsoft Introduces New Command-Line Text Editor9Paul
21 May 25 iii+* Re: Microsoft Introduces New Command-Line Text Editor5Lawrence D'Oliveiro
21 May 25 iiii+* Re: Microsoft Introduces New Command-Line Text Editor2Frank Slootweg
22 May 25 iiiii`- Re: Microsoft Introduces New Command-Line Text Editor1Carlos E. R.
21 May 25 iiii`* Re: Microsoft Introduces New Command-Line Text Editor2rbowman
22 May 25 iiii `- Re: Microsoft Introduces New Command-Line Text Editor1candycanearter07
21 May 25 iii`* Re: Microsoft Introduces New Command-Line Text Editor3Jeff Barnett
21 May 25 iii +- Re: Microsoft Introduces New Command-Line Text Editor1Lawrence D'Oliveiro
21 May 25 iii `- Re: Microsoft Introduces New Command-Line Text Editor1rbowman
21 May 25 ii`- Re: Microsoft Introduces New Command-Line Text Editor1Chris Ahlstrom
20 May 25 i`* Re: Microsoft Introduces New Command-Line Text Editor5Carlos E. R.
21 May 25 i `* Re: Microsoft Introduces New Command-Line Text Editor4rbowman
21 May 25 i  `* Re: Microsoft Introduces New Command-Line Text Editor3Carlos E. R.
21 May 25 i   `* Re: Microsoft Introduces New Command-Line Text Editor2rbowman
22 May 25 i    `- Re: Microsoft Introduces New Command-Line Text Editor1rbowman
20 May 25 +* Re: Microsoft Introduces New Command-Line Text Editor4Paul
21 May 25 i+* Re: Microsoft Introduces New Command-Line Text Editor2Paul
21 May 25 ii`- Re: Microsoft Introduces New Command-Line Text Editor1Carlos E. R.
21 May 25 i`- Re: Microsoft Introduces New Command-Line Text Editor1Chris
21 May 25 +* Re: Microsoft Introduces New Command-Line Text Editor2Chris
21 May 25 i`- Re: Microsoft Introduces New Command-Line Text Editor1rbowman
22 May 25 +- Re: Microsoft Introduces New Command-Line Text Editor1Paul
22 May 25 +* Re: Microsoft Introduces New Command-Line Text Editor3Chris Ahlstrom
22 May 25 i`* Re: Microsoft Introduces New Command-Line Text Editor2rbowman
22 May 25 i `- Re: Microsoft Introduces New Command-Line Text Editor1Farley Flud
22 May 25 `* Re: Microsoft Introduces New Command-Line Text Editor12candycanearter07
22 May 25  `* Re: Microsoft Introduces New Command-Line Text Editor11Farley Flud
24 May 25   +* Re: Microsoft Introduces New Command-Line Text Editor9candycanearter07
26 May 25   i+- Re: Microsoft Introduces New Command-Line Text Editor1vallor
26 May 25   i+- Re: Microsoft Introduces New Command-Line Text Editor1Carlos E. R.
26 May 25   i`* Re: Microsoft Introduces New Command-Line Text Editor6candycanearter07
27 May 25   i `* Re: Microsoft Introduces New Command-Line Text Editor5Carlos E. R.
28 May 25   i  `* Re: Microsoft Introduces New Command-Line Text Editor4Lawrence D'Oliveiro
28 May 25   i   `* Re: Microsoft Introduces New Command-Line Text Editor3Carlos E. R.
30 May 25   i    `* Re: Microsoft Introduces New Command-Line Text Editor2Lawrence D'Oliveiro
30 May 25   i     `- Re: Microsoft Introduces New Command-Line Text Editor1Chris Ahlstrom
26 May 25   `- Re: Microsoft Introduces New Command-Line Text Editor1vallor

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal