Re: Microsoft Introduces New Command-Line Text Editor

Liste des GroupesRevenir à ol advocacy 
Sujet : Re: Microsoft Introduces New Command-Line Text Editor
De : OFeem1987 (at) *nospam* teleworm.us (Chris Ahlstrom)
Groupes : comp.os.linux.advocacy alt.comp.os.windows-11
Date : 30. May 2025, 13:47:33
Autres entêtes
Organisation : None
Message-ID : <101c9d6$ftqq$2@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10 11
User-Agent : slrn/1.0.3 (Linux)
Lawrence D'Oliveiro wrote this post while blinking in Morse code:

On Wed, 28 May 2025 12:38:21 +0200, Carlos E. R. wrote:
>
On 2025-05-28 01:55, Lawrence D'Oliveiro wrote:
>
On Tue, 27 May 2025 13:08:17 +0200, Carlos E. R. wrote:
 
I prefer "jstar", but it breaks inside "tmux", some commands collide.
 
Isn’t tmux like screen, in that all the commands are keyed off a single
prefix key?
 
In screen, I set that prefix key to CTRL/Z. This is normally the key
recognized by the terminal driver for job control. But it’s not needed,
when you have a multiplexer app like screen doing the job control.
 
Most start with ^B. I'm not familiar with screen, though. I have trouble
it ^K^B..^K^K to mark a block of text. I don't remember what happens,
maybe the ^B in ^K^B is intercepted.
>
I’d say you need to redefine your escape prefix. I regularly use Emacs
through a screen session, without keystroke conflicts.
>
Of course, I have also removed the default definition of CTRL/Z in Emacs
(suspend-frame), because I have no need for that function, so that
wouldn’t cause a clash anyway.

I use the backtick in tmux. And the bash construct $() instead of the back
tick.

--
There is perhaps in every thing of any consequence, secret history, which
it would be amusing to know, could we have it authentically communicated.
-- James Boswell

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