Skip to content

Allow custom arguments for ctags  #105

Closed
Closed
Allow custom arguments for ctags #105
Labels
bugIssue identified by VS Code Team member as probable bug

Description

@DonJayamanne
Don Jayamanne (DonJayamanne)
opened on Nov 13, 2017

From Jan Hancic (@janhancic) on April 18, 2017 10:6

I accidentally opened the .vscode/tags file and noticed that ctags built a definition list (or whatever, I'm not familiar with ctags) for stuff in my excluded folders. Can this be made so it doesn't scan excluded files (or maybe create a new setting for this)?

I'm not sure of this is related to my problem of not having full intellisense or not though.

Copied from original issue: DonJayamanne/pythonVSCode#891

Activity

  1. Don Jayamanne (DonJayamanne)
    added
    enhancement
    m
    and removed
    enhancement
    m
    on Nov 13, 2017
  2. Brett Cannon (brettcannon)
    added
    awaiting 1-decision
    feature-code navigation
    feature-requestRequest for new features or functionality
    on Nov 14, 2017
  3. Brett Cannon (brettcannon)
    added
    bugIssue identified by VS Code Team member as probable bug
    needs PR
    and removed
    needs decision
    feature-requestRequest for new features or functionality
    on Apr 5, 2018
  4. Brett Cannon (brettcannon)
    added
    x-exuberant ctags
    on May 2, 2018

  5. victorgabr commented on May 19, 2018

    @victorgabr
    Victor Gabriel Leandro Alves (victorgabr)
    on May 19, 2018

    I tested opening a huge project folder. It's made a .vscode/tags file larger than 10 GB. I am going to post my environment details. Maybe it can help to reproduce this issue.

  6. Brett Cannon (brettcannon)
    added this to the June 2018 milestone on Jun 5, 2018
  7. Brett Cannon (brettcannon)
    removed this from the June 2018 milestone on Oct 17, 2018
  8. Brett Cannon (brettcannon)
    removed
    upstream-exuberant ctags
    on Jul 29, 2019
  9. Luciana Abud (luabud)
    changed the title [-]ctags exclude folders[/-] [+]Allow custom arguments for ctags [/+] on Sep 11, 2019
  10. Luciana Abud (luabud)
    assigned
    Kim-Adeline Miguel (kimadeline)
    on Sep 11, 2019

  11. kimadeline commented on Sep 12, 2019

    @kimadeline
    Kim-Adeline Miguel (kimadeline)
    on Sep 12, 2019

    Closing as we now have python.workspaceSymbols.exclusionPatterns.

  12. Kim-Adeline Miguel (kimadeline)
    closed this as completedon Sep 12, 2019
  13. ghost removed
    needs PR
    on Sep 12, 2019
  14. Kim-Adeline Miguel (kimadeline)
    removed their assignment
    on Sep 12, 2019
  15. lock
    locked as resolved and limited conversation to collaborators on Sep 19, 2019
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

    bugIssue identified by VS Code Team member as probable bug

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions