Jen-Chieh Shen

> `company-keywords` backend is not working after the update. You sure about this? It works on my side. 😕 The newest version of `company-fuzzy` respects the order of your `company-backends`...

Hmm... Since this isn't issue about handling company backend in the different way. Can you open in another issue and so we can discuss over there? Thanks!

@felzix I have added support for async backends in #21. I think this would work with `company-tide`, but not sure how well the performance is.

This issue may no longer be useful since this package should able to handle **ALL** backends after version `1.3.0`. Except some special backends. e.g. `company-yasnippet` since it has a strict...

Hmmm... Interesting, without any configuration with `company-fuzzy` and `company`, does it exactly do what you want? Because it does exactly the same, you describe as default? :/ Just to clarify,...

After using `[email protected]`, most of the platforms work!

Sorry for the inconvenience! The launch issue was caused by saving `custom-file` while starting up Emacs. So I have the fix in: https://github.com/emacs-vs/line-reminder/blob/c0cebef629a98556f5696f78436f4d8428ce8135/line-reminder.el#L417-L420 I reckon the solution may not be...

The diff look like this: (#13) ```diff -(defun line-reminder--custom-file-saving () - "Return t if we are saving `custom-file'." - (and (or print-escape-control-characters inhibit-read-only) - (equal (buffer-file-name) (ignore-errors (expand-file-name custom-file))))) -...

I have tried to remove `~/.emacs.d/elpa/` and install everything from fresh Emacs, but still could not reproduce this issue. Does it affect when using `emacs -q`? Or does it only...

This is good news! I will look into it within a few days! :)