document why some modes are disabled from using beacon

[errge]

Hey,

I know about beacon-dont-blink-major-modes, however I have a couple of questions.

First of all, what is the first t at the beginning of the default value?

Second: would it be possible to properly document all the exceptions, so if circumstances change in the Emacs ecosystem, we can retest previous incompatibilities?

I think some code comments would be enough. I'm happy to prepare the PR, so far I did some git research and know about the following:

• magit: issues with the buffer being filled asynchronously by magit,
• inf-ruby: timing races can cause blink occur left to the cursor,
• gnus: ?
• mu4e: ?

Do you remember the reason for gnus and mu4e? And for the initial t at the beginning of the list?

[Malabarba]

First of all, what is the first t at the beginning of the default value?

It's nothing. It's actually in there as a workaround to make the automatic indentation a little prettier. :-)

Do you remember the reason for gnus and mu4e? And for the initial t at the beginning of the list?

I added those myself a while back, but I haven't used either packages recently. So I'm working off memory here. I think it was the same problem as magit. The buffers where populated assynchronously, and that could lead to weird behaviors when you first open the buffer.