ShellCommands

Troubleshooting.ShellCommands History

Show minor edits - Show changes to markup

November 24, 2009, at 11:26 UTC by Allan Odgaard - Update to reflect r1589’s profile sourcing behavior
Added lines 1-6:
  • Problem:* **Running a command (from a bundle) I get “not found” for a shell command which I know is on my disk.**
  • Solution:* You need to setup `PATH` to contain the directory your shell command is placed in (e.g. `/usr/local/bin`). See the _Search Path_ section of the [manual](http://macromates.com/textmate/manual/shell_commands#search_path).

- - -

Changed lines 9-10 from:
  • Solution:* When executing a shell command TextMate will source your normal bash start files to get a proper `PATH` setup.
to:
  • Solution:* <strike>When executing a shell command TextMate will source your normal bash start files to get a proper `PATH` setup</strike> (_changed in r1589_).
Deleted lines 24-30:

- - -

  • Problem:* **Running a command (from a bundle) I get “not found” for a shell command which I know is on my disk.**
  • Solution:* Please see the note last about [commands using shebang](http://macromates.com/textmate/manual/shell_commands#search_path).
October 25, 2008, at 20:49 UTC by Allan Odgaard - Add info about performance problems with /usr/libexec/path_helper
Added lines 15-21:
  • Problem:* **Running (shell) commands take forever.**
  • Solution:*

Leopard’s version of `/etc/profile` calls `/usr/libexec/path_helper` which has a serious performance problem. The longer the value of the `PATH` value the more severe is this problem.

- - -

Changed line 29 from:

See also: [Templates](Templates)

to:

See also: [Templates](Templates)

May 02, 2008, at 19:11 UTC by Allan Odgaard - Remove (:markdown:)
Deleted lines 0-1:

(:markdown:)

Deleted lines 22-23:

(:markdownend:)

July 19, 2006, at 13:03 UTC by Allan Odgaard -
Changed lines 13-14 from:
    $- = *i* ? && cd screen
to:
    $- = *i* ? && screen
July 07, 2006, at 18:59 UTC by Allan Odgaard -
Added lines 1-26:

(:markdown:)

  • Problem:* **When executing shell commands nothing happens.**
  • Solution:* When executing a shell command TextMate will source your normal bash start files to get a proper `PATH` setup.

This means that if you do something like start e.g. `screen` as part of your regular bash startup then TextMate will be unable to use your shell.

The [files sourced are mentioned here](http://macromates.com/textmate/manual/shell_commands#search_path).

You can restrict execution of things like `screen` to interactive shells by using a line like this:

    $- = *i* ? && cd screen

- - -

  • Problem:* **Running a command (from a bundle) I get “not found” for a shell command which I know is on my disk.**
  • Solution:* Please see the note last about [commands using shebang](http://macromates.com/textmate/manual/shell_commands#search_path).

- - -

See also: [Templates](Templates)

(:markdownend:)