{"action":"created","issue":{"url":"https://api.github.com/repos/mate-desktop/pluma/issues/381","repository_url":"https://api.github.com/repos/mate-desktop/pluma","labels_url":"https://api.github.com/repos/mate-desktop/pluma/issues/381/labels{/name}","comments_url":"https://api.github.com/repos/mate-desktop/pluma/issues/381/comments","events_url":"https://api.github.com/repos/mate-desktop/pluma/issues/381/events","html_url":"https://github.com/mate-desktop/pluma/issues/381","id":381689950,"node_id":"MDU6SXNzdWUzODE2ODk5NTA=","number":381,"title":"C++: Comments not always highlighted correctly","user":{"login":"Friedrich2","id":34623166,"node_id":"MDQ6VXNlcjM0NjIzMTY2","avatar_url":"https://avatars1.githubusercontent.com/u/34623166?v=4","gravatar_id":"","url":"https://api.github.com/users/Friedrich2","html_url":"https://github.com/Friedrich2","followers_url":"https://api.github.com/users/Friedrich2/followers","following_url":"https://api.github.com/users/Friedrich2/following{/other_user}","gists_url":"https://api.github.com/users/Friedrich2/gists{/gist_id}","starred_url":"https://api.github.com/users/Friedrich2/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Friedrich2/subscriptions","organizations_url":"https://api.github.com/users/Friedrich2/orgs","repos_url":"https://api.github.com/users/Friedrich2/repos","events_url":"https://api.github.com/users/Friedrich2/events{/privacy}","received_events_url":"https://api.github.com/users/Friedrich2/received_events","type":"User","site_admin":false},"labels":[{"id":4681942,"node_id":"MDU6TGFiZWw0NjgxOTQy","url":"https://api.github.com/repos/mate-desktop/pluma/labels/confirmed","name":"confirmed","color":"f7c6c7","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":10,"created_at":"2018-11-16T17:20:06Z","updated_at":"2018-12-01T07:04:34Z","closed_at":null,"author_association":"NONE","body":"#### Expected behaviour\r\nC++ comments with // should be ended by the next newline character. (Source: [http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2017/n4640.pdf](a draft (page 23 / 37 of 1589, section 2.7)) Thus, pluma, should highlight all characters between the character sequence // (outside of strings!) and \\n in the same colour.\r\n\r\n#### Actual behaviour\r\npluma does not do this, if the comment contains a \">\" sign (I think that it might have been a \"<\", but only one of the two characters). The coment seems to be ended by this character.\r\n\r\n#### Steps to reproduce the behaviour\r\n1. Make a new file \"test.cpp\" (filename ending is relevant)\r\n2. Open it in pluma.\r\n3. Input \"#include<string> // test < test\" (without the quotes)\r\n\r\nThe first \"test\" word should erroneously have another colour than the second.\r\n\r\n#### MATE general version\r\nUnknown. It was the PC of a friend, with at least one ubuntu core update awaiting installation. Since it was not my PC, I am not able to test it for myself. A (rather short) naive testing seemed to show that the problem is independent of the previous #include<...> directive and of other characters in the comment section.\r\n\r\nI did not test /* ... */ comments.\r\n\r\nI hope that even these tiny pieces of information are sufficient to reproduce this error.\r\n\r\n#### Package version\r\nUnknown.\r\n\r\n#### Linux Distribution\r\n\r\n\r\n#### Link to downstream report of your Distribution\r\n"},"comment":{"url":"https://api.github.com/repos/mate-desktop/pluma/issues/comments/443405625","html_url":"https://github.com/mate-desktop/pluma/issues/381#issuecomment-443405625","issue_url":"https://api.github.com/repos/mate-desktop/pluma/issues/381","id":443405625,"node_id":"MDEyOklzc3VlQ29tbWVudDQ0MzQwNTYyNQ==","user":{"login":"lukefromdc","id":14036792,"node_id":"MDQ6VXNlcjE0MDM2Nzky","avatar_url":"https://avatars1.githubusercontent.com/u/14036792?v=4","gravatar_id":"","url":"https://api.github.com/users/lukefromdc","html_url":"https://github.com/lukefromdc","followers_url":"https://api.github.com/users/lukefromdc/followers","following_url":"https://api.github.com/users/lukefromdc/following{/other_user}","gists_url":"https://api.github.com/users/lukefromdc/gists{/gist_id}","starred_url":"https://api.github.com/users/lukefromdc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lukefromdc/subscriptions","organizations_url":"https://api.github.com/users/lukefromdc/orgs","repos_url":"https://api.github.com/users/lukefromdc/repos","events_url":"https://api.github.com/users/lukefromdc/events{/privacy}","received_events_url":"https://api.github.com/users/lukefromdc/received_events","type":"User","site_admin":false},"created_at":"2018-12-01T07:04:34Z","updated_at":"2018-12-01T07:04:34Z","author_association":"MEMBER","body":"On still further testing, I found that whatever change had been made to GtkSourceView 4 had been backported to  GtkSourceView3, so this issue is now FIXED at least on Debian Unstable. This is true whether or not GtkSourceView4 is even installed, so I can confirm GNOME devs have fixed the problem. \r\n\r\n@Friedrich2 ? can you retest this and see if you are still having this problem? If not we can close this, if so your distro may not have caught up yet."}}
{"actor":{"display_login":"lukefromdc"}}