-
Notifications
You must be signed in to change notification settings - Fork 279
-
Notifications
You must be signed in to change notification settings - Fork 279
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
DocBlockr does not seem to work with latest SublimeText Build (3099) #406
Comments
I have the same issue in Ubuntu 15.10. No errors in the sublime text console. |
This is for all languages? Show a startup log Open the console: Enable command logging Get a log of what is happing when DocBlockr commands should be triggered by enabling some extra logging. In the Console input use the following to enable some extra logging:
Now use docblockr and get a copy of the log. |
I confirm the issue - OS X El Capitan 10.11.3 @gerardroche
I used to |
You're getting:
The jsdocs command is not being called. The log should look like this: On enter.
Or on Tab.
Is auto_indent enabled? In the console input Try uninstalling DocBlockr and reinstalling it? |
@gerardroche |
Same problem for me. |
It seems to be something that has changed in build 3099. If its a bug suddenly exposed in DocBlockr or actually a bug within ST is not clear to me. In fact, reverting ST to build 3095 enables DocBlockr again, just reinstalling does not help. But despite of this workaround it would be of course very nice if this issue could be fixed, I cannot imagine living without DocBlockr ;) |
Here's the changelog for 2 latest dev builds in question (3098, 3099): Build 3099 |
Reverting back to 3096 fixed the issue. |
Works for me on Ubuntu 14.04. Also on fresh install of ST with just package control, and docblockr installed. Ubuntu 14.04
Post your complete startup logs. Be sure to enable command and input logging too e.g. |
Upon further testing it seems that it's somehow related to Sublime projects that were created before update to 3099. I discovered that when I was editing unsaved php file, pre 3099 project -
Freshly created project (same file, same function)
Startup log -
|
@alphanull @FlyingBuddha @thelfensdrfer See #406 (comment) |
Actually, looks like it's only working for functions outside classes, any class methods don't work (PHP) <?php
/**
* [test description]
* @param string $arg [description]
* @return [type] [description]
*/
function test( $arg = '' ) {
}
class MyClass {
/**
*
*/
function test( $args = [] ) {
}
} |
@rinatkhaziev sounds like it could be an issue with ST caches. For those on Ubuntu you can use this script to clean out the cache and optionally sessions and workspaces: https://gist.github.com/gerardroche/6e46cbdf8da19a39f9da |
I've updated the script to work on OSX https://gist.github.com/gerardroche/6e46cbdf8da19a39f9da |
@gerardroche I've ran the script (I'm on OS X 10.11), and it runs successfully but doesn't resolve the problem. I can confirm @rinatkhaziev observation, the plugin works outside of the scope of classes (PHP) |
It's not necessarily if it's in a class. It's when there is whitespace before the opening |
Yes, and whitespace exists in most cases, at least with my code. It might be a bug which is exposed only now, and maybe has something to do with regexp parsing? |
If it's not working in specific php cases then that's another issue. I'm assuming that this entire issue is not just specific to PHP? I'm also not able to reproduce any of these issues yet. |
Nope, here it fails with JS |
@alphanull can you post a complete log. |
Try the new build 3100. Looks like there may have been regex and syntax issues https://www.sublimetext.com/3dev |
Just tried 3100, still the same. |
Build 3102 of SL appears to fix the problem for me. Think it might have something to do with:
|
I can confirm that, 3102 apparently works for me as well. |
Confirm WFM in 3103. |
It's not working for 3114 |
It works well in build 3126. just type |
Not working in build 3126 with docblockr_python |
@mmenschig docblockr_python is not associated with this project. |
Windows 64-bit build 3126 the jsdocs_reparse command does nothing. I just end up with the cursor at the end of the comment block. No reflection of the changes in the function's arguments no fields reactivation. No error in the console. Posts correct command in the console with logging enabled. Any help appreciated. Edit: if there is a [type] or [description] tag in the comment, the reparse command re-activates the fields. But I'd expect the reparse to re-evaluate the code beneath and add/remove the fields to reflect the actual state. -pta- |
@ptaczek Please open a separate issue because your issue sounds like it's specific to jsdocs_reparse. If you can provide a reproducible example it will be easier to address the issue. Give specific steps to reproduce and explain what you expect to happen and what actually happens after completing the steps. |
Me neither sublime test3 3126 on ubuntu 64bits 16.04 system.
useful! |
It was not working for me too, I just fixed by uninstalling and reinstalling it.. thanks! |
Language: Python /** + [enter] results in: Log: |
Title says it all. No idea why this is the case. Autocompletion just stopped working, i.e. typing
/**
and hitting TAB or RETURN afterwards simply does nothing anymore.The text was updated successfully, but these errors were encountered: