Re: Editing HLASM source with Visual Studio - columns 73-80

2019-12-12 Thread Seymour J Metz
of Clark Morris Sent: Wednesday, December 11, 2019 9:15 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Editing HLASM source with Visual Studio - columns 73-80 [Default] On 10 Dec 2019 09:43:02 -0800, in bit.listserv.ibm-main sme...@gmu.edu (Seymour J Metz) wrote: >Modern? Other than assemblers, CO

Re: Editing HLASM source with Visual Studio - columns 73-80

2019-12-11 Thread Clark Morris
[Default] On 10 Dec 2019 09:43:02 -0800, in bit.listserv.ibm-main sme...@gmu.edu (Seymour J Metz) wrote: >Modern? Other than assemblers, COBOL and Fortran, what was the last language >that you saw with column dependencies? The 2002 and 2014 standards for COBOL allows for both fixed and free

Re: Editing HLASM source with Visual Studio - columns 73-80

2019-12-11 Thread Charles Mills
- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jantje. Sent: Wednesday, December 11, 2019 4:10 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Editing HLASM source with Visual Studio - columns 73-80 On Tue, 10 Dec 2019 09:37:08 -0800, Charles Mills wrote

Re: Editing HLASM source with Visual Studio - columns 73-80

2019-12-11 Thread Dan Kelosky
You can add the HLASM extension that I worked on (or any other VS Code extension) alongside IBM Z Open Editor / Zowe Explorer ( https://marketplace.visualstudio.com/items?itemName=Zowe.vscode-extension-for-zowe) today. It would be cool if https://github.com/IBM/zopeneditor-about contained the

Re: Editing HLASM source with Visual Studio - columns 73-80

2019-12-11 Thread Jantje.
On Tue, 10 Dec 2019 09:37:08 -0800, Charles Mills wrote: >FWIW I would love that feature but I have never solved that on Notepad++. I >wanted to make just column 72 display red so (a.) I would know if I crossed >the line and (b.) I would know if I had my continuation character in the right

Re: Editing HLASM source with Visual Studio - columns 73-80

2019-12-11 Thread Support, DUNNIT SYSTEMS LTD.
Oren, כל הכבוד! My error was that "HLASM" should have been in lower case in the JSON code. All set (for the time being). Thanks, everyone! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to

Re: Editing HLASM source with Visual Studio - columns 73-80

2019-12-11 Thread Oren, Yifat
ssion List On Behalf Of Support, DUNNIT SYSTEMS LTD. Sent: Wednesday, December 11, 2019 7:16 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [EXTERNAL] Re: Editing HLASM source with Visual Studio - columns 73-80 Thanks. Your JSON code passed with flying colors and I saved it but no ruler showed. I even tri

Re: Editing HLASM source with Visual Studio - columns 73-80

2019-12-10 Thread Timothy Sipples
Keep an eye on the IBM Z Open Editor: https://ibm.github.io/zopeneditor-about There's no specific Assembler editor/awareness yet, but you can ask. In fact, there's an open feature request already lodged for Assembler (and REXX) support, and there's also a separate feature request to add a menu

Re: Editing HLASM source with Visual Studio - columns 73-80

2019-12-10 Thread Support, DUNNIT SYSTEMS LTD.
Thanks. Your JSON code passed with flying colors and I saved it but no ruler showed. I even tried this: { "editor.wordWrapColumn": 120, "[HLASM]": { "editorRuler.foreground": "#ff4081", "editor.rulers": [ 71,

Re: Editing HLASM source with Visual Studio - columns 73-80

2019-12-10 Thread Dan Kelosky
It is JSON syntax, so I think you'd want something like this. { "editor.wordWrapColumn": 120, "[HLASM]": { "editor.rulers": [ 71, 72, 80 ] } } You can use external tools

Re: Editing HLASM source with Visual Studio - columns 73-80

2019-12-10 Thread Support, DUNNIT SYSTEMS LTD.
Thanks. Not working. Do I have a syntax boo-boo here? { "editor.wordWrapColumn": 120 }, "[HLASM]": { "editor.rulers": [ 71, 72, 80 ], } -- For IBM-MAIN subscribe / signoff / archive access

Re: Editing HLASM source with Visual Studio - columns 73-80

2019-12-10 Thread Dan Kelosky
I think so. If you open the "command pallet" via Ctrl + Shift + P, then type in "Open Settings (JSON)", you can paste this in the top: ... "[hlasm]": { "editor.rulers": [ 71, 72, 80 ], }, ... There's a graphical way to set this, but

Re: Editing HLASM source with Visual Studio - columns 73-80

2019-12-10 Thread Support, DUNNIT SYSTEMS LTD.
Hi Dan, Thanks so much. That worked just fine for the INSERT key. Is there any way in VS to have some sort of a vertical column line or similar between columns 72 and 73? -- For IBM-MAIN subscribe / signoff / archive access

Re: Editing HLASM source with Visual Studio - columns 73-80

2019-12-10 Thread Support, DUNNIT SYSTEMS LTD.
Charles, I just experimented with a very basic code and text editor called TextPad. I installed it, as well as a IBM Z-series Assembly Language syntax addon available from their site. I then went into >Configure>Preferences>Document Classes>Z/OS HLASM (the name I gave to files with an ASM

Re: Editing HLASM source with Visual Studio - columns 73-80

2019-12-10 Thread Dan Kelosky
VS Code doesn't really allow "overtype" via insert key: https://github.com/microsoft/vscode/issues/1012 You can use this though: https://marketplace.visualstudio.com/items?itemName=adammaras.overtype Or, blow away sequence numbers as another suggested :)

Re: Editing HLASM source with Visual Studio - columns 73-80

2019-12-10 Thread Seymour J Metz
__ > From: IBM Mainframe Discussion List on behalf of > Charles Mills > Sent: Tuesday, December 10, 2019 12:37 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Editing HLASM source with Visual Studio - columns 73-80 > > FWIW I would love that feature but I have never

Re: Editing HLASM source with Visual Studio - columns 73-80

2019-12-10 Thread Paul Gilmartin
On Tue, 10 Dec 2019 09:56:50 -0800, Charles Mills wrote: >https://en.wikipedia.org/wiki/Comparison_of_programming_languages does not >even have a column for fixed versus free format. > I understand Python is a special case: indention is syntactically significant, governing nesting level. Take

Re: Editing HLASM source with Visual Studio - columns 73-80

2019-12-10 Thread Steve Thompson
gt; From: IBM Mainframe Discussion List on behalf of > Charles Mills > Sent: Tuesday, December 10, 2019 12:37 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Editing HLASM source with Visual Studio - columns 73-80 > > FWIW I would love that feature but I have never solved that

Re: Editing HLASM source with Visual Studio - columns 73-80

2019-12-10 Thread Charles Mills
AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Editing HLASM source with Visual Studio - columns 73-80 Modern? Other than assemblers, COBOL and Fortran, what was the last language that you saw with column dependencies? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3

Re: Editing HLASM source with Visual Studio - columns 73-80

2019-12-10 Thread Paul Gilmartin
On Tue, 10 Dec 2019 11:01:50 -0600, Support, DUNNIT SYSTEMS LTD. wrote: >Thank you all for your responses. I suppose UNNUM it is! > +1 ISPF LM services has facilities to enumerate members and invoke Edit in background for each, with an initial macro to remove line numbers. >One last Visual

Re: Editing HLASM source with Visual Studio - columns 73-80

2019-12-10 Thread Seymour J Metz
, December 10, 2019 12:37 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Editing HLASM source with Visual Studio - columns 73-80 FWIW I would love that feature but I have never solved that on Notepad++. I wanted to make just column 72 display red so (a.) I would know if I crossed the line and (b

Re: Editing HLASM source with Visual Studio - columns 73-80

2019-12-10 Thread Charles Mills
: Re: Editing HLASM source with Visual Studio - columns 73-80 Thank you all for your responses. I suppose UNNUM it is! One last Visual Studio question: is there a way to display a delimiter/margin line after column 72, so that it's easy to visual discern when I've "crossed over the

Re: Editing HLASM source with Visual Studio - columns 73-80

2019-12-10 Thread Support, DUNNIT SYSTEMS LTD.
Thank you all for your responses. I suppose UNNUM it is! One last Visual Studio question: is there a way to display a delimiter/margin line after column 72, so that it's easy to visual discern when I've "crossed over the line"?

Re: Editing HLASM source with Visual Studio - columns 73-80

2019-12-10 Thread Ward Able, Grant
Mainframe Discussion List On Behalf Of Support, DUNNIT SYSTEMS LTD. Sent: 10 December 2019 16:41 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Editing HLASM source with Visual Studio - columns 73-80 ATTENTION! This email originated outside of DTCC; exercise caution. Hi Peter, Thanks for your reply.

Re: Editing HLASM source with Visual Studio - columns 73-80

2019-12-10 Thread Support, DUNNIT SYSTEMS LTD.
Hi Peter, Thanks for your reply. >> Maybe press the "Insert" key on your PC keyboard to overtype instead of >> inserting characters? >> Or a combination of insert-on and insert-off typing? Yes, I know that. My question was in hope that there might be some editor setting which keeps anything

Re: Editing HLASM source with Visual Studio - columns 73-80

2019-12-10 Thread Charles Mills
Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Farley, Peter x23353 Sent: Tuesday, December 10, 2019 8:25 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Editing HLASM source with Visual Studio - columns 73-80 Maybe press the "Insert" key

Re: Editing HLASM source with Visual Studio - columns 73-80

2019-12-10 Thread Farley, Peter x23353
Maybe press the "Insert" key on your PC keyboard to overtype instead of inserting characters? Or a combination of insert-on and insert-off typing? Logically it shouldn’t be any different than inserting text in a regular document, should it? Unless VS has a really funky text editor . . . But

Re: Editing HLASM source with Visual Studio - columns 73-80

2019-12-10 Thread Pew, Curtis G
On Dec 10, 2019, at 10:12 AM, Support, DUNNIT SYSTEMS LTD. wrote: > > With VS, is there a way to insert text on an existing source line without the > line sequence number in columns 73-80 being shifted to the right? > > Any other VS beginner tips someone has will be greatly appreciated.