Yuriy Pitomets
Yuriy Pitomets
You right here, agree: spaces would be convenient only just after the first paren. Updated behaviour proposal here: | action | result | | --- | --- | | `(`...
For sure, there's should be some flag to enable/disable such behaviour (not sure about per-mode).
It should work even for already exist pairs with content: | action | result | | --- | --- | | _(_`\|`_example)_ => | `(\|example)` | | `` => |...
There no support for gems yet, right?
Would it be something lke: ```elisp (lambda (argv) (let ((original-path (getenv-internal "PATH")) (stack-env-path (shell-command-to-string "stack config env")) ;; TODO: handle case when stack is not present (args ((mapconcat ’identity argv...
Also here possible lags with `direnv-mode` and `lorri` tools, and refreshing their caches (like `M-x direnv-update-environment RET` and [~~`M-& lorri shell RET`~~](https://github.com/target/lorri/issues/495) `M-x eshell-command RET lorri shell RET`.
Both `project1` and `project2` builds fine. `project3` builds only when build info disabled there.
How can I use `dependsOn` and `BuildInfoPlugin` in `project3`?
Looks like it doing ``` [info] Updating project3 [info] Resolved project3 dependencies [info] Updating project3 [info] Resolved project3 dependencies [info] Updating project3 [info] Resolved project3 dependencies ... ``` recursively :disappointed:
Any progress here?