March 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Bug? - auto-show doesn't take account of minibuf prompt 25 years

Jonathan Marten - Network Systems Slough

Probably too late to go into 21.0 now, but has anybody else noticed this problem? Start with '-vanilla' to get the default auto-show options, then do something that prints a reasonably long prompt in the minibuffer (e.g. ^X^R, Om in Gnus or similar). Type or complete a long file name... nothing happens when the cursor reaches the right-hand end of the minibuffer, and you will be typing blind. The minibuffer does not scroll horizontally until a lot more text has been typed. I think what is happening is that auto-show-make-point-visible is not taking account of the prompt at the beginning of the line, therefore the minibuffer does not scroll horizontally until the cursor is that far beyond the right of its window. Unfortunately the current minibuffer prompt or its length doesn't seem to be available at Lisp level, so I have added a new function 'minibuffer-prompt-offset' to make the prompt length available to auto-show. This fixes the minibuffer scrolling problem, but if there is a better solution I'd be interested to hear... Patch originally developed on 20.4, but can be applied to 21.0.67 with no problems. (Sorry for the context diffs, but Solaris patch doesn't understand unified). ChangeLog entries can follow if this is accepted. *** src/minibuf.c.orig Sun Jul 13 23:42:49 1997 --- src/minibuf.c Mon Dec 21 07:50:04 1998 *************** *** 651,656 **** --- 651,670 ---- } #endif /* 0 */ + + DEFUN ("minibuffer-prompt-offset", Fminibuffer_prompt_offset, 0, 0, 0, /* + Return the combined display width of the minibuffer prompt and preprompt. + */ + ()) + { + int width = 0; + + if (STRINGP(Vminibuf_prompt)) width += XSTRING_LENGTH(Vminibuf_prompt); + if (STRINGP(Vminibuf_preprompt)) width += XSTRING_LENGTH(Vminibuf_preprompt); + return make_int (width); + } + + /************************************************************************/ /* echo area */ *************** *** 915,920 **** --- 929,936 ---- DEFSUBR (Fminibuffer_prompt); DEFSUBR (Fminibuffer_prompt_width); #endif + DEFSUBR (Fminibuffer_prompt_offset); + DEFSUBR (Fset_minibuffer_preprompt); DEFSUBR (Fread_minibuffer_internal); *** lisp/auto-show.el.orig Mon Jun 30 00:12:53 1997 --- lisp/auto-show.el Fri Dec 18 07:40:03 1998 *************** *** 167,172 **** --- 167,177 ---- (if (> scroll 0) 2 1))) ;how wide window is on the screen (right-col (+ scroll w-width))) + + (if (and (fboundp 'minibuffer-prompt-offset) + (eq (selected-window) (active-minibuffer-window))) + (setq col (+ col (minibuffer-prompt-offset)))) + (if (and (< col auto-show-show-left-margin-threshold) (< col (window-width)) (> scroll 0)) -- Jonathan Marten, ESG Engineer Network Systems Slough, UK jonathan.marten(a)uk.sun.com Sun Microsystems 01753 566797

1 participants
0 comments

Re: Comparison between integer and character is constant nil (?2 and 0) 25 years

SL Baur

Michael Sperber <sperber(a)informatik.uni-tuebingen.de> writes in xemacs-beta(a)xemacs.org: ... > I often see one from PSGML, but haven't had the time to track it down, > so I don't know. PSGML is clean as far as I've tracked down. > Comparison between integer and character is constant nil (?\- and 0) > [sgml-parse-comment, This one is spurious, I believe.

1 participants
0 comments

Re: Comparison between integer and character is constant nil (?2 and 0) 25 years

Michael Sperber

>>>>> "Hrvoje" == Hrvoje Niksic <hniksic(a)srce.hr> writes: Hrvoje> "Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes: >> I hope you're not talking about disabling Ebola notices by default >> in betas. I see ebola notices occasionally, and often enough >> they're bugs. Hrvoje> Can you name an example? I haven't seen a justified ebola in ages. I often see one from PSGML, but haven't had the time to track it down, so I don't know. Comparison between integer and character is constant nil (?\- and 0) [sgml-parse-comment, sgml-skip-cs, sgml-parse-catalog-buffer, sgml-cache-catalog, sgml-catalog-lookup, sgml-external-file, sgml-push-to-entity, sgml-setup-doctype, sgml-do-doctype, sgml-parse-markup-declaration, sgml-parse-prolog, sgml-load-doctype, sgml-need-dtd, sgml-parse-to, sgml-find-element-of, byte-code, sgml-indent-line, <compiled-function of unknown origin>, call-interactively] Comparison between integer and character is constant nil (?\- and 0) -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: Comparison between integer and character is constant nil (?2 and 0) 25 years

Hrvoje Niksic

"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes: > I hope you're not talking about disabling Ebola notices by default > in betas. I see ebola notices occasionally, and often enough > they're bugs. Can you name an example? I haven't seen a justified ebola in ages.

2 participants
1 comments

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

SL Baur

Hrvoje Niksic <hniksic(a)srce.hr> writes in xemacs-beta(a)xemacs.org: > SL Baur <steve(a)xemacs.org> writes: >> Dmitry Yaitskov <dimas(a)home.com> writes in xemacs-beta(a)xemacs.org: >> >> ... >> > "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.

1 participants
0 comments

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

Hrvoje Niksic

SL Baur <steve(a)xemacs.org> writes: > Dmitry Yaitskov <dimas(a)home.com> writes in xemacs-beta(a)xemacs.org: > > ... > > "Convert MS-DOG style line endings to normal line endings. > > Will somebody please fix this comment? It is impossible to fix it.

1 participants
0 comments

[offtopic] send vote for bzip to support@winzip.com 25 years

Jari Aalto

Hi, I contacted the Winzip Authors and suggested implementing bzip compression (like they did for gzip and tar) and they told that it has been on their "todo" long time, but nobody hasn't brought enought requests to their attention for it. I know XEmacs has started using bzip a lot and it would be great to have our favourite win32 compression program (winzip) to support bzip too. That's why I would like to ask everybody to send a simple request to support(a)winzip.com That would show the bzip feature is wanted. jari

1 participants
0 comments

Re: I have XEmacs running on MacOS 25 years

Ben Wing

I'm thrilled to hear this. Unfortunately I'm not actively working on XEmacs any more but I forwarded the message on to those who are. It shouldn't be too difficult to port this work to XEmacs version 21 which is the latest version. The first thing you should do is get yourself on the Beta list, which is XEmacs-beta(a)XEmacs.org, and post your patches there. As for getting the unexec mechanism working, I've written up a bunch of notes on how to do this in a fairly portable fashion, and they should be available on my architecting XEmacs website, which I think is http://www.666.com/XEmacs. Ben Pitts Jarvis wrote: > I wanted to let you know about some work that I have been doing to > port XEmacs to run on MacOS. > > Currently, I have XEmacs (version 19.14) working on MacOS 8.5.1. (In > fact, I am composing this using XEmacs on my Macintosh 8500.) > > Currently, my port uses console-tty and VT100 emulation and is quite > SLOW. My port is based on the work of Marc Parmet who ported GNU > Emacs 18.59 to Macintosh. XEmacs gives me 28 bits for addresses > compared with 26 bits for GNU Emacs. Those extra two bits make XEmacs > run smoothly on a Macintosh with 256 MB of RAM; the GNU Emacs that I > have been using must take heroic measures to run on a machine with > more than 64 MB. > > I have sub-processes working and can use the `dired', `grep', and > `diff' commands. > > The first item on my agenda is to improve perfromance; however, it is > gratifying to see XEmacs running on my Macintosh desktop. > > At this point, I cannot dump an initialized XEmacs (I must loadup all > of the lisp initialization files every time I launch XEmacs.) > > I believe that XEmacs and GNU Emacs are sufficiently different that > the unexec code found in the existing GNU (18.59) implementation will > be of limited value to me. > > If you could give me some help and/or guidance about what I should do > to dump an initialized XEmacs, I would be greatly appreciative. -- Ben Wing - If this message is long and typed, someone else typed it for me - If it has a .rm (RealAudio) attachment, see http://www.real.com/products/player/downloadrealplayer.html?wp=dl0498 - If this doesn't work and there's a GSM WAV attachment, see http://xanim.va.pubnix.com/home.html

1 participants
0 comments

Re: Comparison between integer and character is constant nil (?2 and 0) 25 years

SL Baur

Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp> writes in xemacs-beta(a)xemacs.org: > ... Is there a way to turn them into an error (so that you can setq > debug-on-error t before "doing that")? I've found them hard to > localize because XEmacs doesn't stop when they occur. Other than putting a breakpoint in `eq_with_ebola_notice' under a debugger, no.

1 participants
0 comments

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

SL Baur

Dmitry Yaitskov <dimas(a)home.com> writes in xemacs-beta(a)xemacs.org: ... > "Convert MS-DOG style line endings to normal line endings. Will somebody please fix this comment?

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 March 1999