Skip to content
This repository was archived by the owner on Dec 15, 2022. It is now read-only.
This repository was archived by the owner on Dec 15, 2022. It is now read-only.

Using a variable as a default in a function definition causes inconsistent highlighting #278

Open

Description

Prerequisites

Description

Using a variable as a default in a function definition causes inconsistent highlighting of variable name. Specifically, the first letter or the variable will not be highlighted.

Steps to Reproduce

  1. Open new file
  2. Set language to Python
  3. Enter def test(test_var = variable):

Expected behavior: variable should be highlighted completely.

Actual behavior: ariable is highlighted while v is not.

Reproduces how often: 100%

Versions

Windows 10
C:\WINDOWS\system32>atom --version

Atom : 1.31.1
Electron: 2.0.7
Chrome : 61.0.3163.100
Node : 8.9.3

C:\WINDOWS\system32>apm --version
apm 2.1.1
npm 6.2.0
node 8.9.3 x64
atom 1.31.1
python 3.6.4
git 2.17.0
visual studio

Additional Information

None

Activity

  1. TheElementalOfDestruction commented on Oct 3, 2018

    @TheElementalOfDestruction
    Author

    Package: language-python 0.51.4

  2. TheElementalOfDestruction commented on Oct 30, 2018

    @TheElementalOfDestruction
    Author

    Still exists in 0.51.6

  3. TheElementalOfDestruction commented on Nov 1, 2018

    @TheElementalOfDestruction
    Author

    Here is a screenshot showing the problem along with the associated styles and stuff that create the problem:

    image

  4. TheElementalOfDestruction commented on Nov 23, 2018

    @TheElementalOfDestruction
    Author

    Hopefully I can get someone to look at this soon

  5. rsese commented on Dec 19, 2018

    @rsese

    Sorry for the delay @TheElementalOfCreation - we're transitioning over to supporting the Tree-sitter grammars only for built-in languages, does this still reproduce with Tree-sitter enabled?

  6. TheElementalOfDestruction commented on Dec 19, 2018

    @TheElementalOfDestruction
    Author

    Tree sitter seems to fix it, but at the same time it breaks a lot of other stuff. The "other stuff" was already discussed in another issue though.

  7. TheElementalOfDestruction commented on Dec 19, 2018

    @TheElementalOfDestruction
    Author

    #281 is the issue I was referring to

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

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions