Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

You can help me improve Blockman extension of VS Code #106

Open
leodevbro opened this issue Mar 19, 2023 · 9 comments
Open

You can help me improve Blockman extension of VS Code #106

leodevbro opened this issue Mar 19, 2023 · 9 comments

Comments

@leodevbro
Copy link
Owner

leodevbro commented Mar 19, 2023

Hi everyone, many of you already helped me a lot with cool ideas, pull requests, feedback and so on.

Now there is one more little thing you can do for Blockman and many other extensions like Blockman.

If you want to help me improve Blockman extension of VS Code, you can like this feature request (link is down below), so the VS Code team will see how many people are interested in this. If the VS Code team implements this feature, Blockman will most likely become much faster and much more flexible with more features/settings/configurations. And it's not just about Blockman, also many other developers will be able to create super cool extensions with the access to the native tokens.

The feature request:
microsoft/vscode#177452

.

@dzienisz
Copy link

Bro! Don't do this!

@mmailaender
Copy link

mmailaender commented Mar 19, 2023

Bro! Don't do this!

I'm thankful that he pinged me here - I like to have a faster Blockman experience and I know from myself that it can be hard to get through the Vscode triage, because they have simply to much feature request. So the most of the people don't even realize that someone opened a feature request that they hardly need.
Thx to this mentioning I saw this feature request and was able to vote it.

@sambacha
Copy link

It took 5 years to get Colorizer to be implemented natively in VSCode -- https://github.com/CoenraadS/Bracket-Pair-Colorizer-2

I think maybe approaching it from an accessibility requirement (helping hard of sight users as an example) vs a feature request may help your case.

Cheers

@leodevbro
Copy link
Owner Author

Bro! Don't do this!

Now I deleted all my comments with the tagged usernames. I hope GitHub will not send them notifications every time a new comment is written here. I don't want to annoy people with non-stop notifications. I just wanted to create quick initial public awareness of my feature request.

@cben
Copy link

cben commented Mar 20, 2023

FYI, @-mentioning a person makes them "subscribed" to the thread: "You’re receiving notifications because you were mentioned." (unless people customized notifications on repo level to ignore mentions).
so yes we're all getting mailed for following comments, and need to click Unsubscribe if we don't want it.

also, when you are mass-mentioning people, even on best intentions, it's polite to explain how you got that list of people. cheers.

[EDIT: oops I caused a notification too 🤦‍♂️. At this point, consider locking this issue; technical discussion can happen on the linked VSCode issue.]

@leodevbro
Copy link
Owner Author

it's polite to explain how you got that list of people

It was just the list of people who starred this repo. And now I see some of them unstarred it. Well, yeah, it's not the best feeling.

@AmyrAhmady
Copy link

Thanks for reminding me I can unstar it as well 👍

@noga-dev
Copy link

noga-dev commented Mar 20, 2023

Thanks for reminding me I can unstar it as well 👍

Unnecessary comment.

it's polite to explain how you got that list of people

It was just the list of people who starred this repo. And now I see some of them unstarred it. Well, yeah, it's not the best feeling.

Yeah, mentioning a slew of your fans en masse like this may have been a temporary lapse of judgement but it happens to the best of us. Ultimately I'm still grateful for your contribution with this plugin even if I've stopped using it due to my laptop not being performant enough to handle it.

FWIW I've 👍 the referenced issue.

@leodevbro
Copy link
Owner Author

I am locking this issue, so there will be no more mass-notifications. If you wish to continue this conversation, you can write new comments here:

#107

.

Repository owner locked as too heated and limited conversation to collaborators Mar 20, 2023
Repository owner unlocked this conversation Mar 20, 2023
Repository owner locked as too heated and limited conversation to collaborators Mar 20, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants