misc/emacs: emacs gofmt error

[LukeMauldin]

What steps will reproduce the problem?
If possible, include a link to a program on play.golang.org.
1. See program at http://play.golang.org/p/AGYuQbd6kd
2. I have the go-mode.el plugin from TIP loaded in .emacs.  Here is the part of my
.emacs file:
(require 'go-mode-load)
(add-hook 'before-save-hook #'gofmt-before-save)
3. When I am editing the program posted on play.golang.org, and I save the file, I get
the "Use file" error displayed in the screenshot.

What is the expected output?
I expected for gofmt to be run on my file and saved automatically.

What do you see instead?
The "Use file" error.

Which operating system are you using?
Windows 7 X64

Which version are you using?  (run 'go version')
1.0.3

Please provide any additional information below.
I am running Emacs 24.2 on Windows 7 X64.

Attachments:

1. EmacsError.png (129915 bytes)

[dustin]

Comment 1:

Can you show the value of temporary-file-directory?
If you go to *scratch* and type the name of the variable and hit ^J, it'll print it into
the buffer.
This is exactly what I was experiencing on OS X before my fix I mentioned in issue3782. 
It's possible something very close to it is needed here.

[rsc]

Comment 3:

Labels changed: added priority-later, removed priority-triage.

Status changed to HelpWanted.

[dominikh]

Comment 4:

tl;dr: It's caused by spaces in the file name/path and a bug in diff-mode
This is actually a bug in diff-apply-patch, more specifically diff-hunk-file-names,
which uses the following regular expression to determine the file names of the diff:
> "[-*][-*][-*] \\(\\S-+\\)\\(\\s-.*\\)?\n[-+][-+][-+] \\(\\S-+\\)"
That, unfortunately, assumes that file names have no spaces in them (\\S-+ meaning 1 or
more non-space characters).
Ultimately this needs to be fixed directly in diff-mode and there's not much go-mode can
do about it, other than telling its users not to use spaces, which might be difficult...

[dominikh]

Comment 5:

I have changes pending that get rid of diff-mode altogether. Those should fix this issue.

[adonovan]

Comment 6:

This issue was closed by revision 77ddbf1.

Status changed to Fixed.