dmadisetti/airlatex.vim

Overleaf / ShareLatex in Vim

airlatex.vim's Issues

Package (nix)

Package so that you can just call airlatex, opposed to having to launch

Need sqlite3 + pip deps

Option to Ignore comments

Sometimes I respond to a comment, but don't resolve (for discussion). It'd be nice to have an "ignore" option

Github sync

GET https://www.overleaf.com/project/<project>/github-sync/status

reponse: {"enabled":true,"merge_status":"success","repo":"dmadisetti/<repo>","unmerged_branch":null}

---

GET https://www.overleaf.com/project/<project>/github-sync/commits/unmerged

response: {"diverged":false,"commits":[]}

---

Not sure if needed?

PUT https://www.overleaf.com/editingSession/<project>

---

Could skip to just this:

POST https://www.overleaf.com/project/<project>/github-sync/merge

payload: {message: "A commit!"}

Print out current users on page

We show the cursors, but it would be nice to know WHO is on the page. I think we can do this with echo, no need for more buffers

Add some e2e CI

overleaf provides some docker containers. With 5547262 I was able to test that airlatex works with these containers.

TrackChanges works, but comments do not since they require a totally difference service. No clear way of turning this one, but could still do tests for:

interaction:

• - connect to project
• - disconnect from project
• - open up multiple files

Mutation

• - addition
• - remove
• - replace lines
• - w/ track changes

Find appropo sync rate.

I think the heart beat is too slow for actual collaborative working. We need to figure out a reasonable rate, otherwise it crashes. Need to have someone (@adyotag?) edit a doc at the same time to help find a better rate.

Syntax for splash page

Kinda boring right now, but whatever

Comment buffer

Thought process:

user                           time
the comment and such and such
-----------------------------------
other user                 time
another reply and such and such
----------------------------------



(intentionally blank space)

Entering insert mode in a section posted by you, allows you to edit
Entering insert mode in the blank section is crafting a response. submission on save
dd resolves the comment
removing all content of a comment deletes the comment

visual mode for comment creation

Implement Fenwick Tree

Get fenwick tree working to match the naive accumulator API:

https://github.com/dmadisetti/AirLatex.vim/blob/master/rplugin/python3/airlatex/lib/range.py

Not sure how much of a difference this optimization will have, but in theory, is the better data structure.

Refresh

Leave doc and rejoin to refresh all comments and buffer in case things get too far out of wack.

Update comment intervals on edit

Using interval tree. Currently not updating interval, so highlights will get out of sync with buffer if too much editing occurs.

There's a grammatical error in the README so I stopped reading

"It's a little like hacking yourself, and a nice reminder that any program you are run on your machine can do this and more. Here's the relevant code if you are interested."

that and I want to spam an issue for attention lol

Resolve / show track changes.

Currently not implemented.

But if others rely on track changes, then this is important enough.

Double highlight for overlapping comment intervals

Fix intervals first, but this would be nice

Firefox plugin for PDF sync

I mean. May as well use this properly. You can do editor/ PDF split mode, but they use browser channels to communicate. AirLatex -> socket -> FireFox Plugin -> PDF mode will allow this functionality from vim. Have partial prototype

Performace (Slow when editing for more than > 2 minutes)

Memory leak maybe? Pretty much only blocker from being usable to me.

Jump to next comment

Should be pretty easy. Scan interval tree and move cursor

More granular undo?

Undo is not great currently

Solve edge case where anotheruser edits something that changes the last line, and then the user makes a change

Naive accumulator gets out out sync with the buffer for last line changes sometimes. I think most the edge cases are solved, but this particular edge case of another user making changes that influences the end, and then trying to change the end yourself, is still broken

To edgecase for me to even care anymore really

Resolve + test comments moving

A refresh fixes this, so no big deal- but something is def up and comments are drifting during edits.

Deeper Cleanup

• Buffer Base class
• Remove nvim from session project handler
• Doc strings
• Change format to f strings
• Use objects instead of dictionary responses
• project manager requests

Comment refresh issues

resolve and reopen need to refresh
new comments on the thread need to refresh
new comment should show correctly

Also issue if you directly comment on something without opening the comment buffer first, it might be full of junk.
I think this is actually a race condition

Allow for track changes

Just send to the server track changes. No point displaying them