bug#6974: Emacs doesn't like Swedish ä (on w32)

bug#6974: Emacs doesn't like Swedish ä (on w32)

[Lennart Borgman]

I have a file whose name contains the Swedish char ä (a with two dots
above, 228 in latin-1).

I have seen several strange things with this. Here are some I remember:


I start from "emacs -Q". In an org-mode file I try to insert a link to
this file with "C-c C-l file FILENAME".


* After M-x set-language-environment RET RET (i.e. "English") and then
opening a new org file.

Works nicely. Examining the char "ä" in the link in the org buffer
gives as expected.

        character: ä (228, #o344, #xe4)
preferred charset: unicode-bmp
		   (Unicode Basic Multilingual Plane (U+0000..U+FFFF))
       code point: 0xE4
           syntax: w 	which means: word
         category: .:Base, j:Japanese, l:Latin
      buffer code: #xC3 #xA4
        file code: #xE4 (encoded by coding system iso-latin-1-dos)
          display: by this font (glyph code)
    uniscribe:-outline-Courier
New-normal-normal-normal-mono-13-*-*-*-c-*-iso8859-1 (#x6C)

In this case I can save the file as usual.


* After M-x set-language-environment RET utf-8 RET and then opening a
new org file.

When choosing the file the char "ä" is shown as \344. It looks the
same when inserted in the buffer as an org link to the file.

        character:   (4194276, #o17777744, #x3fffe4)
preferred charset: eight-bit (Raw bytes 128-255)
       code point: 0xE4
           syntax: w 	which means: word
      buffer code: #xE4
        file code: not encodable by coding system utf-8-dos
          display: no font available

After this I can not save the file (or rather Emacs prompts me for a
coding system).


I also saw that pasting the file name in some circumstances converts
the char "ä" (or was it \344) to a space. Unfortunately I do not
remember how that happened and I can not reproduce it now. (But I am
very sure it happened this morning.)


In GNU Emacs 24.0.50.1 (i386-mingw-nt5.1.2600)
 of 2010-08-10
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4) --no-opt --cflags
-Ic:/g/include -fno-crossjumping'

bug#6974: Emacs doesn't like Swedish ä (on w32)

[Jason Rumney]

On 03/09/2010 05:58, Lennart Borgman wrote:
> I have a file whose name contains the Swedish char ä (a with two dots
> above, 228 in latin-1).
>
> I have seen several strange things with this. Here are some I remember:
>
>
> I start from "emacs -Q". In an org-mode file I try to insert a link to
> this file with "C-c C-l file FILENAME".
>    
> * After M-x set-language-environment RET RET (i.e. "English") and then
> opening a new org file.
>
> Works nicely. Examining the char "ä" in the link in the org buffer
> gives as expected.
>    

OK, but what happens in the default case you tried above, before you 
started messing with the language environment?


> * After M-x set-language-environment RET utf-8 RET and then opening a
> new org file.
>    

Of course it is possible to break things by setting your language 
environment inappropriately. But what happens in the default case?

bug#6974: Emacs doesn't like Swedish ä (on w32)

[Andreas Röhler]

[-- Attachment #1: Type: text/plain, Size: 2978 bytes --]

Am 02.09.2010 23:58, schrieb Lennart Borgman:
> I have a file whose name contains the Swedish char ä (a with two dots
> above, 228 in latin-1).
>
> I have seen several strange things with this. Here are some I remember:
>
>
> I start from "emacs -Q". In an org-mode file I try to insert a link to
> this file with "C-c C-l file FILENAME".
>
>
> * After M-x set-language-environment RET RET (i.e. "English") and then
> opening a new org file.
>
> Works nicely. Examining the char "ä" in the link in the org buffer
> gives as expected.
>
>          character: ä (228, #o344, #xe4)
> preferred charset: unicode-bmp
> 		   (Unicode Basic Multilingual Plane (U+0000..U+FFFF))
>         code point: 0xE4
>             syntax: w 	which means: word
>           category: .:Base, j:Japanese, l:Latin
>        buffer code: #xC3 #xA4
>          file code: #xE4 (encoded by coding system iso-latin-1-dos)
>            display: by this font (glyph code)
>      uniscribe:-outline-Courier
> New-normal-normal-normal-mono-13-*-*-*-c-*-iso8859-1 (#x6C)
>
> In this case I can save the file as usual.
>
>
> * After M-x set-language-environment RET utf-8 RET and then opening a
> new org file.
>
> When choosing the file the char "ä" is shown as \344. It looks the
> same when inserted in the buffer as an org link to the file.
>
>          character:   (4194276, #o17777744, #x3fffe4)
> preferred charset: eight-bit (Raw bytes 128-255)
>         code point: 0xE4
>             syntax: w 	which means: word
>        buffer code: #xE4
>          file code: not encodable by coding system utf-8-dos
>            display: no font available
>
> After this I can not save the file (or rather Emacs prompts me for a
> coding system).
>
>
> I also saw that pasting the file name in some circumstances converts
> the char "ä" (or was it \344) to a space. Unfortunately I do not
> remember how that happened and I can not reproduce it now. (But I am
> very sure it happened this morning.)
>
>
> In GNU Emacs 24.0.50.1 (i386-mingw-nt5.1.2600)
>   of 2010-08-10
> Windowing system distributor `Microsoft Corp.', version 5.1.2600
> configured using `configure --with-gcc (3.4) --no-opt --cflags
> -Ic:/g/include -fno-crossjumping'
>
>
>
>


Hi,

seeing the similar:

when opening a file containing non-ascii chars, german
umlauts for example, in some case these aren't shown
as glyphs but as numbers.

See screenshot attached how the following code looks
like:

(define-abbrev-table
   'global-abbrev-table
   '(("Infinity" "∞" nil 0)
     ("alpha" "α" nil 2)
     ("beta" "β" nil 1)
     ("gamma" "γ" nil 1)
     ("theta" "θ" nil 0)))

As the only thing I remember since, is the use of

GNU Emacs 24.0.50.1 (i686-pc-linux-gnu, GTK+ Version 2.12.0) of 2010-08-28

assume the bug is there.

BTW if I paste the wrongly shown text into this mail for example,
glyphs are shown correctly.

Andreas

--
https://code.launchpad.net/~a-roehler/python-mode
https://code.launchpad.net/s-x-emacs-werkstatt/



[-- Attachment #2: zeichen.png --]
[-- Type: image/png, Size: 83439 bytes --]

bug#6974: Emacs doesn't like Swedish ä (on w32)

[Eli Zaretskii]

> From: Lennart Borgman <lennart.borgman@gmail.com>
> Date: Thu, 2 Sep 2010 23:58:04 +0200
> Cc: 
> 
> * After M-x set-language-environment RET utf-8 RET and then opening a
> new org file.
> 
> When choosing the file the char "ä" is shown as \344. It looks the
> same when inserted in the buffer as an org link to the file.

set-language-environment changes the defaults for various
coding-systems, including file-name-coding-system that's used for
decoding file names.  On Windows, you should _never_ have
file-name-coding-system different from the current codepage, because
that's the only encoding of file names Emacs can currently support on
Windows.  (The other one is UTF-16, which is how Windows encodes file
names on the disk, but Emacs does not yet support that, because such
support would need to switch all the file APIs to use wide
characters.)

So the question is: what is your value of file-name-coding-system,
after you invoke set-language-environment?  If it's anything but your
current Windows codepage, set it back with "C-x RET F" (note: capital
F).

bug#6974: Emacs doesn't like Swedish ä (on w32)

[Eli Zaretskii]

> Date: Fri, 03 Sep 2010 10:03:32 +0200
> From: Andreas Röhler <andreas.roehler@easy-emacs.de>
> Cc: 
> 
> seeing the similar:
> 
> when opening a file containing non-ascii chars, german
> umlauts for example, in some case these aren't shown
> as glyphs but as numbers.

This is a different problem entirely, please file a separate bug
report (although my guess is that this is some cockpit error on your
part, so perhaps discussing this on emacs-devel is a better way of
resolving it).

> See screenshot attached how the following code looks
> like:
> 
> (define-abbrev-table
>    'global-abbrev-table
>    '(("Infinity" "∞" nil 0)
>      ("alpha" "α" nil 2)
>      ("beta" "β" nil 1)
>      ("gamma" "γ" nil 1)
>      ("theta" "θ" nil 0)))

The screenshot shows "t" at the mode-line's left edge, which means
Emacs decoded the file's contents with raw-text coding-system.
raw-text interprets all non-ASCII characters as raw bytes, and
displays them as such, with octal escapes.

The most probable reason for Emacs not to decode the file correctly
(as UTF-8) is that the file includes some bytes that are invalid UTF-8
sequences.  What happens if you force UTF-8 with "C-x RET c" before
visiting the file with "C-x C-f"?

bug#6974: Emacs doesn't like Swedish ä (on w32)

[Andreas Röhler]

Am 03.09.2010 11:01, schrieb Eli Zaretskii:
>> Date: Fri, 03 Sep 2010 10:03:32 +0200
>> From: Andreas Röhler<andreas.roehler@easy-emacs.de>
>> Cc:
>>
>> seeing the similar:
>>
>> when opening a file containing non-ascii chars, german
>> umlauts for example, in some case these aren't shown
>> as glyphs but as numbers.
>
> This is a different problem entirely, please file a separate bug
> report

done with bug#6941

(although my guess is that this is some cockpit error on your
> part,

a theoretically possible source might be code from some 
auto-saved-buffer-file mangled in (?), even if not noticed that.


  so perhaps discussing this on emacs-devel is a better way of
> resolving it).
>
>> See screenshot attached how the following code looks
>> like:
>>
>> (define-abbrev-table
>>     'global-abbrev-table
>>     '(("Infinity" "∞" nil 0)
>>       ("alpha" "α" nil 2)
>>       ("beta" "β" nil 1)
>>       ("gamma" "γ" nil 1)
>>       ("theta" "θ" nil 0)))
>
> The screenshot shows "t" at the mode-line's left edge, which means
> Emacs decoded the file's contents with raw-text coding-system.
> raw-text interprets all non-ASCII characters as raw bytes, and
> displays them as such, with octal escapes.
>
> The most probable reason for Emacs not to decode the file correctly
> (as UTF-8) is that the file includes some bytes that are invalid UTF-8
> sequences.  What happens if you force UTF-8 with "C-x RET c" before
> visiting the file with "C-x C-f"?
>

All fine at the first glance than.

However, re-opening the newly saved buffer repeats the wrong display.

Also when saving, it always prompts for coding-system, suggests raw-text 
first.

Setting buffer-file-coding-system explicitly to utf-8-unix, followed by 
a save, doesn't change the wrong display after new opening.

Difference so for from earlier, it accepts a save at all.

bug#6974: Emacs doesn't like Swedish ä (on w32)

[Lennart Borgman]

On Fri, Sep 3, 2010 at 10:08 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Lennart Borgman <lennart.borgman@gmail.com>
>> Date: Thu, 2 Sep 2010 23:58:04 +0200
>> Cc:
>>
>> * After M-x set-language-environment RET utf-8 RET and then opening a
>> new org file.
>>
>> When choosing the file the char "ä" is shown as \344. It looks the
>> same when inserted in the buffer as an org link to the file.
>
> set-language-environment changes the defaults for various
> coding-systems, including file-name-coding-system that's used for
> decoding file names.  On Windows, you should _never_ have
> file-name-coding-system different from the current codepage, because
> that's the only encoding of file names Emacs can currently support on
> Windows.  (The other one is UTF-16, which is how Windows encodes file
> names on the disk, but Emacs does not yet support that, because such
> support would need to switch all the file APIs to use wide
> characters.)

Using "M-x set-language-environment" was just a way to try to
reproduce the problem. I do not know how to do that otherwise. (I know
very little about coding systems.)

> So the question is: what is your value of file-name-coding-system,
> after you invoke set-language-environment?

It is nil both before and after "M-x set-language-environment".

But something clearly has changed, see what I wrote initially.

bug#6974: Emacs doesn't like Swedish ä (on w32)

[Lennart Borgman]

On Fri, Sep 3, 2010 at 3:44 AM, Jason Rumney <jasonr@gnu.org> wrote:
> On 03/09/2010 05:58, Lennart Borgman wrote:
>>
>> I have a file whose name contains the Swedish char ä (a with two dots
>> above, 228 in latin-1).
>>
>> I have seen several strange things with this. Here are some I remember:
>>
>>
>> I start from "emacs -Q". In an org-mode file I try to insert a link to
>> this file with "C-c C-l file FILENAME".
>>   * After M-x set-language-environment RET RET (i.e. "English") and then
>> opening a new org file.
>>
>> Works nicely. Examining the char "ä" in the link in the org buffer
>> gives as expected.
>>
>
> OK, but what happens in the default case you tried above, before you started
> messing with the language environment?

It works ok.

>> * After M-x set-language-environment RET utf-8 RET and then opening a
>> new org file.
>>
>
> Of course it is possible to break things by setting your language
> environment inappropriately. But what happens in the default case?

Thanks, but please see my reply to Eli.

bug#6974: Emacs doesn't like Swedish ä (on w32)

[Lennart Borgman]

On Fri, Sep 3, 2010 at 1:19 PM, Lennart Borgman
<lennart.borgman@gmail.com> wrote:
> On Fri, Sep 3, 2010 at 10:08 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>>> From: Lennart Borgman <lennart.borgman@gmail.com>
>>> Date: Thu, 2 Sep 2010 23:58:04 +0200
>>> Cc:
>>>
>>> * After M-x set-language-environment RET utf-8 RET and then opening a
>>> new org file.
>>>
>>> When choosing the file the char "ä" is shown as \344. It looks the
>>> same when inserted in the buffer as an org link to the file.
>>
>> set-language-environment changes the defaults for various
>> coding-systems, including file-name-coding-system that's used for
>> decoding file names.  On Windows, you should _never_ have
>> file-name-coding-system different from the current codepage, because
>> that's the only encoding of file names Emacs can currently support on
>> Windows.  (The other one is UTF-16, which is how Windows encodes file
>> names on the disk, but Emacs does not yet support that, because such
>> support would need to switch all the file APIs to use wide
>> characters.)
>
> Using "M-x set-language-environment" was just a way to try to
> reproduce the problem. I do not know how to do that otherwise. (I know
> very little about coding systems.)
>
>> So the question is: what is your value of file-name-coding-system,
>> after you invoke set-language-environment?
>
> It is nil both before and after "M-x set-language-environment".
>
> But something clearly has changed, see what I wrote initially.


It is default-file-name-coding-system that has changed.

I found that my problem was caused by a left over
current-language-environment (set to UTF-8) in my custom file.

Thanks for the help. Sorry for the noise.

bug#6974: Re: bug#6974: Emacs doesn't like Swedish ä (on w32)

[Eli Zaretskii]

> From: Lennart Borgman <lennart.borgman@gmail.com>
> Date: Fri, 3 Sep 2010 13:59:59 +0200
> Cc: 6974@debbugs.gnu.org
> 
> It is default-file-name-coding-system that has changed.

Right, that would be my next question.

> Thanks for the help. Sorry for the noise.

Okay, closing the bug.

bug#6974: Emacs doesn't like Swedish ä (on w32)

[Eli Zaretskii]

> Date: Fri, 03 Sep 2010 11:46:00 +0200
> From: Andreas Röhler <andreas.roehler@easy-emacs.de>
> CC: bug-gnu-emacs@gnu.org
> 
> > The most probable reason for Emacs not to decode the file correctly
> > (as UTF-8) is that the file includes some bytes that are invalid UTF-8
> > sequences.  What happens if you force UTF-8 with "C-x RET c" before
> > visiting the file with "C-x C-f"?
> >
> 
> All fine at the first glance than.
> 
> However, re-opening the newly saved buffer repeats the wrong display.

Sure, because the problem that caused Emacs to decode the file as
raw-text is still in the file.

> Also when saving, it always prompts for coding-system, suggests raw-text 
> first.

Expected, since there are problematic characters in the file.  Try
this:

 M-: (unencodable-char-position (point-min) (point-max) 'utf-8) RET

It should show you the first position in the buffer where you have a
character that cannot be encoded by UTF-8.  If all the characters can
be encoded by UTF-8, this will evaluate to nil.

> Setting buffer-file-coding-system explicitly to utf-8-unix, followed by 
> a save, doesn't change the wrong display after new opening.

And it shouldn't.

bug#6974: Emacs doesn't like Swedish ä (on w32)

[Andreas Röhler]

Am 03.09.2010 15:49, schrieb Eli Zaretskii:
>> Date: Fri, 03 Sep 2010 11:46:00 +0200
>> From: Andreas Röhler<andreas.roehler@easy-emacs.de>
>> CC: bug-gnu-emacs@gnu.org
>>
>>> The most probable reason for Emacs not to decode the file correctly
>>> (as UTF-8) is that the file includes some bytes that are invalid UTF-8
>>> sequences.  What happens if you force UTF-8 with "C-x RET c" before
>>> visiting the file with "C-x C-f"?
>>>
>>
>> All fine at the first glance than.
>>
>> However, re-opening the newly saved buffer repeats the wrong display.
>
> Sure, because the problem that caused Emacs to decode the file as
> raw-text is still in the file.
>
>> Also when saving, it always prompts for coding-system, suggests raw-text
>> first.
>
> Expected, since there are problematic characters in the file.  Try
> this:
>
>   M-: (unencodable-char-position (point-min) (point-max) 'utf-8) RET
>
> It should show you the first position in the buffer where you have a
> character that cannot be encoded by UTF-8.  If all the characters can
> be encoded by UTF-8, this will evaluate to nil.

With buffer narrowed to the code from screen-shot it says:

3993 (#o7631, #xf99)


>
>> Setting buffer-file-coding-system explicitly to utf-8-unix, followed by
>> a save, doesn't change the wrong display after new opening.
>
> And it shouldn't.
>

bug#6974: Emacs doesn't like Swedish ä (on w32)

[Eli Zaretskii]

> Date: Fri, 03 Sep 2010 18:23:33 +0200
> From: Andreas Röhler <andreas.roehler@easy-emacs.de>
> CC: bug-gnu-emacs@gnu.org
> 
> >   M-: (unencodable-char-position (point-min) (point-max) 'utf-8) RET
> >
> > It should show you the first position in the buffer where you have a
> > character that cannot be encoded by UTF-8.  If all the characters can
> > be encoded by UTF-8, this will evaluate to nil.
> 
> With buffer narrowed to the code from screen-shot it says:
> 
> 3993 (#o7631, #xf99)

Well, what is at buffer position 3993?

bug#6974: Emacs doesn't like Swedish ä (on w32)

[Andreas Röhler]

Am 03.09.2010 19:59, schrieb Eli Zaretskii:
>> Date: Fri, 03 Sep 2010 18:23:33 +0200
>> From: Andreas Röhler<andreas.roehler@easy-emacs.de>
>> CC: bug-gnu-emacs@gnu.org
>>
>>>    M-: (unencodable-char-position (point-min) (point-max) 'utf-8) RET
>>>
>>> It should show you the first position in the buffer where you have a
>>> character that cannot be encoded by UTF-8.  If all the characters can
>>> be encoded by UTF-8, this will evaluate to nil.
>>
>> With buffer narrowed to the code from screen-shot it says:
>>
>> 3993 (#o7631, #xf99)
>
> Well, what is at buffer position 3993?
>

the first char not displayed correctly
should display the infinity-symbol,

If I copy this tree numbers here,
it's shown:
"∞"

thats funny.

In this Emacs-buffer it's displayed as "\342\210\236"

bug#6974: Emacs doesn't like Swedish ä (on w32)

[Eli Zaretskii]

> Date: Fri, 03 Sep 2010 21:33:20 +0200
> From: Andreas Röhler <andreas.roehler@easy-emacs.de>
> CC: bug-gnu-emacs@gnu.org
> 
> Am 03.09.2010 19:59, schrieb Eli Zaretskii:
> >> Date: Fri, 03 Sep 2010 18:23:33 +0200
> >> From: Andreas Röhler<andreas.roehler@easy-emacs.de>
> >> CC: bug-gnu-emacs@gnu.org
> >>
> >>>    M-: (unencodable-char-position (point-min) (point-max) 'utf-8) RET
> >>>
> >>> It should show you the first position in the buffer where you have a
> >>> character that cannot be encoded by UTF-8.  If all the characters can
> >>> be encoded by UTF-8, this will evaluate to nil.
> >>
> >> With buffer narrowed to the code from screen-shot it says:
> >>
> >> 3993 (#o7631, #xf99)
> >
> > Well, what is at buffer position 3993?
> >
> 
> the first char not displayed correctly
> should display the infinity-symbol,

Can you use some kind of hex dump program (e.g., `od') to show what's
in the file at that place?

bug#6974: Emacs doesn't like Swedish ä (on w32)

[Andreas Röhler]

Am 03.09.2010 23:05, schrieb Eli Zaretskii:
>> Date: Fri, 03 Sep 2010 21:33:20 +0200
>> From: Andreas Röhler<andreas.roehler@easy-emacs.de>
>> CC: bug-gnu-emacs@gnu.org
>>
>> Am 03.09.2010 19:59, schrieb Eli Zaretskii:
>>>> Date: Fri, 03 Sep 2010 18:23:33 +0200
>>>> From: Andreas Röhler<andreas.roehler@easy-emacs.de>
>>>> CC: bug-gnu-emacs@gnu.org
>>>>
>>>>>     M-: (unencodable-char-position (point-min) (point-max) 'utf-8) RET
>>>>>
>>>>> It should show you the first position in the buffer where you have a
>>>>> character that cannot be encoded by UTF-8.  If all the characters can
>>>>> be encoded by UTF-8, this will evaluate to nil.
>>>>
>>>> With buffer narrowed to the code from screen-shot it says:
>>>>
>>>> 3993 (#o7631, #xf99)
>>>
>>> Well, what is at buffer position 3993?
>>>
>>
>> the first char not displayed correctly
>> should display the infinity-symbol,
>
> Can you use some kind of hex dump program (e.g., `od') to show what's
> in the file at that place?
>

0000000 062050 063145 067151 026545 061141 071142 073145 072055
0000020 061141 062554 020012 023440 066147 061157 066141 060455
0000040 061142 062562 026566 060564 066142 005145 020040 024047
0000060 021050 067111 064546 064556 074564 020042 161042 117210
0000100 020042 064556 020154 024460 020012 020040 024040 060442
0000120 070154 060550 020042 147042 021261 067040 066151 031040
0000140 005051 020040 020040 021050 071141 021061 021040 103342
0000160 021222 067040 066151 030040 005051 020040 020040 021050
0000200 071141 021062 021040 103742 021222 067040 066151 030040
0000220 005051 020040 020040 021050 062542 060564 020042 147042
0000240 021262 067040 066151 030440 005051 020040 020040 021050
0000260 060547 066555 021141 021040 131716 020042 064556 020154
0000300 024461 020012 020040 024040 072042 062550 060564 020042
0000320 147042 021270 067040 066151 030040 024451 005051
0000336

bug#6974: Emacs doesn't like Swedish ä (on w32)

[Eli Zaretskii]

> Date: Sat, 04 Sep 2010 08:22:51 +0200
> From: Andreas Röhler <andreas.roehler@easy-emacs.de>
> CC: bug-gnu-emacs@gnu.org
> 
> > Can you use some kind of hex dump program (e.g., `od') to show what's
> > in the file at that place?
> >
> 
> 0000000 062050 063145 067151 026545 061141 071142 073145 072055
> 0000020 061141 062554 020012 023440 066147 061157 066141 060455
> 0000040 061142 062562 026566 060564 066142 005145 020040 024047
> 0000060 021050 067111 064546 064556 074564 020042 161042 117210
> 0000100 020042 064556 020154 024460 020012 020040 024040 060442
> 0000120 070154 060550 020042 147042 021261 067040 066151 031040
> 0000140 005051 020040 020040 021050 071141 021061 021040 103342
> 0000160 021222 067040 066151 030040 005051 020040 020040 021050
> 0000200 071141 021062 021040 103742 021222 067040 066151 030040
> 0000220 005051 020040 020040 021050 062542 060564 020042 147042
> 0000240 021262 067040 066151 030440 005051 020040 020040 021050
> 0000260 060547 066555 021141 021040 131716 020042 064556 020154
> 0000300 024461 020012 020040 024040 072042 062550 060564 020042
> 0000320 147042 021270 067040 066151 030040 024451 005051
> 0000336

Please post the file as an attachment.

bug#6974: Emacs doesn't like Swedish ä (on w32)

[Andreas Röhler]

[-- Attachment #1: Type: text/plain, Size: 1547 bytes --]

Am 04.09.2010 08:43, schrieb Eli Zaretskii:
>> Date: Sat, 04 Sep 2010 08:22:51 +0200
>> From: Andreas Röhler<andreas.roehler@easy-emacs.de>
>> CC: bug-gnu-emacs@gnu.org
>>
>>> Can you use some kind of hex dump program (e.g., `od') to show what's
>>> in the file at that place?
>>>
>>
>> 0000000 062050 063145 067151 026545 061141 071142 073145 072055
>> 0000020 061141 062554 020012 023440 066147 061157 066141 060455
>> 0000040 061142 062562 026566 060564 066142 005145 020040 024047
>> 0000060 021050 067111 064546 064556 074564 020042 161042 117210
>> 0000100 020042 064556 020154 024460 020012 020040 024040 060442
>> 0000120 070154 060550 020042 147042 021261 067040 066151 031040
>> 0000140 005051 020040 020040 021050 071141 021061 021040 103342
>> 0000160 021222 067040 066151 030040 005051 020040 020040 021050
>> 0000200 071141 021062 021040 103742 021222 067040 066151 030040
>> 0000220 005051 020040 020040 021050 062542 060564 020042 147042
>> 0000240 021262 067040 066151 030440 005051 020040 020040 021050
>> 0000260 060547 066555 021141 021040 131716 020042 064556 020154
>> 0000300 024461 020012 020040 024040 072042 062550 060564 020042
>> 0000320 147042 021270 067040 066151 030040 024451 005051
>> 0000336
>
> Please post the file as an attachment.
>

Attached.

BTW it's my personal note-file, some emacs-issues to remember. So 
doesn't contain real privat stuff, even if not conceived being public 
once... :)

Hex-dump is from the narrowed section containing the example-code.

Encoding-errors are at other positions too.


[-- Attachment #2: befehle.txt --]
[-- Type: text/plain, Size: 15855 bytes --]

(unencodable-char-position (point-min) (point-max) 'utf-8)

match-substitute-replacement

(query-replace (format "%s" 'ä) "ä")
(query-replace (format "%s" 'ü) "ü")
(query-replace (format "%s" '←) "←")
(query-replace (format "%s" '≠) "≠")

(insert (list (read-from-string (format "%s" α))

(setq mon (list "Januar" "Februar" "März" "April" "Mai" "Juni" "Juli" "August" "September" "Oktober"   "November" "Dezember")) 
Mai
\,(pop mon)



git clone git://repo.or.cz/org-mode.git


(message "%s" (case system-type
                (gnu/linux "Linux")
                (window-nt "windows")
                (darwin "mac")
                (t "other")))


  (unless (eq last-command-event 'next)

C-h b  listet alle Tastenbindungen
C-h K  springt in die Info-Dokumentation zu einer Tastenbindung




The read syntax `#'' is a short-hand for using `function'.  For
example,

     #'(lambda (x) (* x x))

is equivalent to

     (function (lambda (x) (* x x)))

;;;;;;;;;;;;;;;;

To represent shared or circular structures within a complex of Lisp
objects, you can use the reader constructs `#N=' and `#N#'.

   Use `#N=' before an object to label it for later reference;
subsequently, you can use `#N#' to refer the same object in another
place.  Here, N is some integer.  For example, here is how to make a
list in which the first element recurs as the third element:

     (#1=(a) b #1#)

This differs from ordinary syntax such as this

     ((a) b (a))
;;;;;;;;;;;;

completion-at-point
multi-isearch-buffers

Once again I recommend that people 

compile with -DUSE_LISP_UNION_TYPE to

catch such bugs.  They're trivial to catch this way.


Florian Diesch wrote:
> Stefan Reuther <stefan.news@arcor.de> writes:
>>im XEmacs kann man im shell den Anfang eines Befehls eingeben und
>>erhält dann mit M-p den vorigen Befehl, der den gleichen Anfang hatte.
>>Kann man dieses Verhalten dem GNU Emacs auch irgendwie beibiegen? M-p
>>ignoriert hier die Eingabe und holt einfach den vorigen Befehl. M-r und
>>dann eine Regexp eingeben geht zwar prinzipiell, aber die Variante mit
>>M-p ist doch irgendwie fluffiger.
> 
> Meinst du sowas wie comint-previous-matching-input-from-input  (C-c M-r)?

Genau das. Das muss ich im Apropos vor lauter Bäumen wohl übersehen haben.


ignore-errors

\([ue]\)st\([0-9][0-9]\)_\([0-9][0-9]\)_
_\1st\2_\1st\3_

dired-mark-files-containing-regexp
\([( ]\)\([a-z-]+\)-atpt
dired-do-query-replace-regexp
\1ar-\2-atpt

raise-sexp

paredit-splice-sexp-killing-backward

.Xresources
emacs.font: Bitstream Vera Sans Mono-10

\([0-9]+\)
\,(+ (string-to-number \1) 240)

(nth \([1-5]\) suffix)
(nth \,(1- (string-to-number \1)) suffix)

diff -u -b /home/speck/emacs/lisp/dired-aux.el /home/speck/progarbeit/emacs/veraendert/dired-aux.el 

;; von auto-save Sicherungen wiederherstellen
recover-this-file

  (interactive (progn
		 (barf-if-buffer-read-only)
		 (list (if current-prefix-arg 'full) t)))


(delq nil (mapcar 'cdr table))

\([^ ]\)\.\([^ ]\)
\1\\\\([[:punct:]]\\\\{0,2\\\\}\\\\|[[:alpha:]]\\\\)\2

\(.*\)fa-\([a-z-]+\) \(reload prot\))\(.*\)
\1fa-\2 \3 "\2")\4

\\\\f\\\\n\\\\r\\\\t
\\f\\n\\r\\t

> >> How can I specify which abbrev table should be loaded in the file itself ?
>
>
> I think the problem is, that the values of file-local-variables
> are not evaluated. This in effect assigns the symbol `my-abbrev-table'
> to the variable `local-abbrev-table' rather than its value
> (the actual table).
>
> One way of fixing it is using the special eval form
>
> -*- eval: (setq local-abbrev-table my-abbrev-table); abbrev-mode: t -
> *-
>
> and adding this form (and forms for other table-symbols you plan to
> use in this way) to `safe-local-eval-forms'.
>
> (push '(setq local-abbrev-table my-abbrev-table) safe-local-eval-
> forms)

C-x 8 RET gives the following prompt:
Unicode (name or hex):


end-of-form-base \\"\(.\)\\" \\"\(.\)\\"
end-of-form-base \\"\1\\" \\"\2\\" nil nil nil nil nil t


hg clone http://bitbucket.org/agr/ropemode/









(define-abbrev-table
  'global-abbrev-table
  '(("Infinity" "∞" nil 0)
    ("alpha" "α" nil 2)
    ("ar1" "→" nil 0)
    ("ar2" "⇒" nil 0)
    ("beta" "β" nil 1)
    ("gamma" "γ" nil 1)
    ("theta" "θ" nil 0)))








(insert 8592)← 
(insert #X2260)≠
haskell-mode


strace
gcore

;;;;;;;;;

Emacs' Schnellstarter (Geladenes als Binärdatei)

#!/usr/bin/make -f
emacs=/usr/bin/emacs 
fast-emacs: /usr/share/emacs/site-lisp/site-start.el     /usr/local/bin/emacs   ~/.emacs      
$(emacs) --batch --execute "(dump-emacs \"fast-emacs\" \"$(emacs)\")"
         

und 

#!/bin/bash
pushd `dirname $0` 
make-emacs
popd
exec fast-emacs $@

;;;;;;;;;

compilation-next-error

All regular
expression replacement commands now allow `\?' in the replacement
string to specify a position where the replacement string can be
edited for each replacement.


If the string begins with `@', Emacs searches the key sequence which
 invoked the command for its first mouse click (or any other event
 which specifies a window).
If the string begins with `^' and `shift-select-mode' is non-nil,
 Emacs first calls the function `handle-shift-select'.
You may use `@', `*', and `^' together.  They are processed in the
 order that they appear, before reading any arguments.


;;;;;;;;;

> > Is it possbile to highligh the column of the page where the cursonr is
> > located ?

M-x column-marker-1 RET 
(or 2 or 3, you can mark up to three columns).

C-u M-x column-marker-1 RET  to disable it.


;;;;;;;;;

> >
> >   (autoload 'muse-mode "muse-mode" "" t)
> >   (eval-after-load "muse-mode"
> >     '(progn
> >        (require 'muse-html)
> >        (require 'muse-journal)
> >        (require 'muse-latex)
> >        (require 'muse-texinfo)
> >        (require 'muse-docbook)
> >        (require 'muse-blosxom)
> >        (require 'muse-project)))

;;;;;;;;;

Von Emacs-keys zu Universal
"\(\\C\-\)\([^\"]\)\([^\"]*\)"
[(control \2)(\3)]



;;;;;;;;;

FWIW, I've got this in my ~/.emacs:

(add-hook 'text-mode-hook
          (defun text-mode-punctuation-syntax ()
            ;; Change non-letter characters from word syntax to punctuation:
            (modify-syntax-entry ?\240 ".") ; NO-BREAK SPACE
            (modify-syntax-entry ?' ".")))  ; APOSTROPHE

-- 
Kevin Rodgers
Denver, Colorado, USA


;;;;;;;;;

Check out the Emacs manual
- 22.17.1.2 Extended Menu Items

I think they are extended the same way as binding commands to keys.

> > That said, if we're adding menu items, how could I add one that basically did
> > "shift region right", but twice?

First you need to write such a command. (Then bind the command to a
menu.)

(defun my-command-name ()
  (interactive)
  (call-interactively 'original-command-name)
  (call-interactively 'original-command-name))

You can find the original command name with C-h k <click on menu>.


;;;;;;;;;

Notice that regexp don't 'show' anything, they 'match' input.  It's
the program that use the regexp that may decide to show or hide lines
depending on whether a regexp match them.

Here is such a regexp matching any line but those containing "--":
  
           ^\([^-]\|-[^-]\)*\(\|-\)$


-- __Pascal Bourguignon__ 

;;;;;;;;;

epa-dired-do-encrypt

Du kannst es natõ‚‰…õ€ˆ¦ï½½ï½¼rlich auch unter Linux ausprobieren, z.B.:

(define-key global-map [kp-decimal] [?*])

Dann mõ‚‰…õ€ˆ¦ï½½ï½¼sstest Du mit Komma-Taste ein Stern bekommen. Aber auf meinem
Windows XP SP3 und GNU Emacs 22.3.1 hat es funktioniert.


;; Groõ‚‰…õ€ˆï½­æ®·chstaben
^\([;]+[ ]+\)\([A-Z]\)

;; c-comment-start suchen
  (re-search-backward "\/\\* " nil t 1)
  (re-search-backward "\\/\\* " nil t 1)



(setq ispell-program-name "/opt/local/bin/aspell")

;;;;;;;;;;

Emacs mit nXhtml-Mode <http://www.emacswiki.org/cgi-bin/wiki/NxhtmlMode>
Nachteile: - Emacs ist natõ‚‰…õ€ˆ¦ï½½ï½¼rlich Geschmackssache
           - unterstõ‚‰…õ€ˆ¦ï½½ï½¼tzt nur XHTML

;;;;;;;;;

Mit Einzel-, Doppel-, Dreifachklick der linken Maustaste markiert man
Zeichen, Wort, Zeile des Anfangs einer Region, mit der rechten Maustaste
das Ende, zweimal rechts lõ‚‰…õ€ˆ¦ï½½ï½¶scht die Region.  Ob gelõ‚‰…õ€ˆ¦ï½½ï½¶scht oder nicht, mit
der mittleren Maustaste fõ‚‰…õ€ˆ¦ï½½ï½¼gt man sie anderswo ein.


Nil oder Eingabe
  (let ((s (read-from-minibuffer "Description for %s: ")))
    (message "%s" (when (not (string= "" s)) s))))


 (global-set-key [(control button3)] 'describe-face-at-mouse-point)

uuid.el v0.2
 Von: Stefan Arentz <stefan.arentz@gmail.com>
 An: gnu-emacs-sources@gnu.org
;;
;; uuid.el - This tiny emacs extension defines a new command,
;; insert-random-uuid, which will insert a randomly generated
;; UUID at the point.
;;

(defun generate-random-hex-string (length)
  (let (result (digits "0123456789abcdef"))
    (dotimes (number length result)
      (setq result (cons (elt digits (random 16)) result)))
    (concat result)))
  
(defun generate-random-uuid ()
  "Generate a random UUID."
  (mapconcat 'generate-random-hex-string (list 8 4 4 4 12) "-"))

(defun insert-random-uuid ()
  "Insert a random UUID at the point."
  (interactive)
  (insert (generate-random-uuid)))

;;;;;;;;
Re: Basic Emacs Lisp question
 Von: Giorgos Keramidas <keramida@ceid.upatras.gr>
 An: help-gnu-emacs@gnu.org
 
On Tue, 29 Apr 2008 20:56:17 +0300, Giorgos Keramidas <keramida@ceid.upatras.gr> wrote:
> On Tue, 29 Apr 2008 17:49:19 +0200, Matthias Pfeifer <pfemat@web.de> wrote:
>> Hello,
>>
>> What is the difference between
>>
>> (list 0 nil -1)
>>
>> and
>>
>> '(0 nil -1)
>
> In Common Lisp (list 0 nil -1) is required to 'cons' a new list every
> time it is called. Quoting the list as in '(0 nil -1) is not required
> to build a new list. In fact, in compiled code it may reuse the same
> static object over and over again.

Reading my own post reveals that I may have been too terse. To clarify
the point I was trying to make, here's a small test in Common Lisp, and
the equivalent test in Emacs Lisp.

1. Common Lisp test
-------------------

* Save the following Lisp code to a file called "foo.lisp":

 (defun foo-quoted ()
  '(0 nil -1))

 (defun foo-list ()
  (list 0 nil -1))

* Then compile the file, and load it. Here's the output from loading
 the compiled file in SBCL:

 CL-USER> (compile-file "foo")

 ; compiling file "/home/keramida/foo.lisp" (written 30 APR 2008 01:48:02 AM):
 ; compiling (DEFUN FOO-QUOTED ...)
 ; compiling (DEFUN FOO-LIST ...)

 ; /home/keramida/foo.fasl written
 ; compilation finished in 0:00:00
 #P"/home/keramida/foo.fasl"
 NIL
 NIL
 CL-USER> (load "foo")     ;; This actually loads "foo.fasl" in SBCL.
 T
 CL-USER>

* Every time the `foo-quoted' function runs it returns exactly the same
 compiled object. The object returned by separate calls to
 `foo-quoted' is all of EQ, EQL and EQUAL to any previous call, as you
 can see in:

 CL-USER> (let ((one-list (foo-quoted))
        (another-list (foo-quoted)))
      (mapcar (lambda (test)
           (funcall test one-list another-list))
          (list #'eq #'eql #'equal)))
 (T T T)
 CL-USER>

* In contrast, the object returned by the `foo-list' function is a newly
 CONS-ed list every time the function runs:

 CL-USER> (let ((one-list (foo-list))
        (another-list (foo-list)))
      (mapcar (lambda (test)
           (funcall test one-list another-list))
          (list #'eq #'eql #'equal)))
 (NIL NIL T)
 CL-USER>

The lists returned by `foo-list' are EQUAL, but they are neither EQ nor
EQL to each other. They are created from scratch by allocating new
storage for the value of the expression every time the `foo-list'
function is called.

2. Emacs Lisp test
------------------

* Save the same two functions in a file called "foo.el".

* Fire up Emacs, and byte-compile the file by typing

 M-x byte-compile-file RET foo.el RET

* Load the byte-compiled file by typing

 M-x load-file RET foo.elc RET

* Now evaluate the same two LET forms in your scratch buffer, by pasting
 them in the buffer and typing `C-x C-e' after each expression.

 Emacs Lisp should also evaluate them as:

 (let ((one-list (foo-quoted))
    (another-list (foo-quoted)))
  (mapcar (lambda (test)
       (funcall test one-list another-list))
      (list #'eq #'eql #'equal)))
 => (t t t)

 (let ((one-list (foo-list))
    (another-list (foo-list)))
  (mapcar (lambda (test)
       (funcall test one-list another-list))
      (list #'eq #'eql #'equal)))
 => (nil nil t)

I hope this makes what I initially wrote a bit easier to grasp :-)

Giorgos

;;;;;;;;;

An alternative way of evaluating Emacs Lisp expressions interactively is to use Inferior Emacs-Lisp mode, which provides an interface rather like Shell mode (see section Shell Mode) for evaluating Emacs Lisp expressions. Type M-x ielm to create an `*ielm*' buffer which uses this mode.

; Kastrup
(progn (setq x '(5)) (dotimes (i 5) (push i x)) x)

and get
(4 3 2 1 0 5)

and that is the only permitted behavior.

In contrast, list must always create a fresh object.
,, meins
(progn (setq x (list 5)) (dotimes (i 5) (push i x)) x)
;;;;;;;;;

Ansi Color Names Vector, py-shell, face

;;;;;;;;;

M-x apropos RET hyper RET

This is specified by: x-hyper-keysym
Usually, it's Hyper_L and Hyper_R.

You can choose what key generate these keysyms with xmodmap(1).

;;;;;;;;;

;; oxdivk Optionen
 -fullscreen -s 6

;;;;;;;;;



(add-hook 'dired-mode-hook
          (lambda ()
            (local-set-key [mouse-2] 'my-dired-mouse-find-file-same-window)))

;;;;;;;;;


(defun insert-hyphen-or-two ()
  (interactive "*")
  (cond
   ((or (bolp) (not (looking-back "'")))
    ;; insert just one '
    (self-insert-command 1))
   ((save-excursion
      (backward-char)
      ;; Skip symbol backwards.
      (and (not (zerop (skip-syntax-backward "w_")))
       (not (looking-back "`"))
       (or (insert-and-inherit "`") t))))
   (t
    ;; insert `' around following symbol
    (delete-backward-char 1)
    (unless (looking-back "`") (insert-and-inherit "`"))
    (save-excursion
      (skip-syntax-forward "w_")
      (unless (looking-at "'") (insert-and-inherit "'"))))))

(global-set-key [39] 'insert-hyphen-or-two)

martin (Rudalics)

;;;;;;;;;

;; Internal function for test
(defun highlight-current-line-reload ()
  "Reload library highlight-current-word for test purposes."
  (unload-feature 'highlight-current-word)
  (load-library "highlight-current-word"))

;

emacs C-x C-c sudo apt-get


	
Re: Fast emacs?: msg#00074
help-gnu-emacs-gnu
Subject: 	Re: Fast emacs?
	

> C-x C-f /sudo::/etc/fstab RET

I use this which is great. Open the file in normal mode, and then 
C-x C-r to switch to root privs.

,----
| (defun find-alternative-file-with-sudo ()
| "Open current buffer as root!"
| (interactive)
| (when buffer-file-name
| (find-alternate-file
| (concat "/sudo:root@localhost:"
| buffer-file-name))))
|
| (global-set-key (kbd "C-x C-r") 'find-alternative-file-with-sudo)
;;;;;;;;;;;;;

It is possible to use your aliases with M-x shell-command, I do it all
the time. Do the following:

  * in you bash config (.bashrc): shopt -s -q expand_aliases
    This makes bash aliases work in non-interactive bashs.

  * In your emacs config (.emacs): (setenv "BASH_ENV" "~/.bashrc")
    This tells emacs that non-interactive bash subprocesses should
    load .bashrc.
;;;;;;;;;

tramp
C-x C-f /su::/path/to/file/owned/by/root

scp MYFILE USER@HOST:/MYDIR

 /[ra@akronyx.de]/PATH/

M-x list-charset-chars RET unicode-bmp RET

And also check `M-x list-load-path-shadows' to find which external elisp
files shadow emacs builtins.

Bye,
Tassilo

;;;;;;;;;;

> The shell of Emacs gives me,
> > WARNING: terminal is not fully functional
> >
> > This is quite disturbing. Anyone knows how to get out of this warning
> > plz?

By "the shell of Emacs" do you mean "M-x shell" command? If so, the
warning is correct, "M-x shell" is not terminal at all, it's a kind of
repeated shell command prompt. If you need a terminal inside Emacs use
"M-x term".

bug#6971: bug#6974: Emacs doesn't like Swedish ä (on w32)

[Eli Zaretskii]

> Date: Sat, 04 Sep 2010 09:30:55 +0200
> From: Andreas Röhler <andreas.roehler@easy-emacs.de>
> CC: bug-gnu-emacs@gnu.org
> 
> > Please post the file as an attachment.
> >
> 
> Attached.

Thanks.  Here's your culprit:

> > \240 (autoload 'muse-mode "muse-mode" "" t)

You have literal \240 characters in the file, which are invalid UTF-8
sequences.

This file has also other similar problems, like this one:

  Du kannst es nat\365\202\211\205\365\200\210\246\357\275\357\275\274rlich auch unter Linux ausprobieren, z.B.:

I believe the 4th word should have been "natűrlich", and the invalid
long byte sequence instead of ű (which Emacs decodes into some
Japanese Kanji character that cannot be encoded by UTF-8) is the
result of multiple saving of this file with incorrect encoding.

To fix all this corruption, I suggest the following steps:

  1) C-x RET c utf-8 RET C-x C-f befehle.txt RET

  2) M-: (unencodable-char-position (point) (point-max) 'utf-8) RET

  3) Go to the position shown by the previous command, and edit the
     file to replace invalid bytes with valid characters.

  4) Move point past the corrected portion.

  5) Go back to 2.  When unencodable-char-position returns nil, you
     are done; save the file.

I'm closing bug #6971 with this message, since there's no Emacs bug
here.