I take it you don't know the difference between vi and vim. ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of David Crayford <[email protected]> Sent: Thursday, February 10, 2022 9:07 AM To: [email protected] Subject: Re: Rocket Vim fileencoding (was: ... ASCII ...)
On 10/2/22 8:29 pm, Seymour J Metz wrote: > I couldn't imagine voluntarily using an editor that didn't have a good macro > language. The ubiquity of vi is certainly a good reason to learn it, but not > to use it routinely. Huh? I use nvim (neovim) which has the full force of Lua for writing plugins, and that includes customizing the UI. I can't even write a custom syntax highlighter for ISPF! I take it you don't know much about Vim? > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3 > > ________________________________________ > From: IBM Mainframe Discussion List [[email protected]] on behalf of > David Crayford [[email protected]] > Sent: Wednesday, February 9, 2022 6:15 PM > To: [email protected] > Subject: Re: Rocket Vim fileencoding (was: ... ASCII ...) > > On 9/2/22 9:40 pm, Paul Gilmartin wrote: >> On Wed, 9 Feb 2022 15:20:52 +0800, David Crayford wrote: >> >>> On 9/2/22 12:48 pm, Paul Gilmartin wrote: >>>>> ... >>>>> I ran Vim on z/OS. It's part of the Rocket Ported Tools suite. It's uses >>>>> enhanced ASCII like all of the ported tools. >>>>> >>>> Have you played with Vim ":set fileencoding=..."? It works >>>> splendidly on Linux. >> It might be useful for generating tests or with such as: >> : w ! iconv -f IBM-1047 -t UTF-8 >codes > I just tried it and it works. Rockets Vim port is surprisingly good. We > also have emacs and a lot of our young guys use that. I like Vim because > it's the default editor > on *nix sysems and it's always there. Its mode of operation takes some > learning but it's worth it. I couldn't imagine using ISPF to edit Unix > files but customers do it > which is why I'm researching this EBCDIC issue. > > >>> No need. I'm convinced that ISPF edit does not support any codepage >>> other than 1047. I've opened a case with IBM to confirm. Pretty shabby >>> implementation if that's true. >>> >> It used to support UTF-8. Regression. But my recollection might not be >> probative. > I would avoid tagging files UTF-8. For text conversion to work in the > shell you need to set _BPXK_AUTOCVT=ALL, at which point almost all > programs that use enhanced ASCII > will break. That includes Python, Git, all of Rockets ported tools suite! > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
