Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[emacs] type '/f' trigger autocomplete but got many blank lines. #171

Closed
hackwaly opened this issue Nov 30, 2013 · 2 comments
Closed

[emacs] type '/f' trigger autocomplete but got many blank lines. #171

hackwaly opened this issue Nov 30, 2013 · 2 comments

Comments

@hackwaly
Copy link

Types / before fmt.Printf and delay a while (insert / at last time). It trigger autocomplete, then the document got extra blank lines at document end.
I reproduce it every time after open new buffer for editing .go file.

eg.

package main

import (
    "fmt"
)

func main() {
    /fmt.Printf("hello world")
}

I didn't know if it's bug of go-autocomplete or auto-complete-mode.
my init.el

(require 'package)
(package-initialize)
(exec-path-from-shell-initialize)
;; golang
(require 'go-mode-load)
(require 'auto-complete-config)
(ac-config-default)
(require 'go-autocomplete)
(require 'auto-complete-config)
;; (add-to-list 'load-path "~/.go/src/github.com/dougm/goflymake")
;; (require 'go-flymake)
;; (require 'go-eldoc)
@nsf
Copy link
Owner

nsf commented Nov 30, 2013

It's not a gocode script bug. Scripts are super simple, they just query gocode and return the output to auto-complete-mode. I don't know what's wrong here. Try company-mode (https://github.com/nsf/gocode/tree/master/emacs-company), it usually works better.

@hackwaly
Copy link
Author

Yes, I confirm it's autocomplete bug.
auto-complete/popup-el#32

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants