4:32 a.m.
Hello Hrvoje!
The comment above `savehist-coding-system' says it prefers utf-8, this
patch lets savehist use utf-8 even in XEmacs 21.4 providing utf-8 is
present in the coding system list.
edit-utils patch:
ChangeLog files diff command: cvs -q diff -U 0
Files affected: ChangeLog
Source files diff command: cvs -q diff -uN
Files affected: savehist.el
Index: ChangeLog
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/ChangeLog,v
retrieving revision 1.216
diff -u -p -U0 -r1.216 ChangeLog
--- ChangeLog 5 Dec 2005 06:19:11 -0000 1.216
+++ ChangeLog 19 Dec 2005 04:22:52 -0000
＠＠ -0,0 +1,5 ＠＠
+2005-12-19 Steve Youngs <steve(a)sxemacs.org>
+
+ * savehist.el (savehist-coding-system): Use utf-8 even in XEmacs
+ 21.4 providing it is in coding system list.
+
Index: savehist.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/edit-utils/savehist.el,v
retrieving revision 1.4
diff -u -p -u -r1.4 savehist.el
--- savehist.el 14 Nov 2005 07:05:54 -0000 1.4
+++ savehist.el 19 Dec 2005 04:22:37 -0000
＠＠ -135,12 +135,12 ＠＠ save."
;; This should be capable of representing characters used by Emacs.
;; We prefer UTF-8 over ISO 2022 because it is well-known outside
-;; Mule. XEmacs prir to 21.5 had UTF-8 provided by an external
-;; package which may not be loaded, which is why we check for version.
+;; Mule. XEmacs prior to 21.5 had UTF-8 provided by an external
+;; package which may not be loaded, which is why we check
+;; coding-system-list.
(defvar savehist-coding-system (if (and (featurep 'xemacs)
- (<= emacs-major-version 21)
- (< emacs-minor-version 5))
- 'iso-2022-8 'utf-8)
+ (member 'utf-8 (coding-system-list)))
+ 'utf-8 'iso-2022-8)
"The coding system savehist uses for saving the minibuffer history.
Changing this value while Emacs is running is supported, but considered
unwise, unless you know what you are doing.")
--
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
| I am Dyslexic of Borg. |
| Fusistance is retile. Your arse will be laminated. |
|------------------------------------<steve(a)sxemacs.org>---|
8:55 a.m.
Steve Youngs <steve(a)sxemacs.org> writes:
The comment above `savehist-coding-system' says it prefers
utf-8,
this patch lets savehist use utf-8 even in XEmacs 21.4 providing
utf-8 is present in the coding system list.
I know you can check for UTF-8 at runtime. The code avoids using it
for a different reason: if UTF-8 is available through an external
package, it can be present in one XEmacs invocation, but not in the
next one. For example, someone can load the mule-ucs package by
mistake or by loading a third package that depends on mule-ucs. It
would be a mistake for savehist to conclude that it is safe to use
UTF-8 because it probably won't work when XEmacs is next restarted.
Note that a user can always override savehist's choice of coding
system by customizing `savehist-coding-system'. That is what a person
who uses XEmacs 21.4 and wants to use UTF-8 should do.
12:42 p.m.
Hrvoje Niksic <hniksic(a)xemacs.org> writes:
Steve Youngs <steve(a)sxemacs.org> writes:
[snip]
Note that a user can always override savehist's choice of coding
system by customizing `savehist-coding-system'. That is what a person
who uses XEmacs 21.4 and wants to use UTF-8 should do.
Can somebody on this planet tell me when it comes to UTF-8 encoded strings
in the minibuffer?!
Sebastian
8:36 p.m.
* Sebastian Freundt <hroptatyr(a)gna.org> writes:
Hrvoje Niksic <hniksic(a)xemacs.org> writes:
> Steve Youngs <steve(a)sxemacs.org> writes:
>
[snip]
> Note that a user can always override savehist's choice of coding
> system by customizing `savehist-coding-system'. That is what a person
> who uses XEmacs 21.4 and wants to use UTF-8 should do.
Can somebody on this planet tell me when it comes to UTF-8 encoded
strings
in the minibuffer?!
I'm curious... was there ever an answer to this?
--
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
| I am Dyslexic of Borg. |
| Fusistance is retile. Your arse will be laminated. |
|------------------------------------<steve(a)sxemacs.org>---|
11:58 p.m.
Ar an dara lá de mí Eanair, scríobh Steve Youngs:
* Sebastian Freundt <hroptatyr(a)gna.org> writes:
> Hrvoje Niksic <hniksic(a)xemacs.org> writes:
>> Steve Youngs <steve(a)sxemacs.org> writes:
>>
> [snip]
>> Note that a user can always override savehist's choice of coding
>> system by customizing `savehist-coding-system'. That is what a person
>> who uses XEmacs 21.4 and wants to use UTF-8 should do.
> Can somebody on this planet tell me when it comes to UTF-8 encoded
> strings in the minibuffer?!
I'm curious... was there ever an answer to this?
I'm not sure I ever saw it.
"UTF-8 encoded strings in the minibuffer" makes no sense, taking it at face
value. If a string has made it into the minibuffer, it's in XEmacs' internal
encoding, not UTF-8.
If Sebastian means something more like "could someone tell me when I have a
need to use non-Latin-1 text in the minibuffer, and as such have a need to
save my minibuffer history in a more comprehensive encoding than Latin 1,"
then there are a few answers. One possibility is never; there's no shortage
of Germans on Usenet and Unix mailing lists scrupulously writing ae for ä
and ss for ß twenty years after ISO 8859-1 was introduced, and I'm sure
Sebastian can spend the rest of his hacking life in ISO 8859-1 if he chooses
to.
Another possibility is the next time he does search and replace on a Euro
sign; another is the next time he pastes something from the web into his
source code and ends up with directed quotes that he wants to change to
undirected quotes unconditionally.
Another possibility is that he decides in the morning to learn Vietnamese
and to use SXEmacs to write it up; suddenly every interaction with things
external to the editor, like the file system, the windowing system, other
applications, becomes an adventure in working out which level of the many
layers that specify character sets fucked up, and the coding system of the
savehist history really starts to matter to him.
But Sebastian knew this already, I think. It might have cleared things up a
little for you, though. In that spirit, voilà, a post in Latin 1 and Latin 1
only ;-) .
--
I AM IN JAIL AND ALLOWED SEND ONLY ONE CABLE SINCE WAS ARRESTED WHILE
MEASURING FIFTEEN FOOT WALL OUTSIDE PALACE AND HAVE JUST FINISHED COUNTING
THIRTY EIGHT THOUSAND FIVE HUNDERED TWENTY TWO NAMES WHOS WHO IN MIDEAST.
10:52 a.m.
New subject: [A akm] posting in Latin 1
APPROVE aidan-kehoe-microprogram
Please commit.
>>>> "Aidan" == Aidan Kehoe
<kehoea(a)parhasard.net> writes:
Aidan> But Sebastian knew this already, I think. It might have
Aidan> cleared things up a little for you, though. In that spirit,
Aidan> voilà, a post in Latin 1 and Latin 1 only ;-) .
Make it a New Year's resolution, and the multitudes will genuflect at
your feet.
<wink>
--
School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
11:25 a.m.
Ar an dara lá de mí Eanair, scríobh Aidan Kehoe:
One possibility is never; there's no shortage of Germans on
Usenet and
Unix mailing lists scrupulously writing ae for ä and ss for ß twenty
years after ISO 8859-1 was introduced,
A bit of tangental clarification here for ovr non-Evropean friends. Vsing ae
for ä and ss for ß is mvch like vsing v for u and i for j; historically it
makes some sense, and the information gets throvgh, bvt it’s that minority
very accvstomed to dealing with svch text, and ivst them, who are
comfortable with it. A hvge maiority wovld choose the more natvral spelling,
bvt the strength of their feeling isn’t something Vnix hackers recognise,
exactly becavse of their long-standing exposvre to the other.
--
I AM IN IAIL AND ALLOWED SEND ONLY ONE CABLE SINCE WAS ARRESTED WHILE
MEASVRING FIFTEEN FOOT WALL OVTSIDE PALACE AND HAVE IVST FINISHED COVNTING
THIRTY EIGHT THOVSAND FIVE HVNDERED TWENTY TWO NAMES WHOS WHO IN MIDEAST.
6686
days inactive
6700
days old
6 comments
5 participants
participants (5)
-
Aidan Kehoe -
Hrvoje Niksic -
Sebastian Freundt -
Stephen J. Turnbull -
Steve Youngs