[PATCH] Update man page for init file, one nroff format error
17 years, 2 months
Shyamal Prasad
Shyamal Prasad
etc/ChangeLog addition:
2004-12-03 Shyamal Prasad <shyamal(a)member.fsf.org>
* xemacs.1: Now describe $HOME/.xemacs/init.el as the
preferred init file. Fixed excessive space insertion
in the description of the '-vanilla' option
XEmacs source patch:
Diff command: cvs -q diff -u
Files affected: etc/xemacs.1
Index: etc/xemacs.1
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/etc/xemacs.1,v
retrieving revision 1.13
diff -u -r1.13 xemacs.1
--- etc/xemacs.1 2001/04/12 18:20:52 1.13
+++ etc/xemacs.1 2004/12/04 01:33:45
＠＠ -147,12 +147,7 ＠＠
.TP
.B \-vanilla
Load no extra files at startup. Equivalent to the combination of
-.B \-q
-,
-.B \-no-site-file
-, and
-.B \-no-early-packages
-\.
+.BR \-q ", " \-no-site-file ", and " \-no-early-packages .
.TP
.BI \-u " user, " \-user " user"
Load
＠＠ -628,7 +623,8 ＠＠
META-left Make a rectangular selection.
.SH FILES
Lisp code is read at startup from the user's init file,
-\fB$HOME/.emacs\fP.
+\fB$HOME/.xemacs/init.el\fP. If this file does not exist then
+\fB$HOME/.emacs\fP will be read if it is present.
/usr/local/info - files for the Info documentation browser
(a subsystem of
- 2 participants
- 1 comments
[PATCH] Synch up format-time-string % specifiers with Emacs 21.3.1
17 years, 2 months
Shyamal Prasad
Shyamal Prasad
This patch adds % specifiers to format-time-string that are missing in
XEmacs but supported by Emacs 21.3.1
src/ChangeLog addition:
2004-12-08 Shyamal Prasad <shyamal(a)member.fsf.org>
* editfns.c:
* editfns.c (Fformat_time_string):
Added documentation for %z, %g, %G and %V specifiers. This synchs
up the set of % specifiers for format-time-string with Emacs
21.3.1. Make copy of static buffer returned by localtime().
* strftime.c:
* strftime.c (strftime):
Implemented %z, %g, %G and %V in a style similar to existing
implementation of other specifiers.
XEmacs source patch:
Diff command: cvs -q diff -u
Files affected: src/strftime.c src/editfns.c
Index: src/editfns.c
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/editfns.c,v
retrieving revision 1.51
diff -u -r1.51 editfns.c
--- src/editfns.c 2004/12/06 03:52:03 1.51
+++ src/editfns.c 2004/12/09 02:40:17
＠＠ -1015,6 +1015,8 ＠＠
%d is replaced by the day of month, zero-padded.
%D is a synonym for "%m/%d/%y".
%e is replaced by the day of month, blank-padded.
+%G is replaced by the year containing the ISO 8601 week
+%g is replaced by the year of the ISO 8601 week within the century (00-99)
%h is a synonym for "%b".
%H is replaced by the hour (00-23).
%I is replaced by the hour (00-12).
＠＠ -1033,12 +1035,14 ＠＠
%t is a synonym for "\\t".
%T is a synonym for "%H:%M:%S".
%U is replaced by the week of the year (00-53), first day of week is Sunday.
+%V is replaced by the ISO 8601 week number
%w is replaced by the day of week (0-6), Sunday is day 0.
%W is replaced by the week of the year (00-53), first day of week is Monday.
%x is a locale-specific synonym, which defaults to "%D" in the C locale.
%X is a locale-specific synonym, which defaults to "%T" in the C locale.
%y is replaced by the year without century (00-99).
%Y is replaced by the year with century.
+%z is replaced by the time zone as a numeric offset (e.g +0530, -0800 etc.)
%Z is replaced by the time zone abbreviation.
The number of options reflects the `strftime' function.
＠＠ -1063,13 +1067,15 ＠＠
{
Extbyte *buf = alloca_extbytes (size);
Extbyte *formext;
+ /* make a copy of the static buffer returned by localtime() */
+ struct tm tm = * localtime(&value);
+
*buf = 1;
/* !!#### this use of external here is not totally safe, and
potentially data lossy. */
LISP_STRING_TO_EXTERNAL (format_string, formext, Qnative);
- if (emacs_strftime (buf, size, formext,
- localtime (&value))
+ if (emacs_strftime (buf, size, formext, &tm)
|| !*buf)
return build_ext_string (buf, Qnative);
/* If buffer was too small, make it bigger. */
Index: src/strftime.c
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/strftime.c,v
retrieving revision 1.6
diff -u -r1.6 strftime.c
--- src/strftime.c 2002/03/29 04:48:37 1.6
+++ src/strftime.c 2004/12/09 02:40:18
＠＠ -58,6 +58,7 ＠＠
%S second (00..61)
%T time, 24-hour (hh:mm:ss)
%X locale's time representation (%H:%M:%S)
+ %z time zone offset (e.g. +0530, -0800 etc)
%Z time zone (EDT), or nothing if no time zone is determinable
Date fields:
＠＠ -70,10 +71,13 ＠＠
%d day of month (01..31)
%e day of month ( 1..31)
%D date (mm/dd/yy)
+ %G year corresponding to the ISO 8601 week
+ %g Year of the ISO 8601 week within century (00 - 99)
%h same as %b
%j day of year (001..366)
%m month (01..12)
%U week number of year with Sunday as first day of week (00..53)
+ %V ISO 8601 week number (first week is the earliest one with Thu)
%w day of week (0..6)
%W week number of year with Monday as first day of week (00..53)
%x locale's date representation (mm/dd/yy)
＠＠ -235,6 +239,30 ＠＠
return dl <= 0 ? 0 : dl / 7 + (dl % 7 != 0);
}
+#ifndef __isleap
+/* Nonzero if YEAR is a leap year (every 4 years,
+ except every 100th isn't, and every 400th is). */
+# define __isleap(year) \
+ ((year) % 4 == 0 && ((year) % 100 != 0 || (year) % 400 == 0))
+#endif
+
+/* The number of days from the first day of the first ISO week of this
+ year to the year day YDAY with week day WDAY. ISO weeks start on
+ Monday; the first ISO week has the year's first Thursday. YDAY may
+ be as small as YDAY_MINIMUM. */
+#define ISO_WEEK_START_WDAY 1 /* Monday */
+#define ISO_WEEK1_WDAY 4 /* Thursday */
+#define YDAY_MINIMUM (-366)
+static int
+iso_week_days (int yday, int wday)
+{
+ /* Add enough to the first operand of % to make it nonnegative. */
+ int big_enough_multiple_of_7 = (-YDAY_MINIMUM / 7 + 2) * 7;
+ return (yday
+ - (yday - wday + ISO_WEEK1_WDAY + big_enough_multiple_of_7) % 7
+ + ISO_WEEK1_WDAY - ISO_WEEK_START_WDAY);
+}
+
#if !defined(HAVE_TM_ZONE) && !defined(HAVE_TZNAME)
char *zone_name (const struct tm *tp);
char *
＠＠ -362,10 +390,125 ＠＠
length +=
strftime (&string[length], max - length, "%H:%M:%S", tm);
break;
+
+ case 'V':
+ case 'g':
+ case 'G':
+ {
+ int year = tm->tm_year + 1900;
+ int days = iso_week_days (tm->tm_yday, tm->tm_wday);
+
+ if (days < 0)
+ {
+ /* This ISO week belongs to the previous year. */
+ year--;
+ days =
+ iso_week_days (tm->tm_yday + (365 + __isleap (year)),
+ tm->tm_wday);
+ }
+ else
+ {
+ int d =
+ iso_week_days (tm->tm_yday - (365 + __isleap (year)),
+ tm->tm_wday);
+ if (0 <= d)
+ {
+ /* This ISO week belongs to the next year. */
+ year++;
+ days = d;
+ }
+ }
+
+ switch (*format)
+ {
+ /*
+ #### FIXME
+ We really can't assume 1000 <= year <= 9999
+ once time_t gets beyond 32 bits, but it's true
+ of the rest of the code here so get with the
+ program
+ */
+ case 'g':
+ length +=
+ add_num2 (&string[length], year % 100,
+ max - length, pad);
+ break;
+
+ case 'G':
+ add_char (year / 1000 + '0');
+ length += add_num3 (&string[length], year % 1000,
+ max - length, zero);
+ break;
+
+ default:
+ length +=
+ add_num2 (&string[length], days / 7 + 1,
+ max - length, pad);
+ break;
+ }
+ }
+ break;
case 'X':
length +=
strftime (&string[length], max - length, "%H:%M:%S", tm);
break;
+ case 'z':
+ {
+ /*
+ #### FIXME: could use tm->tm_gmtoff if present. Since
+ the other code in xemacs does not do so we follow the
+ leaders (and don't add a autoconf macro to detect
+ its presence).
+ */
+ long int offset;
+ long int minutes;
+ struct tm lt, *ut;
+ time_t utc;
+
+ lt = *tm;
+ utc = mktime(<);
+ ut = gmtime(&utc);
+ /* assume that tm is valid so the others will be too! */
+ assert( utc != (time_t) -1 && ut != NULL );
+
+ /* tm diff code below is based on mktime.c, glibc 2.3.2 */
+ {
+ int lt4, ut4, lt100, ut100, lt400, ut400;
+ int intervening_leap_days, years, days;
+
+ lt4 = (lt.tm_year >> 2) + (1900 >> 2) -
+ ! (lt.tm_year & 3);
+ ut4 = (ut->tm_year >> 2) + (1900 >> 2) -
+ ! (ut->tm_year & 3);
+ lt100 = lt4 / 25 - (lt4 % 25 < 0);
+ ut100 = ut4 / 25 - (ut4 % 25 < 0);
+ lt400 = lt100 >> 2;
+ ut400 = ut100 >> 2;
+ intervening_leap_days =
+ (lt4 - ut4) - (lt100 - ut100) + (lt400 - ut400);
+ years = lt.tm_year - ut->tm_year;
+ days = (365 * years + intervening_leap_days
+ + (lt.tm_yday - ut->tm_yday));
+ offset = (60 * (60 * (24 * days + (lt.tm_hour - ut->tm_hour))
+ + (lt.tm_min - ut->tm_min))
+ + (lt.tm_sec - ut->tm_sec));
+ }
+
+ minutes = offset / ( offset < 0 ? -60 : 60 );
+
+ add_char ((offset < 0 ? '-' : '+'));
+
+ if ( minutes / 600 != 0 )
+ add_char (minutes / 600 + '0');
+ else if ( pad != none )
+ add_char ((pad == zero ? '0' : ' '));
+
+ length +=
+ add_num3 (&string[length],
+ ((minutes / 60 ) % 10) * 100 + (minutes % 60),
+ max - length, pad);
+ break;
+ }
case 'Z':
#ifdef HAVE_TM_ZONE
length += add_str (&string[length], tm->tm_zone, max - length);
- 2 participants
- 1 comments
[AC21.4R21.5] Email truncation bug begone!
19 years, 2 months
Jerry James
Jerry James
APPROVE COMMIT 21.5 RECOMMEND 21.4
David,
I took much too long to process this. I can only claim extreme busyness
with some Real Life stuff over the last several weeks. Thank you so
much for analyzing the problem and coming up with a fix. I'm going to
give credit where credit is due (although I did tweak your patch very
slightly in a couple of ways). The 21.5 patch, which I am committing,
is first, followed by the 21.4 version of the patch. Both have the same
ChangeLog entry.
See the discussion rooted here for more information:
http://list-archive.xemacs.org/xemacs-beta/200412/msg00128.html
src/ChangeLog addition:
2005-02-03 David Evers <extsw(a)appliedgenerics.com>
* process-unix.c (unix_send_process): Flush the last chunk, even
when the pipe is blocked.
xemacs-21.5 source patch:
Diff command: cvs -q diff -uN
Files affected: src/process-unix.c
Index: src/process-unix.c
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/process-unix.c,v
retrieving revision 1.56
diff -d -u -r1.56 process-unix.c
--- src/process-unix.c 2005/01/24 23:34:05 1.56
+++ src/process-unix.c 2005/02/04 03:53:40
＠＠ -1511,30 +1511,38 ＠＠
Ibyte chunkbuf[512];
Bytecount chunklen;
- while (1)
+ do
{
int writeret;
chunklen = Lstream_read (lstream, chunkbuf, 512);
- if (chunklen <= 0)
- break; /* perhaps should ABORT() if < 0?
- This should never happen. */
old_sigpipe =
(SIGTYPE (*) (int)) EMACS_SIGNAL (SIGPIPE, send_process_trap);
- /* Lstream_write() will never successfully write less than
- the amount sent in. In the worst case, it just buffers
- the unwritten data. */
- writeret = Lstream_write (XLSTREAM (DATA_OUTSTREAM (p)), chunkbuf,
- chunklen);
- {
- int save_errno = errno;
- EMACS_SIGNAL (SIGPIPE, old_sigpipe);
- errno = save_errno;
- if (writeret < 0)
- /* This is a real error. Blocking errors are handled
- specially inside of the filedesc stream. */
- report_process_error ("writing to process", proc);
- }
+ if (chunklen > 0)
+ {
+ int save_errno;
+
+ /* Lstream_write() will never successfully write less than
+ the amount sent in. In the worst case, it just buffers
+ the unwritten data. */
+ writeret = Lstream_write (XLSTREAM (DATA_OUTSTREAM(p)), chunkbuf,
+ chunklen);
+ save_errno = errno;
+ EMACS_SIGNAL (SIGPIPE, old_sigpipe);
+ errno = save_errno;
+ if (writeret < 0)
+ /* This is a real error. Blocking errors are handled
+ specially inside of the filedesc stream. */
+ report_file_error ("writing to process", list1 (proc));
+ }
+ else
+ {
+ /* Need to make sure that everything up to and including the
+ last chunk is flushed, even when the pipe is currently
+ blocked. */
+ Lstream_flush (XLSTREAM (DATA_OUTSTREAM(p)));
+ EMACS_SIGNAL (SIGPIPE, old_sigpipe);
+ }
while (Lstream_was_blocked_p (XLSTREAM (p->pipe_outstream)))
{
/* Buffer is full. Wait, accepting input;
＠＠ -1549,7 +1557,9 ＠＠
Lstream_flush (XLSTREAM (p->pipe_outstream));
EMACS_SIGNAL (SIGPIPE, old_sigpipe);
}
+ /* Perhaps should ABORT() if < 0? This should never happen. */
}
+ while (chunklen > 0);
}
else
{ /* We got here from a longjmp() from the SIGPIPE handler */
Index: src/process-unix.c
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/process-unix.c,v
retrieving revision 1.20.2.8
diff -d -u -r1.20.2.8 process-unix.c
--- src/process-unix.c 2005/01/31 02:55:26 1.20.2.8
+++ src/process-unix.c 2005/02/04 03:31:08
＠＠ -1293,26 +1293,38 ＠＠
Bufbyte chunkbuf[512];
Bytecount chunklen;
- while (1)
+ do
{
Lstream_data_count writeret;
chunklen = Lstream_read (lstream, chunkbuf, 512);
- if (chunklen <= 0)
- break; /* perhaps should ABORT() if < 0?
- This should never happen. */
old_sigpipe =
(SIGTYPE (*) (int)) signal (SIGPIPE, send_process_trap);
- /* Lstream_write() will never successfully write less than
- the amount sent in. In the worst case, it just buffers
- the unwritten data. */
- writeret = Lstream_write (XLSTREAM (DATA_OUTSTREAM(p)), chunkbuf,
- chunklen);
- signal (SIGPIPE, old_sigpipe);
- if (writeret < 0)
- /* This is a real error. Blocking errors are handled
- specially inside of the filedesc stream. */
- report_file_error ("writing to process", list1 (proc));
+ if (chunklen > 0)
+ {
+ int save_errno;
+
+ /* Lstream_write() will never successfully write less than
+ the amount sent in. In the worst case, it just buffers
+ the unwritten data. */
+ writeret = Lstream_write (XLSTREAM (DATA_OUTSTREAM(p)), chunkbuf,
+ chunklen);
+ save_errno = errno;
+ signal (SIGPIPE, old_sigpipe);
+ errno = save_errno;
+ if (writeret < 0)
+ /* This is a real error. Blocking errors are handled
+ specially inside of the filedesc stream. */
+ report_file_error ("writing to process", list1 (proc));
+ }
+ else
+ {
+ /* Need to make sure that everything up to and including the
+ last chunk is flushed, even when the pipe is currently
+ blocked. */
+ Lstream_flush (XLSTREAM (DATA_OUTSTREAM(p)));
+ signal (SIGPIPE, old_sigpipe);
+ }
while (Lstream_was_blocked_p (XLSTREAM (p->pipe_outstream)))
{
/* Buffer is full. Wait, accepting input;
＠＠ -1327,7 +1339,9 ＠＠
Lstream_flush (XLSTREAM (p->pipe_outstream));
signal (SIGPIPE, old_sigpipe);
}
+ /* Perhaps should abort() if < 0? This should never happen. */
}
+ while (chunklen > 0);
}
else
{ /* We got here from a longjmp() from the SIGPIPE handler */
--
Jerry James
http://www.ittc.ku.edu/~james/
- 4 participants
- 6 comments
patch: DESTDIR support for XEmacs 21.5.18
19 years, 9 months
Mike FABIAN
Mike FABIAN
A patch to add DESTDIR support to the Makefiles of XEmacs 21.5.18
is attached. This should make it a bit easier for distributors to build
XEmacs packages.
I had already submitted such a patch in February 2004, but Steve
Youngs pointed out some problems. As I was busy with other things I
had no time to improve this patch until now.
2004-12-31 Mike FABIAN <mfabian(a)suse.de>
* Makefile.in.in:
* dynodump/Makefile.in.in:
* etc/tests/external-widget/Makefile:
* lib-src/Makefile.in.in:
* lwlib/Makefile.in.in:
* man/Makefile:
* modules/base64/Makefile:
* modules/common/Makefile.common:
* modules/zlib/Makefile:
* netinstall/Makefile.in.in:
* src/Makefile.in.in:
* tests/tooltalk/Makefile:
Add DESTDIR support.
--
Mike FABIAN <mfabian(a)suse.de> http://www.suse.de/~mfabian
睡眠不足はいい仕事の敵だ。
- 3 participants
- 5 comments
[CVSROOT] Show C function in log diffs
19 years, 9 months
Steve Youngs
Steve Youngs
Being able to see what function a hunk is from can be very handy.
BTW, Mike, I love these new CVS commit mails! :-)
xemacs-CVSROOT patch:
ChangeLog files diff command: cvs -q diff -U 0
Files affected: ChangeLog
Source files diff command: cvs -q diff -uN
Files affected: log_accum
Index: ChangeLog
===================================================================
RCS file: /pack/xemacscvs/CVSROOT/ChangeLog,v
retrieving revision 1.136
diff -u -U0 -r1.136 ChangeLog
--- ChangeLog 4 Jan 2005 15:53:22 -0000 1.136
+++ ChangeLog 29 Jan 2005 02:40:44 -0000
＠＠ -0,0 +1,5 ＠＠
+2005-01-29 Steve Youngs <steve(a)sxemacs.org>
+
+ * log_accum: Add `-p' to $difftype to show the C function a hunk
+ is from.
+
Index: log_accum
===================================================================
RCS file: /pack/xemacscvs/CVSROOT/log_accum,v
retrieving revision 1.57
diff -u -u -r1.57 log_accum
--- log_accum 27 Jan 2005 17:17:46 -0000 1.57
+++ log_accum 29 Jan 2005 02:40:34 -0000
＠＠ -63,7 +63,7 ＠＠
#$EMULATE_LOCAL_MAIL_USER="cvshome.org";
# Set this to '-c' for context diffs; defaults to '-u' for unidiff format.
-$difftype = '-uN';
+$difftype = '-uNp';
############################################################
#
--
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
| In space, |
| No one can hear you rip a stinky |
|------------------------------------<steve(a)sxemacs.org>---|
- 2 participants
- 1 comments
[PATCH] Saner MIME character set defaults in Gnus.
19 years, 9 months
Aidan Kehoe
Aidan Kehoe
This incorporates an upstream change I made to
Gnus--cf. http://quimby.gnus.org/cgi-bin/cvsweb.cgi/gnus/lisp/mm-util.el.diff?r1=6....
, http://tinyurl.com/46rzs , together with a non-nil default for
mm-coding-system-priorities, which is an ordered list of preferred MIME
character sets for a message.
xemacs-packages/gnus/ChangeLog addition:
2005-02-27 Aidan Kehoe <kehoea(a)parhasard.net>
* lisp/mm-util.el (mm-coding-system-priorities):
Give it a non-nil default value even when we're not in Japan,
containing the UTF-8 character set if that's available.
* lisp/mm-util.el (mm-xemacs-find-mime-charset-1): New.
* lisp/mm-util.el (mm-xemacs-find-mime-charset): New.
* lisp/mm-util.el (mm-find-mime-charset-region):
Incorporate upstream XEmacs-specific changes, use latin-unity to
work out which MIME character set is appropriate.
These two changes eliminate the "needs to be split into N charset
parts. Really post?" bug on the default configuration.
XEmacs Packages source patch:
Diff command: cvs -q diff -u
Files affected: xemacs-packages/gnus/lisp/mm-util.el
Index: xemacs-packages/gnus/lisp/mm-util.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/gnus/lisp/mm-util.el,v
retrieving revision 1.5
diff -u -u -r1.5 mm-util.el
--- xemacs-packages/gnus/lisp/mm-util.el 2004/09/28 02:21:14 1.5
+++ xemacs-packages/gnus/lisp/mm-util.el 2005/02/27 16:18:47
＠＠ -304,7 +304,11 ＠＠
(cond ((string= lang "Japanese")
;; Japanese users may prefer iso-2022-jp to shift-jis.
'(iso-2022-jp iso-2022-jp-2 japanese-shift-jis
- iso-latin-1 utf-8)))))
+ iso-latin-1 utf-8))
+ ((find-coding-system 'utf-8)
+ '(iso-8859-1 iso-8859-2 iso-8859-15 utf-8))
+ (t
+ '(iso-8859-1 iso-8859-2 iso-8859-15 iso-2022-jp)))))
"Preferred coding systems for encoding outgoing messages.
More than one suitable coding system may be found for some text.
＠＠ -539,6 +543,83 ＠＠
(> (length (memq a priorities))
(length (memq b priorities)))))
+(eval-when-compile
+ (autoload 'latin-unity-massage-name "latin-unity")
+ (autoload 'latin-unity-maybe-remap "latin-unity")
+ (autoload 'latin-unity-representations-feasible-region "latin-unity")
+ (autoload 'latin-unity-representations-present-region "latin-unity")
+ (defvar latin-unity-coding-systems)
+ (defvar latin-unity-ucs-list))
+
+(defun mm-xemacs-find-mime-charset-1 (begin end)
+ "Determine which MIME charset to use to send region as message.
+This uses the XEmacs-specific latin-unity package to better handle the
+case where identical characters from diverse ISO-8859-? character sets
+can be encoded using a single one of the corresponding coding systems.
+
+It treats `mm-coding-system-priorities' as the list of preferred
+coding systems; a useful example setting for this list in Western
+Europe would be '(iso-8859-1 iso-8859-15 utf-8), which would default
+to the very standard Latin 1 coding system, and only move to coding
+systems that are less supported as is necessary to encode the
+characters that exist in the buffer.
+
+Latin Unity doesn't know about those non-ASCII Roman characters that
+are available in various East Asian character sets. As such, its
+behavior if you have a JIS 0212 LATIN SMALL LETTER A WITH ACUTE in a
+buffer and it can otherwise be encoded as Latin 1, won't be ideal.
+But this is very much a corner case, so don't worry about it."
+ (let ((systems mm-coding-system-priorities) csets psets curset)
+
+ ;; Load the Latin Unity library, if available.
+ (when (and (not (featurep 'latin-unity)) (locate-library "latin-unity"))
+ (require 'latin-unity))
+
+ ;; Now, can we use it?
+ (if (featurep 'latin-unity)
+ (progn
+ (setq csets (latin-unity-representations-feasible-region begin end)
+ psets (latin-unity-representations-present-region begin end))
+
+ (catch 'done
+
+ ;; Pass back the first coding system in the preferred list
+ ;; that can encode the whole region.
+ (dolist (curset systems)
+ (setq curset (latin-unity-massage-name 'buffer-default curset))
+
+ ;; If the coding system is a universal coding system, then
+ ;; it can certainly encode all the characters in the region.
+ (if (memq curset latin-unity-ucs-list)
+ (throw 'done (list curset)))
+
+ ;; If a coding system isn't universal, and isn't in
+ ;; the list that latin unity knows about, we can't
+ ;; decide whether to use it here. Leave that until later
+ ;; in `mm-find-mime-charset-region' function, whence we
+ ;; have been called.
+ (unless (memq curset latin-unity-coding-systems)
+ (throw 'done nil))
+
+ ;; Right, we know about this coding system, and it may
+ ;; conceivably be able to encode all the characters in
+ ;; the region.
+ (if (latin-unity-maybe-remap begin end curset csets psets t)
+ (throw 'done (list curset))))
+
+ ;; Can't encode using anything from the
+ ;; `mm-coding-system-priorities' list.
+ ;; Leave `mm-find-mime-charset' to do most of the work.
+ nil))
+
+ ;; Right, latin unity isn't available; let `mm-find-charset-region'
+ ;; take its default action, which equally applies to GNU Emacs.
+ nil)))
+
+(defmacro mm-xemacs-find-mime-charset (begin end)
+ (when (featurep 'xemacs)
+ `(mm-xemacs-find-mime-charset-1 ,begin ,end)))
+
(defun mm-find-mime-charset-region (b e &optional hack-charsets)
"Return the MIME charsets needed to encode the region between B and E.
nil means ASCII, a single-element list represents an appropriate MIME
＠＠ -580,8 +661,12 ＠＠
(setq systems nil
charsets (list cs))))))
charsets))
- ;; Otherwise we're not multibyte, we're XEmacs, or a single
- ;; coding system won't cover it.
+ ;; If we're XEmacs, and some coding system is appropriate,
+ ;; mm-xemacs-find-mime-charset will return an appropriate list.
+ ;; Otherwise, we'll get nil, and the next setq will get invoked.
+ (setq charsets (mm-xemacs-find-mime-charset b e))
+
+ ;; We're not multibyte, or a single coding system won't cover it.
(setq charsets
(mm-delete-duplicates
(mapcar 'mm-mime-charset
--
“I, for instance, am gung-ho about open source because my family is being
held hostage in Rob Malda’s basement. But who fact-checks me, or Enderle,
when we say something in public? No-one!” -- Danny O’Brien
- 3 participants
- 15 comments
[PATCH] Alias grep-find to find-grep
19 years, 9 months
Aidan Kehoe
Aidan Kehoe
David Kastrup mentions on a thread on emacs-devel(a)gnu.org that
> I have quite often used `find-grep-dired' and it has been a nuisance
> that the more often needed `find-grep' is not available. I only
> discovered by accident that it _does_ exist, but only under the name
> `grep-find'.
My reaction was similar; I was used to
find . -type f -exec grep -nH whatever {} \;
in the shell and the word order of M-x grep-find RET seemed totally alien.
So, yeah, the alias is worth adding.
xemacs-packages/xemacs-base/ChangeLog addition:
2005-02-26 Aidan Kehoe <kehoea(a)parhasard.net>
* compile.el (find-grep): Alias it to grep-find--if you're used to
the shell, find and _then_ grep is the word order that springs to
mind.
XEmacs Packages source patch:
Diff command: cvs -q diff -u
Files affected: xemacs-packages/xemacs-base/compile.el
Index: xemacs-packages/xemacs-base/compile.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/xemacs-packages/xemacs-base/compile.el,v
retrieving revision 1.32
diff -u -u -r1.32 compile.el
--- xemacs-packages/xemacs-base/compile.el 2004/06/28 20:19:43 1.32
+++ xemacs-packages/xemacs-base/compile.el 2005/02/26 15:57:26
＠＠ -768,6 +768,9 ＠＠
(let ((grep-null-device nil)) ; see grep
(grep command-args)))
+;; XEmacs addition
+(defalias find-grep grep-find)
+
;; XEmacs addition: all grep-all-files stuff
(defun construct-grep-all-files-command (find-segment grep-segment)
--
“I, for instance, am gung-ho about open source because my family is being
held hostage in Rob Malda’s basement. But who fact-checks me, or Enderle,
when we say something in public? No-one!” -- Danny O’Brien
- 2 participants
- 1 comments
Re: Patch my ego
19 years, 9 months
Simon Josefsson
Simon Josefsson
Hrvoje Niksic <hniksic(a)xemacs.org> writes:
> Simon Josefsson <jas(a)extundo.com> writes:
>
>> Hi all! Would it be very presumptuous of me to propose a blurb for
>> lisp/about.el about myself?
>
> Not at all! Go ahead.
Thanks. How about this? Feel free to fix my abuse of the English
language.
(My CVS karma didn't seem strong enough to install this.)
2005-02-28 Simon Josefsson <jas(a)extundo.com>
* about.el (xemacs-hackers): Add jas.
(about-other-current-hackers): Likewise.
(about-url-alist): Add URL for jas.
(about-personal-info): Document jas.
(about-hacker-contribution): Describe jas contributions.
Index: about.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/lisp/about.el,v
retrieving revision 1.45.2.10
diff -u -p -r1.45.2.10 about.el
--- about.el 2003/11/08 02:35:01 1.45.2.10
+++ about.el 2005/02/28 15:53:09
＠＠ -1,6 +1,6 ＠＠
;;; about.el --- the About The Authors page (shameless self promotion).
-;; Copyright (c) 1997 Free Software Foundation, Inc.
+;; Copyright (c) 1997, 2005 Free Software Foundation, Inc.
;; Copyright (C) 2001 Ben Wing.
;; Keywords: extensions
＠＠ -123,6 +123,7 ＠＠
(hobley "David hobley" "hobley(a)xemacs.org")
(jan "Jan Vroonhof" "jan(a)xemacs.org")
(jareth "Jareth Hein" "jareth(a)xemacs.org")
+ (jas "Simon Josefsson" "simon(a)xemacs.org")
(jason "Jason R. Mastaler" "jason(a)xemacs.org")
(jens "Jens Lautenbacher" "jens(a)xemacs.org")
(jmiller "Jeff Miller" "jmiller(a)xemacs.org")
＠＠ -173,8 +174,9 ＠＠
;; to sort this list or the one below, use:
;; M-x sort-regexp-fields RET [a-z]+ RET \(.*\) RET
'(aj alastair cgw craig daiki dan dv fabrice golubev gunnar hisashi hniksic
- jan jareth jmiller jason jonathan kazz kirill larsi morioka mta ograf
- olivier oscar pittman tomonori tuck wmperry yoshiki))
+ jan jareth jas jason jmiller jonathan kazz kirill larsi
+ morioka mta ograf olivier oscar pittman tomonori tuck
+ wmperry yoshiki))
(defvar about-once-and-future-hackers
'(ajc baw bw chr cthomp darrylo devin dkindred dmoore eb hbs hmuller
＠＠ -201,6 +203,7 ＠＠
(dv . "http://www.lrde.epita.fr/~didier/")
(fabrice . "http://www.ese-metz.fr/~popineau/")
(fptex . "http://www.fptex.org/")
+ (jas . "http://josefsson.org/")
(jason . "http://www.mastaler.com/")
(juhp . "http://www.01.246.ne.jp/~juhp/")
(jwz . "http://www.jwz.org/")
＠＠ -1067,6 +1070,25 ＠＠ become a cel-animator, and a more succes
computer-game programmer. As he happens to be bilingual (guess which
two?) he's been doing quite a bit of MULE hacking. He's also getting
his hands dirty in the graphics areas as well.\n"))
+ (jas
+ (widget-insert "\
+
+Simon lives in Stockholm where he has discovered that computers
+can be a powerful procrastinating tool. Combined with a
+frustrating desire to see computers simply work, he spends most
+of his time complaining. Occasionally he rises up to the task
+and produces something that others may complain about, which
+brings him increased satisfaction with every bug report. Today
+he is pretending to be a network security guy, with a preference
+for standardization issues, while secretly longing to start a
+cafe or becoming a theoretical computer scientist. His personal
+interest is literature, and to some extent traveling, but will
+try anything for fun, such as juggling, skiing, wine, and
+long-distance biking.
+
+See: ")
+ (about-url-link 'jas nil "Visit Simon's homepage")
+ (widget-insert ".\n"))
(jason
(widget-insert "\
Jason resides in Northern New Mexico where he works as a Systems
＠＠ -1609,6 +1631,13 ＠＠ of the XEmacs custom subsystem and gnuse
(widget-insert "\
Owner of cvs.xemacs.org, the machine that holds the XEmacs CVS
repository, and author of some of the graphics code in XEmacs.\n"))
+ (jas
+ (widget-insert "\
+Wrote and/or integrated several packages for Gnus, such as
+support for IMAP, Sieve, format=flowed, GnuTLS, S/MIME, and PGP.
+Irregularly synchronize lisp code between Emacs and XEmacs. He
+maintain the mail-lib, sieve, sasl, pgg and ecrypto XEmacs
+packages. Operate the secondary MX for xemacs.org.\n"))
(jason
(widget-insert "\
Beta tester, manager of the various XEmacs mailing lists and binary
- 2 participants
- 3 comments
[PATCH] Bump gc-cons-threshold to 4MB.
19 years, 9 months
Aidan Kehoe
Aidan Kehoe
It’s been 500k since 1996. Computers ship with significantly more RAM
now. As discussed about a month ago.
XEmacs Trunk source patch:
Diff command: cvs -q diff -u
Files affected: src/alloc.c
Index: src/alloc.c
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/alloc.c,v
retrieving revision 1.106
diff -u -u -r1.106 alloc.c
--- src/alloc.c 2005/02/03 16:14:04 1.106
+++ src/alloc.c 2005/02/27 18:49:10
＠＠ -5340,7 +5340,7 ＠＠
funcall_alloca_count = 0;
#if 1
- gc_cons_threshold = 500000; /* XEmacs change */
+ gc_cons_threshold = 4194304; /* XEmacs change */
#else
gc_cons_threshold = 15000; /* debugging */
#endif
--
“I, for instance, am gung-ho about open source because my family is being
held hostage in Rob Malda’s basement. But who fact-checks me, or Enderle,
when we say something in public? No-one!” -- Danny O’Brien
- 3 participants
- 3 comments
[COMMIT] Underline data-loss risks with Mule-UCS, add mule-ucs.el to load the pkg
19 years, 10 months
Aidan Kehoe
Aidan Kehoe
NOTE: This patch has been committed.
The warnings about data loss are subsequent to discussion with Stephen; the
addition of mule-ucs.el is entirely on my initiative.
mule-packages/mule-ucs/ChangeLog addition:
2005-02-28 Aidan Kehoe <kehoea(a)parhasard.net>
* doc/mule-ucs.texi (Top):
"latin-unity may be of use" -> "latin-unity will probably be of use"
* doc/mule-ucs.texi (Overview):
Mention that Mule-UCS will probably trash data.
* doc/mule-ucs.texi (Configuration):
Re-iterate that Mule-UCS will probably trash data. Comment out
the hope that advanced features will be documented; I don't
anticipate that happening.
mule-packages/mule-ucs/lisp/ChangeLog addition:
2005-02-28 Aidan Kehoe <kehoea(a)parhasard.net>
* unicode.el (ucs-to-char):
Document that many code points won't have an XEmacs mapping.
* unicode.el (char-to-ucs):
Add a docstring.
* mule-ucs.el: Add a Lisp library that just does a (require
'un-define), on the assumption that people may hear about Mule-UCS
as the way to get Unicode support in 21.4 and try M-: (require
'mule-ucs) RET before going and reading docs.
XEmacs Packages source patch:
Diff command: cvs -q diff -Nu
Files affected: mule-packages/mule-ucs/lisp/unicode.el mule-packages/mule-ucs/lisp/mule-ucs.el mule-packages/mule-ucs/doc/mule-ucs.texi
Index: mule-packages/mule-ucs/doc/mule-ucs.texi
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/mule-packages/mule-ucs/doc/mule-ucs.texi,v
retrieving revision 1.5
diff -u -u -r1.5 mule-ucs.texi
--- mule-packages/mule-ucs/doc/mule-ucs.texi 2005/01/30 18:43:09 1.5
+++ mule-packages/mule-ucs/doc/mule-ucs.texi 2005/02/28 21:47:23
＠＠ -108,6 +108,14 ＠＠
＠c You can find the latest version of this document on the web at
＠c ＠uref{http://www.xemacs.org/}.
+IMPORTANT NOTE; Mule-UCS translates from Unicode to XEmacs' internal
+Mule encoding, and vice-versa. This internal encoding does not have a
+mapping for every Unicode code point, so if you are using any code point
+that is remotely obscure, there's a good chance it will be trashed, and
+you will lose data. Examples of such code points are U+264A WHITE
+SMILING FACE and U+201A SINGLE LOW-9 QUOTATION MARK, the latter as often
+used in Central Europe.
+
＠ifhtml
＠c This manual is also available as a ＠uref{mule-ucs_ja.html, a Japanese
＠c translation}.
＠＠ -233,7 +241,7 ＠＠
character sets, where by international standard as well as common
practice characters common to more than one character set are considered
identical (not "unified" as for the Han characters in Unicode), the
-＠file{latin-unity} package may be of use.
+＠file{latin-unity} package will probably be of use.
＠c #### need examples of un-define-change-charset-order usage
＠＠ -241,7 +249,8 ＠＠
translate multilingual texts into non-Unicode encodings such as ISO 2022
will have to be done by hand.)
-That is all that most users of Mule-UCS need to know.
+That is all that most users of Mule-UCS need to know---but make sure
+you've read the warning at the start of this document about losing data!
Mule-UCS is still under development and any problems you encounter,
trivial or major, should be reported to the Mule-UCS developers. Use
＠＠ -359,14 +368,15 ＠＠
implemented in XEmacs itself. Mule-UCS provides some utilities in the
＠file{un-tools} library, but these are of unknown reliability.
-That is all that most users of Mule-UCS need to know. The rest of this
-section documents various advanced features which allow Mule-UCS to be
-tuned to resolve ambiguities (such as the unification of the Han
-characters across several languages) more appropriately.
+That is all that most users of Mule-UCS need to know---but make sure
+you've read the warning at the start of this document about losing data!
-＠c #### FIXME!
-Well, it will once it's written. ＠code{:-P}
+＠c The rest of this section documents various advanced features which allow
+＠c Mule-UCS to be tuned to resolve ambiguities (such as the unification of
+＠c the Han characters across several languages) more appropriately.
+＠c #### FIXME!
+＠c Well, it will once it's written. ＠code{:-P}
＠node Design of Mule-UCS, , Configuration, Top
＠chapter Design goal
Index: mule-packages/mule-ucs/lisp/mule-ucs.el
===================================================================
RCS file: mule-ucs.el
diff -N mule-ucs.el
--- /dev/null Mon Feb 28 22:47:21 2005
+++ mule-packages/mule-ucs/lisp/mule-ucs.el Mon Feb 28 22:47:23 2005
＠＠ -0,0 +1,37 ＠＠
+;;; mule-ucs.el --- Create an entry point for Mule-UCS on the pattern of
+;;; every other Lisp package out there.
+
+;; Copyright (C) 2005 Free Software Foundation
+
+;; Author: Aidan Kehoe
+;; Keywords: mule, multilingual, unicode
+;; Created: 2005-02-28
+
+;; This file is part of XEmacs
+
+;; XEmacs is free software; you can redistribute it and/or modify it under
+;; the terms of the GNU General Public License as published by the Free
+;; Software Foundation; either version 2, or (at your option) any later
+;; version.
+
+;; XEmacs is distributed in the hope that it will be useful, but WITHOUT ANY
+;; WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
+;; FOR A PARTICULAR PURPOSE. See the GNU General Public License for more
+;; details.
+
+;; You should have received a copy of the GNU General Public License
+;; along with this program; see the file COPYING. If not, write to the
+;; Free Software Foundation, Inc., 59 Temple Place - Suite 330,
+;; Boston, MA 02111-1307, USA.
+
+;; Comment:
+
+;; I don't advocate pointing people towards this file; this is purely to
+;; make the thing Just Work for people who hear about Mule-UCS as the means
+;; to Unicode support in 21.4 and guess that it works on the model of every
+;; Lisp library out there.
+
+(require 'un-define)
+
+(provide 'mule-ucs)
+
Index: mule-packages/mule-ucs/lisp/unicode.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/packages/mule-packages/mule-ucs/lisp/unicode.el,v
retrieving revision 1.2
diff -u -u -r1.2 unicode.el
--- mule-packages/mule-ucs/lisp/unicode.el 2002/03/18 09:29:02 1.2
+++ mule-packages/mule-ucs/lisp/unicode.el 2005/02/28 21:47:24
＠＠ -89,9 +89,19 ＠＠
;;;
(defun ucs-to-char (codepoint)
+ "Convert Unicode codepoint to an XEmacs character.
+CODE should be a non-negative integer.
+
+If `codepoint' cannot be represented as an XEmacs character--that is,
+Mule-UCS doesn't know about any registered translation from it to some
+character in the multiple-character-set non-Unified Mule model, return nil.
+Beware that *many* Unicode codepoints have no representation in the Mule
+model, and since the Mule-UCS coding systems have the same backend as does
+this function, they will tend to trash data. "
(ucs-representation-decoding-backend 'ucs codepoint nil))
(defun char-to-ucs (char)
+ "Convert character to Unicode codepoint. "
(ucs-representation-encoding-backend char 'ucs nil))
;;;
--
“I, for instance, am gung-ho about open source because my family is being
held hostage in Rob Malda’s basement. But who fact-checks me, or Enderle,
when we say something in public? No-one!” -- Danny O’Brien
- 1 participants
- 0 comments