Lisp HUG Maillist Archive

Encoding option

Hi!

Emacs uses "coding" modeline option to specify external encoding,
while lispworks uses "encoding". I found that there is
system::*modeline-strings* variable where I can replace "encoding"
with "coding" and make lispworks to use the same modeline option.

Will it be ok? Or maybe Lispworks uses another word intentionally?

_______________________________________________
Lisp Hug - the mailing list for LispWorks users
lisp-hug@lispworks.com
http://www.lispworks.com/support/lisp-hug.html


Re: Encoding option

"73budden ." <budden73@gmail.com> writes:

> Emacs uses "coding" modeline option to specify external encoding,
> while lispworks uses "encoding". I found that there is
> system::*modeline-strings* variable where I can replace "encoding"
> with "coding" and make lispworks to use the same modeline option.
>
> Will it be ok? Or maybe Lispworks uses another word intentionally?


You don't need to replace or modify anything: "coding" works out of the
box (at least in LispWorks 7). See the LispWorks User Guide and
Reference Manual:
"...looks in the EMACS-style (-*-) attribute line for an option called
'encoding' or 'external-format' or 'coding'; or (if that fails), chooses
from among likely encodings by analyzing the bytes near the start of the
file."
http://www.lispworks.com/documentation/lw70/LW/html/lw-387.htm#pgfId-1039952

But, note that in the LispWorks Preferences, under option "Environment",
tab "File Encodings", "Input" needs to be set to "AUTO-DETECT",
otherwise it will override the option specified in the Emacs style
attribute line (or rather, the attribute line will not be consulted).

Regards.
Nico

_______________________________________________
Lisp Hug - the mailing list for LispWorks users
lisp-hug@lispworks.com
http://www.lispworks.com/support/lisp-hug.html


Re: Encoding option

Unable to parse email body. Email id is 13459

Updated at: 2020-12-10 08:33 UTC