Skip to content

Task property "presentation": {"reveal": "never"} is not working when Python extension is active #3852

Closed

Description

@jcrmatos

Environment data

  • VS Code version: 1.30.1
  • Extension version (available under the Extensions sidebar): 2018.12.1
  • OS and version: Windows 7 Pro SP1 + all updates
  • Python version (& distribution if applicable, e.g. Anaconda): 3.7.1 (WinPython)
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): virtualenv created by pipenv

Expected behaviour

Task property "presentation": {"reveal": "never"} should never show the terminal panel when the task runs.

Actual behaviour

Task property "presentation": {"reveal": "never"} always shows the terminal panel when the task runs and the Python extension is active.

Steps to reproduce:

  1. Activate the Python extension.
  2. Create a task, eg.
        {
            "label": "Py3 Help",
            "type": "shell",
            "windows": {
                "command": "${env:OneDrive}\\Python\\winpython371-32\\python-3.7.1\\Doc\\python371.chm"
            },
            "presentation": {
                "reveal": "never"
            }
        },
  1. Create a keyboard shortcut, eg.
[{
    "key": "shift+f1",
    "command": "workbench.action.tasks.runTask",
    "args": "Py3 Help"
}]
  1. Run the task, in my eg. shift+F1

Output in terminal (that should not appear)

> Executing task in folder uniclave: C:\Users\JMatos\OneDrive\Python\winpython371-32\python-3.7.1\Doc\python371.chm <


Terminal will be reused by tasks, press any key to close it.

I created a simple Task and added the presentation item, hoping that that would allow me to never show the integrated terminal (as it is reported in the doc at
https://code.visualstudio.com/docs/editor/tasks#vscode
but it isn't working. It always shows the integrated terminal.

{
    // See https://go.microsoft.com/fwlink/?LinkId=733558
    // for the documentation about the tasks.json format
    "version": "2.0.0",
    "tasks": [
        {
            "label": "Py3 Help",
            "type": "shell",
            "command": "C:\\Python354-32\\Doc\\python354.chm",
            "problemMatcher": [],
            "presentation": {
                "reveal": "never"
            }
        }
    ]
}

Thanks,

JM

Activity

  1. ghost added
    triage-neededNeeds assignment to the proper sub-team
    on Jan 3, 2019
  2. ghost removed
    triage-neededNeeds assignment to the proper sub-team
    on Jan 4, 2019
  3. d3r3kk commented on Jan 4, 2019

    @d3r3kk

    Issue moved to Microsoft/vscode #66056 via ZenHub

  4. d3r3kk commented on Jan 4, 2019

    @d3r3kk

    Don Jayamanne (@DonJayamanne) could you have a look at #65179 before we close this one on our repo. It would seem that the integrated terminal only opens when the Python extension is active...

  5. jcrmatos commented on Jan 4, 2019

    @jcrmatos
    Author

    Hello,

    It was me who opened issue #65179 at vscode, but because it only occurs when using the Python extension, I closed it and opened a new issue here.

    Thanks,

    JM

  6. d3r3kk commented on Jan 4, 2019

    @d3r3kk

    because it only occurs when using the Python extension...

    Yes, I didn't realize that bit when I closed it! Thanks, we will have a look and see if there is something we are doing on our end.

  7. DonJayamanne commented on Jan 8, 2019

    @DonJayamanne

    Please add the following setting "python.terminal.activateEnvironment": false in your workspace settings.json file.
    This will ensure the terminal doesn't get activated with the workspace virtual environment.

  8. ghost removed on Jan 8, 2019
  9. jcrmatos commented on Jan 8, 2019

    @jcrmatos
    Author

    Hello,

    I'm sorry but that makes no sense. I want the terminal to activate the venv.

    What should not happen is the task to show in terminal if the option

    "presentation": {
                    "reveal": "never"
                }
    

    is present.

    And this only happens with the Python extension activated.
    If I disable it everything works.

    Thanks,

    JM

  10. locked as resolved and limited conversation to collaborators on Feb 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

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