Zhenhui Xie

> everything listed as being stored in coc.source.bibtex is now in coc.preferences.bibtex Yes, that's it. I have not fully tested other keys (e.g. `list.*`) but they seem unchanged. Thank you...

Thank you for your update! I'm sorry for that I have provided the wrong information related to the config location change. Most plugins actually stored their configurations [in the object...

Here is a cleaner workaround to have event-based subscription, though it needs another graphql server instance to expose the subscription API. See [heyrict/hasura-trigger-subscription-server](https://github.com/heyrict/hasura-trigger-subscription-server).

@0x777 Well, I like hasura's performant design and don't think bundling another layer inside to maintain state is a good choice. However, there are still use cases for event based...

@bkniffler I am not sure if I have understand `live-queries + optimistic response` properly. You CAN use live queries with optimistic response. If you are using ```javascript.jsx {this.renderLiveQuery} ``` Then...

A quick alternative is to create multiple configs and point `STARSHIP_CONFIG` environment variable to the config.

@johnletey What do you think about altering the `style` option instead of using a new key, so that `style` can accept - A style string "bold dimmed red" - An...

@johnletey I mean this ```toml # ~/.config/starship.toml [hostname] ssh_only = false prefix = "⟪" suffix = "⟫" style = [ # Set style to "bold dimmed red" if $HOSTNAME ==...

@johnletey what do you think about reducing the level of nested objects? I think this should look better, but we won't able to implement a more complex match pattern (say...

@johnletey Another use case as I mentioned in #616: Users may want to change styles based on - If the environment variable equals to some value - If the environment...