Kilian Sprotte
Kilian Sprotte
Changing the line from above ``` loc.colorize(@code_type) if color ``` to ``` loc.colorize(@code_type || :ruby) if color ``` has worked for me as a workaround.
I was going to report this issue myself. :) The second option, using `contract-check` is of course doable. The first one looks more composable, though. But how exactly would it...
The relevant change in the above commit seems to be: Changing the `destination` arg of `call-process` from `nil` to `(list (current-buffer) t)`.
Note: I am not 100% sure that this behavior is really caused by smartparens. Could you help me and tell me what I need to do to find out?
It would be nice if this could be fixed. :slightly_smiling_face: I guess - as a workaround - the easiest thing would be to redefine `projectile-ripgrep` as `my/projectile-ripgrep`. But for a...
@dncrash I just tried, and for me, it also doesn't work.
@ScottFreeCode Would also be possible to store it like in Emacs org-mode, so using colon instead of space. Tagged by `foo` and `bar` would become `:foo:bar:`. Personally, this feature has...
I also think this would be useful. I would want to use this for reading the outputs of commands like `help` or `ls`.
Evaluating ``` (defadvice compile (before ad-compile-smart activate) "Advises `compile' so it sets the argument COMINT to t." (ad-set-arg 1 t)) ``` (see https://www.masteringemacs.org/article/compiling-running-scripts-emacs) makes it work for me by using...
Maybe it would be possible to derive `projectile-rails-generate-mode` from `comint-mode`?