runtime error: index out of range #565
Comments
|
I think this is a duplicate of #457 |
|
I was editing a .txt file without any syntax highlighting, if that makes any difference. |
|
Can you reproduce the error? and which plugins do you have installed? ( |
|
Did you have autoclose disabled or enabled? |
|
I'm not sure what happened. I didn't change the default plugins.
4 The following plugins are currently installed:
5
6 ftoptions (0.0.0-unknown)
7 linter (0.0.0-unknown)
8 autoclose (0.0.0-unknown)
9 ----------------
10 Filename:
- http://www.linkedin.com/in/pjbrunet
…On Sun, Feb 26, 2017 at 5:48 AM, Nicolai Søborg ***@***.***> wrote:
Can you reproduce the error? and which plugins do you have installed? (ctrl
+ e + plugin list)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#565 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ACYuLeh9JZMq-U85rY3tRowHCfMBJvGoks5rgWaBgaJpZM4MMQtR>
.
|
|
"autoclose": true
- http://www.linkedin.com/in/pjbrunet
…On Sun, Feb 26, 2017 at 8:29 AM, Zachary Yedidia ***@***.***> wrote:
Did you have autoclose disabled or enabled?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#565 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ACYuLfi-XLrUmYqdONir-uFMQF13g_rQks5rgYw8gaJpZM4MMQtR>
.
|
|
@pjbrunet This issue is intermittent for many and we're still investigating the cause. Zyedidia thinks it's related to the autoclose plugin, but we have yet to find any hard evidence as to the cause that I know of. Please try disabling autoclose by using |
|
Micro crashed randomly with this, seems similar Version: 1.3.5-dev.22 |
|
I seem to commonly get this issue if I have one file open for a long time, after lots of saves. I don't recall it happening when making quick edits. |
|
Been running into this error quite a bit lately. And I mean more than once an hour while working on a project. Version: 1.4.1-dev.35 |
|
Since #457 seems distinct from all the other open Using 1.4.0. It had been working fine, then splat! No data loss thankfully. I started using micro this week. This was the first time I ran into this bug. Every time I tried to reopen after the bug: when I tried to type, a bug splat on the first character entry or so. It saved this freshly pressed character though. In the same shell, I switched to nano and finished my work. Some more info.. Even before I closed the first shell: I opened a new shell and used it to run micro on the same file. This worked. Considering the contrast of working states between micro and nano in the same environment, the successful run of micro in a fresh environment, and Although there's since been commits to relevant files and they may have fixed this issue, it's not obvious to me those commits would've fix the issue. However, assuming there's no data loss from this bug for anybody, if you're going to release 1.4.1 in a few months, I'd recommend instead seeing if the newer version with updated dependencies even run into this problem. Stack trace |
Description of the problem or steps to reproduce
runtime error: index out of range
stack traceback:
[G]: in function 'sub'
:7: in function 'charAt'
:23: in main chunk
[G]: ?
Press enter to continue
Then I pressed ^C accidentally, because I was trying to copy the error, LOL. Luckily I only lost one sentence. No idea what happened.
Specifications
You can use
micro -versionto get the commit hash.Version: 1.1.4-78
Commit hash: 5dc8fe4
Compiled on February 10, 2017
Commit hash:
OS: Manjaro
Terminal: Terminology
The text was updated successfully, but these errors were encountered: