Lime

与文本编辑器 Sublime Text 的开源 API 兼容的替代方案。(Open source API-compatible alternative to the text editor Sublime Text.)

  • 所有者: limetext/lime
  • 平台: Linux, Mac, Raspbian, Windows, Vagrant
  • 許可證: BSD 2-Clause "Simplified" License
  • 分類:
  • 主題:
  • 喜歡:
    0
      比較:

Github星跟蹤圖

lime(石灰)

欢迎来到 Lime 的 meta 项目。

对于后端,请参阅 limetext/lime-backend

目前还有三个前端正在开发中: limetext/lime-qml limetext/lime-termbox limetext/lime-html 一>

状态

前端还没有准备好替换您最喜欢的编辑器,但是后端已经差不多了。

如果你想帮助我们做 Lime,太棒了!我们很乐意接受帮助。请参阅 此处 了解最有用的方式。

该项目尚未准备好日常使用,我们目前缺乏支持用户的资源。 如果您需要帮助构建,运行或以其他方式使用 Lime,请尝试使用 wiki 或您最喜爱的搜索引擎。 如果您仍需要帮助,请考虑在 limetext/support 中打开一个问题。 此项目中打开的与错误或改进无关的问题将被关闭。

推动项目前进需要您的帮助!声明 问题 并提交拉取请求!

什么是 Lime?

我喜欢 Sublime Text 编辑器。 我有 创建 多个 插件 使它更好。但有一件事让我感到害怕,那就是它不是开源的,每晚的夜间发布速度最近几乎不是每晚,即使现在版本3已经在 Beta 中。

在Sublime Text 2 "稳定"版本发布后大约6个月的时间里,几乎没有任何内容传达给用户关于未来会发生什么,也没有在论坛中提供太多支持。 包括我在内的人都想知道产品是否已经死了,我个人想知道ST2中仍存在的所有错误,崩溃和烦恼会发生什么。 这种缺乏沟通对我来说是一个破坏者,我决定不再因为它而在这个产品上花费更多的钱。

由于我尝试过的其他文本编辑器都没有接近我对 Sublime Text 的热爱,所以我决定创建自己的。

-@quarnster

为什么要 API 兼容?

Sublime Text 有一个很好的插件体系结构和为它创建的 大量现有插件。我们希望用户能够利用这些扩展,而无需开发人员支持多种 API。

目标

请参阅 wiki 中的 Goals 页。

构建说明

请参阅 wiki 中的 Building 页。

贡献

想帮助建立 Lime?真棒!我们总是很高兴收到请求,并尽我们所能尽快处理它们。不知道这个错字是否值得一拉请求?做吧!我们将不胜感激。

如果第一次尝试不接受拉取请求,请不要气馁!如果实施存在问题,希望您收到有关改进内容的反馈。

哪里是开始的好地方? Wiki中的 Contributing 页面有一些建议。认为 wiki 需要澄清,或缺少一些东西?继续并进行更改。

许可证

该项目的许可证是 2-clause BSD license

概覽

名稱與所有者limetext/lime
主編程語言
編程語言 (語言數: 0)
平台Linux, Mac, Raspbian, Windows, Vagrant
許可證BSD 2-Clause "Simplified" License
發布數0
創建於2012-10-03 18:10:02
推送於2021-01-02 13:10:47
最后一次提交2021-01-02 16:40:46
星數15.3k
關注者數755
派生數1.1k
提交數1.1k
已啟用問題?
問題數403
打開的問題數22
拉請求數160
打開的拉請求數0
關閉的拉請求數28
已啟用Wiki?
已存檔?
是復刻?
已鎖定?
是鏡像?
是私有?

Bountysource Bounties
Bountysource Raised

Gitter

lime

Welcome to the meta project for Lime.

For the backend, please see limetext/lime-backend.

There are also three frontends currently in development: limetext/lime-qml, limetext/lime-termbox, and limetext/lime-html.

Status

The frontends are not ready to replace your favourite editor, but the backend isn't too far away.

If you want to help us build Lime, great! We'd love your help. See here for how you could be most useful.

This project is not yet ready for daily use, and we currently lack the resources to support users. If you need help building, running, or otherwise using Lime, try the wiki or your favorite search engine. If you still need help, consider opening an issue in limetext/support. Issues opened in this project that don't relate to bugs or improvements will be closed.

Your help is needed to move the project forward! Claim an issue and submit a pull request!

What is Lime?

Screenshot taken Aug 27 2014

I love the Sublime Text editor. I have created several plugins to make it even better. One thing that scares me though is that it is not open sourced and the pace of nightly releases have recently been anything but nightly, even now that version 3 is out in Beta.

There was a period of about 6 months after the Sublime Text 2 "stable" version was released where pretty much nothing at all was communicated to the users about what to expect in the future, nor was there much support offered in the forums. People including myself were wondering if the product was dead and I personally wondered what would happen to all the bugs, crashes and annoyances that still existed in ST2. This lack of communication is a dealbreaker to me and I decided that I will not spend any more money on that product because of it.

As none of the other text editors I've tried come close to the love I had for Sublime Text, I decided I had to create my own.

-- @quarnster

Why API compatibility?

Sublime Text has a good plugin architecture and a large collection of existing plugins created for it. We want users to be able to take advantage of these extensions without requiring developers to support multiple APIs.

Goals

Please refer to the Goals page in the wiki.

Build instructions

Please refer to the Building page in the wiki.

Contributing

Want to help build Lime? Awesome! We are always thrilled to receive pull requests, and do our best to process them as fast as possible. Not sure if that typo is worth a pull request? Do it! We will appreciate it.

If your pull request is not accepted on the first try, don't be discouraged! If there's a problem with the implementation, hopefully you received feedback on what to improve.

Where is a good place to start? The Contributing page in the wiki has some suggestions. Think the wiki needs clarifying, or something is missing? Go ahead and make the change.

Guidelines for making contributions can be found in CONTRIBUTING.md.

Want to chat? Find us on Gitter.

License

The license of the project is the 2-clause BSD license.

去到頂部