Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Error when starting Atom from terminal

Aberta
#189 1 comentário 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
25/100
Tipo de issue
Bug
Clareza
Precisa de esclarecimento
Status de atividade
Estagnada
Stack de tecnologia
javascript, python
Domínio
devtools

Direção de pesquisa

Reproduza a falha iniciando o Atom com atom . e, em seguida, inspecione as entradas da stack do ide-python em torno de python/lib/utils.js e python/lib/main.js, especialmente detectPipEnv. Compare os ambientes de inicialização do terminal e da área de trabalho; considera-se concluído quando a inicialização pelo terminal não produzir mais spawn ENOTDIR e os pacotes dos ambientes virtuais permanecerem disponíveis.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

Hey,
I have the follow error when opening atom from the terminal with atom .
Once atom is opened, every time a open a python module I get the error.

internal/child_process.js:358 Uncaught (in promise) Error: spawn ENOTDIR
    at ChildProcess.spawn (internal/child_process.js:358)
    at Object.spawn (child_process.js:543)
    at resolve (/home/somnium/.atom/…thon/lib/utils.js:9)
    at new Promise (<anonymous>)
    at detectPipEnv (/home/somnium/.atom/…thon/lib/utils.js:8)
    at PythonLanguageClient.startServerProcess (/home/somnium/.atom/…thon/lib/main.js:50)
    at PythonLanguageClient.<anonymous> (auto-languageclient.ts:298)
    at Generator.next (<anonymous>)
    at /home/somnium/.atom/…languageclient.js:7
    at new Promise (<anonymous>)
    at __awaiter (/home/somnium/.atom/…languageclient.js:3)
    at process.reportBusyWhile (auto-languageclient.ts:298)
    at AtomIdeProvider.<anonymous> (atom-ide-provider.js? [sm]:7)
    at Generator.next (<anonymous>)
    at step (/home/somnium/.atom/…m-ide-provider.js:9)
    at /home/somnium/.atom/…m-ide-provider.js:9
    at new Promise (<anonymous>)
    at AtomIdeProvider.<anonymous> (/home/somnium/.atom/…m-ide-provider.js:9)
    at Object.reportBusyWhile (index.js? [sm]:33)
    at PythonLanguageClient.<anonymous> (auto-languageclient.ts:798)
    at Generator.next (<anonymous>)
    at /home/somnium/.atom/…languageclient.js:7
    at new Promise (<anonymous>)
    at __awaiter (/home/somnium/.atom/…languageclient.js:3)
    at PythonLanguageClient.AutoLanguageClient.reportBusyWhile (auto-languageclient.ts:796)
    at PythonLanguageClient.<anonymous> (auto-languageclient.ts:296)
    at Generator.next (<anonymous>)
    at /home/somnium/.atom/…languageclient.js:7
    at new Promise (<anonymous>)
    at __awaiter (/home/somnium/.atom/…languageclient.js:3)
    at PythonLanguageClient.startServer (auto-languageclient.ts:295)
    at ServerManager._serverManager.server_manager_js_1.ServerManager [as _startServer] (auto-languageclient.ts:253)
    at ServerManager.<anonymous> (server-manager.ts:155)
    at Generator.next (<anonymous>)
    at /home/somnium/.atom/…server-manager.js:7
    at new Promise (<anonymous>)
internal/child_process.js:358 Uncaught (in promise) Error: spawn ENOTDIR
    at ChildProcess.spawn (internal/child_process.js:358)
    at Object.spawn (child_process.js:543)
    at resolve (/home/somnium/.atom/…thon/lib/utils.js:9)
    at new Promise (<anonymous>)
    at detectPipEnv (/home/somnium/.atom/…thon/lib/utils.js:8)
    at PythonLanguageClient.startServerProcess (/home/somnium/.atom/…thon/lib/main.js:50)
    at PythonLanguageClient.<anonymous> (auto-languageclient.ts:298)
    at Generator.next (<anonymous>)
    at /home/somnium/.atom/…languageclient.js:7
    at new Promise (<anonymous>)
    at __awaiter (/home/somnium/.atom/…languageclient.js:3)
    at process.reportBusyWhile (auto-languageclient.ts:298)
    at AtomIdeProvider.<anonymous> (atom-ide-provider.js? [sm]:7)
    at Generator.next (<anonymous>)
    at step (/home/somnium/.atom/…m-ide-provider.js:9)
    at /home/somnium/.atom/…m-ide-provider.js:9
    at new Promise (<anonymous>)
    at AtomIdeProvider.<anonymous> (/home/somnium/.atom/…m-ide-provider.js:9)
    at Object.reportBusyWhile (index.js? [sm]:33)
    at PythonLanguageClient.<anonymous> (auto-languageclient.ts:798)
    at Generator.next (<anonymous>)
    at /home/somnium/.atom/…languageclient.js:7
    at new Promise (<anonymous>)
    at __awaiter (/home/somnium/.atom/…languageclient.js:3)
    at PythonLanguageClient.AutoLanguageClient.reportBusyWhile (auto-languageclient.ts:796)
    at PythonLanguageClient.<anonymous> (auto-languageclient.ts:296)
    at Generator.next (<anonymous>)
    at /home/somnium/.atom/…languageclient.js:7
    at new Promise (<anonymous>)
    at __awaiter (/home/somnium/.atom/…languageclient.js:3)
    at PythonLanguageClient.startServer (auto-languageclient.ts:295)
    at ServerManager._serverManager.server_manager_js_1.ServerManager [as _startServer] (auto-languageclient.ts:253)
    at ServerManager.<anonymous> (server-manager.ts:155)
    at Generator.next (<anonymous>)
    at /home/somnium/.atom/…server-manager.js:7
    at new Promise (<anonymous>)

Everything works if I'm starting Atom from desktop icon, however I need to be able to running it from the terminal.
When running sudo atom . it works, but I don't get my virtual env installed packages available which makes it impossible to use some other atom plugins features.

My setup:
OS: Ubuntu 18
Atom: 1.42
ide-python: 1.5.0

Any help is welcome.
Thanks

Linguagem predominante
JavaScript
Estrelas
238
Forks
41
Métricas de merge de PRs
Nenhum PR com merge em 30d

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de atom-community/ide-python

Todas as issues de atom-community/ide-python

Issues semelhantes

Mais issues de JavaScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.