abingham/emacs-ycmd

On windows is the ycmd-debug-info supposed to look like this ?

Closed this issue · 6 comments

The paths looks all messed up and ycmd is not reporting any errors ?

Ycmd debug information for buffer run_gui.cpp in c++-mode:

((python
  (executable . "c:\\Python27\\python.exe")
  (version . "2.7.13"))
 (completer
  (items
   ((value . "None")
    (key . "compilation database path"))
   ((value . "['-Wall', '-Wextra', '-Werror', '-Wno-long-long', '-Wno-variadic-macros', '-fexceptions', '-DNDEBUG', '-x', 'c++', '-isystem', 'c:\\\\Users\\\\BoostParts', '-isystem', 'c:\\\\Python27\\\\include', '-isystem', 'c:\\\\Users\\\\llvm\\\\include', '-isystem', 'c:\\\\Users\\\\llvm\\\\tools\\\\clang\\\\include', '-I', 'c:\\\\Users\\\\Justin', '-I', 'c:\\\\Users\\\\Justin\\\\ClangCompleter', '-resource-dir=c:\\\\Program Files\\\\ycmd\\\\ycmd\\\\..\\\\clang_includes', '-fno-delayed-template-parsing', '-fspell-checking']")
    (key . "flags")))
  (name . "C-family")
  (servers))
 (extra_conf
  (path . "c:/Users/Justin/.ycm_extra_conf.py")
  (is_loaded . t))
 (clang
  (has_support . t)
  (version . "clang version 5.0.1 (tags/RELEASE_501/final)")))


Server is running at: 127.0.0.1:50492

Ycmd Mode is enabled

--------------------

Ycmd version:   1.3snapshot (package: 20171111.854)
Emacs version:  25.3.1
System:         x86_64-w64-mingw32
Window system:  w32

I have no idea. Most of this output is just directly fetched from ycmd and printed without any modification. You might check with the ycmd project.

But are you saying that emacs-ycmd is not working properly, or are you just concerned about the path formatting?

Well like I said, flycheck is not working at all.

I'm sorry, I think must have missed something. Where did you talk about flycheck?

There seems to be a pull request and an older issue that is suggesting the same problems as I am having ? I will open an issue at ycmd to see if the paths are supposed to look like that.

Can confirm its definitely working.