On Tue, 28 May 2002, Kai moaned:
When reading, have BBDB apply the normal Emacs machinery for decoding
the file contents. Take note of any coding: tag in the file. If it
is there, just preserve it on write. But if there is no coding:
tag, invoke the migration machinery as follows:
I don't
Nix [EMAIL PROTECTED] writes:
I don't know whether this matters here, but XEmacs doesn't respect
coding tags (and never will, IIRC: the XEmacs developers hate them).
Amazing. Okay, then another mechanism which can do without coding
tags needs to be thought out. (But that doesn't mean the
On Wed, 29 May 2002, Kai said:
Nix [EMAIL PROTECTED] writes:
I don't know whether this matters here, but XEmacs doesn't respect
coding tags (and never will, IIRC: the XEmacs developers hate them).
Amazing.
Er, sorry, I misremembered. Setting the coding system in the local
variables part
Once upon a time, BBDB used one method for the coding system for
.bbdb. Now there is the variable bbdb-file-coding-system.
What's the right setting for this variable to provide safe migration
with no data corruption?
Stupid me, I fooled around with things. But other people are having
problems
On May 28, [EMAIL PROTECTED] said:
So I would like to find a way that BBDB loads the file in the old
coding system (whatever it was, probably Latin-1 because I have
(set-language-environment Latin-1) in the init files), and then
saves it in a better encoding (utf-8? emacs-mule?).
Prior to
Kai == Kai Großjohann [EMAIL PROTECTED]
writes:
Kai Once upon a time, BBDB used one method for the coding system
Kai for .bbdb. Now there is the variable bbdb-file-coding-system.
I don't have it.
Kai What's the right setting for this variable to provide safe
Kai migration with no
Ronan Waide [EMAIL PROTECTED] writes:
On May 28, [EMAIL PROTECTED] said:
So I would like to find a way that BBDB loads the file in the old
coding system (whatever it was, probably Latin-1 because I have
(set-language-environment Latin-1) in the init files), and then
saves it in a better
Ronan Waide [EMAIL PROTECTED] writes:
Prior to the patch, BBDB didn't have any coding-system handling beyond
whatever Emacs uses natively. I applied the patch because
(a) it didn't break my test setup
(b) as described by the contributor, it solved a problem
Heh :-)
Not to cast aspersions
On 28 May 2002 18:34:39 +0700, Sergei Pokrovsky [EMAIL PROTECTED] wrote:
Kai == Kai Großjohann [EMAIL PROTECTED]
writes:
Kai Once upon a time, BBDB used one method for the coding system
Kai for .bbdb. Now there is the variable bbdb-file-coding-system.
Some time ago I considered
Kai Gro,b_(Bjohann writes:
Kai When reading, have BBDB apply the normal Emacs machinery for
Kai decoding the file contents. Take note of any coding: tag in
Kai the file. If it is there, just preserve it on write. But if
Kai there is no coding: tag, invoke the migration machinery as
Kai
Urban Boquist [EMAIL PROTECTED] writes:
If I understand this correctly you want to start migrating as soon as
there is no coding: tag in the file. I don't think that is a good
idea, because there are other ways of telling emacs the coding system
you want for files.
Hm. So is there a way to
Sergei Pokrovsky [EMAIL PROTECTED] writes:
So, I've remained with the raw encoding, but these are incompatible
between the Emacsen (20/21). This is why I avoid emacs-21: it spoils
.bbdb so badly that opening a gnus article crashes emacs-20.7 (which I
still prefer for some reasons).
I think
[EMAIL PROTECTED] (Kai Großjohann) writes:
So I would like to find a way that BBDB loads the file in the old
coding system (whatever it was, probably Latin-1 because I have
(set-language-environment Latin-1) in the init files), and then
saves it in a better encoding (utf-8? emacs-mule?).
13 matches
Mail list logo
