Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Isidor Nikolic
    @isidorn

    Inlay hints add additional inline information to source code to help you understand what the code does. This can help you understand the meaning of each argument at a glance, which is especially helpful for functions that take Boolean flags or have parameters that are easy to mix up.
    For example this.tokens.forEach(t => t.cancel()); with inlay hints would become this.tokens.forEach(callbackfn: t : CancellationTokenSource => t.cancel());
    So visually we add grayed out hints in the line. These hints are not accessible so we were thinking how to make them accessible, and for now we went with the command
    "Read Line With Inlay Hints" that would move focus to the HTML elements that has this additional richness. This is still in early development so we are very much looking for feedback.
    Have in mind that inlay hints are currently only supported by TypeScript and JavaScript. Java and Python will probably come in the future. To turn on this setting you can add the following settings:

    "editor.inlayHints.enabled": true,
    "typescript.inlayHints.enumMemberValues.enabled": true,
    "typescript.inlayHints.parameterNames.enabled": "all",
    "typescript.inlayHints.parameterTypes.enabled": true,
    "typescript.inlayHints.functionLikeReturnTypes.enabled": true

    For javascript just search for the javascript inlayHints settings.
    So if you are using js/ts try it out and let us know what you think.

    Isidor Nikolic
    @isidorn
    FYI we will revert back to Electron 13 for this stable release. We have discovered a bug which we need more time to fix. Our plan to is ship the next stable (start of April) with E16. Insiders will continue being on E16 starting with next week. Sorry about this revert!
    Bryan Duarte
    @bjduarte
    I have been using VSCode at work and at home a lot over the last few weeks and I am finding some things frustrating because I am using Windows at work and Mac OsX at home. When I use ctrl, shift, E to move to the editors I can press Enter to have my cursor put into the editor of the selected file. On Mac osX this does not work in fact it does not move my cursor any where. Is there a better command on Mac osX to move the cursor into the current working file? I wanted to say I do like the audio additions in the editor. I saw above in the thread audio was added and I like the addition. Finally for now, I am working with Anaconda and while VS code works with it a bit and the plug in should help out, I am finding that it is unable to activate my environment and spams the terminal output window with that message everytime a command is entered! Any help on this?
    Isidor Nikolic
    @isidorn
    Hi Bryan, thanks a lot for your feedback! Glad you like the sound cue additions.
    1. On mac try cmd+shift+e to move focus into explorer and then cmd+down to move focus back into the editor. Let me know if it works
    2. I am not a Python expert, I suggest that for the Anaconda issue you simply open a new issue in the Python repo and ping me @isidorn on the issue https://github.com/microsoft/vscode-python
    Bryan Duarte
    @bjduarte
    @isidorn That worked perfectly for moving between the explorer and editor! Thank you! I will keep playing with the Anaconda issue. If things do not work out once I understand it better I will file an issue. Thank you again!
    Isidor Nikolic
    @isidorn
    Our sound designer is wondering if our users are using mostly headphones or speakers when working in VS Code. So a quick poll, what do you use headphones or speakers?
    alex19EP
    @alex19ep:alex19ep.me
    [m]
    Headphones
    José Vilmar Estácio de Souza
    @jvesouza
    eheadphones
    Jared Stofflett
    @jareds
    Headphones
    Dickson Tan
    @Neurrone
    Primarily speakers
    José Vilmar Estácio de Souza
    @jvesouza
    In the settings editor there are some nodes that apparently can be expanded or collapsed, for example Commonly Used. I can not collapse using the key board. Am I doing something wrong?
    Isidor Nikolic
    @isidorn
    @jvesouza correct the Commonly Used can not be collapsed. I noticed that we are not setting the aria-expanded on it, so I am not sure what more should we do to make this more obvious to the screen reader. Would you mind opening a new issue for this.
    Michał Zegan
    @webczat
    does anyone have any idea on how to accessibly use the interactive window in jupyter extension?
    Isidor Nikolic
    @isidorn
    @webczat I do not. I suggest to open a new issue here https://github.com/microsoft/vscode-jupyter
    And ping me on it and we can work with the Jupyter team.
    Michał Zegan
    @webczat
    I mean, the general accessibility issue is still open...
    Isidor Nikolic
    @isidorn
    Yeah that is sometimes a problem with the general issues = they are too general and they loose traction. If we can open a new one that is more focused that might be more actionable and we might get some movement.
    Michał Zegan
    @webczat
    sure. the thing is i am not sure what is the issue. i mean unsure how that looks like from the perspective of sighted users, so might be better to focus on general notebook stuff first, because then it would clarify whether the normal workflow is okay or not
    currently I barely know how this is going to work at all, I mean interactive window
    and part of this might even be bugs in the extension, like dotnet interactive. there are behavior differences between it and juppyter even though both use the same notebook capabilities
    Isidor Nikolic
    @isidorn
    @webczat I can help and try to figure it out. But whatever works better for you, if you want you can file a new issue. If not I can ping the notebook people to gain some traction on the current one.
    Michał Zegan
    @webczat
    well, let notebooks first work better, then interactive window might become usable, and then it will be possible to think if there is something interactive window specific to improve. so the current one is the best for now, I think.
    or people can start reporting specific issues but I am not using notebooks daily and barely know what to expect.
    Michał Zegan
    @webczat
    mainly stuff related to navigating into or between outputs.
    Isidor Nikolic
    @isidorn
    @webczat whatever you prefer works. Navigating into or between outputs sounds like it could be distilled into specific issues. So I think if we file those, the notebook people can look into fixing that specific problem.
    Isidor Nikolic
    @isidorn

    VS Code supports multiple cursors. More about this feature can be found here https://code.visualstudio.com/docs/editor/codebasics#_multiple-selections-multicursor
    The idea behind multiple cursors is what you type at one cursor the other cursors will replicate. So it makes refactorings faster.

    When you have multiple cursors there is still a “primary” cursor and screen reader will read what is on the line of the primary cursor.
    Because of this we have introduced “Focus Next Cursor” and “Focus Previous Cursor” commands. So you can change what is the active cursor, so that you can choose based on which cursor line does the screen reader read.
    You can try it out in latest VS Code Insiders and let us know what you think about this feature.

    Isidor Nikolic
    @isidorn
    We are discussing to use treegrid instead of tree role for our trees. If you are interested more details can be found here microsoft/vscode#146210
    AmandaChongCE
    @AmandaChongCE
    Hello,
    I am fairly new to programming, and was wondering if the community could advise me on how I can use the Jupyter Notebooks extension on VS code - I am able to focus my jaws cursor on the various input cells, and type in my code by pressing enter. But I'm uncertain how to read the out. Pressing (control+U) doesn't seem to provide me with any output. For now, all I hear is that
    AmandaChongCE
    @AmandaChongCE

    Hello,

    I am fairly new to coding, and was hoping for some advice from this community. I can't figure out how to read my output when I use VS code Jupyter Notebooks extension to run my code. Control+shift+U brings me to the pannel that says tasks - output editor and jaws asks me to use arrow keys to read the text. But there's nothing there even though I'm pretty sure there should be (tested it using Jupyter Notebook application).

    Thanks for the advice in advance!

    Isidor Nikolic
    @isidorn
    @AmandaChongCE hi and welcome to this gitter channel. I must confess that the Notebook experience is not super polished - I just reached out to my colleague working on Notebooks and hopefully she will help in driving improvements here.
    In the meantime, the output is unrelated to the notebooks, it has output from different channels. For the Notebook output you should be able to just navigate to it using Tab / Up / Down
    I hope this doc can help as well https://code.visualstudio.com/docs/datascience/jupyter-notebooks
    Try it out and let me know how it goes.
    bgt lover
    @albertotirla:matrix.org
    [m]
    hello there!
    Recently, I opened an microsoft/vscode#147794 for screenreaders not reading warnings about git commit messages that have lines longer than 72 characters, even though it appears visually. Can someone confirm it, post on there or something? I don't think I should have to jump to vim just because that stuff is autoformatted in there. I get the fact vscode wants to support many languages or something, but the warning should at least be read.
    bgt lover
    @albertotirla:matrix.org
    [m]
    I mean, I think the fix is only afew lines or something, like, just use the component for the warning that is also accessible and reads, such as the one where you're prevented from typing invalid names for your filesystem as a file.
    Michał Zegan
    @webczat
    pretty sure it is a regression as i remember it being read. or at least a warning for too long commit subject
    bgt lover
    @albertotirla:matrix.org
    [m]
    btw, it's my first time opening an issue against that repo, so dk if I included enough detail. O yeah, I used the built-in issue thingy in the vscode help menu, even though it wasn't really accessible, like dk how they made it so that I can't go into browse mode and read the labels that tell me what box is for what. Still, it didn't do formatting very well, didn't follow any templates, so I had to edit my comment and add the headings manually.
    Isidor Nikolic
    @isidorn
    @albertotirla:matrix.org Thank you very much for opening that issue. For now it has just enough details. Lad is looking into it and we should know more soon. If he has questions he will reach out to you on the issue.
    2 replies
    Isidor Nikolic
    @isidorn
    If you have feedback regarding what audio cues you would like us to add please let me know. Next ones we are thinking about are sounds for quick fixes, and sounds for diff view (removed, added, conflict lines)
    1 reply
    bgt lover
    @albertotirla:matrix.org
    [m]
    what would also be nice is that when we hear the sound of an error, there should either be a way for the screenreader to read the text of the error on that line if we stay longer on it without moving the cursor, similar to parameter hints. Alternatively, there should be a keyboard shortcut that makes the error text be read by the sr if you're on an error line and you press it, for people who don't want error texts to be automatically read to them.
    next, perhaps this should be generalised to include every audio warning, not only errors, since the information is in the ide already, so why not expose it?
    for example, for breakpoints, the feature should read what kind of breakpoint it is, if conditional what condition triggers it, etc.
    Isidor Nikolic
    @isidorn
    @albertotirla:matrix.org thanks for feedback, I think we already have a similar flow, where you can press Ctrl + Shift + M and pass focus to the problems view. Similarly you can trigger a command to focus on the breakpoints view. Can you try that flow and let me know how it works for you? Thanks
    4 replies
    bgt lover
    @albertotirla:matrix.org
    [m]
    perhaps a more general hotkey of mouse over would be useful, then the tooltip to be read by the screenreader anyway? I mean, in that case, it would potentially add many more applications than just error reporting. For example, if you use the mouseover command on a js line that says let age=42;, it should say age, variable, number or something like that, basically type inference as offered by the extensions already. This feature could be very useful for other things as well, dk the full extent of what mouseover can do because obviously I can't perform it.
    2 replies
    bgt lover
    @albertotirla:matrix.org
    [m]
    I used the f8 stuff before, but I dk about ctrl+k, ctrl+i
    bgt lover
    @albertotirla:matrix.org
    [m]
    btw, I just realised that even when it works, I can't simply focus to the code where I was, I have to either ctrl+tab back to the file where I was editting stuff, or perhaps focuse the explorer and enter on the file I was viewing before to open in the same place. Does anyone know how to focus the current editor view after reading the tooltip?
    1 reply
    bgt lover
    @albertotirla:matrix.org
    [m]
    OK, I'll do that
    1 reply
    bgt lover
    @albertotirla:matrix.org
    [m]
    actually, there are many separate issues in the range of the error thing. Should I open one about a keybinding that makes the sr read the error on the currently focused line and making it more generalised so that each audio queue can be inspected to see why is it there, or one about the mouseover key sequence not working unless you're on a specific char of the line in the editor?
    5 replies
    bgt lover
    @albertotirla:matrix.org
    [m]
    I'm writing the issue now. However, I wish the issue reporter was a lot more accessible and had more fields, now I have to do many things by hand in stead of just completing fields with detailed info
    bgt lover
    @albertotirla:matrix.org
    [m]
    hmm, should this be a bug report or a feature?
    I think it should be a feature because it doesn't describe a bug with the tools we currently have, rather it explains what would be nice for us to have in order to make our dev experience more productive
    bgt lover
    @albertotirla:matrix.org
    [m]
    all done, check the issue out on microsoft/vscode#148634
    1 reply