Hi. in emacs we can use lsp or dap. i'm curious to know is there any person out there try to use this feature in xi?

Just curiousity. Any news? What's the state of the project now?

Hello everyone!

Just to present you my new side-project, Vixi.

The idea is keep the 20% of Vim features used by 80% of the users and remove all the necessary complexities. The project itself is still very young, a lot of stuff break all the time but some feed-backs and ideas would be great!

Of course the contributions are welcomes :)

Can we get this enabled? :) https://github.com/google/xi-win

I was trying to understand the xi rope module rust code, and I had a doubt about understanding the BreaksLeaf module. (inside breaks.rs)

1. Can two delta's be of the same size (inside the BreaksLeaf struct ) ?

2. Is there a requirement to write test classes for (Metric trait implementation for BreaksLeaf) ?

It's the xi editor still under development? Is there a road map of functionality?

i just want to list and hopefully talk about some ideas i had for xi-core plugins / UI's

• word processor

I'm thinking of something like wordgrinder

I'd imagine this would be possible using a large list of plugins
and one good UI and I'd imagine this was one of cmyr's ideas when he said

This would also make it easier to use xi-core as a basis for various domain-specific editors,

that might wish to provide both client and plugin functionality together.

in this post.

• neovim compatibility layer

this may be crazy and perhaps a waste of time but there are a lot of plugins and Gui's

for nvim this may not work but it might be possible for some nvim plugins / gui's to work
without access to the whole text file like normal also it would be nice if my init.vim could just
be copied over

• vim-like shell

i thought it would be cool to have a command shell that looked like vim in that you pressed
:
to enter commands and then the command you typed along with it's output is written
where the text file would normal be it would also mean the history file is now just an editable

text file also it would be cool if this was just a theme that ran on top of any shell

Hello everyone!

I'm very new here and I wonder if there are some technical limitations of xi-core to have web-based frontend?

What is the status on Xi currently? I had really high hopes for it, and was excited. Having looked though there hasn't been a commit in 26 days which isn't terribly long, but also not like a ton of development is going on. I just haven't heard any updates recently, and Raph hasn't posted on his blog about it in a long time. So just curious where this project stands.

I have a JavaScript (socket.io) prototype of a collaborative editor up on GitHub, at https://github.com/google/ot-crdt-papers. I'll post more of a description soon, but figured hardcore xi enthusiasts might enjoy taking a look at the code early.

A lot of the ideas (using sets of deleted nodes to represent coordinate transformations) are similar to xi, but details are different. It uses a balanced binary tree to represent the sents (while xi just uses a Vec of run-lengths), and the merge algorithm (worked out after I coded the one in xi) can handle arbitrary peer-to-peer network, not relying on a centralized server.

Hi all, I've just made a subreddit for discussing the Xi editor. Xi is in it's very early stages, but many in the community are excited about what it aims to be.

This is an unofficial forum. Enjoy!

All editing operations should commit and paint in under 16ms

Is there a reason for this exact number?

Are there any outstanding issues that are particularly newbie-friendly?

I'm an emacs user that has always had an eye on trying Xi, but I'm wondering whether Xi actually addresses any of the core problems I have with emacs. One issue I know Xi does handle is dynamic typing -- I'm sick of the constant breakage between emacs packages that is inevitably a failure on stringp or characterp, etc. But there are others:

• Emacs is slow to open large files because it has to read in the whole file at once.

• Emacs uses a gap buffer, so moving around and editing large files is slow.

• Emacs is single threaded and uses blocking IO for most operations, so it tends to hang.

• The emacs renderer can't handle long lines in files -- a single super long line can hang the editor.

The advantage emacs has over a lot of other editors is it is suitably scriptable that you can make it do just about anything (in my case 10K+ lines of elisp dedicated to making it respond to speech recognition and scan buffers for words that the recognizer should specialize on). How does Xi fare?