Important
Lilly is in a pre-alpha state, and only suitable for use by developers. This editor is technically usable, it is the exclusive editor used to work on itself, however many features are missing, and there is no guarantee of stable features or a lack of bugs. Features, bug fixes and issues are welcome.
Our project is focused on the development of a text editor that serves as a practical alternative to Vim and Neovim. The primary aim is to provide users with essential features, eliminating the need to navigate a complex ecosystem of Lua plugins. This approach is intended to be welcoming to users of all experience levels.
-
Install the clockwork build tool by executing this command:
v run ./install-clockwork.vsh -
Build lilly by executing:
clockwork buildor build and run withclockwork run
You can see what other tasks are available to run with clockwork --tasks
We have set out to create an editor that encompasses the fundamental capabilities expected by users, rendering it a compelling choice as a Vim/Neovim alternative. Our emphasis is on streamlining the editing process without the necessity of configuring numerous plugins – our core features aim to fulfill these needs.
The intricacies of Lua plugins can be daunting for newcomers and even pose a management challenge for seasoned users. Our editor simplifies the user experience by removing the requirement for extensive plugin management. It offers an approachable and intuitive platform, eliminating the complexities that often accompany plugin management.
Our editor is optimized to offer improved performance, particularly when handling extensive files. It is engineered for speed and responsiveness, designed to enhance your editing efficiency.
We've crafted the editor to deliver a VIM-like experience, preserving the functionalities that VIM users appreciate. The difference lies in the absence of reliance on a multifaceted ecosystem – our editor consolidates these features within a unified framework.
Transition to our text editor to explore an alternative that is rooted in functionality, accessibility, and performance.
Not a problem, Neovim/VIM are fantastic existing projects and are freely available for you to use today.
On macOS we get this output from running:
leaks --atExit -- ./lilly .
lilly(53176) MallocStackLogging: could not tag MSL-related memory as no_footprint, so those pages will be included in process footprint - (null)
lilly(53176) MallocStackLogging: recording malloc and VM allocation stacks using lite mode
Process 53176 is not debuggable. Due to security restrictions, leaks can only show or save contents of readonly memory of restricted processes.
Process: lilly [53176]
Path: /Users/USER/*/lilly
Load Address: 0x10294c000
Identifier: lilly
Version: 0
Code Type: ARM64
Platform: macOS
Parent Process: leaks [53172]
Date/Time: 2024-12-05 11:07:02.409 +0000
Launch Time: 2024-12-05 11:06:46.429 +0000
OS Version: macOS 13.2.1 (22D68)
Report Version: 7
Analysis Tool: /usr/bin/leaks
Physical footprint: 4513K
Physical footprint (peak): 4529K
Idle exit: untracked
----
leaks Report Version: 4.0, multi-line stacks
Process 53176: 226 nodes malloced for 22 KB
Process 53176: 0 leaks for 0 total leaked bytes.
Look at that. 0 memory leaks.
(experimental GUI render target)
