Exclude private/internal functions defined in a different file from auto-complete suggestions

[YuriyYatsyk]

@a2ndrade - feature request. Currently autocomplete suggests matches from the entire project, including the ones flagged as private/internal. I think it would make sense to only include private/internal suggestions from the current file.

[a2ndrade]

Do you think this is generally applicable? Since there is no internal function concept in q, it's really just a convention that may not be widely followed. Maybe we could add an additional checkbox (next to where the pattern for internal functions is defined) to control this behavior. What are your thoughts?

[YuriyYatsyk]

Sure, makes sense

…

On Nov 14, 2019, at 12:57 PM, Antonio Andrade ***@***.***> wrote: Do you think this is generally applicable? Since there is no internal function concept in q, it's really just a convention that may not be widely followed. Maybe we could add an additional checkbox (next to where the pattern for internal functions is defined) to control this behavior. What are your thoughts? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[wibotwi]

I think 99% of users use .i. as private.
QPad for example shows such functions as private.

[YuriyYatsyk]

99% of the users is a bit of a bold claim :)

…

On Tue, May 19, 2020 at 5:10 PM Wi ***@***.***> wrote: I think 99% of users use .i. as private. QPad for example shows such functions as private. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#50 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKQHPENYIWUR4DDXGAUWUOTRSLYVVANCNFSM4JL52UKA> .