Peter S Galbraith wrote:
Many thanks for finding the solution! I'll fix it soon.
Okay, thank you. :-) I guess I was a bit lucky to hit on the right track so
soon. BTW, could you reproduce the bug? I am a bit surprised that nobody
had noticed it before.
In my patch, instead of binding
(default-process-coding-system '(no-conversion . no-conversion))
it is probably cleaner to use
(coding-system-for-write 'no-conversion)
, since I found the following in the Emacs Lisp Manual, Version 2.9:
,----
| -- Variable: coding-system-for-write
| This works much like `coding-system-for-read', except that it
| applies to output rather than input. It affects writing to files,
| as well as sending output to subprocesses and net connections.
|
| When a single operation does both input and output, as do
| `call-process-region' and `start-process', both
| `coding-system-for-read' and `coding-system-for-write' affect it.
`----
The variables coding-system-for-{read,write} take precedence over all other
methods of specifying a coding system, according to the manual, so they
should be used here.
Here is the updated patch:
diff -u deb-view.el~ deb-view.el
--- deb-view.el~ 2005-10-25 01:02:32.000000000 +0200
+++ deb-view.el 2005-12-22 20:49:36.000000000 +0100
@@ -343,6 +343,7 @@
(get-buffer-create data-buffer-name)))
(return-buffer (current-buffer))
(coding-system-for-read 'no-conversion)
+ (coding-system-for-write 'no-conversion)
file-buffer
new-archive-format)
(message "deb-view processing deb file %s..." deb-view-buffer-name)
Cheers,
Sven
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
