Re: VS Code Compile messages

[Sam_L <lennon_s_j@xxxxxxxxxxx>]

For completeness:

Expand the "HELP AND SUPPORT" section, usually found at the top left of 
Code for i. That's the best way to report issues and takes you to Github.

It also gives you a link to the documentation, which has more details on 
how to report issues so that you can best help those who maintain the code.


On 6/5/2026 3:31 PM, Greg Wilburn wrote:
> I would... If I could find where that can be done.
>
> I looked on here all afternoon... found it just now.
>
>
>
>
> From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Sam_L
> Sent: Friday, June 5, 2026 2:13 PM
> To: midrange-l@xxxxxxxxxxxxxxxxxx
> Subject: Re: VS Code Compile messages
>
> Caution: The sender of this email could not be verified, which may indicate an impersonation attempt. Verify the email's authenticity with the sender using your organization's trusted contact list before replying or taking further action.
> Secured by Check Point
>
> You would be better asking on Github where it is possible to post images
> of both the question and the answer.
>
>
> On 6/5/2026 12:18 PM, Greg Wilburn wrote:
> > Two tings driving me nuts:
> >
> > I have been all over looking for a way to eliminate the "informational" level messages when compiling in VS Code for i.
> > I was able to remove them from the Problems list, but not from the source itself.
> > Is there any way to do this?
> >
> > Why are my source members not listed under "Open Recent"?