karan / atom-terminal Goto Github PK

View Code? Open in Web Editor NEW

70.0 70.0 30.0 1.14 MB

Atom package to open terminal on current file's directory with "ctrl-shift-t"

Home Page: https://atom.io/packages/atom-terminal

License: MIT License

CoffeeScript 100.00%

atom-terminal's People

Stargazers

Watchers

atom-terminal's Issues

Open Terminal won't show up when using the cmd+shift+P search command

Sometimes it fixes itself, sometimes it doesn't
Also using vim mode package

atom-terminal is activated only after triggering `atom-terminal:open-project-root` by menu

During using atom-terminal, I found keymap 'ctrl-shift-t' not always working. After some digging, I've located the reason for this: atom-terminal is activated only after triggering atom-terminal:open-project-root by menu "Open Terminal At Root", so the command of "atom-terminal:open" was not added at all.

This is caused by config item "activationCommands" in package.json. In https://atom.io/docs/v1.0.0/hacking-atom-package-word-count :

activationCommands: an Object identifying commands that trigger your package’s activation. The keys are CSS selectors, the values are Arrays of Strings identifying the command. The loading of your package is delayed until one of these events is triggered within the associated scope defined by the CSS selector.

If we remove this config item, atom-terminal would be activated at atom load time, thus fix the problem.

Deprecated Atom APIs will be removed June 1st

Atom will no longer load this package after June 1st without changes. There are a couple deprecations on the latest version (0.8.0) of this package:

Requiring $ from atom is no longer supported. If you are using space-pen, please require $ from atom-space-pen-views. Otherwise require jquery instead: {$} = require 'atom-space-pen-views' or $ = require 'jquery' Add "atom-space-pen-views": "^2.0.3" to your package dependencies. Or add "jquery": "^2" to your package dependencies.
Requiring $$ from atom is no longer supported. Please require atom-space-pen-views instead: {$$} = require 'atom-space-pen-views' Add "atom-space-pen-views": "^2.0.3" to your package dependencies.
Requiring View from atom is no longer supported. Please require atom-space-pen-views instead: {View} = require 'atom-space-pen-views' Add "atom-space-pen-views": "^2.0.3" to your package dependencies.
The context menu CSON format has changed. Please see https://atom.io/docs/api/latest/ContextMenuManager#context-menu-cson-format for more info.

Visit https://gist.github.com/benogle/6d09e295c84b717ef9b4 and search for your package name to see up-to-date deprecations.

If this package has been replaced by another package or functionality in core, please reply with this information.

See atom/atom#6867 for more info. Thanks!

Does not work in Maverics

For some reason the key binding does not work in OS X Maverics

Atom.Object.defineProperty.get is deprecated.

atom.workspaceView is no longer available.
In most cases you will not need the view. See the Workspace docs for
alternatives: https://atom.io/docs/api/latest/Workspace.
If you do need the view, please use atom.views.getView(atom.workspace),
which returns an HTMLElement.

Atom.Object.defineProperty.get (/usr/share/atom/resources/app/src/atom.js:54:11)
Object.activate (/home/marcos/.atom/packages/atom-terminal/lib/atom-terminal.coffee:45:13)

Atom.Object.defineProperty.get is deprecated.

Atom.Object.defineProperty.get (c:\Users\...\AppData\Local\atom\app-0.174.0\resources\app\src\atom.js:55:11)
Object.activate (c:\Users\...\.atom\packages\atom-terminal\lib\atom-terminal.coffee:45:13)

Choose terminal app

It would be useful to choose / set in package settings, which terminal app should be used. I for example use iTerm2, not the standard terminal on mac. Thanks.

Package.getActivationCommands is deprecated.

Use activationCommands instead of activationEvents in your package.json
Commands should be grouped by selector as follows:

  "activationCommands": {
    "atom-workspace": ["foo:bar", "foo:baz"],
    "atom-text-editor": ["foo:quux"]
  }

Package.getActivationCommands (/usr/share/atom/resources/app.asar/src/package.js:810:9)
Package.hasActivationCommands (/usr/share/atom/resources/app.asar/src/package.js:735:20)
<unknown> (/usr/share/atom/resources/app.asar/src/package.js:189:24)
Package.measure (/usr/share/atom/resources/app.asar/src/package.js:167:15)

Created from atom 0.198.0

Uncaught TypeError: Cannot read property 'file' of undefined

Installed atom using the rpm package on fedora 20
Installed the atom-terminal package using the settings view
Used the shortcut Ctrl-Shift-t

Atom Version: 0.165.0
System: linux 3.17.7-200.fc20.x86_64
Thrown From: atom-terminal package, v0.6.0

Stack Trace

Uncaught TypeError: Cannot read property 'file' of undefined

At /home/pprince/.atom/packages/atom-terminal/lib/atom-terminal.coffee:49

TypeError: Cannot read property 'file' of undefined
  at Object.module.exports.open (/home/pprince/.atom/packages/atom-terminal/lib/atom-terminal.coffee:49:30)
  at atom-workspace.<anonymous> (/home/pprince/.atom/packages/atom-terminal/lib/atom-terminal.coffee:45:62)
  at atom-workspace.handler (/usr/local/share/atom/resources/app/src/space-pen-extensions.js:115:32)
  at atom-workspace.jQuery.event.dispatch (/usr/local/share/atom/resources/app/node_modules/space-pen/vendor/jquery.js:4681:9)
  at atom-workspace.elemData.handle (/usr/local/share/atom/resources/app/node_modules/space-pen/vendor/jquery.js:4359:46)
  at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/usr/local/share/atom/resources/app/src/command-registry.js:243:29)
  at /usr/local/share/atom/resources/app/src/command-registry.js:3:61
  at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/usr/local/share/atom/resources/app/node_modules/atom-keymap/lib/keymap-manager.js:549:16)
  at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/usr/local/share/atom/resources/app/node_modules/atom-keymap/lib/keymap-manager.js:391:22)
  at HTMLDocument.module.exports.WindowEventHandler.onKeydown (/usr/local/share/atom/resources/app/src/window-event-handler.js:167:20)

Commands

  6x -1:11.7 core:move-down (input.hidden-input)
  7x -1:07.8 core:move-up (input.hidden-input)
  2x -1:05.7 core:move-down (input.hidden-input)
     -1:03.6 core:confirm (input.hidden-input)
     -1:03.6 settings-view:install-packages (input.hidden-input)
     -0:56.2 core:select-all (input.hidden-input)
     -0:56.1 core:backspace (input.hidden-input)
     -0:54.7 core:confirm (input.hidden-input)
     -0:35.9 core:select-all (input.hidden-input)
  2x -0:34.6 core:confirm (input.hidden-input)
     -0:23.5 core:select-all (input.hidden-input)
     -0:20.8 core:confirm (input.hidden-input)
     -0:04.3 command-palette:toggle (atom-workspace.workspace.scrollbars-visible-always.theme-atom-dark-syntax.theme-atom-dark-ui)
     -0:01.1 editor:consolidate-selections (input.hidden-input)
     -0:01.1 core:cancel (input.hidden-input)
     -0:00.0 atom-terminal:open (atom-workspace.workspace.scrollbars-visible-always.theme-atom-dark-syntax.theme-atom-dark-ui)

Config

{}

Installed Packages

# User
No installed packages

# Dev
No dev packages

/cc @atom/core

Open Terminal keybinding conflicts on Windows and Linux

On Windows and Linux, Ctrl Shift T is set to reopen closed tab by default. This package overrides that with the atom-terminal:open command.

win7 Powershell or Git Bash

hi ,
I want to use another terminal than poor ' cmd.exe '
I tried unsuccessfully PowerShell:
app: "% SystemRoot% \ system32 \ \ \ v1.0 WindowsPowerShell powershell.exe '
and Git bash:
app: "% SystemDrive% \ Program Files (x86) \ \ \ bin bash.exe Git '
tried usual arg' '

just a popup and disappears
there's an another way?
Thanks.

(edit)
I found Powershell Starting options from technet
app: "% SystemRoot% \ system32 \ \ \ v1.0 WindowsPowerShell powershell.exe '
args '-noexit -command clear'
work fine..

Package.activateResources is deprecated.

The context menu CSON format has changed. Please see
https://atom.io/docs/api/latest/ContextMenuManager

Uncaught TypeError: Cannot read property 'file' of undefined

[Enter steps to reproduce below:]

Atom Version: 0.168.0
System: linux 3.14.26-100.fc19.x86_64
Thrown From: atom-terminal package, v0.6.0

Stack Trace

Uncaught TypeError: Cannot read property 'file' of undefined

At /home/kevin/.atom/packages/atom-terminal/lib/atom-terminal.coffee:49

TypeError: Cannot read property 'file' of undefined
  at Object.module.exports.open (/home/kevin/.atom/packages/atom-terminal/lib/atom-terminal.coffee:49:30)
  at atom-workspace.<anonymous> (/home/kevin/.atom/packages/atom-terminal/lib/atom-terminal.coffee:45:62)
  at atom-workspace.handler (/usr/local/share/atom/resources/app/src/space-pen-extensions.js:115:32)
  at atom-workspace.jQuery.event.dispatch (/usr/local/share/atom/resources/app/node_modules/space-pen/vendor/jquery.js:4681:9)
  at atom-workspace.elemData.handle (/usr/local/share/atom/resources/app/node_modules/space-pen/vendor/jquery.js:4359:46)
  at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/usr/local/share/atom/resources/app/src/command-registry.js:243:29)
  at /usr/local/share/atom/resources/app/src/command-registry.js:3:61
  at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/usr/local/share/atom/resources/app/node_modules/atom-keymap/lib/keymap-manager.js:549:16)
  at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/usr/local/share/atom/resources/app/node_modules/atom-keymap/lib/keymap-manager.js:391:22)
  at HTMLDocument.module.exports.WindowEventHandler.onKeydown (/usr/local/share/atom/resources/app/src/window-event-handler.js:167:20)

Commands

     -6:01.8 pane:reopen-closed-item (div.am-panel.tool-panel.panel-bottom.native-key-bindings)
     -5:53.0 application:open-folder (atom-text-editor.editor)
     -5:35.9 timecop:view (atom-text-editor.editor)
     -5:19.7 core:save (atom-text-editor.editor)
     -3:17.6 settings-view:open (ul.list-inline.tab-bar.inset-panel)
  3x -2:58.2 core:backspace (atom-text-editor.editor.mini)
     -0:20.4 core:save (atom-text-editor.editor)
     -0:00.0 atom-terminal:open (atom-workspace.workspace.scrollbars-visible-always.theme-atom-dark-syntax.theme-atom-dark-ui)

Config

{
  "core": {}
}

Installed Packages

# User
autocomplete-plus, v1.1.0
go-plus, v3.0.13

# Dev
No dev packages

/cc @atom/core

More than one terminal paths support or fallback to default if custom terminal not found. (Feature request)

I'm using atom-sync-settings to sync atom settings between two computers, one is mac and one is windows.

I'm not using window's default cmd and so I configured custom terminal app in this atom-terminal package. But, when atom-sync-settings sync that settings from windows to mac, the custom terminal path from windows is invalid and not working on mac.

It'll be better if this package can support multiple path settings or fallback second path if first path not found or some other ways to solve this issue.

Package.getActivationCommands is deprecated.

Use activationCommands instead of activationEvents in your package.json
Commands should be grouped by selector as follows:

  "activationCommands": {
    "atom-workspace": ["foo:bar", "foo:baz"],
    "atom-text-editor": ["foo:quux"]
  }

Package.getActivationCommands (/usr/share/atom/resources/app.asar/src/package.js:806:9)
Package.hasActivationCommands (/usr/share/atom/resources/app.asar/src/package.js:731:20)
<unknown> (/usr/share/atom/resources/app.asar/src/package.js:185:24)
Package.measure (/usr/share/atom/resources/app.asar/src/package.js:163:15)
Package.load (/usr/share/atom/resources/app.asar/src/package.js:177:12)
PackageManager.loadPackage (/usr/share/atom/resources/app.asar/src/package-manager.js:355:14)

Is it possible to open just a Terminal tab instead of a new window?

In Sublime text I use a plugin, I think it's called MacTerminal, that allows me to open files in the Terminal, but if the Terminal is already open, it just adds a tab.
Is that possible to achieve in atom-terminal with some setting?
I really find annoying a new window terminal every time.

Ctrl-Shift-T opens twice [Linux]

the terminal opens twice since version 0.5.0

iTerm 2 support

Would be great if this would open a iTerm Terminal.

alt-shift-T [Linux]

alt-shift-T does nothing

Opening terminal results in 2 windows opening

On Windows 8.1 Enterprise pressing ALT+SHIFT+T runs the openroot function twice causing two windows to open, it should only open one.

I also checked open (CTRL+SHIFT+T), that's the same but the broken code prevents it working anyway.

Uncaught TypeError: undefined is not a function

[Enter steps to reproduce below:]

Open file
CTRL+SHIFT+T

Atom Version: 0.182.0
System: Microsoft Windows 8.1 Enterprise
Thrown From: atom-terminal package, v0.7.0

Stack Trace

Uncaught TypeError: undefined is not a function

At C:\Users\z269cjbb\.atom\packages\atom-terminal\lib\atom-terminal.coffee:52

TypeError: undefined is not a function
  at Object.module.exports.open (C:\Users\z269cjbb\.atom\packages\atom-terminal\lib\atom-terminal.coffee:52:32)
  at atom-workspace.<anonymous> (C:\Users\z269cjbb\.atom\packages\atom-terminal\lib\atom-terminal.coffee:45:71)
  at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (C:\Users\z269cjbb\AppData\Local\atom\app-0.182.0\resources\app\src\command-registry.js:243:29)
  at C:\Users\z269cjbb\AppData\Local\atom\app-0.182.0\resources\app\src\command-registry.js:3:61
  at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (C:\Users\z269cjbb\AppData\Local\atom\app-0.182.0\resources\app\node_modules\atom-keymap\lib\keymap-manager.js:558:16)
  at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (C:\Users\z269cjbb\AppData\Local\atom\app-0.182.0\resources\app\node_modules\atom-keymap\lib\keymap-manager.js:396:22)
  at HTMLDocument.module.exports.WindowEventHandler.onKeydown (C:\Users\z269cjbb\AppData\Local\atom\app-0.182.0\resources\app\src\window-event-handler.js:176:20)

Commands

     -8:08.2 command-palette:toggle (atom-pane.pane.active)
     -8:03.7 core:confirm (atom-text-editor.editor.mini)
  2x -8:03.7 atom-terminal:open (atom-pane.pane.active)
     -3:39.6 window:toggle-dev-tools (atom-pane.pane.active)
     -3:35.3 fuzzy-finder:toggle-file-finder (atom-pane.pane.active)
     -3:30.2 atom-terminal:open (atom-pane.pane.active)
     -3:18.9 fuzzy-finder:toggle-file-finder (atom-pane.pane.active)
 36x -3:16.6 core:backspace (atom-text-editor.editor.mini)
     -2:32.3 atom-terminal:open-project-root (div.settings-view.pane-item)
     -2:24.5 atom-terminal:open (div.settings-view.pane-item)
  2x -2:22.0 atom-terminal:open-project-root (div.settings-view.pane-item)
  2x -1:25.3 atom-terminal:open (div.settings-view.pane-item)

Config

{
  "core": {
    "themes": [
      "atom-dark-ui",
      "atom-dark-syntax"
    ]
  },
  "atom-terminal": {}
}

Installed Packages

# User
atom-terminal, v0.7.0
open-recent, v2.2.0
remote-ftp, v0.6.1

# Dev
No dev packages

Can't run sudo from atom-terminal

I use Linux Mint and ran into this problem today, but could not reproduce it on my Mac (though they have very different configurations).

If I run sudo from a terminal opened through atom-terminal I get this error message:

sudo: effective uid is not 0, is /usr/bin/sudo on a file system with the 'nosuid' option set or an NFS file system without root privileges?

Sudo works fine in a regular terminal.

Permissions:

$ ls -l /usr/bin/sudo
-rwsr-xr-x 1 root root 155008 Mar 12 17:27 /usr/bin/sudo

Package.activateResources is deprecated.

The context menu CSON format has changed. Please see
https://atom.io/docs/api/latest/ContextMenuManager

Created from atom 0.198.0

Doesn't run on Windows.

The terminal is not running on Windows 8.

Any updates?

Hello @karan. I see you have activity on github, but do not have any activity in this repo for 20 days. Maybe you will add collaborators?

Package.activateConfig is deprecated.

Use a config schema instead. See the configuration section
of https://atom.io/docs/latest/hacking-atom-package-word-count and
https://atom.io/docs/api/latest/Config for more details

Package.activateConfig (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:247:11)
Package.activateNow (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:218:14)
<unknown> (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:754:25)
Emitter.emit (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/event-kit/lib/emitter.js:82:11)
CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:219:20)

Uncaught Error: Cannot find module './minimap-quick-settings-view'

[Enter steps to reproduce below:]

Click the gear icon of minimap package.
The error appeared.

Atom Version: 0.187.0
System: Unknown Windows Version
Thrown From: atom-terminal package, v0.7.0

Stack Trace

Uncaught Error: Cannot find module './minimap-quick-settings-view'

At module.js:353

Error: Cannot find module './minimap-quick-settings-view'
  at Module._resolveFilename (module.js:351:15)
  at Function.Module._resolveFilename (C:\Users\Martin\AppData\Local\atom\app-0.187.0\resources\app\src\module-cache.js:383:52)
  at Function.Module._load (module.js:293:25)
  at Module.require (module.js:380:17)
  at require (module.js:399:17)
  at HTMLDivElement.<anonymous> (C:\Users\Martin\.atom\packages\minimap\lib\minimap-element.coffee:175:11)

Commands

Config

{
  "core": {
    "autoHideMenuBar": true,
    "disabledPackages": [
      "autocomplete"
    ],
    "themes": [
      "atom-dark-ui",
      "solarized-dark-syntax"
    ]
  }
}

Installed Packages

# User
linter, v0.12.0
minimap, v4.5.0
script, v2.18.0
vim-mode, v0.37.0

# Dev
No dev packages

Dangerous environment variables being set

I noticed my node related commands showing unexpected output when run from terminals opened with this. Finally I found the reason. When you open a terminal from atom-terminal, you get these environment variables set:

ATOM_HOME=/home/user/.atom
GOOGLE_API_KEY=3h4kjhb4go9h4ntgwk
NODE_PATH=/usr/share/atom/resources/app.asar/exports
CHROME_DESKTOP=Atom.desktop
NODE_ENV=production

I don't know why this is done, but I understand that for a general use of a terminal at least GOOGLE_API_KEY ,NODE_PATH and NODE_ENV shouldn't be there. They can (and do) corrupt the terminal environment.

Keybindings is not available on v0.8.0

I've used atom-terminal... but since I updated it to v0.8.0, Terminal does not open with ctrl-shift-t.
I considered conflicting keybindings, but setting->keybindings is not conflicting.
Please modify.
OS: OSX Yosemite
Atom-Version: 0.201.0

Failed to activate the atom-terminal package

[Enter steps to reproduce below:]

Atom Version: 0.194.0 ⚠️ in 1.0 API Preview Mode ⚠️
System: Mac OS X 10.10.2
Thrown From: atom-terminal package, v0.7.0

Stack Trace

Failed to activate the atom-terminal package

At Cannot read property 'command' of undefined

TypeError: Cannot read property 'command' of undefined
  at Object.module.exports.activate (/Users/mohitnarang/.atom/packages/atom-terminal/lib/atom-terminal.coffee:45:28)
  at Package.module.exports.Package.activateNow (/Users/mohitnarang/Downloads/Atom.app/Contents/Resources/app.asar/src/package.js:222:19)
  at /Users/mohitnarang/Downloads/Atom.app/Contents/Resources/app.asar/src/package.js:203:30
  at Package.module.exports.Package.measure (/Users/mohitnarang/Downloads/Atom.app/Contents/Resources/app.asar/src/package.js:147:15)
  at Package.module.exports.Package.activate (/Users/mohitnarang/Downloads/Atom.app/Contents/Resources/app.asar/src/package.js:195:14)
  at PackageManager.module.exports.PackageManager.activatePackage (/Users/mohitnarang/Downloads/Atom.app/Contents/Resources/app.asar/src/package-manager.js:434:21)
  at /Users/mohitnarang/Downloads/Atom.app/Contents/Resources/app.asar/node_modules/settings-view/lib/package-manager.js:234:29
  at exit (/Users/mohitnarang/Downloads/Atom.app/Contents/Resources/app.asar/node_modules/settings-view/lib/package-manager.js:43:16)
  at BufferedProcess.triggerExitCallback (/Users/mohitnarang/Downloads/Atom.app/Contents/Resources/app.asar/src/buffered-process.js:63:47)
  at ChildProcess.<anonymous> (/Users/mohitnarang/Downloads/Atom.app/Contents/Resources/app.asar/src/buffered-process.js:85:18)
  at emitTwo (events.js:87:13)
  at ChildProcess.emit (events.js:169:7)
  at Process.ChildProcess._handle.onexit (child_process.js:1057:12)

Commands

     -0:19.4.0 settings-view:check-for-package-updates (atom-workspace.workspace.scrollbars-visible-when-scrolling.theme-atom-dark-syntax.theme-atom-light-ui)

Config

{
  "core": {
    "themes": [
      "atom-light-ui",
      "atom-dark-syntax"
    ]
  }
}

Installed Packages

# User
atom-terminal, v0.7.0
javascript-snippets, v1.0.0
language-javascript-better, v1.4.0
turbo-javascript, v0.0.8

# Dev
No dev packages

Cannot open terminal in the directory of the selected file

Always go to the root directory

Cannot get terminal to open

alt - shift - T: does nothing
cmd - shift - T:

Console Output
Uncaught TypeError: Cannot read property 'file' of undefined [~]/.atom/packages/atom-terminal/lib/atom-terminal.coffee:62

shortcuts no more working on mac ctrl+shift+t

Uncaught TypeError: Cannot read property 'file' of undefined /Users/vallabh/.atom/packages/atom-terminal/lib/atom-terminal.coffee:62

Allow environment variable config

Currently opening the terminal from atom screws up my npm install process because the NODE_ENV variable is set to production by atom. This makes npm ignore the devDependencies that I need for building my project.

Is there any chance we could get a way to set environment variables before launching the terminal? Or maybe just setting NODE_ENV to something else?

Use the `atom-workspace` tag instead of the `workspace` class.

In keymaps/atom-terminal.cson: Use the atom-workspace tag instead of the workspace class.

Package.getActivationCommands is deprecated.

Use activationCommands instead of activationEvents in your package.json
Commands should be grouped by selector as follows:

  "activationCommands": {
    "atom-workspace": ["foo:bar", "foo:baz"],
    "atom-text-editor": ["foo:quux"]
  }

Package.getActivationCommands (C:\Users\Christopher\AppData\Local\atom\app-0.199.0\resources\app.asar\src\package.js:806:9)
Package.hasActivationCommands (C:\Users\Christopher\AppData\Local\atom\app-0.199.0\resources\app.asar\src\package.js:731:20)
<unknown> (C:\Users\Christopher\AppData\Local\atom\app-0.199.0\resources\app.asar\src\package.js:185:24)
Package.measure (C:\Users\Christopher\AppData\Local\atom\app-0.199.0\resources\app.asar\src\package.js:163:15)
Package.load (C:\Users\Christopher\AppData\Local\atom\app-0.199.0\resources\app.asar\src\package.js:177:12)
PackageManager.loadPackage (C:\Users\Christopher\AppData\Local\atom\app-0.199.0\resources\app.asar\src\package-manager.js:355:14)

Stopped working around Atom 0.180.0

Cannot support open Iterm2 on current file's directory

Cannot support open Iterm2 on current file's directory .
My app setting is:
/Applications/iTerm.app

Would I put something in Args?

Package.getActivationCommands is deprecated.

Use activationCommands instead of activationEvents in your package.json
Commands should be grouped by selector as follows:

  "activationCommands": {
    "atom-workspace": ["foo:bar", "foo:baz"],
    "atom-text-editor": ["foo:quux"]
  }

Package.getActivationCommands (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:790:9)
Package.hasActivationCommands (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:715:20)
<unknown> (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:169:24)
Package.measure (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:147:15)

Open Terminal does not execute

ctrl-shift-t does nothing.

Not working with Linux

It just happens nothing.

TOO MANY terminals spawn

If you disable and re-enable the package, it will apply the keybinding +1 times and will effectively run the command that many times.

Package.activateConfig is deprecated.

Use a config schema instead. See the configuration section
of https://atom.io/docs/latest/hacking-atom-package-word-count and
https://atom.io/docs/api/latest/Config for more details

Package.activateConfig (/usr/share/atom/resources/app.asar/src/package.js:267:11)
PackageDetailView.activate (/usr/share/atom/resources/app.asar/node_modules/settings-view/lib/package-detail-view.js:163:26)
PackageDetailView.initialize (/usr/share/atom/resources/app.asar/node_modules/settings-view/lib/package-detail-view.js:146:12)
PackageDetailView.View (/usr/share/atom/resources/app.asar/node_modules/atom-space-pen-views/node_modules/space-pen/lib/space-pen.js:184:25)

Created from atom 0.198.0

keybindings stopped working.

Applied recent update and keybindings have stopped working. They do open a terminal, but not at the root of the project. I didn't realize how convenient this tool was until it stopped working. Any help would be greatly appreciated. Thank you.

Publish new version

For example 0.6.1 to resolve deprecation warning.

Terminal does not open in directory when "Surpress Directory Argument" is set.

When "Surpress Directory Argument" is set my terminal only ever opens in my home directory, never in the file or project root directory. Disabling "Surpress Directory Argument" resolved the issue. I tested it with with Terminal & iTerm

Opens terminal but not in project directory

First off thanks for creating such a great plugin!

When I use the "terminal open" and the "terminal open in root" commands it just opens my terminal but not in the correct directory.

Failed to activate the minimap package

[Enter steps to reproduce below:]

Manually updated Minimap to version 4.5.0
Failed to activate the minimap package

Atom Version: 0.187.0
System: Unknown Windows Version
Thrown From: atom-terminal package, v0.7.0

Stack Trace

Failed to activate the minimap package

At undefined is not a function

TypeError: undefined is not a function
  at Package.module.exports.Package.activateServices (c:\Users\Martin\AppData\Local\atom\app-0.187.0\resources\app\src\package.js:355:117)
  at Package.module.exports.Package.activateNow (c:\Users\Martin\AppData\Local\atom\app-0.187.0\resources\app\src\package.js:243:16)
  at c:\Users\Martin\AppData\Local\atom\app-0.187.0\resources\app\src\package.js:221:30
  at Package.module.exports.Package.measure (c:\Users\Martin\AppData\Local\atom\app-0.187.0\resources\app\src\package.js:167:15)
  at Package.module.exports.Package.activate (c:\Users\Martin\AppData\Local\atom\app-0.187.0\resources\app\src\package.js:214:14)
  at PackageManager.module.exports.PackageManager.activatePackage (c:\Users\Martin\AppData\Local\atom\app-0.187.0\resources\app\src\package-manager.js:465:21)
  at c:\Users\Martin\AppData\Local\atom\app-0.187.0\resources\app\node_modules\settings-view\lib\package-manager.js:226:29
  at exit (c:\Users\Martin\AppData\Local\atom\app-0.187.0\resources\app\node_modules\settings-view\lib\package-manager.js:43:16)
  at BufferedProcess.triggerExitCallback (c:\Users\Martin\AppData\Local\atom\app-0.187.0\resources\app\src\buffered-process.js:63:47)
  at ChildProcess.<anonymous> (c:\Users\Martin\AppData\Local\atom\app-0.187.0\resources\app\src\buffered-process.js:85:18)
  at ChildProcess.emit (events.js:119:17)
  at Process.ChildProcess._handle.onexit (child_process.js:1072:12)

Commands

  4x -0:52.9 core:move-down (atom-text-editor.editor.vim-mode.command-mode)
  4x -0:51.2 core:move-up (atom-text-editor.editor.vim-mode.command-mode)
  4x -0:50.0 core:move-down (atom-text-editor.editor.vim-mode.command-mode)
  4x -0:48.7 core:move-up (atom-text-editor.editor.vim-mode.command-mode)
  4x -0:47.6 core:move-down (atom-text-editor.editor.vim-mode.command-mode)
  4x -0:46.3 core:move-up (atom-text-editor.editor.vim-mode.command-mode)
  2x -0:45.0 core:move-down (atom-text-editor.editor.vim-mode.command-mode)
  2x -0:44.4 core:move-up (atom-text-editor.editor.vim-mode.command-mode)
  3x -0:43.8 core:move-down (atom-text-editor.editor.vim-mode.command-mode)
  2x -0:42.7 core:move-up (atom-text-editor.editor.vim-mode.command-mode)
  3x -0:42.0 core:move-down (atom-text-editor.editor.vim-mode.command-mode)
  3x -0:41.0 core:move-up (atom-text-editor.editor.vim-mode.command-mode)
  3x -0:32.9 core:move-down (atom-text-editor.editor.vim-mode.command-mode)
  5x -0:32.0 core:move-up (atom-text-editor.editor.vim-mode.command-mode)
     -0:25.4 core:move-left (atom-text-editor.editor.vim-mode.command-mode)
  3x -0:25.4 core:move-up (atom-text-editor.editor.vim-mode.command-mode)

Config

{
  "core": {
    "autoHideMenuBar": true,
    "disabledPackages": [
      "autocomplete"
    ]
  }
}

Installed Packages

# User
linter, v0.12.0
minimap, v4.5.0
script, v2.18.0
vim-mode, v0.37.0

# Dev
No dev packages

Not working on Windows

I have tried in Package Settings:

APP: "C:\Program Files (x86)\Git\bin\sh.exe"
APP: C:\Program Files (x86)\Git\bin\sh.exe
APP: C:/Program Files (x86)/Git/bin/sh.exe
APP: C:/Program\ Files\ \(x86\)/Git/bin/sh.exe
APP: /C/Program\ Files\ \(x86\)/Git/bin/sh.exe

Args: --login -i
Args:

...with no success. Nothing happens when I open a file from -lets say C:\folder\file.ext- and press ctrl+shift+t

http://msysgit.github.io

"Terminal Open" doesn’t exist if you don’t do "Terminal open in root" first

The command Terminal Open requires the command Terminal Open In root to be activated first; if you don’t, the command will not exist even in the Command Palette

karan / atom-terminal Goto Github PK

atom-terminal's People

Stargazers

Watchers

Forkers

atom-terminal's Issues

Stack Trace

Commands

Config

Installed Packages

Stack Trace

Commands

Config

Installed Packages

Stack Trace

Commands

Config

Installed Packages

Stack Trace

Commands

Config

Installed Packages

Stack Trace

Commands

Config

Installed Packages

Stack Trace

Commands

Config

Installed Packages

Recommend Projects

Recommend Topics

Recommend Org