ChangeLog problems

ChangeLog problems

[Luc Teirlinck]

Since the latest changelog entry for the synching with Tramp, I got
problems with the ChangeLog.  I am not sure what to do about them:

These default coding systems were tried to encode text
in the buffer `ChangeLog<lisp>':
  iso-2022-7bit-unix iso-latin-1
However, each of them encountered these problematic characters:
  iso-2022-7bit-unix:		
  iso-latin-1:		  
The first problematic character is at point in the displayed buffer,
and C-u C-x = will give information about it.

Select one of the following safe coding systems, or edit the buffer:
  utf-8 utf-16 utf-16 utf-16 utf-16be utf-16le
Or specify any other coding system
at the risk of losing the problematic characters.

Re: ChangeLog problems

[Michael Albinus]

Luc Teirlinck <teirllm@dms.auburn.edu> writes:

> Since the latest changelog entry for the synching with Tramp, I got
> problems with the ChangeLog.  I am not sure what to do about them:

[...]

This entry was inserted by me. Locally, I don't use any coding system,
so the local setting from the file (iso-2022-7bit) should be active.
No problems here.

Maybe the following line by my entry could be the problem:

	`buffer-auto-save-file-name' to ?\600 as fallback solution.

You could try to remove this line, and see whether the problem
disappears? If yes, I will modify the string.

Best regards, Michael.

Re: ChangeLog problems

[Luc Teirlinck]

Michael Albinus wrote:

   Maybe the following line by my entry could be the problem:

	   `buffer-auto-save-file-name' to ?\600 as fallback solution.

No, it is caused by the accented e's:

insertion (`expand-file' and alike).  Reported by Fr	d	ric Bothamy

Sincerely,

Luc.

Re: ChangeLog problems

[Andreas Schwab]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 829 bytes --]

Michael Albinus <michael.albinus@gmx.de> writes:

> Luc Teirlinck <teirllm@dms.auburn.edu> writes:
>
>> Since the latest changelog entry for the synching with Tramp, I got
>> problems with the ChangeLog.  I am not sure what to do about them:
>
> [...]
>
> This entry was inserted by me. Locally, I don't use any coding system,
> so the local setting from the file (iso-2022-7bit) should be active.
> No problems here.

You've entered two latin-1 encoded characters here:

	insertion (`expand-file' and alike).  Reported by Frédéric Bothamy

I've fixed that now.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: ChangeLog problems

[Michael Albinus]

Andreas Schwab <schwab@suse.de> writes:

> Michael Albinus <michael.albinus@gmx.de> writes:
>
>> Luc Teirlinck <teirllm@dms.auburn.edu> writes:
>>
>>> Since the latest changelog entry for the synching with Tramp, I got
>>> problems with the ChangeLog.  I am not sure what to do about them:
>>
>> [...]
>>
>> This entry was inserted by me. Locally, I don't use any coding system,
>> so the local setting from the file (iso-2022-7bit) should be active.
>> No problems here.
>
> You've entered two latin-1 encoded characters here:
>
> 	insertion (`expand-file' and alike).  Reported by Frédéric Bothamy
>
> I've fixed that now.

Thanks a lot! I should switch to iso-2022-7bit permanently.

> Andreas.

Best regards, Michael.