IDEs Support (IntelliJ Platform) | JetBrains

Peter Gromov

活动总数 2258
最后的活动 2023年05月09日 12:44
成员加入日期 2008年07月25日 18:59
关注 0 名用户
关注者数 1 名用户
投票数 0
订阅数 739

创建于 2014年05月07日 13:14

Is your lexer obeying the contract described in Lexer#start javadoc? It should only return 0 from getState on the tokens that it's capable to restart from.
- 0 票
创建于 2014年05月07日 13:13

The reasons for that ordering are motivated by internal architectural needs and complicated. It depends on the reason that PSI event was fired, which is unclear to me. A stacktrace could shed some ...
- 0 票
创建于 2014年05月07日 16:00

To get a stacktrace, you can always do new Throwable().printStackTrace(), or pause on a breakpoint and invoke "Get thread dump" action.That said, I'm not that interested in the stacktrace :) If you...
- 0 票
创建于 2014年04月28日 16:27

Judging by the stack trace, there's no fixed order. One of projectClosed listeners files fileClosed, so it really depends on the order of listeners. Sorry.To dispose something on project closing, y...
- 0 票
创建于 2014年04月28日 18:29

It doesn't look like an easy/intuitive way. Besides, fileClosed and projectClosed should both be fired on EDT, so synchronization shouldn't be of any help here.
- 0 票
创建于 2014年04月28日 18:50

They should be called from EDT only.
- 0 票
创建于 2014年04月27日 14:03

Congratulations!
- 0 票
创建于 2014年07月23日 15:58

Do you have a custom insert handler in your items? It could be removing the spaces, or invoking reformat which does this.I'd suggest to put a breakpoint to DocumentImpl.changedUpdate, then you'll s...
- 0 票
创建于 2014年07月23日 19:07

When debugging, you can also see the stack trace of the event. Please provide it. "Get Thread Dump" debugger action might be useful for that purpose.
- 0 票
创建于 2014年07月24日 21:20

It still looks like "* " is included into the prefix that a particular lookup item was matched against.Yes, if you share your plugin project, it'll definitely make the investigation easier.
- 0 票