Nikolaos Bezirgiannis

`:persistent` also does not work for me with the `notifications` style backend. After a bit of debugging it seems that the `:persistent` is never passed to the `alert-notifications-notify` notifier function

Custom styles using `alert-define-style` are also unaware of the `:persistent` kwarg. Example: ```lisp (alert-define-style 'style-name :title "My Style's title" :notifier (lambda (info) (plist-get info :message) (message (if (plist-get info :persistent)...

I ran into the exact same problem, this time using `new-impure-nix` dante method. Suggestion: wouldn't this problem be fixed if `dante.el` prepends the the paths returned from cabal `usually beginning...

I do have completion of LANGUAGE pragmas, when using the standard `haskell-mode` package combined with `company` auto-completion package. Just make sure that `company-capf` is part of the local variable `company-backends`:...

> > Any V3 script will be rejected for not having a cost model. > > Won't it be rejected before that for simply not being recognized as a known...

@JaredCorduan your logic makes sense. > * Note that we need to figure out a way to become more permissive in the cost models serialization scheme _only_ at a hard...

@michaelpj a) if we make it phase1 error, we preclude submitting+executing any new-language scrips until HF. b) if we make it phase2 error, we allow submitting new-language scripts but disallow...

Could this setup (taking from README) be the culprit? ```emacs-lisp (eval-after-load 'company '(add-to-list 'company-backends 'company-omnisharp)) ```

> > This feature would be really useful if you would like to send over a reference to a file or a highlighted couple of lines to somebody over chat...

@tittoassini Any updates on this? Is this a bug or intended behaviour?