Compilation mode output is badly displayed

Compilation mode output is badly displayed

[Francis Moreau]

Hello,

I'm currently trying to use the Compilation mode and all symbol names
are prefixed and suffixed with some escape sequences, well I think.

For example, I can see:

drivers/scsi/sata_via.c:1237: error: â\200\230struct inodeâ\200\231
has no member named â\200\230i_semâ\200\231

where the "drivers/scsi/sata_via.c" is correctly printed in red color.

Oh, yes I'm using emacs with -nw switch.

Can anyone help me to sort this out ?

Thanks
-- 
Francis

Re: Compilation mode output is badly displayed

[Peter Dyballa]

Am 29.01.2008 um 12:51 schrieb Francis Moreau:

> drivers/scsi/sata_via.c:1237: error: â\200\230struct inodeâ\200\231
> has no member named â\200\230i_semâ\200\231


You just need to switch your *compilation* buffer to display the  
contents as UTF-8 contents. ``â\200\230´´ and ``â\200\231´´ are the  
byte triplets that make the UTF representation of ``‘´´ and ``’´´, U 
+2018 and U+2019. ``â\200\230´´ and ``â\200\231´´ are equivalent to  
0xE28098 and 0xE28099.

--
Greetings

   Pete

There is no worse tyranny than to force a man to pay for what he does  
not want merely because you think it would be good for him.
				– Robert Heinlein

Re: Compilation mode output is badly displayed

[Francis Moreau]

Hello,

On Jan 29, 2008 6:06 PM, Peter Dyballa <Peter_Dyballa@web.de> wrote:
>
> You just need to switch your *compilation* buffer to display the
> contents as UTF-8 contents. ``â\200\230´´ and ``â\200\231´´ are the
> byte triplets that make the UTF representation of ``'´´ and ``'´´, U
> +2018 and U+2019. ``â\200\230´´ and ``â\200\231´´ are equivalent to
> 0xE28098 and 0xE28099.
>

How do you do that ?

BTW why doesn't the *compilation* buffer display UTF8 contents by default
it the used enconding is UTF8 ?

Thanks
-- 
Francis

Re: Compilation mode output is badly displayed

[Eli Zaretskii]

> Date: Tue, 29 Jan 2008 18:29:04 +0100
> From: "Francis Moreau" <francis.moro@gmail.com>
> Cc: help-gnu-emacs@gnu.org
> 
> > You just need to switch your *compilation* buffer to display the
> > contents as UTF-8 contents. ``â\200\230´´ and ``â\200\231´´ are the
> > byte triplets that make the UTF representation of ``'´´ and ``'´´, U
> > +2018 and U+2019. ``â\200\230´´ and ``â\200\231´´ are equivalent to
> > 0xE28098 and 0xE28099.
> >
> 
> How do you do that ?

Try typing "C-x RET c UTF-8 RET" immediately before "M-x compile".

Re: Compilation mode output is badly displayed

[Peter Dyballa]

Am 29.01.2008 um 12:51 schrieb Francis Moreau:

> Can anyone help me to sort this out ?


These typographic quotes come from GCC: can you try to put it into an  
8- or 7-bit environment, like in:

	env LC_CTYPE=FR_fr.ISO8859-15 make -k ...
	env LANG=FR_fr.ISO8859-15 make -k ...
	env LANG=FR_fr.ISO8859-15 LC_CTYPE=FR_fr.ISO8859-15 make -k ...

There must be a reason why GCC emits these typographic quotes. I am  
sure outside an UTF-8 based environment GCC won't emit those Unicode  
characters ...

--
Greetings

   Pete

They that can give up essential liberty to obtain a little temporary  
safety deserve neither liberty nor safety.
		-Benjamin Franklin, Historical Review of Pennsylvania.

Re: Compilation mode output is badly displayed

[Francis Moreau]

On Jan 29, 2008 9:47 PM, Peter Dyballa <Peter_Dyballa@web.de> wrote:
>
> Am 29.01.2008 um 12:51 schrieb Francis Moreau:
>
> > Can anyone help me to sort this out ?
>
>
> These typographic quotes come from GCC: can you try to put it into an
> 8- or 7-bit environment, like in:
>
>         env LC_CTYPE=FR_fr.ISO8859-15 make -k ...

It works fine

>         env LANG=FR_fr.ISO8859-15 make -k ...

It works fine

>         env LANG=FR_fr.ISO8859-15 LC_CTYPE=FR_fr.ISO8859-15 make -k ...

It works fine

>
> There must be a reason why GCC emits these typographic quotes. I am
> sure outside an UTF-8 based environment GCC won't emit those Unicode
> characters ...
>

From a shell:

$ echo $LANG
en_US.UTF-8

$ echo  $LC_CTYPE


So it seems the reason why GCC emits UTF-8 encoding.

That said why doesn't Emacs notice the UTF-8 environment too ? It could
switch automatically to UTF-8 in this case ?

Thanks
-- 
Francis

Re: Compilation mode output is badly displayed

[Sven Joachim]

On 2008-01-30 09:28 +0100, Francis Moreau wrote:

> From a shell:
>
> $ echo $LANG
> en_US.UTF-8
>
> $ echo  $LC_CTYPE
>
>
> So it seems the reason why GCC emits UTF-8 encoding.
>
> That said why doesn't Emacs notice the UTF-8 environment too ? It could
> switch automatically to UTF-8 in this case ?

Normally it does, but you may have cruft in your init file that sets up
a non-UTF-8 environment.  Look there for calls to
set-language-environment and standard-display-european.

Sven

Re: Compilation mode output is badly displayed

[Peter Dyballa]

Am 30.01.2008 um 17:42 schrieb Sven Joachim:

>> $ echo  $LC_CTYPE
>>
>>
>> So it seems the reason why GCC emits UTF-8 encoding.

I don't see it ...

>>
>> That said why doesn't Emacs notice the UTF-8 environment too ? It  
>> could
>> switch automatically to UTF-8 in this case ?
>
> Normally it does, but you may have cruft in your init file that  
> sets up
> a non-UTF-8 environment.  Look there for calls to
> set-language-environment and standard-display-european.


LC_CTYPE, the kind or type of characters used, is the most important  
environment variable in this case. If it's not set, then everything  
can happen. To me set-language-environment looks like an obsolete  
call: does it change the language in which you are informed about a  
character's, variable's, function's, or symbol's value? Is *calendar*  
showing the legal holidays in your country in your language?

If UTF-8 is not correctly or sufficiently established, then it helps  
a bit to have a

	(prefer-coding-system 'utf-8)

--
Greetings

   Pete

I wouldn't recommend sex, drugs or insanity for everyone, but they've  
always worked for me.
				– Hunter S. Thompson

Re: Compilation mode output is badly displayed

[Sven Joachim]

On 2008-01-30 20:18 +0100, Peter Dyballa wrote:

> Am 30.01.2008 um 17:42 schrieb Sven Joachim:
>
>>> $ echo  $LC_CTYPE
>>>
>>>
>>> So it seems the reason why GCC emits UTF-8 encoding.
>
> I don't see it ...

If LANG is set to en_US.UTF-8 (and it is in Francis' environment),
LC_CTYPE does not need to be set.

Sven

Re: Compilation mode output is badly displayed

[Francis Moreau]

On Jan 30, 2008 5:42 PM, Sven Joachim <svenjoac@gmx.de> wrote:
> Normally it does, but you may have cruft in your init file that sets up
> a non-UTF-8 environment.  Look there for calls to
> set-language-environment and standard-display-european.
>

You're right !

In my .emacs, I have the following line:

(set-language-environment "Latin-1")

Should it be removed ?

FYI, here's the output of the command "describe-coding-system":

Coding system for saving this buffer:
  Not set locally, use the default.
Default coding system (for new files):
  1 -- iso-latin-1 (alias: iso-8859-1 latin-1)

Coding system for keyboard input:
  u -- utf-8 (alias of mule-utf-8)

Coding system for terminal output:
  u -- utf-8 (alias of mule-utf-8)

Defaults for subprocess I/O:
  decoding: 1 -- iso-latin-1 (alias: iso-8859-1 latin-1)

  encoding: 1 -- iso-latin-1 (alias: iso-8859-1 latin-1)


Priority order for recognizing coding systems when reading files:
  1. iso-latin-1 (alias: iso-8859-1 latin-1)
  2. windows-1252 (alias: cp1252)
  3. mule-utf-8 (alias: utf-8)
  4. mule-utf-16be-with-signature (alias: utf-16be-with-signature
mule-utf-16-be utf-16-be)
  5. mule-utf-16le-with-signature (alias: utf-16le-with-signature
mule-utf-16-le utf-16-le)
  6. iso-2022-jp (alias: junet)
  7. iso-2022-7bit
  8. iso-2022-7bit-lock (alias: iso-2022-int-1)
  9. iso-2022-8bit-ss2
  10. emacs-mule
  11. raw-text
  12. japanese-shift-jis (alias: shift_jis sjis cp932)
  13. chinese-big5 (alias: big5 cn-big5 cp950)
  14. no-conversion

  Other coding systems cannot be distinguished automatically
  from these, and therefore cannot be recognized automatically
  with the present coding system priorities.

  The following are decoded correctly but recognized as iso-2022-7bit-lock:
    iso-2022-7bit-ss2 iso-2022-7bit-lock-ss2 iso-2022-cn
iso-2022-cn-ext iso-2022-jp-2 iso-2022-kr


Thanks for your support !
-- 
Francis

Re: Compilation mode output is badly displayed

[Stefan Monnier]

> In my .emacs, I have the following line:

> (set-language-environment "Latin-1")

> Should it be removed ?

Yes,


        Stefan