Danylo Malyuta

Results 7 comments of Danylo Malyuta

For your first answer, I tried to use `.clang_complete` with success. My remaining question is that currently here is my project tree, showing where I placed my `.clang_complete` and what...

Thanks, I read through those issues but it doesn't solve the problem that I'm reporting here. The specific issue here is that long file names cause the prompt to overflow...

Is one not supposed to compile `init.el` when using `use-package`? Is that functionality not possible?

I guess my question is more out of curiosity for why this error comes up, and whether it is a symptom of me doing something wrong in my `init.el`

If I use the following `init.el`: ``` ;; MELPA (require 'package) (setq package-enable-at-startup nil) (setq package-check-signature nil) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages/")) (add-to-list 'package-archives '("elpy" . "https://jorgenschaefer.github.io/packages/")) ;; boostrap 'use-package'...

I did add the suggested statement in my last reply... There is an error `Cannot open load file`, like I posted.

It seems the issue goes away if I compile from inside Emacs using `M-x byte-compile-init-dir`. How come the terminal version then isn't working?