bobthecow / coda-cli Goto Github PK

View Code? Open in Web Editor NEW

53.0 6.0 4.0 124 KB

Makes Panic's Coda a first-class *nix citizen

Home Page: http://justinhileman.info/coda-cli/

License: MIT License

Python 100.00%

coda-cli's Introduction

coda-cli -- Shell integration for Coda

http://justinhileman.info/coda-cli

`coda` makes Panic's Coda a first-class *nix citizen

This tool provides shell integration for Coda. You can now open files and directories from a terminal:

coda foo.html
coda foo.html bar.css
coda ./

If foo.html or bar.css doesn't exist, coda will create it automatically for you.

You can also edit a file and wait for it to close (-w or --wait). This is really important if you plan on making coda your default $EDITOR. Now you can use Coda for writing Git or SVN commit messages. Simply add this line to your .bash_profile or .bashrc or .zshrc:

export EDITOR='coda -w'

In addition to knowing how to wait, coda plays nice with pipes. You can use it just like any other POSIX utility... Invoke it from the command line and pass the output from any command to Coda, or from Coda to another command. Try a couple of these:

echo 'foo' | coda
echo 'bar' | coda >> out.txt
coda >> somefile.html
find . -name "*.css" | xargs coda
coda < config.yaml > config_new.yaml

Note that piping output from coda implies --wait.

Installation

Make sure coda is executable and somewhere in your $PATH. The easiest way to do that is with Homebrew ...

brew update
brew install coda-cli

Or you can strike out on your own:

mkdir -p /usr/local/bin
curl https://raw.github.com/bobthecow/coda-cli/master/coda > /usr/local/bin/coda
chmod 777 /usr/local/bin/coda

Usage

coda --help

License

Copyright 2011 Justin Hileman
Distributed under the MIT License

coda-cli's People

Contributors

Stargazers

Watchers

Forkers

brutuscat anybucket rosenhagen leighvl

coda-cli's Issues

coda -w not waiting

I did configure 'coda -w' as my EDITOR in .profile and checked with 'echo $EDITOR'.
Now if I git commit (or manually coda -w somefile) it does not work (i.e. coda opens, but Terminal is not waiting).

I installed coda 1.0.3 via brew

Add Coda project

This is a feature idea.

It would be great if you could add project to coda using the command line. An example of this functionality can ben found in git tower, by using "gittower add ." you can add the current directory as a project in git tower.

rmate-like ssh tunneling?

I know this is a LONG shot, but if you could pull off rmate-like ssh tunneling it would be amazing!

Git integration with coda -w

I'm having some trouble with the git integration.
The commit message file opens up in coda but it doesn't save it correctly to the stream.

output

$ git commit
Traceback (most recent call last):
  File "/usr/local/bin/coda", line 200, in <module>
    while list(set(files) & set(open_tabs())):
TypeError: 'NoneType' object is not iterable
error: There was a problem with the editor 'coda -w'.
Please supply the message using either -m or -F option.

--new-window option not working in Coda 2

Running the command below doesn't open a new window in Coda 2. Instead, the file opens as a tab in an already open Coda window.

$ coda -n file.txt

-n switch doesn't work?

I can't get -n or --new-window to work at all.

Add site-aware magick

--line flag?

Would it be possible to add a --line flag? I'm a front-end developer, and I find myself doing this frequently:

Inspect Element in Chrome
Identify style sheet and line number that I'd like to change
Open style sheet using, for example, coda layout.css
Return to Chrome because I've forgotten the line number
⌘⇥ to Coda
⇧⌘L
Enter line number

It'd be awesome to be able to instead do this:

Inspect Element in Chrome
Identify style sheet and line number that I'd like to change
Open style sheet at the correct position using coda layout.css --line 231

I've no idea, though, whether Coda exposes this functionality.

--new-window has timing issues

I open a file with coda -n test.txt from another desktop than the one running Coda (and Coda is fixed to its own desktop, so all Coda windows open there). What happens is that Coda opens a new window, but the document is opened in the "old" window. If I open the file from the same desktop as Coda, it works fine.