Re: What is the status of 21.5?
17 years, 2 months
Jeff Miller
Can I go on the record and say that for me 21.5 is a non-starter currently?
My biggest complaint is that vm is just not usable with 21.5. The is a horrible
amount of flickering of the toolbars for each message movement. Also, the point in
the buffer seems to get totally messed up. Any time I've tried it lately, I get
nervous when i see the scrambled INBOX buffer.
Is this vm? Is this 21.5? i'm guessing 21.5 since 21.4 works perfectly with the
same vm version. I see the same flickering though not as extensive with gnus on
21.5 as well.
Sorry for the not-so-great problem report, but I'm still away on business and don't
have a 21.5 handy. I just wanted to interject that all is not perfect, at least
from my viewpoint.
jeff
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Bug tracker?
17 years, 2 months
Hans de Graaff
I'm finding that I'm increasingly less motivated to report issues, bug
fixes, and patches that are coming out of maintenance of XEmacs for
Gentoo. I think that this is mainly caused by the lack of a bug tracker,
so I'll present the case for one and end by asking why there isn't one
currently, whether one is wanted, and what steps are needed to make this
happen.
For me providing patches to XEmacs is really a fire-and-forget thing. I
send out the message, maybe something happens, maybe not, depending on
interestingness and availability, and if nothing happens in a short
period of time the work is essentially lost. Other people won't be able
to easily search for it, comment on it, or amend it. It also makes
tracking fixes much harder than it would need to be. Having a single
reference to a bug report or patch makes it a lot easier to keep an eye
on progress and help things along if needed.
I also feel that the lack of a bug tracker is holding back growth of
XEmacs development. Helping out with filling bugs, commenting on bugs,
testing patches, providing fixes for easy problems and progressing to
more complex work is a natural way to attract new people to the
development team, but without a place to work on it this is much less
likely to happen. A set of mailing lists is really a very poor
substitute for such a workflow.
Looking at http://www.xemacs.org/Debug/index.html it seems that there is
latent interest in having a bug tracker in place, given the comment at
the bottom. So, my questions:
Is a bug tracker still wanted?
Has any work been done on this already?
What would be the next steps for making this happen?
Kind regards,
Hans
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Re: What is the status of 21.5?
17 years, 2 months
Julian Bradfield
In article <77.23.10837.6CD54D64(a)mxo6.broadbandsupport.net> <jmiller(a)cablespeed.com> writes:
>Can I go on the record and say that for me 21.5 is a non-starter currently?
>
>My biggest complaint is that vm is just not usable with 21.5. The is a horrible
>amount of flickering of the toolbars for each message movement. Also, the point in
>the buffer seems to get totally messed up. Any time I've tried it lately, I get
>nervous when i see the scrambled INBOX buffer.
Seconded. It's for this reason that I've installed 21.4 over the 21.5 on our
FC6 systems.
I'd like to try to work out what's going on, but semester is looming,
and I don't see myself having the time.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Access to CVS?
17 years, 2 months
Jerry James
Hi folks,
I'm trying to come back to life, so to speak, after yet another job
change and move. I don't yet know how to make email be From: my
xemacs.org email address, but I'll try to figure that out Real Soon
Now. I'm also having some difficulty with XEmacs CVS. I've been
trying to get an up-to-date workspace all weekend, but I always get
this:
$ cvs -d :pserver:cvs＠cvs.xemacs.org:/pack/xemacscvs login
Logging in to :pserver:cvs＠cvs.xemacs.org:2401/pack/xemacscvs
CVS password:
cvs [login aborted]: connect to cvs.xemacs.org(130.225.247.90):2401
failed: Connection timed out
Ping tells me that the destination network is unreachable. Traceroute
gets to hop 26, then says this:
26 130.225.242.102 reports: Destination net unreachable.
Is this a known problem? If so, what's the ETA on getting CVS back up?
Thanks,
--
Jerry James
http://loganjerry.googlepages.com/
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
bug-report
17 years, 3 months
Mario Natiello
Hallo
I have a problem with xemacs 21.5
When running in LaTeX mode (editing files
with name foo.tex) the option to change
fontsize (options -> fontsize -> choose)
crashes the process, with the following
output on terminal screen:
=================================================
Fatal Error: Received SIGSEGV (11) for address 0x8
WARNING: Unable to auto-save your files properly.
Some or all may in fact have been auto-saved.
Fatal error (11).
Your files have been auto-saved.
Use `M-x recover-session' to recover them.
Your version of XEmacs was distributed with a PROBLEMS file that may describe
your crash, and with luck a workaround. Please check it first, but do report
the crash anyway.
Please report this bug by invoking M-x report-emacs-bug, or by selecting
`Send Bug Report' from the Help menu. If that won't work, send ordinary
email to `xemacs-beta(a)xemacs.org'. *MAKE SURE* to include this entire
output from this crash, especially including the Lisp backtrace, as well as
the XEmacs configuration from M-x describe-installation (or equivalently,
the file `Installation' in the top of the build tree).
*Please* try *hard* to obtain a C stack backtrace; without it, we are unlikely
to be able to analyze the problem. Locate the core file produced as a result
of this crash (often called `core' or `core.<process-id>', and located in
the directory in which you started XEmacs or your home directory), and type
gdb /usr/bin/xemacs core
then type `where' at the debugger prompt. No GDB on your system? You may
have DBX, or XDB, or SDB. (Ask your system administrator if you need help.)
If no core file was produced, enable them (often with `ulimit -c unlimited')
in case of future recurrance of the crash.
Lisp backtrace follows:
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (condition-case ... . t)
# (unwind-protect ...)
# (unwind-protect ...)
specifier-instance(#<font-specifier global=<unspecified>Segmentation fault
==========================================
M-x describe-installation:
uname -a: Linux albeniz 2.6.18 #1 SMP Tue Nov 21 12:59:21 UTC 2006 x86_64 x86_64 x86_64 GNU/Linux
./configure 'x86_64-suse-linux' '--with-gcc' '--with-dynamic' '--with-debug' '--enable-error-checking=none' '--with-cflags=-O2 -fmessage-length=0 -Wall -D_FORTIFY_SOURCE=2 -g -Wall -Wno-switch -pipe -fno-strict-aliasing -DLDAP_DEPRECATED ' '--with-ldflags=' '--prefix=/usr' '--exec-prefix=/usr' '--bindir=/usr/bin' '--datadir=/usr/share' '--with-archlibdir=/usr/lib/xemacs/21.5.27.20060705/x86_64-suse-linux' '--with-docdir=/usr/lib/xemacs/21.5.27.20060705/x86_64-suse-linux' '--with-lispdir=/usr/share/xemacs/21.5.27.20060705/lisp' '--with-etcdir=/usr/share/xemacs/21.5.27.20060705/etc' '--with-statedir=/var/lib/xemacs' '--with-moduledir=/usr/lib/xemacs/21.5.27.20060705/x86_64-suse-linux/modules' '--infodir=/usr/share/xemacs/info' '--mandir=/usr/share/man/man1' '--enable-database=gdbm,berkdb' '--with-ncurses' '--with-canna' '--with-tty=yes' '--with-site-lisp' '--with-mc-alloc' '--with-kkcc' '--with-newgc' '--enable-sound=native' '--with-gpm' '--enable-pdump' '--disable-dump-in-exe
c' '--with-xpm' '--with-gif' '--with-tiff' '--with-jpeg' '--with-png' '--with-x' '--with-athena=3d' '--enable--menubars=lucid' '--enable-scrollbars=lucid' '--enable-dialogs=athena' '--enable-widgets=athena' '--x-includes=/usr/include' '--x-libraries=/usr/lib64' '--enable-mule' '--with-xim=xlib' '--with-xfs' '--enable-clash-detection' '--with-ldap' '--with-pop' 'build_alias=x86_64-suse-linux' 'host_alias=x86_64-suse-linux' 'target_alias=x86_64-suse-linux' 'CFLAGS=-O2 -fmessage-length=0 -Wall -D_FORTIFY_SOURCE=2 -g -Wall -Wno-switch -pipe -fno-strict-aliasing -DLDAP_DEPRECATED ' 'LDFLAGS='
XEmacs 21.5-b27 "fiddleheads" (+CVS-20060704) configured for `x86_64-suse-linux'.
Compilation Environment and Installation Defaults:
Source code location: /usr/src/packages/BUILD/xemacs-21.5.27.20060705
Installation prefix: /usr
Operating system description file: `s/linux.h'
Not using any machine description file
Compiler version: gcc (GCC) 4.1.2 20061115 (prerelease) (SUSE Linux)
- GCC specs file: specs.
- Compiler command: gcc -Wall -Wno-switch -Wundef -Wsign-compare -Wno-char-subscripts -Wpacked -Wunused-parameter -g -O2 -fmessage-length=0 -Wall -D_FORTIFY_SOURCE=2 -g -Wall -Wno-switch -pipe -fno-strict-aliasing -DLDAP_DEPRECATED
libc version:
Relocating allocator for buffers: no
GNU version of malloc: yes
- Using Doug Lea's new malloc from the GNU C Library.
Window System:
Compiling in support for the X window system:
- X Windows headers location: /usr/include
- X Windows libraries location: /usr/lib64
- Handling WM_COMMAND properly.
Compiling in support for the Athena widget set:
- Athena headers location: X11/Xaw3d
- Athena library to link: Xaw3d
Using Lucid menubars.
Using Lucid scrollbars.
Using Athena dialog boxes.
Using Athena native widgets.
TTY:
Compiling in support for ncurses.
Compiling in support for GPM (General Purpose Mouse).
Images:
Compiling in support for GIF images (builtin).
Compiling in support for XPM images.
Compiling in support for PNG images.
Compiling in support for JPEG images.
Compiling in support for TIFF images.
Compiling in support for X-Face message headers.
Sound:
Compiling in support for sound (native).
Databases:
Compiling in support for Berkeley database.
Compiling in support for GNU DBM.
Compiling in support for LDAP.
Internationalization:
Compiling in support for Mule (multi-lingual Emacs).
Compiling in support for XIM (X11R5+ I18N input method).
- Using raw Xlib to provide XIM support.
- Using XFontSet to provide bilingual menubar.
Compiling in support for Canna on Mule.
Compiling in support for the WNN input method on Mule.
Mail:
Compiling in support for POP mail retrieval.
Compiling in support for "file" mail spool file locking method.
Other Features:
Inhibiting IPv6 canonicalization at startup.
Compiling in support for dynamic shared object modules.
Using the new GC mark algorithms (KKCC).
WARNING: ---------------------------------------------------------
WARNING: The new algorithms are experimental. They are enabled by
WARNING: default for this release. Use `--disable-kkcc' to
WARNING: turn it off.
WARNING: ---------------------------------------------------------
Using the new incremental garbage collector and the new allocator.
Using POSIX sigaction() to install fault handler.
Using the new portable dumper.
Compiling in support for extra debugging code.
=============================================
No core-file found.
Yours,
M. Natiello
--
Mario.Natiello(a)math.lth.se
Professor in Applied Mathematics
Centre for Mathematical Sciences, Lund University
Box 118, S-221 00 LUND, SWEDEN Tel: +46-46-2220919
http://www.maths.lth.se/~mario Fax: +46-46-2224010
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Re: What is the status of 21.5?
17 years, 3 months
Ville Skyttä
On Tuesday 28 August 2007, Mike FABIAN wrote:
> "Stephen J. Turnbull" <stephen(a)xemacs.org> さんは書きました:
> >
> > Anyway, the question is not whether you or Steve Baur or I will be
> > happy with the release. The real question is "when will the distros
> > start installing XEmacs 21.5 as the default version of XEmacs?"
> > That's what will really mark release of 21.5.
>
> SuSE already does. That’s my fault because there were so many problems
> with the Unicode support in 21.4 that I thought 21.5 would cause less
> problems. And it really does cause less problems.
Ditto Fedora since FC-6 (about 10 months ago) mostly for the same reasons.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Re: What is the status of 21.5?
17 years, 3 months
Aidan Kehoe
Ar an t-ochtú lá is fiche de mí Lúnasa, scríobh robert delius royar:
> Mon, 27 Aug 2007 (18:08 -0700 UTC) SL Baur wrote:
>
> > The only acceptable license solution would be to port the stuff in FSF
> > Emacs. At least that's vetted.
>
> Have you seen Aquamacs (http://sourceforge.net/projects/aquamacs)? I
> believe it presents a much more Mac-like interface than do either
> X11-GNU-Emacs or Carbon Emacs. Its code is GPLed. It is supposed to
> have more complete support for unicode than do the other versions.
As I understand it, this is based on Andrew Choi’s GNU Emacs work, but with
various things included and turned on by default (like cua-mode, or whatever
that’s called on OS X) to make it friendlier to the OS X user.
> I don't suppose anyone is working on creating a CoCoa-based version.
There’s this one, based on the NeXTStep code from way back:
http://emacs-app.sourceforge.net/
--
On the quay of the little Black Sea port, where the rescued pair came once
more into contact with civilization, Dobrinton was bitten by a dog which was
assumed to be mad, though it may only have been indiscriminating. (Saki)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
ucs->big5 translation failure in 21.4.20
17 years, 3 months
Julian Bradfield
I'm not yet putting in a formal bug report, as I still have ambitions to
sort it out myself, but I'd like to mention the problem in case
somebody else already knows about it, or can guess the likely location
of the problem.
I use 21.4.20, with mule-ucs handling unicode. My packages are the
most recent sumos.
Since I'm usually dealing with old-ish Chinese, I want to
(un-define-change-charset-order '(ascii chinese-big5-1 chinese-big5-2))
so that I get big5 characters whenever possible, rather than the
default Japanese.
Unfortunately, there is a bug in the conversion from UCS to Big5: a
UCS codepoint that is found to be in the chinese-big5-2 charset is
mistranslated into an Emacs character. Depending on the precise
character, this may simply result in corruption, or it may result in a
crash.
For example, create a file containing the single character U+8F46
(corresponding to Big5 F146) in the UTF-8 encoding.
Do the above change of charset ordering, and visit the file in utf-8.
XEmacs crashes with a segfault inside buffer_insert_string_1 at
insdel.c:359.
(That's with a standard build; with a build without optimization (just
-g), it goes into an infinite loop instead.)
The problem seems to be specific to chinese-big5-2 : if I prioritize
the CNS character sets instead, it's fine - but unfortunately my big5
fonts are better than my CNS fonts, so I prefer big5, and anyway I
want to save big5 versions in parallel with utf-8 versions.
Since the translation process is an unholy mess of
semi-automatically generated CCL programs, it's, erm, challenging to
debug. If anybody has any private notes about how it all fits
together, I'd appreciate any hints!
As a side question, is all this CCL stuff necessary? Even ten years
ago, and possibly 15 years ago, I'd have thought that everything in
the Basic Multilingual Plane could be dealt with by simple look-up
tables.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
[COMMIT] Revert the last change to mule-ccl.c, on Steve Baur's objection
17 years, 3 months
Aidan Kehoe
Ar an seachtú lá is fiche de mí Lúnasa, scríobh SL Baur:
> NAK the mule-ccl.c change, it isn't necessary with your change to
> lisp.h and it makes ugly code even uglier. (And it's cargo cult
> programming. There must be no side-effects in macros due to
> multiple evaluation of parameters. Period.).
Okay, reverted.
> The change to lisp.h is OK.
>
> Are we reviewing patches any more before commit? (Question
> not a flame).
Commit-and-review is the current state of things. It is rare enough that
people (besides SJT) actually review, though (which is not a good state of
affairs; lots of Mule questions end up with myself and SJT getting cranky
with each other and no-one else injecting sense into the discussion). I tend
to directly commit without submitting patches previously more than most;
other folk tend to post patches and wait a few days before committing. But
there are exceptions in both directions.
APPROVE COMMIT
NOTE: This patch has been committed.
src/ChangeLog addition:
2007-08-28 Aidan Kehoe <kehoea(a)parhasard.net>
* mule-ccl.c (ccl_driver):
Revert the last change to mule-ccl.c, on objection from SL
Baur. The change to lisp.h in the same commit sufficed.
XEmacs Trunk source patch:
Diff command: cvs -q diff -u
Files affected: src/mule-ccl.c
===================================================================
RCS
Index: src/mule-ccl.c
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/src/mule-ccl.c,v
retrieving revision 1.34
diff -u -r1.34 mule-ccl.c
--- src/mule-ccl.c 2007/08/21 20:32:37 1.34
+++ src/mule-ccl.c 2007/08/28 09:46:04
＠＠ -1578,7 +1578,7 ＠＠
Lisp_Object map, content, attrib, value;
int point, size, fin_ic;
- j = XCHAR_OR_INT (ccl_prog[ic]); ic++; /* number of maps. */
+ j = XCHAR_OR_INT (ccl_prog[ic++]); /* number of maps. */
fin_ic = ic + j;
op = reg[rrr];
if ((j > reg[RRR]) && (j >= 0))
＠＠ -1693,7 +1693,7 ＠＠
stack_idx_of_map_multiple = 0;
map_set_rest_length =
- XCHAR_OR_INT (ccl_prog[ic]); ic++; /* number of maps and separators. */
+ XCHAR_OR_INT (ccl_prog[ic++]); /* number of maps and separators. */
fin_ic = ic + map_set_rest_length;
op = reg[rrr];
＠＠ -1880,7 +1880,7 ＠＠
{
Lisp_Object map, attrib, value, content;
int size, point;
- j = XCHAR_OR_INT (ccl_prog[ic]); ic++;/* map_id */
+ j = XCHAR_OR_INT (ccl_prog[ic++]); /* map_id */
op = reg[rrr];
if (j >= XVECTOR (Vcode_conversion_map_vector)->size)
{
--
On the quay of the little Black Sea port, where the rescued pair came once
more into contact with civilization, Dobrinton was bitten by a dog which was
assumed to be mad, though it may only have been indiscriminating. (Saki)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
