search

gareth-rees / p4.el

Emacs Perforce Integration
46 stars 29 forks source link

Backtraces from p4.el #238

Open mnsanghvi opened 6 years ago

mnsanghvi commented 6 years ago

I keep seeing backtraces like the following:


Debugger entered--Lisp error: (file-error "Writing to process" "Input/output error" #<process P4>)
  process-send-string(#<process P4> "/Users/msanghvi/.emacs.d/_scratchpad")
  p4-maybe-start-update-statuses()
  p4-update-status-sentinel-1(#<process P4> "exited abnormally with code 1\n")

and

Debugger entered--Lisp error: (file-error "Writing to process" "Bad file descriptor" #<process P4>)
  process-send-string(#<process P4> "/Users/msanghvi/.emacs.d/_scratchpad")
  p4-maybe-start-update-statuses()
  p4-update-status-sentinel-1(#<process P4> "exited abnormally with code 1\n")

This happens very frequently, whenever a new buffer is opened or when I am switching to an existing buffer. It gets annoying, especially with email (mu4e).

Why does this occur ? /Users/msanghvi/.emacs.d/_scratchpad is a file that is opened in a buffer at start-up. It is always present. Some times the file mentioned is one of the many Org files I have opened as part of my GTD workflow.

mnsanghvi commented 6 years ago

Another update on this issue. This keeps happening. Here are some more Backtraces and messages from the *Messages* buffer:

;; while trying to open up a Lisp file
p4-maybe-start-update-statuses: Writing to process: Input/output error, P4

;; while trying to open up a FORTRAN file
p4-maybe-start-update-statuses: Writing to process: Bad file descriptor, P4

;; while trying to open up the init_bash.sh file
Debugger entered--Lisp error: (file-error "Writing to process" "Input/output error" #<process P4>)
  process-send-string(#<process P4> "/Users/msanghvi/Mail/Maildir/My-Proj/Drafts/cur/1510669055.68aa2915fd4743f5.msanghvi-mac:2,DS")
  p4-maybe-start-update-statuses()
  p4-update-status()
  run-hooks(find-file-hook)
  after-find-file(t t)
  find-file-noselect-1(#<buffer init_bash.sh> "~/.emacs.d/init_bash.sh" nil nil "~/.emacs.d/.bash_profile" nil)
  find-file-noselect("/Users/msanghvi/.emacs.d/init_bash.sh" nil nil)
  ido-file-internal(raise-frame)
  ido-find-file()
  funcall-interactively(ido-find-file)
  call-interactively(ido-find-file nil nil)
  command-execute(ido-find-file)

This gets very annoying especially when I'm trying to respond to emails using mu4e. Every email, whether a reply or a new one, causes similar errors to the backtrace given above, to occur. If I repeat the command it will work fine.