March 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Ben Wing

I've compiled a short list of bugs that I consider to be showstoppers for the 21.0 release. It's located at: http://devel.xemacs.org/xemacs/showstoppers.html Ben (typed by Martin)

6 participants
6 comments

Re: gud.el broken or is it just me? 23 years, 6 months

SL Baur

Aki Vehtari <Aki.Vehtari(a)hut.fi> writes in xemacs-beta(a)xemacs.org: ... > Btw. gud.el in XEmacs is dated 1993 and gud.el in emacs-20.3 is > dated 1998. Unfortunately gud.el in emacs-20.3 does not work in > XEmacs and I don't know much work it would need to make it work and I've done the initial port of gud.el to XEmacs. It mostly works[1], but it sorely lacks the functionality in gdbsrc.el. Making a gudsrc.el mode is on my list of things to do. It was in ftp://altair.xemacs.org/pub/xemacs-futures/ when I was on the 'net. It was delayed integration into the XEmacs packages pending 21.0 release. I also have a ported cua-mode.el to integrate. NOTE: The gud.el and cua-mode.el XEmacs portings are courtesy of Altrasoft, Inc. Thank you Altrasoft. Footnotes: [1] I have a report that my port does not work on Solaris with dbx.

2 participants
1 comments

RoboCup 23 years, 9 months

Akram Khodadadi

Hello Please answer my question. We maked a player in Linux with Lisp languaege ,but we dont know how to make a UDP connection between our player and the server with Lisp languaege. We looked in many sources ,but we didn't attain any affects. Please say to us for making a UDP connection and geting and sending messages with that Lisp languaege which orders . Please explan with an example. Thanks Mrs Khodadadi

3 participants
2 comments

Assertion failure int event-msw.c 25 years, 6 months

David Bush

On repeated exposure events in the Cygwin build I get an assertion failure in mswindows_dequeue_dispatch_event. I've never looked at this code before so there is little chance I could resolve the issue by the deadline for the next beta. If no one else can get a quick handle on the problem I will look more closely fore the following beta. I found it easy to reproduce the problem in gnus by simply getting into a newsgroup and repeatedly covering part of the Xemacs frame and then minimizing the covering window.

4 participants
7 comments

A few problems with XEmacs 21.2.11. 25 years, 6 months

Dan Glastonbury

G'Day, I'm having a problem with package management and Shell-script mode with font-lock-mode. Firstly to the Shell-script mode problem. If I load a shell script, say my .bashrc file, and then try turning on font-locking, the following message appears in the mini buffer: No match 2 in highlight (2 font-lock-comment-face t) This occurs if I start xemacs with xemacs, xemacs -vanilla, xemacs -q -no-site-file. My other problem is when I try required packages in the package list buffer with the `r' key. I get in the mini-buffer" Wrong type argument: number-char-or-marker-p, nil How do I fix these problems?! I'm running XEmacs 21.2.11 on Windows NT/SP4 (XEmacs 21.2 "Calliope" (cygwin32) of Tue Mar 02 1999 on polyester) with version 1.08 of sh-script package and thanks in advance Dan --KAA00789.921540713/gauss.adelaide.maptek.com.au Content-Type: text/plain -- Daniel Glastonbury <dan at adelaide.maptek.com.au> --------------------------------------------------- It is so hot in some parts of the world that the people there have to live other places.

2 participants
1 comments

[21.0b62] mouse copy and paste on NT4.0 25 years, 6 months

Roger Wimmer

Hi I have built Xemacs 21.0b62 on NT 4.0. All works fine except the mouse binding. I can highlight a region with the left button of the mouse. But if i try to paste the selection with the middle button, nothing appears in the buffer. But I have the following error message in the minibuffer: "Kill ring is empty" When I use C-Insert after highlighting the region, paste with the middle button works fine. How can I change that the highlighted region is in the kill ring? Roger -- Lieber wenige Programme die laufen als viele die abstuerzen! (Ein gluecklicher SUN-user ;-) Aber zuhause hat man ja Zeit zum Basteln.

2 participants
1 comments

Re: pop3.el - treating "From " at the beginning of lines 25 years, 7 months

Dmitry Yaitskov

Andy Piper <andy(a)xemacs.org> wrote: > At 12:34 PM 3/30/99 +0200, Hrvoje Niksic wrote: > >SL Baur <steve(a)xemacs.org> writes: > > > >> >> > "Convert MS-DOG style line endings to normal line endings. > >> >> > >> >> Will somebody please fix this comment? > >> > >> > It is impossible to fix it. > >> > >> I thought we had agreed that comments referring to `MS-DOG' were lame > >> and should be removed from the code. > > > >Yes, but we had also agreed not to change packages written by external > >contributors. Isn't pop3.el such a package? > > Not anymore, heh, heh :) > > andy Yes, I suppose it is okay to change that comment, here's what Stainless Steel Rat <ratinox(a)peorth.gweep.net> (who wrote the code I think) said to me in the pgnus list about that pop3.el: <snip> > No, just not my code. And I've asked them to change the name because it is > not my code. Either they have not, or you have an older version. <snip> So I think it's ok to change the comment. Here's my patch with the changed comment: ----------------------------cut here------------------------------- --- e:\bin\XEmacs\xemacs-packages\lisp\mail-lib\pop3.el Mon Mar 08 22:36:12 1999 +++ pop3.el Tue Mar 30 12:46:08 1999 ＠＠ -309,13 +309,17 ＠＠ (funcall pop3-read-passwd prompt)) (defun pop3-clean-region (start end) - "Convert MS-DOG style line endings to normal line endings. -Also remove '.' from the beginning of lines." + "Convert CRLF line endings to LF line endings. +Also remove '.' from the beginning of lines. +Also escape 'From ' after '\n\n' with '>' (for mbox)." (setq end (set-marker (make-marker) end)) (save-excursion (goto-char start) (while (and (< (point) end) (search-forward "\r\n" end t)) (replace-match "\n" t t)) + (goto-char start) + (while (re-search-forward "\n\n\\(From \\)" end t) + (replace-match "\n\n>\\1" t nil)) (goto-char start) (while (and (< (point) end) (re-search-forward "^\\." end t)) (replace-match "" t t) ----------------------------cut here------------------------------- I still am not sure this is the best place to do it - it makes sense only for mbox, but it IMHO surely beats losing mail. FWIW. -- Cheers, -Dima.

2 participants
1 comments

Re: 'quoted-insert broken?' 25 years, 7 months

Adrian Aichner

>>>>> "Matthew" == Matthew Persico <Matthew.Persico(a)lazard.com> writes: Matthew> Ok. Here it is. I started xemacs like this: Matthew> xemacs foo.c Matthew> where foo.c does not exist. I set the debug on error Matthew> option on and then entered this text in the foo.c buffer: Matthew> main() { Matthew> int i; Matthew> I then placed the cursor AFTER the semi-colon on line 2 Matthew> and attempted to put a tab in, as if to space a trailing Matthew> comment, and got this text in the *Backtrace* buffer: Matthew> Signaling: (wrong-type-argument integerp ?\t) Matthew> int-char(?\t) Matthew> read-quoted-char() Matthew> quoted-insert(1) Matthew> call-interactively(quoted-insert) Matthew, seemse like your 21.2-b13 no-mule has a different definition of `quoted-insert' than mine, 21.2-b13 mule, native Windows NT. Did you apply any patches, namely to simple.el? My definition of the function comes from d:\export\home\tmp\21.2\xemacs\lisp\simple.el and does not attempt to convert the `integer' ?\t (which it is not) into a character (which it already is). When I evaluate this: (int-char ?\t) I get that: Signaling: (wrong-type-argument integerp ?\t) int-char(?\t) eval((int-char ?\t)) eval-interactive((int-char ?\t)) eval-last-sexp(nil) call-interactively(eval-last-sexp) Try M-x find-function RET quoted-insert RET and see where it takes you. My suspision is that you get a bad definition of that function. Let's see whether I'm correct. Adrian Matthew> Do you need more? Matthew> -------- Original Message -------- Matthew> Subject: Re: 'quoted-insert' broken? Matthew> Date: 26 Mar 1999 23:42:29 +0100 Matthew> From: Adrian Aichner <aichner(a)ecf.teradyne.com> Matthew> To: xemacs-beta(a)xemacs.org Matthew> References: Matthew> <A69969F402E9B0228525674000774A6B.007770C280256740(a)notes.teradyne.com> >>>>> "Matthew" == Matthew Persico <Matthew.Persico(a)lazard.com> writes: Matthew> Running xemacs 21.2.13 on sloaris 2.6, no mule. Tried to Matthew> type keystrokes 'C-q tab' in cperl and c modes to get a Matthew> tab at the end of the line before a comment. I got this Matthew> error: Matthew> wrong type argument: integerp, ?\t Matthew> What other info/steps are required to help diagnose? Matthew> Try Matthew> Options -> General Options -> Debug On Error Matthew> run the offending operation and send the contents of Matthew> *Backtrace* to this list. Matthew> Regards, Matthew> Adrian Matthew> Matthew O. Persico Matthew> http://www.lazard.com Matthew> Opinions expressed are MINE, not Lazard's. Matthew> -- Matthew> Adrian Aichner Teradyne GmbH, European Design Center Matthew> Integra Test Division Telephone +49/89/41861(0)-208 Matthew> Dingolfinger Strasse 2 Fax +49/89/41861-217 (What is a Fax?) Matthew> D-81673 MUENCHEN E-mail adrian.aichner(a)teradyne.com -- Adrian Aichner Teradyne GmbH, European Design Center Integra Test Division Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-217 (What is a Fax?) D-81673 MUENCHEN E-mail adrian.aichner(a)teradyne.com

2 participants
1 comments

Re: completion-ignored-extensions 25 years, 8 months

John Jones

>>>>> Didier Verna writes: > I find the default value of this variable particularly agressive > and arbitrary. I think it should be reduced to the minimum, like > binary files or so. I think the default matches what many users would want. For example, many of the entries are there from TeX/LaTeX. This wouldn't affect non-TeX users (so no harm done) and it is really nice for people who do use TeX. Occasionally, one may want to visit one of the various auxillary files like a .toc file, but that is pretty rare (and is never for most users). The way things are, you can still edit the .toc file, you just can't complete to it. John Jones jj(a)asu.edu

3 participants
3 comments

BUG REPORT: Custom Unwanted Face/Color interaction 25 years, 8 months

Martin Buchholz

Let me add a bug report to the custom faces debate. Being perverse, I like my shell buffers to look different from all my other buffers. So I do something like this: (add-hook 'shell-mode-hook (lambda () (set-face-background 'default "midnightblue" (current-buffer)))) If I start a shell, then change fonts by doing Options->Size->14, my font sizes do indeed change, but my background color customization is gone. Subsequently started shell buffers are back to midnightblue.

2 participants
1 comments

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

XEmacs-Beta March 1999