Re: Bug in Exmh or Tcl?
"Andy Bradford" <[email protected]> 10 Sep 2013 00:31:07 -0600
| Newsgroups | gmane.mail.exmh.devel |
|---|---|
| Message-ID | <[email protected]> |
Thus said "Andy Bradford" on 10 Sep 2013 00:22:54 -0600:
> What I don't understand is how this is even happening. How is it
> possible that the source command doesn't know about the ``-encoding
> utf-8'' option?
Ok, it looks like an Exmh bug. Apparently Exmh renames source to
source-orig:
info body source
global SourceHook
set result [uplevel 1 [list source-orig $file]]
set fn [file rootname [file tail $file]]
if [info exists SourceHook($fn)] {
if [catch {uplevel 1 $SourceHook($fn)} err] {
Exmh_Status "Error in source hook for $fn: $err" warning
}
}
return $result
And replaces it with a broken source:
wrong # args: should be "source file"
while executing
"source"
("uplevel" body line 1)
invoked from within
"uplevel #0 $exmh(command)"
Here's the original:
source-orig
ERROR
wrong # args: should be "source-orig ?-encoding name? fileName"
while executing
"source-orig"
("uplevel" body line 1)
invoked from within
"uplevel #0 $exmh(command)"
Andy
--
TAI64 timestamp: 40000000522ebccb