June 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Redisplay while evaluating Lisp code 26 years, 5 months

Hrvoje Niksic

Do this simple test. Evaluate (while t), and while XEmacs is looping, minimize it and then maximize it. Under X, the frame is not redrawn, and this has been the case since as long as I've used XEmacs (19.12). However, under Windows this is handled correctly -- redisplay is invoked even when XEmacs is evaluating Lisp code. Just how did you guys do that?! :-) Perhaps Ben can shed additional light on this? -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Which is worse: ignorance or apathy? Who knows? Who cares?

3 participants
2 comments

Re: [PROPOSAL] fix for bad Xrefs in man/*.texi 26 years, 5 months

SL Baur

Adrian Aichner <aichner(a)ecf.teradyne.com> writes: > Hello texi-perts! > Seems like the info manuals can almost be produced by xemacs -batch, > hence removing the requirement for the makeinfo program, provided the > man/ Makefiles get adjusted or the step is performed manual (see > interactive function `makeinfo-file' atend. Using makeinfo is a feature not a bug. The texinfo files are not intended to be formatted by the end user. Formatting documents with multibyte characters with XEmacs/Mule was done out of expediency (I still have no capability for dealing with TeX documents with multibyte characters outside of XEmacs/Mule). Formatting with the editor instead of makeinfo is much slower. The info files are provided in a standard tarball so there isn't a need to work around the possible absence of makeinfo.

1 participants
0 comments

Re: more info on my gnus problems on digital unix w. 21.0b42 26 years, 5 months

Hrvoje Niksic

Andrew J Cosgriff <ajc(a)bing.wattle.id.au> writes: > looks like it's open-network-stream (or -internal) that's causing all my > grief - anything else i've tried (zenirc, ldap-search, etc.) exhibits a > similar problem - > > Signaling: (wrong-type-argument stringp open-network-stream-internal) > string-match("^Unknown host" open-network-stream-internal) > byte-code("..." [string-match "^Unknown host" data zenirc-message buffer > conn$ > zenirc-establish-server-connection(#<buffer "*zenirc*">) > zenirc(nil) Try loading uncompiled zenirc (something like (load "zenirc.el")) and getting the backtrace. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Personifiers Unite! You have nothing to lose but Mr. Dignity!

2 participants
1 comments

[PROPOSAL] fix for bad Xrefs in man/*.texi 26 years, 5 months

Adrian Aichner

Hello texi-perts! Seems like the info manuals can almost be produced by xemacs -batch, hence removing the requirement for the makeinfo program, provided the man/ Makefiles get adjusted or the step is performed manual (see interactive function `makeinfo-file' atend. Please let me know if you find a flaw with my below assessment and suggestions. Thanks, Adrian Some issues: 1. `batch-texinfo-format' goes into infinite recursion when called with a directory argument. I'll submit a patch for this. This is probably not a critical bug since translating all individual .texi files in a directory will not produce valid info files anyway (e.g. "makeinfo -o internals.info internals.texi" will produce a proper lispref info manual, not "makeinfo *.texi"). 2. I've noticed some breakage in cross-references between manuals for internals lispref new-users-guide xemacs in 21.0-b42 (and 20.3 as well). Please notice the empty fourth argument to many .*ref{} constructs. In places where `emacs' is the fourth agument, it should rather be `xemacs' since there is no emacs.texi in XEmacs. It's called xemacs.texi here. I'll submit a patch the fix these references to work for current filenames used. cd /export/home/tmp/CVSroot/xemacs-20/man/ find . -type d $ -name SCCS -o -name RCS $ -prune -o $ -type f -o -type l $ -name "*.texi" -exec grep -n '＠[a-z]ref.*,,.*}' "{}" /dev/null \; Compilation started at Mon Jun 8 21:17:24 1998 ./custom.texi:151:＠xref{Sexp Types,,,widget,The Widget Library}, for information about ./texinfo.texi:13767:＠xref{Definition Commands}, and ＠ref{deffnx,, Def Cmds in Detail}. ./texinfo.texi:13833:＠xref{Definition Commands}, and ＠ref{deffnx,, Def Cmds in Detail}. ./texinfo.texi:13855:＠xref{Definition Commands}, and ＠ref{deffnx,, Def Cmds in Detail}. ./texinfo.texi:13941:＠xref{dots,,＠code{＠＠dots＠{＠}}}. ./texinfo.texi:14252:＠xref{pounds,,＠code{＠＠pounds＠{＠}}}. ./texinfo.texi:14355:Generate a minimal title page. ＠xref{titlepage,,＠code{＠＠titlepage}}. ./internals/internals.texi:5734:case. ＠xref{Case Tables,,, lispref, XEmacs Lisp Programmer's Manual}. ./internals/internals.texi:5738:case. ＠xref{Case Tables,,, lispref, XEmacs Lisp Programmer's Manual}. ./internals/internals.texi:5747:＠xref{Case Tables,,, lispref, XEmacs Lisp Programmer's Manual}. ./internals/internals.texi:5758:＠xref{Markers,,, lispref, XEmacs Lisp Programmer's Manual}. ./lispref/commands.texi:2301: ＠xref{Disabling,,, emacs, The XEmacs Reference Manual}, for the details on ./lispref/frames.texi:142:created. ＠xref{Resources X,, X Resources, emacs, The XEmacs User's Manual}. ./lispref/os.texi:198: ＠xref{Init File Examples,,, emacs, The XEmacs Reference Manual}, for ./lispref/text.texi:1135:boundaries. ＠xref{Paragraphs,,, emacs, The XEmacs User's Manual}. ./new-users-guide/custom1.texi:147:mode. ＠xref{Major Modes,,,,XEmacs User's Manual}, for more ./new-users-guide/custom2.texi:197:file. ＠xref{Variables,,,,XEmacs User's Manual}, for information on ./new-users-guide/custom2.texi:427:＠xref{Init File,,,,XEmacs User's Manual}. You should also look at ./new-users-guide/edit.texi:85:＠xref{Filling,,,,XEmacs User's Manual}, for information on using Auto Fill ./new-users-guide/edit.texi:290: ＠xref{Undoing Changes,,,,XEmacs User's Manual}, for more information on ./new-users-guide/enter.texi:124:again. ＠xref{Exiting Emacs,,,,XEmacs User's Manual}. ./new-users-guide/enter.texi:171:in ＠var{buf}. ＠xref{Buffers,,,,XEmacs User's Manual}. ./new-users-guide/files.texi:74:＠xref{File Names,,,,XEmacs User's Manual}. ./new-users-guide/files.texi:200:＠xref{Reverting,,,,XEmacs User's Manual}. ./new-users-guide/files.texi:212:backups, ＠xref{Backup,,,,XEmacs User's Manual}. ./new-users-guide/files.texi:222:auto-saving, ＠xref{Auto Save Files,,,,XEmacs User's Manual}. ./new-users-guide/files.texi:231:editing, ＠xref{Interlocking,,,,XEmacs User's Manual}. ./new-users-guide/modes.texi:69:commands. ＠xref{Nroff Mode,,,,XEmacs User's Manual}, for information ./new-users-guide/modes.texi:103:commands. ＠xref{C Indent,,,,XEmacs User's Manual}. ./new-users-guide/modes.texi:114:information on this mode, ＠xref{Fortran,,,,XEmacs User's Manual}. ./new-users-guide/modes.texi:119:text characters. ＠xref{Picture,,,,XEmacs User's Manual}, for more ./new-users-guide/modes.texi:219: ＠xref{Abbrevs,,,,XEmacs User's Manual}, for more information on this ./new-users-guide/region.texi:103: ＠xref{Selecting Text with the Mouse,,,,XEmacs User's Manual}, for ./new-users-guide/region.texi:125:region. ＠xref{Killing,,,,XEmacs User's Manual}, for more information. ./new-users-guide/region.texi:141:＠xref{Indentation,,,,XEmacs User's Manual}, for more information. ./new-users-guide/region.texi:227:＠xref{Accumulating Text,,,,XEmacs User's Manual}, for more ./new-users-guide/region.texi:231:areas of text. ＠xref{Rectangles,,,,XEmacs User's Manual}, for more ./new-users-guide/region.texi:239:manipulate registers ＠xref{Registers,,,,XEmacs User's Manual}. ./new-users-guide/new-users-guide.texi:224:commands relevant to a topic. ＠xref{Help,,,,XEmacs User's Manual}. ./new-users-guide/new-users-guide.texi:234:＠xref{Customization,,,,XEmacs User's Manual}. ./new-users-guide/search.texi:75:expressions, ＠xref{Search,,,,XEmacs User's Manual}. ./new-users-guide/xmenu.texi:103:＠xref{Sending Mail,,,,XEmacs User's Manual}, for information on how ./new-users-guide/xmenu.texi:302:applications. ＠xref{X Clipboard Selection,,,,XEmacs User's Manual}, ./new-users-guide/xmenu.texi:389:on. ＠xref{Customization,,,,XEmacs User's Manual}, for more ./xemacs/files.texi:187:prints a warning message. ＠xref{Interlocking,,Simultaneous Editing}. ./xemacs/files.texi:370:＠xref{Interlocking,, Simultaneous Editing}. ./xemacs/glossary.texi:218:＠xref{ListDir,,Directories}. ./xemacs/glossary.texi:313:that character (in ordinary editing modes). ＠xref{Basic,,Basic Editing}. ./xemacs/glossary.texi:656:user to investigate them. ＠xref{Interlocking,,Simultaneous Editing}. ./xemacs/killing.texi:753:＠xref{RegRect,,Rectangle Registers}. igrep finished at Mon Jun 8 21:17:32 3. Would it be desireable to remove the dependency on `makeinfo' and use "xemacs -no-site-file -no-init-file -batch -l texinfmt -f \ batch-texinfo-format FILE" instead? I couldn't get makeinfo.exe compiled on Windows NT, so this seems a worthwhile approach to me. Here is what I use successfully on UNIX and NT as well: (defun makeinfo-file (file) "Run XEmacs in batch-mode in a compilation buffer to produce info files from Texinfo input FILE." (interactive "fXEmacs Texinfo file: ") (cd (file-name-directory file)) (compile (concat (expand-file-name "../src/xemacs" source-directory) " -no-site-file -no-init-file" " -batch -l texinfmt -f batch-texinfo-format" " " file))) 4. texinfmt.el does not support ＠uref and support for ＠email is rudimentary. I may submit a patch for that as well. 5. Should we introduce angle brackets around email addresses? Any comments? -- Adrian Aichner Applications Engineer Teradyne GmbH Semiconductor Test Group Telephone +49/89/41861(0)-208 Dingolfinger Straße 2 Fax +49/89/41861-217 D-81673 MÜNCHEN E-mail aichner(a)ecf.teradyne.com

2 participants
1 comments

Info warnings 26 years, 5 months

Hrvoje Niksic

OK, for quite a few betas Info has been pretty insistent in throwing warnings in my face. I was kind of hoping this would be resolved, so I stayed silent. However, it is not getting solved, so I have to speak up. The warning is this: (1) (info/notice) Outdated info dir file: /usr/local/info/dir Of course, I don't even have permission to modify the /usr/local/info/dir file, and neither has any of the users on the machine I run XEmacs on. So, the warning will be seen by all of them, and likely many more of our users in the world. What is the *purpose* of this warning, anyway? Warnings should inform the user of a condition he/she should remedy. I don't see how I could remedy this -- even if I bug my sysadmin into updating `dir', it will get outdated the first time he installs another package. I don't even see why I *should* remedy this situation, because XEmacs appears perfectly able to deal with the situation. I believe my situation is not unique to me, as others on this list used to complain in pretty much the same way (Jan Vroonhof and Mike Sperber to name some, unless I am misremembering.) So, I would like to ask the person who introduced the warning to take it out, or give us a good reason why it should remain. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Your lucky number today is 29842924728. Look for it everywhere.

2 participants
1 comments

Re: 21.0-b42: Success under WinNT 26 years, 5 months

Martin Buchholz

>>>>> "Hrvoje" == Hrvoje Niksic <hniksic(a)srce.hr> writes: Hrvoje> Martin, we'll *have* to resolve current INLINE yuckage somehow. I, Hrvoje> for one, would expect INLINE to expand either to `inline' or nothing. Yup. Especially given that: - CONST resolving to either `const' or `' suggests INLINE should resolve to `inline' or `'. - Stallmacs 20.2 has this (primitive) code that at least conforms to the standard intuition: /* If using GNU, then support inline function declarations. */ #ifdef __GNUC__ #define INLINE __inline__ #else #define INLINE #endif In 21.1 we should (will?): - nuke CONST by renaming to `const', in accord with AC_C_CONST. - start using `inline' liberally in .c files for small or heavily called static functions. - rename INLINE to something more meaningful. Hmmmmm..... Can't think of a good name .... maybe EXTERN_INLINE or HEADER_INLINE or INLINE_FUNCTION_USED_WITHIN_MULTIPLE_COMPILATION_UNITS ?? Martin

1 participants
0 comments

Re: ????? 26 years, 5 months

Didier Verna

Hrvoje Niksic <hniksic(a)srce.hr> writes: > Didier Verna <verna(a)inf.enst.fr> writes: > > > It doesn't contain the simplest reference to the message that > > produced the error. Not even a reminder of the subject line or > > something. > > OK, now we at least have something to work with. Note that this remark was in my first message already. > When one is posting to a patches-only no-discussion mailing list, why > should it be so strange that the robot moderator rejects the message? I never said it was strange. > In the first incarnation, the robot would reject the message with _no_ > feedback. This is much better, so we *do* give a damn what he says > apart from diff -u. Much better, I wouldn't go that far ... > > There could be a more friendly message instead, like "This list is > > for patches only. If your message contains a bug report or general > > comments on xemacs, please try xemacs-beta", but not just "You > > lost. Try again." > > I'll ask Kyle to implement this. It's been a while since she posted something here. Did she leave the list ? -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C214 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 80 72 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19

2 participants
1 comments

BS/DEL change on TTY's 26 years, 5 months

Hrvoje Niksic

Something looks mightily wrong with BS/DEL on TTY's. I am working on a "normal" TTY which emits ?\177 for key-above-enter, and `stty erase' is ^?. However, in XEmacs, pressing `C-h c DEL' produces: BS runs the command delete-backward-char WTF? Now I tried `C-q DEL', and I got ^H inserted in the buffer! I tried `C-q C-h' and it also inserts C-h. In XEmacs 20.3, the same inserts ^H and ^? respectively. While this change is guided with good intentions, I believe it obfuscates the distinction between C-h and C-? further, and it should be rethought before the release. To sum it up, I believe pressing `C-q DEL' should result with C-?, not C-h being inserted to the buffer. Compare with `C-q up' on TTY's. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- "Listen, kid, we're all in it together!" -- Harry Tuttle in _Brazil_

3 participants
2 comments

Re: browse-url.el 26 years, 5 months

Barry A. Warsaw

Thanks for the bug fix Martin. Actually, browse-url-grail doesn't need to ignore the new-window argument... -Barry -------------------- snip snip -------------------- (defun browse-url-grail (url &optional new-window) "Ask the Grail WWW browser to load URL. Default to the URL around or before point. Runs the program in the variable `browse-url-grail'." (interactive (browse-url-interactive-arg "Grail URL: ")) (message "Sending URL to Grail...") (save-excursion (set-buffer (get-buffer-create " *Shell Command Output*")) (erase-buffer) ;; don't worry about this failing. (if new-window (call-process browse-url-grail nil 0 nil "-b" url) (call-process browse-url-grail nil 0 nil url)) (message "Sending URL to Grail... done")))

1 participants
0 comments

Re: ????? 26 years, 5 months

Hrvoje Niksic

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > Tot stay on topic, how often does the human moderator look at the > reject cue? Judging from experience, every day. But I can't really guarantee that. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- The end of the world is coming... SAVE YOUR BUFFERS!

1 participants
0 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 June 1998