InsertDate suddenly stopped working #24
Comments
|
Could you post your entire console log after trying to call one or multiple insert date commands? |
|
Thanks. I turned on log commands. As you can see, there are no messages. Nothing happened elsewhere: the panel didn't open, the prompt line didn't open, nothing got inserted. loaded 1104 snippets // i started inserting dates here:
// oops, typed bad sequence, so I looked up the good ones: command: show_overlay {"overlay": "command_palette"} // nothing happened when I typed these: command: insert_date_prompt // preparing to copy console command: drag_select {"event": {"button": 1, "x": 269.0390625, "y": 628.27734375}} |
|
What about the part before |
|
That's the first line in the console log when I open it after starting Sublime fresh. |
|
If I start it fresh and quickly hit control tick, log contains this: theme loaded I'll see if I can catch more by being faster. Log isn't open on restart ... |
|
Got this: theme loaded |
|
I appreciate your looking at this: it's almost certainly not your problem, but I'm hoping you can spot what's happening. I haven't changed any package control stuff in ages, other than removing rspect and ruby after this started happening, to see if that would help. |
|
Do you perhaps have multiple Sublime Text windows? If yes, check all of them since newer windows do not percieve the old console log. Also, it most likely is my fault because I pushed an update this morning that I honestly did not test thouroughly on ST2, for example. |
|
Ah. In fact I had a million windows hiding away somewhere. Doing it again really clean: Still a very empty console ...
|
|
misunderstood instructions about checking old windows, sorry. anyway the above is a clean start from no windows. |
|
I found a bug (2 actually) while testing the most recent release on my ST2 version. You most likely ran into that, although the lack of a proper console print is weird. I could clearly see a traceback of where the exception occured, also coupled with many other debug lines that every ST version prints on every start. Edit: It should look like this: and the traceback would have been somewhere in that, after |
|
ah. perhaps i'm using console wrong. it doesn't auto open when i start ST. anyway maybe you've found the issue. please let me know if/when you push an update. relatedly: what are your thoughts on going to ST3? I've been holding off from fear of a difficult upgrade. |
|
It never auto opens, but one window must contain the above snippet, you just need to crawl all of them to see which window opened first. Update pushed via 1543700, should be available on package control in <1h. I recommend everyone to use ST3, no excuses. It's just so much better. Also, thanks for the report. I should stop being lazy and test my releases on ST2 before pushing them, if I claim to support it. This isn't the first time this has happened. |
|
Thanks. I mistakenly closed them. Sounds like you found it anyway. Thanks again! |
|
If you copy over the User folder you should be good 99% of the time. Unless you developed your own packages, everything should have been placed in the User folder. Package Control will automatically download the packages you had installed because that is saved in |
|
Ah, didn't know that. I'll give it a go soon. Thanks! |
|
works, thanks! |
Today when I started Sublime, InsertDate has stopped working. The console log shows that the key strokes are generating the right calls, insert_date_panel and so on. None of them do anything: the panel never shows up, the prompt window never opens, and the ones with default formats do not insert anything.
I removed InsertDate and installed it with no change. I was getting log errors from ruby and rubytest and have disabled those, so now my python console is clean. It's just that nothing happens.
I hope you'll get this and have some advice. Thanks!
The text was updated successfully, but these errors were encountered: