-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FR] Show 'position/size' in the editor statusbar #234
base: master
Are you sure you want to change the base?
Conversation
126 additional bytes in the dictionary
I think the cart build failing is the easiest way to detect a too-large dictionary. That said, I've mentioned before that the V editor will no longer fit on the cart with more than a few changes. Maybe the editor should be a stripped down version for the cart with a full-featured editor on the disk? |
Is the editor stored as text on the cart? Compression could be used to fit more in |
@Kroc no, the editor is compiled into the dictionary of the cart. |
I like this, maybe especially the options "line/lines" or "100%". At this moment though, it seems we are tight on space, so maybe this should wait until more space is freed up? |
Fine with me! 😁 |
More space is freed up :) |
I'm tied up in other things and not really working on durexforth now :-/ |
Soo... finally I got the time and peace of mind to try this out now. I'm happy to see it works as expected, even if some time passed. I find that byte position + file size is not that helpful. Would it be possible to switch to line and column, just like default Vim ruler? Are you interested in working on this further, by the way? |
Submitted for your consideration, 126 additional bytes in the dictionary adding a display bottom right in the editor, showing the current cursor position and the total length of the file (minus the prg header, I guess).
Alternatives:
x/100% (size)
line, column
(not that useful without the size)All these will cost more bytes, of course. I measured the size by comparing
here
with and without the addition. How can I tell how many bytes are left free, other than watching the cart build fail? xDhere $801 -
perhaps, or do I have to account for some more bytes?