-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Yet another "runtime error: index out of range" #1250
Comments
Here is another one, on OSX.
|
I'm also having this error on macOS. |
Have you confirmed that you have no illegal/invalid characters in the file which you are trying to save? |
What are illegal/invalid characters in this case? My file was just plaintext, including scandinavian letters |
I seriously hope that you understand/agree that 'illegal/invalid' characters should be handled without crashing. A quick glance at search.go:125, it's easy to see that you do not bounds check 'end.Y'. Although this means you also have a bug causing this function to be called with out of range parameters, the function itself should check and error accordingly. |
I--or rather, a friend of mine--have also received this error. Are there any fixes or progress on it?
|
I have not been able to reproduce this error. However I believe this error is caused by some buggy interaction between gopher lua and the utf8 parser. I think this will be fixed when I get around to continuing the next version of micro which will involve rewriting the default plugins to use the go stdlib for handling utf8. |
Curious.
And here's my system information. I have not experienced this problem. At least... not yet.
|
I got the error now too. (Or something kinda like it, I guess?)
|
Okay, this is more like the error I'm "supposed to" get. Seems to happen when I'm in the editor for a particularly long time.
|
Not sure how to reproduce, but I'm getting this as well.
Edit: also seems to happen mostly after having the file open for long periods of time. |
I get this, is that related ?
It comes every 10-20 min of writing (markdown in my case). @zyedidia mentions Lua above. Can I uninstall plugin autoclose ? What does it do ? |
To turn autoclose plugin off.
|
The code from the refactor that I have been working on is now more or less ready to be merged. These changes make some breaking changes, notably with regards to the plugin interface. Once a lot more documentation has been written, I will release this code as micro 2.0. There are a lot of new features, and in the coming days I will try to go through the open issues to see exactly which ones are addressed by the new features, and write lots more documentation regarding what has been implemented. Some highlights include: * Simple autocompletion. * Autocompletion (tab by default) will do a simple "buffer completion" which will autocomplete according to words used elsewhere in the buffer. In the future plugin support could be added along with support for interfacing with language-specific autocompletion tools. * Automatic backups. * Backup files are stored in `~/.config/micro/backups` for every open buffer and are saved roughly every 8 seconds if the buffer is being modified. Backups are removed when the buffer is closed, but if micro or the system crashes, any unsaved changes can be recovered by re-opening the file (micro will auto- recover) or by manually viewing the backup in the `~/.config/micro/backups` directory. * Configurable statusline. * Configurable linter plugin. * Resizeable splits. * Complete re-organization of the code to support better go modules and maintain a better directory structure. * Better plugin interface with better access to the Go standard library and internal Micro functions (lots of documentation still needs to be written). * Documentation still needs to be written, but in the meantime please see the default plugins as examples as they have been converted from their old versions to be compatible with the new interface. * Buffer synchronization when the same file is opened multiple times. * Keybindings and mouse support in the command bar. * Support for non-utf8 encodings. * General QoL improvements and bug fixes. * Notably I believe the autoclose plugin crash issue is fixed. * No more plugin manager. * Plugin installation will now be performed manually by git cloning into the `~/.config/micro/plug` directory. This may not be a highlight for some but I believe it is much simpler, and there is no need to have a heavyweight dependency manager. Perhaps in the future, a good command-line tool can be made to manage plugins if people would find it useful. * Other features that I have forgotten. Next I plan to write up more documentation for all the new features, and make a "release candidate" for micro 2.0. I will also be working to fix any bugs that come up (hopefully not too many, but this is a big change and bound to have some issues). After release I hope to focus more on optimization (for example loading syntax files is currently somewhat inefficient, and the bottleneck for startup time #1427). Sorry for not being so active recently, but I hope merging this big change can help me get back to more regular development. Thanks to everyone for using micro and for giving feedback and engaging with development online (even if I don't always respond). Merry Christmas! Issues that are fixed/affected by this change: Ref #1419 (configurable statusline) Ref #1413 (cursor behaves better) Ref #1401 (softwrap problems) Ref #1383 (better save with sudo) Ref #1424 (better save with sudo) Ref #1382 (go modules) Ref #1381 (install plugins from command line) Ref #1357 (sorting -- textfilter) Ref #1351 (custom linting) Ref #1350 (sudo problem might be fixed) Ref #1298 (readonly option) Ref #1250 (autoclose bug) Ref #1239 (go modules) Ref #813 (autoclose bug) Ref #812 (cursor sync across same buffers) Ref #770 (resizeable panes) Ref #635 (keybindings in infobar) Ref #596 (disable builtin plugins) Ref #550 (backups) Ref #174 (autocompletion)
This issue was caused by the autoclose plugin and should be fixed now. |
When I was editing a Tcl script today and hit
Ctrl+S
to save it, I got the following error:After hitting
Enter
got me back to my script, I hitCrtl+S
again and got:I've been using micro for about two weeks to work on that script now and this is the first time that error has occured.
Version: 1.4.1
Commit hash: 1856891
OS: Linux
Terminal: urxvt
The text was updated successfully, but these errors were encountered: