Iku Iwasa
Iku Iwasa
I've sent `deadgrep` support PR to `wgrep`. https://github.com/mhayashi1120/Emacs-wgrep/pull/58 I hope it could solve the issue.
Looks #66 is same request as this.
FYI: There is an attempt to make standard with `NO_COLOR` environment variable. http://no-color.org/
Try to eval `(url-retrieve-synchronously "https://www.example.com")`. If it fails, it is not problem of restclient.el, but probably environment problem. [exec-path-from-shell](https://github.com/purcell/exec-path-from-shell) might help if you use macOS.
@satanas @telepath FYI, I replied to the comments on Gist.
I am using it in 2 back-ends [1], [2]. I will update them not to use `keep-prefix`. [1] https://github.com/iquiw/company-cabal [2] https://github.com/iquiw/company-restclient
@dgutov Sure. But these back-ends use `keep-prefix` information only for capitalizing completion result. (e.g. "Cont" => "Content-Type", "cont" => "content-type") So I think I need only a flag (declared by...
> it seems to be it will decide capitalization of the whole candidate strings, not just the part inside prefix. Maybe that's what you meant, though. Yes. It is the...
I gave up the flag approach since prefix is changed when completing common with `(ignore-case t)`. I will try to modify candidates according to prefix, something like follows. ``` emacs-lisp...
My comment was not clear, sorry. I like the current behavior and want to keep it as is even after removing `keep-prefix`. So when I add the user option, it...