limetext / lime Goto Github PK

View Code? Open in Web Editor NEW

15.3K 15.3K 1.1K 2.08 MB

Open source API-compatible alternative to the text editor Sublime Text

Home Page: http://limetext.github.io

License: BSD 2-Clause "Simplified" License

editor golang text-editor

lime's People

Contributors

Stargazers

Watchers

Forkers

xeno-by richardfontana prongs dusteye grantsp intfrr wojons tompivoq jaseg jimlawton barretron kavern1128 piaoger muzinian derekchiang zaopuppy rantonov tiagobarreto phytax yux0 changguanghua johngummadi rumel plainspace kusl thla tinkerwell carleeto zeezhang bruce2008github cswanghan xyangfd dolfly oulan haisee matrixchan devnetfx lzy7199 singleton7 hardpass zbzcyeq imtech txdyc mrxiaoz xiaozhen1900 supercrawler nicedreamer catufunwa chid dsymquen vinkesh childebao vdt zhao-bookmarks rasyidm lijinchao sebastiani zlx sharehub ragsagar choka leon1108 allensh929 mvc4 webcoding pshrinivas derekparker iomato dading lucasroesler alfredzh alexdeoliveira davidnuon z3i icytaha entropin bradparks terrancy dengmin akers wulin2008 xwzhang001 setsession zhutoulwz wavesun imloama lqcys flyfire fashtimedotcom gregschulberg lankyworm rjbj dyxushuai isu007 sxhao lnsoso 2mauis zhailei proximamonkey cheloizaguirre

lime's Issues

The api's should be documented. Much of the backend is stable (won't change) due to Sublime Text compatibility so someone with experience working with Sublime Text plugins should have a good idea of what the api accomplishes and be able to document the expectations.

Command: paste

Create milestones and issues for the incomplete goals

The incomplete goals in the readme file are an ideal case for creating milestones and related issues.

I have noticed since opening the issues section in the repo you've started to organize tasks with issues and I have always thought you have a Goals section, because you have closed the issues and milestones one.

Command: focus_neighbouring_group

Command: show_overlay

Command: lower_case

Command: find_next

Command: open_file

Command: next_view

Command: copy

Command: slurp_find_string

Extend test suite

Go 1.2 supports code coverage reporting so it's easy to see exactly which code is covered by tests and which isn't.

Command: focus_group

Command: toggle_minimap

Finish "backend/render"

This should contain a common code path for frontends to deal with functionality related to rendering the editor.

Command: new_pane

Command: redo_or_repeat

Command: swap_with_mark

Command: insert_snippet

Command: yank

Command: select_all

Command: set_file_type

Document how to create new commands

Inspiration can be found in backend/commands. This should also describe how to use sublime.log_commands(True) in Sublime Text to get the exact arguments used to invoke the command in the original editor.

Command: show_panel

Command: new_file

Command: save

Command: toggle_record_macro

Command: expand_selection

Command: wrap_block

Command: nop

Command: context_menu

Command: auto_complete

Command: indent

Command: join_lines

Command: close_others_by_index

Command: toggle_tabs

Command: build

Command: cancel

Configure drone.io and/or other services for continuous integration

BTW, all issues that are not "assigned" are up for grabs, please chime in and claim them if you want to work on something!

Document pre commit hook in CONTRIBUTING.md

Mine's currently cd build && . ~/.bash_profile && go run build.go which obviously is specific to my system.

HTML/javascript frontend

Just because we can

Unable to `go get` lime dependencies

Following all the build instructions I have encountered the following error:

$ go get code.google.com/p/log4go github.com/quarnster/parser github.com/quarnster/completion github.com/quarnster/util github.com/howeyc/fsnotify
~/.go/src/github.com/quarnster/completion/clang/clang.go:6:2: no Go source files in ~/.go/src/github.com/quarnster/completion/clang/parser
can't load package: package github.com/quarnster/util: no Go source files in ~/.go/src/github.com/quarnster/util

(Replaced home dir with ~.)

Sorry to report troubles with the build as an issue with so thorough build instructions, but people able to build it is essential to more people contributing to the project.