November 2000 - XEmacs-Beta - XEmacs Mailing List Archives

Small windows with scroll-step set 24 years

Mike Alexander

The problem described in <http://www.xemacs.org/list-archives/xemacs-beta/200003/msg00645.html> is still occurring for me sometimes. This causes random crashes if you have a value set for scroll-step. One way that I've made it happen, although not every time, is to run XEmacs -vanilla, immediately use M-: (i.e., don't type into the *scratch* buffer) to set toolbar-visible-p and gutter-buffers-tab-visible-p to nil and scroll-step to 15, then do a File->Save As. This doesn't make much sense to do since it tries to save the default *scratch* buffer, but it sometimes causes the crash. The patch below avoids this problem. It occurs if the height of a window is so small that not even one line can be formatted in it. In this case the line cache will always be empty and point-in-line-start-cache will return -1 which was causing vmotion-1 to assert. I looked at the various callers of vmotion-1 and it appears that it is reasonable to just have it return the input point unchanged in this case, so that's what I did. If this is not the right thing to do, I'd be happy to hear alternative suggestions. Mike 2000-04-29 Mike Alexander <mta(a)arbortext.com> * indent.c (vmotion_1): If point_in_line_start_cache fails simply return the input position instead of asserting out. Index: src/indent.c =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs/src/indent.c,v retrieving revision 1.9.2.4 diff -u -r1.9.2.4 indent.c --- indent.c 2000/02/07 07:59:19 1.9.2.4 +++ indent.c 2000/04/29 06:58:00 ＠＠ -624,8 +624,15 ＠＠ /* #### This assertion must be true before the if statements are hit but may possibly be wrong after the call to point_in_line_start_cache if orig is outside of the visible - region of the buffer. Handle this. */ - assert (elt >= 0); + region of the buffer. Handle this. + + This occurs sometimes if scroll-step is non-zero and the window + is very small. In this case it's not possible to lay out any lines + in the window and point_in_line_start_cache returns -1 because + the line cache is empty. In this case we will just return the + original point and hope for the best. */ + if (elt < 0) + return orig; /* Moving downward. */ if (vtarget > 0)

2 participants
2 comments

Re: file-truename in Windows native build 24 years

Gleb Arshinov

>>>>> "Andy" == Andy Piper <andyp(a)bea.com> writes: Dan> At 12:23 AM 9/1/00 +0200, Dan Holmsand wrote: Dan> Dan> I totally agree. In fact I also started to fix this a while Dan> ago... Dan> Andy> I'm going to apply this unless anyone has any objections. I Andy> don't think it conflicts with Mike's patch and adds Andy> functionality for cygwin. Please do. I've been using this patch for some time with improved functionality and no additional problems on XEmacs NT. Gleb

1 participants
0 comments

Re: Small windows with scroll-step set 24 years

Jan Vroonhof

Andy Piper <andyp(a)bea.com> writes: > Did this ever get applied? Is it relevant? It should not be needed anymore since I fixed the underlying problem with the line_start_cache[1]. Jan Footnotes: [1] After two years(1!) of Gunnar and me hunting for it. Which it why it doesn't surprise me at all you found your self in the snake pit with regard to the widgets

1 participants
0 comments

Re: Error Starting VM in XEmacs 21.2 b36 24 years

Gunnar Evermann

Craig Lanning <lanning(a)scra.org> writes: > Now XEmacs just picks what seems to be a random time and freezes. > Does anyone have an idea of how I might track this down? attach a debugger and get a backtrace, e.g. 'gdb xemacs <PID>'. Gunnar

1 participants
0 comments

Re: Attention Mule users... 24 years

Nickolay Pakoulin

>>>>> "NVP" == Nick V Pakoulin <npak(a)ispras.ru> writes: NVP> After some hacking I made it print russian text. The patch below Sorry for the patch ;)) The previous "patch" is an example of postscript printing with russian text. NVP> contains changes to ps-mule that I made to enable printing in russian. Now the real patch. Nick.

1 participants
0 comments

Re: Commenting out code in lisp 24 years

Adrian Aichner

>>>>> "Stephen" == Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp> writes: Stephen> Shouldn't this discussion be on xemacs-beta? I agree. >>>>> "APA" == Adrian Aichner <Adrian.Aichner(a)t-online.de> writes: APA> For 1: APA> comment-region without prefix argument should default to prefix APA> argument of 3 in lisp modes or bind comment-start to ";;;". Stephen> I find triply commented code hard to mesh with the Stephen> surrounding code, unless it's the whole function. I should have made my intent clearer. My concern is about code which gets commented out quickly in a block because that code doesn't work in XEmacs, is no longer needed, etc. Some people do this using comment-region. By default, the region will get commented with single ;. The next guy changing the file and re-indenting that function will see this comment block jump to comment-column. This makes lines excessively long and, more importantly, C-u comment-region can no longer uncomment that block. Using double-semicolon will set up the same re-indentation trap and make uncomment-region impossible. If my proposal to comment broken or unneeded blocks of code (if they shouldn't be deleted alltogether) by triple semicolon makes sense, then we should make it the dafault. Few people will actually use C-3 comment-region to do this. Stephen> I prefer to comment with double semicolons, which Stephen> indicates the nesting depth of the commented code. I like this commenting style to document tricky pieces of code. End-of-line comments I don't like much, because it brings up all these line-up and filling issues. This will still leave us with indentation issues when merging or changing externally maintained code. However, re-indenting XEmacs core lisp files (unless otherwise noted explicitely) should be harmless and desirable. I want to actually take advantage of the great auto-indent feature of XEmacs! Whenever I feel an urge for manual indentation I'll fire up MS Visual Studio -> MS Visual Basic. :-) What does everybody think about this issue? Best regards, Adrian Stephen> Highly personal of course, and I don't feel that strongly Stephen> about it. (I rarely use comment-region.) Stephen> -- Stephen> University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Stephen> Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 Stephen> _________________ _________________ _________________ _________________ Stephen> What are those straight lines for? "XEmacs rules." -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org

2 participants
1 comments

Re: Attention Mule users... 24 years

Nickolay Pakoulin

>>>>> "JV" == Jan Vroonhof <jan.vroonhof(a)ntlworld.com> writes: JV> npak(a)ispras.ru (Nick V. Pakoulin) writes: JV> 2. Can you print a text in your native language/charset? >> No. When I try to print the following phrase in russian: >> >> ðÒÏ×ÅÒËÁ ÒÕÓÓËÏÇÏ ÔÅËÓÔÁ (Test of russian text) >> >> I get the error in function `ps-output-string-prim': (args-out-of-range >> ["\\000" "\\001" "\\002" "\\003" "\\004" "\\005" "\\006" "\\364" "\\365" >> "\\366" "\\367" "\\370" "\\371" "\\372" "\\373" "\\374" "\\375" "\\376" >> "\\377"] ?ð) >> >> I played with `ps-multibyte-buffer', setting it to all allowed values (see >> ps-mule.el), but nothing changed. JV> Could you do a debug-on-entry on ps-mule-string-encoding and single-step? JV> In particular is the line (encode-coding-string str encoding), hit? If no JV> what is the value of 'encoding' if yet, what is the value of 'encoding' JV> and what does encode-coding-string return? After some hacking I made it print russian text. The patch below contains changes to ps-mule that I made to enable printing in russian. But it is not enough -- ps-mule uses undefined function `chars-in-region' and i supposed that it should be something like (defun chars-in-region (from to) (- to from)) ps-mule uses cyrillic-iso-8bit encoding for russian. XEmacs seems not to have such coding system so I defaliased it to iso-8859-5: (define-coding-system-alias 'cyrillic-iso-8bit 'iso-8859-5) This is rather raw solution but it works for me now. JV> Jan Nick.

1 participants
0 comments

vm crashes on linux console 24 years

Giacomo Boffi

This bug report will be sent to the XEmacs Development Team, not to your local site managers!! Please write in English, because the XEmacs maintainers do not have translators to read other languages for them. In XEmacs 21.2 (beta34) "Molpe" [Lucid] (i586-pc-linux) of Tue Jul 18 2000 on boffi95 configured using `configure --extra-verbose --without-wmcommand --with-athena=3d --with-modules --debug --error-checking=none --use-union-type --with-clash-detection --rel-alloc' Please describe exactly what actions triggered the bug and the precise symptoms of the bug: i started xemacs on linux console, then i started vm (M-x vm RET), bang Recent keystrokes: inappropriate Lisp backtrace follows: # (unwind-protect ...) # (unwind-protect ...) # (catch #<INTERNAL OBJECT (XEmacs bug?) (opaque-ptr, adr=0x81e9df8) 0x823bd68> ...) # (unwind-protect ...) # bind (inhibit-quit frame-being-created) make-frame(nil) # bind (params types) vm-goto-new-frame(primary-folder folder) apply(vm-goto-new-frame (primary-folder folder)) # bind (w types) vm-goto-new-folder-frame-maybe(primary-folder folder) apply(vm-goto-new-folder-frame-maybe (primary-folder folder)) # bind (full-startup did-read-index-file folder-buffer first-time totals-blurb preserve-auto-save-file) byte-code("..." [bufferp folder nil preserve-auto-save-file totals-blurb first-time folder-buffer did-read-index-file full-startup expand-file-name vm-primary-inbox vm-folder-directory file file-directory-p error "%s is a directory" vm-get-file-buffer default-directory t no-conversion coding-system-for-read default-enable-multibyte-characters enable-local-variables inhibit-local-variables message "Reading %s..." find-file-noselect item vm-folder-history "Reading %s... done" vm-fsfemacs-mule-p enable-multibyte-characters set-buffer-multibyte buffer-file-coding-system current-load-list vm-xemacs-mule-p get-coding-system no-conversion-unix no-conversion-dos no-conversion-mac binary buffer-modified-p omodified buffer-read-only ((set-buffer-modified-p omodified)) encode-coding-region set-buffer-file-coding-system decode-coding-region coding-system-base ((set-buffer-modified-p omodified)) vm-check-for-killed-summary vm-check-for-killed-presentation 0 vm-messages-not-on-disk major-! mode vm-mode buffer-file-name file-newer-than-file-p make-auto-save-file-name read-only default-value vm-folder-read-only buffer-disable-undo abbrev-mode auto-fill-mode vm-mode-internal vm-read-index-file-maybe vm-assimilate-new-messages vm-gobble-visible-header-variables vm-gobble-bookmark vm-gobble-pop-retrieved vm-gobble-imap-retrieved vm-gobble-summary vm-gobble-labels vm-start-itimers-if-needed this-command apply vm-goto-new-folder-frame-maybe (folder) (primary-folder folder) vm-summary-buffer vm-presentation-buffer buffer-to-display vm-display vm startup vm-raise-frame-at-startup vm-raise-frame vm-emit-totals-blurb vm-thoughtfully-select-message vm-update-summary-and-mode-line vm-toolbar-support-possible-p vm-use-toolbar "Initializing toolbar..." vm-toolbar-install-toolbar "Initializing toolbar... done" vm-toolbar-update-toolbar vm-use-menus vm-menu-support-possible-p vm-menu-install-visited-folders-menu vm-should-generate-summary vm-summarize vm-mutable-frames vm-frame-! per-summary vm-mutable-windows switch-to-buffer vm-message-list vm-preview-current-message run-hooks vm-visit-folder-hook substitute-command-keys "Auto save file is newer; consider \\[recover-file]. FOLDER IS READ ONLY." throw done vm-auto-get-new-mail vm-block-new-mail "Checking for new mail for %s..." buffer-name vm-get-spooled-mail vm-startup-message-displayed vm-display-startup-message input-pending-p] 7) # (catch done ...) # bind (read-only folder) #<compiled-function (&optional folder read-only) "...(7)" [vm-session-initialization done (byte-code "À !?ÂÀ !« ªà ®É\n\"Í!«ÎÏ\"ªÇÐ!®Á«É!®ÒÂÓØÙ\"Ú! ®\n＠¬B)ØÝ\"-)q««àÂ!á\"B\"#«Åä!!äå!=¬»ä!!äæ!=¬±ä!!äç!=¬§ä!!äè!=¬Âé *+ìíed!#îÓÂ\"ïed!#+«±ð!!ðÓ!=¬§ð!!ðè!=¬Âé *+ñíed!#îÓÂ\"ïed!#+ò ó é ¬ô56÷=?8é ?ùú 8\"®;®üý!® += «þp!ÿô!＠

2 participants
1 comments

Re: working on getting XEmacs/GTK to 21.2... 24 years

William M. Perry

"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes: > >>>>> "-BP" == William M Perry <wmperry(a)aventail.com> writes: > > -BP> Any objections? This would land on the main 21.2 branch. I > -BP> really think GTK should be made the default on systems that > -BP> support it, and that is how > > GTK still doesn't support multiple X displays, right? I need that a lot > more than I need prettier dialogs---I see a dialog about once a week.... > Of course, this is a personal issue and should be handled by my own > configuration. Correct - no multidisplay, and it doesn't look like GTK 2.0 is going to have it either. *sigh* > Also, until GTK is used for Custom, I think it's going to look very very > half-assed. Why is that not the case for X and Motif then? Or Windows? > On that basis, my vote is "not yet". I've almost got it running here (compiles, but craps out at initialization when I try to set the specifiers for the pointers). -Bill P.

5 participants
7 comments

Re: Strange crash 24 years

Nickolay Pakoulin

>>>>> "Andy" == Andy Piper <andyp(a)bea.com> writes: Andy> Can you resend the recipe - I will try under Linux. andy I did it with xemacs-21.2.37 configured to use athena widgets with both mule and no-mule. xemacs -vanilla C-h p Place cursor on line starting with say, build. Then click with the middle mouse button on that line. It seems to be important to click to the same line where cursor is, otherwise mouse click does no harm. When i click with middle button on the line with cursor i get crash. When i click on the line without cursor i get normal finder buffer. Nick.

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 November 2000