Re: [oi-dev] Shipping the nano editor alongside with vi

On January 13, 2021 2:13:43 PM UTC, Bob Friesenhahn wrote: >On Tue, 12 Jan 2021, Jim Klimov wrote: >> >> Bob, FWIW I think you can generally copy-paste in terminals with >mouse if you hold SHIFT while click-dragging to select the text. > >Usually the problem I encounter is with a paste over a

Re: [oi-dev] Shipping the nano editor alongside with vi

On Tue, 12 Jan 2021, Jim Klimov wrote: Bob, FWIW I think you can generally copy-paste in terminals with mouse if you hold SHIFT while click-dragging to select the text. Usually the problem I encounter is with a paste over a ssh login. The source system has either already been dealt with or

Re: [oi-dev] Shipping the nano editor alongside with vi

On January 11, 2021 9:28:09 PM UTC, "Klaus Ziegler - owner of sunfreeware.de" wrote: > > >On 11.01.21 21:59, Bob Friesenhahn wrote: >> It would be good if fresh systems would default to fewer quirky >> wiz-bang features yet allow them to easily be enabled for a >Linux-like >> experience. >> >>

Re: [oi-dev] Shipping the nano editor alongside with vi

On Mon, 11 Jan 2021 at 12:36, Gary Mills wrote: > On Mon, Jan 11, 2021 at 09:54:23AM -0800, Chris wrote: > > While vim(1) is my "goto" editor, and vi(1) really isn't difficult. My > > frustration > > comes in the fact that each OS implements a different version, with > > different > > keyboard

Re: [oi-dev] Shipping the nano editor alongside with vi

On 11.01.21 21:59, Bob Friesenhahn wrote: It would be good if fresh systems would default to fewer quirky wiz-bang features yet allow them to easily be enabled for a Linux-like experience. Bob I absolutely agree and vote for it :-) Much

Re: [oi-dev] Shipping the nano editor alongside with vi

On 2021-01-11 12:59, Bob Friesenhahn wrote: On Mon, 11 Jan 2021, Chris wrote: While vim(1) is my "goto" editor, and vi(1) really isn't difficult. My frustration comes in the fact that each OS implements a different version, with different keyboard macros. Which quickly made ee(1) my goto when

Re: [oi-dev] Shipping the nano editor alongside with vi

On Mon, 11 Jan 2021, Chris wrote: While vim(1) is my "goto" editor, and vi(1) really isn't difficult. My frustration comes in the fact that each OS implements a different version, with different keyboard macros. Which quickly made ee(1) my goto when I was working in a "constrained" env (like

Re: [oi-dev] Shipping the nano editor alongside with vi

On 2021-01-11 12:36, Gary Mills wrote: On Mon, Jan 11, 2021 at 09:54:23AM -0800, Chris wrote: While vim(1) is my "goto" editor, and vi(1) really isn't difficult. My frustration comes in the fact that each OS implements a different version, with different keyboard macros. Which quickly made

Re: [oi-dev] Shipping the nano editor alongside with vi

On Mon, Jan 11, 2021 at 09:54:23AM -0800, Chris wrote: > While vim(1) is my "goto" editor, and vi(1) really isn't difficult. My > frustration > comes in the fact that each OS implements a different version, with different > keyboard macros. Which quickly made ee(1) my goto when I was working in a

Re: [oi-dev] Shipping the nano editor alongside with vi

On 2021-01-11 08:23, Hung Nguyen Gia via oi-dev wrote: I know how to install nano, sir. ... I can't deal with vi at all. Not the modern VIM let alone your old vi. Without nano, I can't do text editing. Yes, vi is historically part of any Unix. But at least, on FreeBSD, they have a

Re: [oi-dev] Shipping the nano editor alongside with vi

best regards >> >> Vincent Torri >> >>> If you are making decision to use minimal image, you should be aware that >>> such image is missing many things and is not intended to be used by someone >>> who does not know how to use the system. >&

Re: [oi-dev] Shipping the nano editor alongside with vi

y, in my POV) telling you to follow what used to be called > "netiquette". > > > > regards > > Michael > > > > > > On Sun, 10 Jan 2021 14:19:14 +0700 Tim Mooney via oi-dev < > oi-dev@openindiana.org> wrote > >

Re: [oi-dev] Shipping the nano editor alongside with vi

my POV) telling you to follow what used to be called "netiquette". > > regards > Michael > > > On Sun, 10 Jan 2021 14:19:14 +0700 Tim Mooney via oi-dev > wrote > > > In regard to: Re: [oi-dev] Shipping the nano editor alongside wi

Re: [oi-dev] Shipping the nano editor alongside with vi

king decision to use minimal image, you should be aware that > >such image is missing many things and is not intended to be used by someone > >who does not know how to use the system. > > > > PS: I see no problem to include nano with larger image. > > > >

Re: [oi-dev] Shipping the nano editor alongside with vi

gds, > toomas > > > On Sun, 10 Jan 2021 14:19:14 +0700 Tim Mooney via oi-dev > > wrote > > > >> In regard to: Re: [oi-dev] Shipping the nano editor alongside with vi, > >> Hung...: > >> > >>> Yes, it's just

Re: [oi-dev] Shipping the nano editor alongside with vi

you to follow what used to be called "netiquette". regards Michael > > On Sun, 10 Jan 2021 14:19:14 +0700 Tim Mooney via oi-dev < > oi-dev@openindiana.org> wrote > > > In regard to: Re: [oi-dev] Shipping the nano editor alongside with

Re: [oi-dev] Shipping the nano editor alongside with vi

how to use the system. > > PS: I see no problem to include nano with larger image. > > my 2 cents. > > rgds, > toomas > > > ---- On Sun, 10 Jan 2021 14:19:14 +0700 Tim Mooney via oi-dev > > wrote > > > >> In regard to: Re: [oi-dev]

Re: [oi-dev] Shipping the nano editor alongside with vi

re that such image is missing many things and is not intended to be used by someone who does not know how to use the system. PS: I see no problem to include nano with larger image. my 2 cents. rgds, toomas > On Sun, 10 Jan 2021 14:19:14 +0700 Tim Mooney via oi-dev > wrote ---- > >

Re: [oi-dev] Shipping the nano editor alongside with vi

!'. Straight forward so I could know to silently go away. This will not waste our time with a bunch of back and forth emails. On Sun, 10 Jan 2021 14:19:14 +0700 Tim Mooney via oi-dev wrote > In regard to: Re: [oi-dev] Shipping the nano editor alongside with vi, > Hung...: >

Re: [oi-dev] Shipping the nano editor alongside with vi

In regard to: Re: [oi-dev] Shipping the nano editor alongside with vi, Hung...: Yes, it's just a single line. But why you give me a read-only file and asked me to modified it? It's much more simpler for developer with write access to do it, not me. And it's within a second, just a single line

Re: [oi-dev] Shipping the nano editor alongside with vi

Yes, it's just a single line. But why you give me a read-only file and asked me to modified it? It's much more simpler for developer with write access to do it, not me. And it's within a second, just a single line. On Sun, 10 Jan 2021 00:49:50 +0700 Aurélien Larcher wrote > >

Re: [oi-dev] Shipping the nano editor alongside with vi

In regard to: [oi-dev] Shipping the nano editor alongside with vi, Hung...: This should be done for none desktop OI flavors: OI text and OI minimal. Nano is already packaged for OI, though it may not be getting installed by default. It's a balancing act, to decide what to include

Re: [oi-dev] Shipping the nano editor alongside with vi

On Sat, Jan 9, 2021 at 9:09 AM Hung Nguyen Gia via oi-dev < oi-dev@openindiana.org> wrote: > This should be done for none desktop OI flavors: OI text and OI minimal. > > It will help novice user like me very much. Please consider it, > developers. I have trouble using the vi editor even though I

[oi-dev] Shipping the nano editor alongside with vi

This should be done for none desktop OI flavors: OI text and OI minimal. It will help novice user like me very much. Please consider it, developers. I have trouble using the vi editor even though I have my mobile phone with me as a backup showing the vi tutorial. And I think many other novice