Re: VS Code and Editing Classic Source Members -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: VS Code and Editing Classic Source Members
From: Richard Schoen <richard@xxxxxxxxxxxxxxxxx>
Date: Mon, 15 Feb 2021 19:25:53 +0000
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Tim,

If you feel motivated, check out building VS Code plugins. It doesn't look too hard.

I plan to look in to it as time permits. Seems there could be some interesting plugins, but the developer market for these plug-ins seems a little niche 😊

Regards,
Richard Schoen
Web: http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx
------------------------------
message: 4
date: Mon, 15 Feb 2021 09:11:52 +0000
from: Tim Fathers <tim@xxxxxxxxxxxxx>
subject: Re: VS Code and Editing Classic Source Members

I would love to see VS Code support for IBM i developed further, I find Eclipse horribly clunky by comparison.

Follow-Ups:

Re: VS Code and Editing Classic Source Members , John Yeung

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.