{"action":"closed","issue":{"url":"https://api.github.com/repos/vhda/verilog_systemverilog.vim/issues/166","repository_url":"https://api.github.com/repos/vhda/verilog_systemverilog.vim","labels_url":"https://api.github.com/repos/vhda/verilog_systemverilog.vim/issues/166/labels{/name}","comments_url":"https://api.github.com/repos/vhda/verilog_systemverilog.vim/issues/166/comments","events_url":"https://api.github.com/repos/vhda/verilog_systemverilog.vim/issues/166/events","html_url":"https://github.com/vhda/verilog_systemverilog.vim/issues/166","id":349695152,"node_id":"MDU6SXNzdWUzNDk2OTUxNTI=","number":166,"title":"Handling of fold test cases when // comment block folding is enabled","user":{"login":"jrudess","id":22512163,"node_id":"MDQ6VXNlcjIyNTEyMTYz","avatar_url":"https://avatars1.githubusercontent.com/u/22512163?v=4","gravatar_id":"","url":"https://api.github.com/users/jrudess","html_url":"https://github.com/jrudess","followers_url":"https://api.github.com/users/jrudess/followers","following_url":"https://api.github.com/users/jrudess/following{/other_user}","gists_url":"https://api.github.com/users/jrudess/gists{/gist_id}","starred_url":"https://api.github.com/users/jrudess/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jrudess/subscriptions","organizations_url":"https://api.github.com/users/jrudess/orgs","repos_url":"https://api.github.com/users/jrudess/repos","events_url":"https://api.github.com/users/jrudess/events{/privacy}","received_events_url":"https://api.github.com/users/jrudess/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2018-08-11T01:26:32Z","updated_at":"2018-10-22T23:00:27Z","closed_at":"2018-10-22T23:00:27Z","author_association":"CONTRIBUTOR","body":"When enabling // comment-block folding, the folding.sv test case is impacted due to usage of // comments on the end of every line.   \r\n\r\nThe new syntax definition  is [here](https://github.com/jrudess/verilog_systemverilog.vim/blob/jrudess/comment_block/plugin/verilog_systemverilog.vim#L120-L124)\r\n\r\nAnd the test-case errors are like this:\r\n\r\n    Error: level=1 level_expected=0 >>>>                                                              //<0><0><0>\r\n    Error: level=1 level_expected=0 >>>>                                                              //<0><0><0>\r\n    Error: level=1 level_expected=0 >>>>                                                              //<0><0><0>\r\n    Error: level=2 level_expected=1 >>>>                                                              //<1><1><1>\r\n    Error: level=2 level_expected=1 >>>>                                                              //<1><1><1>\r\n    Error: level=1 level_expected=0 >>>>                                                              //<0><0><0>\r\n    Error: level=1 level_expected=0 >>>>                                                              //<0><0><0>\r\n    Error: level=1 level_expected=0 >>>>                                                              //<0><0><0>\r\n    Error: level=0 level_expected=1 >>>>assign a = b & c;                                             //<1><1><1>\r\n    Error: level=1 level_expected=0 >>>>                                                              //<0><0><0>\r\n\r\nThe // comments that get folded have fold level increased by 1., causing most of the errors listed.\r\n\r\nThe assign statement line is due to [run_test.vim](https://github.com/vhda/verilog_systemverilog.vim/blob/master/test/run_test.vim#L5-L11) defining a custom `spyglass` syntax to fold the contents of a spyglass disable/enable comment block.   The new // comment-block fold interfers with this custom rule due to having a // comment on the prior line.\r\n\r\nShould the // comment-block folding build in an exception for this spyglass case?"}}
{"actor":{"display_login":"vhda"}}