David Masterson <[EMAIL PROTECTED]> writes:
> In general, having a coding cookie in a file sounds like a good idea.
> However, does it really sound like a good idea for BBDB? I would
> think that there is the potential for the entries to be in a number of
> different coding systems depending upo
Malcolm Purvis <[EMAIL PROTECTED]> writes:
> If it would fail what sort of errors would you expect?
Create two identical files with some nonascii characters. Verify
that XEmacs opens the files "correctly".
Now put "-*- coding: gb2312; -*-" in (the first line of) one of the
two files, and open
John Paul Wallington <[EMAIL PROTECTED]> writes:
> XEmacs can be built --with-mule=no and it used to be the case that it
> could be built --with-file-coding=no. Would a coding cookie cause
> problems for those kinds of builds, or would it be ignored?
Good question. Anyone?
kai
--
~/.signatur
Once upon a time, I suggested to include a coding cookie in ~/.bbdb
so that Emacs knows how to read the file. I vaguely recall that some
XEmacs expert said that XEmacs doesn't heed such cookies.
But now I did an experiment: I started XEmacs and opened a file with
-*- coding: iso-8859-2; -*-
Ronan Waide <[EMAIL PROTECTED]> writes:
> Of course, that's why "make" gets confused between tabs and spaces. I
> should probably do /something/ with this someday.
You could rename the variable and make an alias for the old name.
kai
--
A large number of young women don't trust men with beards
Alex Schroeder <[EMAIL PROTECTED]> writes:
> Write some elisp -- or just search and replace in the .bbdb file using
> a keyboard macro. I would do the later, I guess.
I just did it with a kbd macro, and it was quite quick. Do M-x bbdb
RET, then C-x ( C-s FIELD-NAME: RET C-k y C-x )
After this
Alex Schroeder <[EMAIL PROTECTED]> writes:
> ("Subject" "=?ks_c_5601-1987" "mail.spam")
Maybe Patrick's SO is Korean...
kai
--
Silence is foo!
___
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las
Sam Steingold <[EMAIL PROTECTED]> writes:
> some people put their non-ASCII names in the "From: " line.
> when that happens, BBDB will insist on putting all possible encodings
> in the AKA list (that's what you get when you use Mule instead of
> UNICODE).
> the appended patch fixes the offending
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
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
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 aspe
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
12 matches
Mail list logo
