[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: wrong-type-argument in gud-tooltip-mode
From: |
Herbert Euler |
Subject: |
RE: wrong-type-argument in gud-tooltip-mode |
Date: |
Sun, 27 Jan 2008 19:14:36 +0800 |
> How about the patch below. There seems to be no point in running call-process
> with no input file. I could probably also remove the string-match for
> "\\`\\*.+\\*\\'" in gud-tooltip-mode too, as these buffers have no files
> associated with them anyway.
It works. However, calling `call-process' with its second argument
(INFILE) set to nil here might not be trivial, since at least gcc
prints something when its input is /dev/null:
$ gcc -E -dM -
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
- wrong-type-argument in gud-tooltip-mode, Herbert Euler, 2008/01/26
- RE: wrong-type-argument in gud-tooltip-mode, Herbert Euler, 2008/01/26
- RE: wrong-type-argument in gud-tooltip-mode, Nick Roberts, 2008/01/26
- RE: wrong-type-argument in gud-tooltip-mode, Herbert Euler, 2008/01/27
- RE: wrong-type-argument in gud-tooltip-mode, Nick Roberts, 2008/01/27
- RE: wrong-type-argument in gud-tooltip-mode, Herbert Euler, 2008/01/27
- RE: wrong-type-argument in gud-tooltip-mode, Nick Roberts, 2008/01/27
- RE: wrong-type-argument in gud-tooltip-mode,
Herbert Euler <=
- RE: wrong-type-argument in gud-tooltip-mode, Herbert Euler, 2008/01/27
- RE: wrong-type-argument in gud-tooltip-mode, Nick Roberts, 2008/01/27
- RE: wrong-type-argument in gud-tooltip-mode, Herbert Euler, 2008/01/27