Skip to content
This repository was archived by the owner on Jul 31, 2023. It is now read-only.
This repository was archived by the owner on Jul 31, 2023. It is now read-only.

Symbol strings (ex. :abc) via "Remote - SSH" are not correctly highlighted #483

Closed

Description

@danglduy

Your environment

  • vscode-ruby version: 0.22.3
  • Ruby version: 2.6.3
  • Ruby version manager (if any): rbenv
  • VS Code version: 1.34.10-insider
  • Operating System: Windows
  • Using language server? Solargraph
  • Using via "Remote - SSH" remote environment (Link)

Expected behavior

Symbol strings syntax is correctly highlighted

Actual behavior

Symbol strings syntax is incorrectly highlighted

In the picture below :exception should be highlighted
image

Activity

  1. connorshea commented on May 12, 2019

    @connorshea
    Contributor

    I assume this is the same problem as microsoft/vscode-remote-release#153

  2. danglduy commented on May 13, 2019

    @danglduy
    Author

    I think these are not the same problems. Ruby symbols are correctly highlighted without any language servers anyway.

  3. minkir014 commented on May 13, 2019

    @minkir014

    Have you tried that on an ordinary vs code?

  4. danglduy commented on May 13, 2019

    @danglduy
    Author

    @minkir014 "Remote - SSH" extension does only work on VS Code Insider I'm afraid.

  5. wingrunr21 commented on May 13, 2019

    @wingrunr21
    Collaborator

    hi @danglduy

    Can you use the Developer: Inspect TM Scopes tool (accessible via the command palette) to tell me what scopes are being matched for the with: :exception part of that code?

    The with: should be matching the grammar with a scope of constant.language.symbol.hashkey.ruby and :exception should be constant.language.symbol.ruby.

  6. danglduy commented on May 13, 2019

    @danglduy
    Author

    @wingrunr21 I inspected with: and :exception
    image
    image

  7. wingrunr21 commented on May 13, 2019

    @wingrunr21
    Collaborator

    Ok. What theme are you using? The Ruby grammar is correctly matching the TM scopes but it appears your theme does not have support.

  8. danglduy commented on May 13, 2019

    @danglduy
    Author

    @wingrunr21 I am using the default theme.

  9. wingrunr21 commented on May 13, 2019

    @wingrunr21
    Collaborator

    Which is that? Dark+?

  10. danglduy commented on May 13, 2019

    @danglduy
    Author

    Yes it’s Dark+

  11. wingrunr21 commented on May 14, 2019

    @wingrunr21
    Collaborator

    interesting. I also use Dark+ and I get those keywords highlighted in blue. Do you get highlighting with a different theme?

  12. danglduy commented on May 14, 2019

    @danglduy
    Author

    @wingrunr Have you tried using in “Remote SSH” environment? I get highlighted normally in local environment.

  13. wingrunr21 commented on May 14, 2019

    @wingrunr21
    Collaborator

    No but that's what I'm trying to determine what the problem is. Does another theme give you correct highlighting?

    The Remote SSH environment isn't stable yet and this extension doesn't explicitly support it. Theming is a core VSCode function as well. The grammar is supplying and matching a TM Scope but the theme doesn't have a matching style.

  14. OmriSama commented on Jul 16, 2019

    @OmriSama

    Following

  15. OmriSama commented on Jul 18, 2019

    @OmriSama

    Here's the difference between correctly working TM scope and a not correctly working one:

    CORRECT
    image

    INCORRECT
    image

    Issue is in constant.language vs constant.other.symbol

  16. minkir014 commented on Jul 18, 2019

    @minkir014

    How have you displayed this in vscode insiders??? I mean what is displayed in the images.

  17. OmriSama commented on Jul 18, 2019

    @OmriSama

    How have you displayed this in vscode insiders??? I mean what is displayed in the images.

    I opened the same directory in two windows, one was local VSCode and another one was Remote SSH.

  18. connorshea commented on Jul 18, 2019

    @connorshea
    Contributor

    There's a command in the command palette called "Inspect TM Scopes", I think that's what they're asking for.

  19. wingrunr21 commented on Jul 18, 2019

    @wingrunr21
    Collaborator

    That's what it is. I'm digging into Remote environments after I fix the current issue with tree-sitter. I haven't yet researched why VSCode is assigning different TextMate scopes between the two environments.

  20. OmriSama commented on Jul 27, 2019

    @OmriSama

    Any updates on this?

  21. added this to the v0.26.0 milestone on Oct 20, 2019
  22. wingrunr21 commented on Nov 19, 2019

    @wingrunr21
    Collaborator

    This has been resolved in v0.26.0

  23. OmriSama commented on Nov 19, 2019

    @OmriSama

    @wingrunr21 thank you so much! This has been sorely lacking in my Ruby experience :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions