× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



You can do LIB/*ALL and all source members will show up.

If you want another wildcard options, go ahead and write it up as an issue.

https://github.com/halcyon-tech/vscode-ibmi/issues

Regards,
Richard Schoen
Web: http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx
----------------------------------------------------------------------

message: 1
date: Wed, 3 Nov 2021 12:50:57 -0500
from: Brad Stone <bvstone@xxxxxxxxx>
subject: Re: Visual Studio vs. RDi.

I just made the switch from ILEditor to VSC. The one thing I wish it had was when adding source PFs to your list, you could just say

LIB/Q*

And it would load them all. Instead it seems you have to do each source PF at a time.

Of course, I imagine my next step would be moving to the IFS for source instead of source PFs. :) But honestly I don't see much of an advantage to that. And I haven't tested if wildcards work there either.

One other thing that gets annoying is after a compile where the errors and warnings are listed those lines all get squiggly lines (like ones for
typos) on them.. combine that with all of the nesting lines for loops, if/select/etc... and it gets messy pretty quick.

Finally, I haven't figured out a way to open the same source member twice..
as someone said they did. It would be cool to have one open in case you fat finger a copy/paste/etc to see what it was before.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.