From 6661374a97ebbdc051d17b3aec3a4eb77cf6e5a4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E2=80=9Crahuldkjain=E2=80=9D?= <“rahuldkjain@gmail.com”> Date: Sun, 26 Aug 2018 10:04:30 +0530 Subject: [PATCH] editor_support: Removed emacs coala/coala-eclipse#25 is replaced with coala/coala-eclipse#51. coala/coala-emacs#11 is removed. emacs from the project body is also removed. Fixes https://github.com/coala/projects/issues/652 --- _projects/editor_support.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/_projects/editor_support.md b/_projects/editor_support.md index 715b7a0e..86ef927b 100644 --- a/_projects/editor_support.md +++ b/_projects/editor_support.md @@ -9,8 +9,7 @@ initiatives: - RGSoC issues: - "https://github.com/coala/coala-atom/issues/37" - - "https://github.com/coala/coala-emacs/issues/11" - - "https://github.com/coala/coala-eclipse/issues/25" + - "https://github.com/coala/coala-eclipse/issues/51" - "https://github.com/coala/coala-vim/issues/24" - "https://github.com/coala/coala-gedit/issues/5" - "https://github.com/coala/coala-sublime/issues/4" @@ -47,7 +46,7 @@ For sublime, we'll be using the which is a plugin by itself. For atom, we have the apm testing architecture which does not require a GUI. -For VI and emacs, we will most likely use a testing framework such as +For VI, we will most likely use a testing framework such as [Vimcasts](https://github.com/kana/vim-vspec). For some editors like gedit, running tests is not easy and there is no api to do it. In such cases we would want to use