Re: [SUCCESS with kludges] Current CVS source under Red Hat 6.2
25 years
Jan Vroonhof
Jan Vroonhof
"Kirill 'Big K' Katsnelson" <kkm(a)dtmx.com> writes:
> $ ~/xemacs/src/xemacs -nw -q
> Cannot open load file: /xemacs/lisp/auto-autoloads
> (bails out)
Is you shell setting up the HOME environment variable correctly? Is
every directory in the path readable?
Jan
- 2 participants
- 1 comments
Re: Weird redisplay crash
25 years
Jan Vroonhof
Jan Vroonhof
npak(a)kazbek.ispras.ru (Nick V. Pakoulin) writes:
> To reproduce -- first hide your resources.
> Save the following code in a file
YIPPEE! (This bug is actually several years old. It just that the
window-height problem with ispell finally makes the situation less rare).
If you are careful with your mouse you can get really funny things for
the "Choices" window, like
(window-end (second (window-list)))
-643
This patch should fix the crash (I left in a debug message) and the
weird value of window-end.
The XEmacs redisplay engine sure doesn't like windows without
contents...
Could you try it out...?
Jan
P.S. Please ignore the comments. No I am not under the influence of drugs.
Index: redisplay.c
===================================================================
RCS file: /usr/CVSroot/XEmacs/xemacs/src/redisplay.c,v
retrieving revision 1.55.2.41
diff -u -u -r1.55.2.41 redisplay.c
--- redisplay.c 2000/02/17 14:16:46 1.55.2.41
+++ redisplay.c 2000/02/24 17:48:24
＠＠ -5157,6 +5157,9 ＠＠
else
prop = 0;
+ /* Make sure this is set always */
+ /* Note the conversion at end */
+ w->window_end_pos[type] = start_pos;
while (ypos < yend)
{
struct display_line dl;
＠＠ -5260,10 +5263,14 ＠＠
Dynarr_free (prop);
/* #### More not quite right, but close enough. */
- /* #### Ben sez: apparently window_end_pos[] is measured
+ /* Ben sez: apparently window_end_pos[] is measured
as the number of characters between the window end and the
end of the buffer? This seems rather weirdo. What's
- the justification for this? */
+ the justification for this?
+
+ JV sez: Because BUF_Z (b) would be a good initial value, however
+ that can change. This representation allows initalizing with 0.
+ */
w->window_end_pos[type] = BUF_Z (b) - w->window_end_pos[type];
if (need_modeline)
＠＠ -7553,11 +7560,20 ＠＠
displayed. The end of the last line is also know as the window end
position.
+ WARNING: Under some circumstances it is possible that rediplay failed
+ to layout any lines for the windows. In that case this function returns
+ 0 as an error condition when may_error is non-zero and a normalized
+ value of startp otherwise.
+ Under normal circumstances this is rare. However it seems that it seems
+ that in can occur when computing the window a mouse event occured in and
+ the code their can handle the 0 error condition.
+
#### With a little work this could probably be reworked as just a
call to start_with_line_at_pixpos. */
static Bufpos
-start_end_of_last_line (struct window *w, Bufpos startp, int end)
+start_end_of_last_line (struct window *w, Bufpos startp, int end,
+ int may_error)
{
struct buffer *b = XBUFFER (w->buffer);
line_start_cache_dynarr *cache = w->line_start_cache;
＠＠ -7577,8 +7593,11 ＠＠
start_elt = point_in_line_start_cache (w, cur_start, 0);
if (start_elt == -1)
- abort (); /* this had better never happen */
-
+ {
+ stderr_out ("Soft assert triggered (start_end_of_last_line)\n");
+ return may_error ? 0 : startp;
+ }
+
while (1)
{
int height = Dynarr_atp (cache, start_elt)->height;
＠＠ -7641,7 +7660,7 ＠＠
Bufpos
start_of_last_line (struct window *w, Bufpos startp)
{
- return start_end_of_last_line (w, startp, 0);
+ return start_end_of_last_line (w, startp, 0 , 0);
}
/* For the given window W, if display starts at STARTP, what will be
＠＠ -7651,9 +7670,16 ＠＠
Bufpos
end_of_last_line (struct window *w, Bufpos startp)
{
- return start_end_of_last_line (w, startp, 1);
+ return start_end_of_last_line (w, startp, 1, 0);
}
+static Bufpos
+end_of_last_line_may_error (struct window *w, Bufpos startp)
+{
+ return start_end_of_last_line (w, startp, 1, 1);
+}
+
+
/* For window W, what does the starting position have to be so that
the line containing POINT will cover pixel position PIXPOS. */
＠＠ -8807,7 +8833,7 ＠＠
if (!MARKERP ((*w)->start[CURRENT_DISP]))
*closest = 0;
else
- *closest = end_of_last_line (*w,
+ *closest = end_of_last_line_may_error (*w,
marker_position ((*w)->start[CURRENT_DISP]));
*col = 0;
UPDATE_CACHE_RETURN;
- 1 participants
- 0 comments
Re: Tabs problems
25 years
Hrvoje Niksic
Hrvoje Niksic
Andy Piper <andy(a)xemacs.org> writes:
> >I see. Is there any documentation on how they're supposed to
> >behave? It needn't be full-fledged Texinfo -- a README will do.
>
> I'm about to commit Stephen's docs.
Correct me if I'm wrong, but Stephen's docs are for Lispref, i.e. they
explain the Lisp API of the feature. What I'm talking about is the
most basic *user* documentation, explaining how the buffer tabs are
supposed to behave by default.
- 2 participants
- 1 comments
Re: Buffer tabs still flickering
25 years
Hrvoje Niksic
Hrvoje Niksic
Martin Buchholz <martin(a)xemacs.org> writes:
> >>>>> "Hrvoje" == Hrvoje Niksic <hniksic(a)iskon.hr> writes:
>
> Hrvoje> The buffer tabs are still flickering when used with Gnus.
> Hrvoje> Specifically, whenever I press SPC or DEL in the Summary buffer in
> Hrvoje> order to scroll the current article by one page, the tabs flicker.
> Hrvoje> Even if nothing really happen, as when I press DEL and I'm already at
> Hrvoje> the beginning of the article.
>
> Hrvoje> Is this a known bug that's supposed to be fixed, or does it happen
> Hrvoje> only for me?
>
> I get really bad buffer tab flickering as well. Best way to
> reproduce:
>
> M-x occur RET somestring RET
>
> Then move the mouse around in the *Occur* buffer.
I don't get flicker in that case. On Linux.
- 1 participants
- 0 comments
Re: Dynamic size spec for widgets
25 years
Hrvoje Niksic
Hrvoje Niksic
Martin Buchholz <martin(a)xemacs.org> writes:
> Hrvoje> I've been told that in C++ `inline' means `static inline'.
> Hrvoje> Do all C++ compilers grok `static inline'?
>
> In standard C++, `inline' does not affect the extern-ness of a
> function.
I have been misinformed, then; good. (I think the information came
from Ben, but I could be wrong.)
> If different translations units have definitions for an external
> inline function, they must be identical. Older C++ implementations
> considered `extern inline' illegal. I guess that adds to the number
> of distinct inline implementations - we're up to 6 now!
We can conclude that inline in headers sucks. Macros rule and we
should have more of them.
(The above was of course a joke.)
> Hrvoje> it's especially important to *document* what it means. The
> Hrvoje> annoying thing about the INLINE confusion is that it crops
> Hrvoje> up time and again, by different people and with different
> Hrvoje> code.
>
> OK. I'm convinced. I'll implement this, if there are no further
> objections.
>
> Again, the proposal:
>
> 1. Rename INLINE to INLINE_HEADER.
>
> 2. Document the two approved ways of creating inline functions - in
> .h files, using INLINE_HEADER, and in .c files, using `static inline'.
That's it.
- 1 participants
- 0 comments
Weird redisplay crash
25 years
Nick V. Pakoulin
Nick V. Pakoulin
To reproduce -- first hide your resources.
Save the following code in a file
say
xemacs -vanilla -l /tmp/crash.el &
Then move mouse pointer over "Choices" subwindow and boom!.
-------------------------------------------------------------------------------
uname -a: Linux hookah 2.2.12-20 #5 Thu Feb 3 17:25:10 MSK 2000 i686 unknown
./configure '--with-sound=none' '--with-pop' '--error-checking=none'
XEmacs 21.2-b31 "Iris" configured for `i686-pc-linux'.
Where should the build process find the source code? /local/src/xemacs-21.2.31
What installation prefix should install use? /usr/local
What operating system and machine description files should XEmacs use?
`s/linux.h' and `m/intel386.h'
What compiler should XEmacs be built with? gcc -g -O3 -Wall -Wno-switch -Wpointer-arith -Winline -Wmissing-prototypes -Wshadow
Should XEmacs use the GNU version of malloc? yes
(Using Doug Lea's new malloc from the GNU C Library.)
Should XEmacs use the relocating allocator for buffers? no
What window system should XEmacs use? x11
Where do we find X Windows header files? /usr/X11R6/include
Where do we find X Windows libraries? /usr/X11R6/lib
Athena library to link: Xaw
Athena header include path: X11/Xaw
Compiling in support for XAUTH.
Compiling in support for XPM images.
Compiling in support for PNG image handling.
Compiling in support for (builtin) GIF image handling.
Compiling in support for JPEG image handling.
Compiling in support for TIFF image handling.
Compiling in support for X-Face message headers.
Compiling in support for Berkeley DB.
Compiling in support for LDAP.
Compiling in support for ncurses.
Compiling in support for GPM (General Purpose Mouse).
Compiling in support for proper WM_COMMAND handling.
Using Lucid menubars.
Using Lucid scrollbars.
Using Athena native widgets.
Using Athena dialog boxes.
Compiling in dynamic shared object module support.
movemail will use "dot-locking" for locking mail spool files.
Using POP for mail access.
Compiling in extra code for debugging.
-------------------------------------------------------------------------------
Fatal error: assertion failed, file redisplay.c, line 7580, abort()
Fatal error (6).
Your files have been auto-saved.
Use `M-x recover-session' to recover them.
If you have access to the PROBLEMS file that came with your
version of XEmacs, please check to see if your crash is described
there, as there may be a workaround available.
Otherwise, please report this bug by running the send-pr
script included with XEmacs, or selecting `Send Bug Report'
from the help menu.
As a last resort send ordinary email to `crashes(a)xemacs.org'.
*MAKE SURE* to include the information in the command
M-x describe-installation.
If at all possible, *please* try to obtain a C stack backtrace;
it will help us immensely in determining what went wrong.
To do this, locate the core file that was produced as a result
of this crash (it's usually called `core' and is located in the
directory in which you started the editor, or maybe in your home
directory), and type
gdb /usr/local/bin/xemacs core
then type `where' when the debugger prompt comes up.
(If you don't have GDB on your system, you might have DBX,
or XDB, or SDB. A similar procedure should work for all of
these. Ask your system administrator if you need more help.)
Lisp backtrace follows:
event-window(#<motion-event 130, 27>)
# bind (frame event)
default-mouse-motion-handler(#<motion-event 130, 27>)
next-command-event()
# bind (event ch)
read-char-exclusive()
# bind (inhibit-quit)
# (unwind-protect ...)
# bind (count line max-lines choices window-min-height command-characters dedicated skipped char num result textwin dedicated-win end start word guess miss)
ispell-command-loop(("name") nil "uname" 1 6)
# bind (word-start word-len line-end line-start recheck-region replace poss accept-list shift string)
ispell-process-line("^uname -a: Linux hookah \n" nil)
# bind (string end start transient-mark-mode case-fold-search skip-region-start skip-regexp skip-alist key)
byte-code("..." [reg-start nil case-fold-search make-marker ispell-begin-skip-region-regexp ispell-skip-region-alist key skip-alist skip-regexp skip-region-start transient-mark-mode ispell-parser tex append ispell-tex-skip-alists message-log-max message "searching for regions to skip" re-search-forward reg-end t buffer-substring-no-properties 0 "Continuing spelling check using %s dictionary..." ispell-dictionary "default" ispell-region-end ispell-quit marker-position ispell-skip-region match-data start end ispell-get-line string ispell-process-line recheckp shift] 7)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# bind (shift recheckp reg-end reg-start)
ispell-region(1 1967)
ispell-buffer()
# bind (current-load-list)
# (unwind-protect ...)
# bind (load-file-name)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
load-internal("/tmp/crash.el" nil t nil nil nil)
# bind (nosuffix nomessage noerror file)
load("/tmp/crash.el" nil t)
# bind (file arg)
command-line-do-load("-l")
# bind (dir file-count line end-of-options first-file-buffer file-p arg tem)
command-line-1()
# bind (command-line-args-left)
command-line()
# (unwind-protect ...)
normal-top-level()
# (condition-case ... . error)
# (catch top-level ...)
-------------------------------------------------------------------------------
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux"...
Core was generated by `xemacs -vanilla -l /tmp/crash.el'.
Program terminated with signal 6, Aborted.
Reading symbols from /usr/X11R6/lib/libXaw.so.6...done.
Reading symbols from /usr/lib/libtiff.so.3...done.
Reading symbols from /usr/lib/libpng.so.2...done.
Reading symbols from /usr/lib/libjpeg.so.62...done.
Reading symbols from /usr/lib/libz.so.1...done.
Reading symbols from /usr/X11R6/lib/libXpm.so.4...done.
Reading symbols from /usr/X11R6/lib/libXmu.so.6...done.
Reading symbols from /usr/X11R6/lib/libXt.so.6...done.
Reading symbols from /usr/X11R6/lib/libXext.so.6...done.
Reading symbols from /usr/X11R6/lib/libX11.so.6...done.
Reading symbols from /usr/X11R6/lib/libSM.so.6...done.
Reading symbols from /usr/X11R6/lib/libICE.so.6...done.
Reading symbols from /lib/libdl.so.2...done.
Reading symbols from /lib/libdb.so.3...done.
Reading symbols from /usr/lib/libgpm.so.1...done.
Reading symbols from /usr/lib/libncurses.so.4...done.
Reading symbols from /usr/lib/libldap.so.1...done.
Reading symbols from /usr/lib/liblber.so.1...done.
Reading symbols from /lib/libm.so.6...done.
Reading symbols from /lib/libc.so.6...done.
Reading symbols from /lib/ld-linux.so.2...done.
Reading symbols from /lib/libnss_dns.so.2...done.
Reading symbols from /lib/libresolv.so.2...done.
Reading symbols from /lib/libnss_files.so.2...done.
#0 0x402f14e1 in __kill () from /lib/libc.so.6
(gdb) where
#0 0x402f14e1 in __kill () from /lib/libc.so.6
#1 0x8078851 in fatal_error_signal (sig=6) at emacs.c:272
#2 0x402f1408 in __restore ()
at ../sysdeps/unix/sysv/linux/i386/sigaction.c:127
#3 0x402f2868 in abort () at ../sysdeps/generic/abort.c:88
#4 0x80787b7 in assert_failed (file=0x817002b "redisplay.c", line=7580,
expr=0x8170075 "abort()") at emacs.c:2770
#5 0x80fe33c in start_end_of_last_line (w=0x84b8168, startp=1, end=1)
at redisplay.c:7580
#6 0x81007d8 in pixel_to_glyph_translation (f=0x8468890, x_coord=130,
y_coord=-14, col=0xbfffe564, row=0xbfffe568, obj_x=0xbfffe56c,
obj_y=0xbfffe570, w=0xbfffe574, bufpos=0xbfffe578, closest=0xbfffe57c,
modeline_closest=0xbfffe580, obj1=0xbfffe584, obj2=0xbfffe588)
at redisplay.c:7654
#7 0x8082773 in event_pixel_translation (event=139220156, char_x=0x0,
char_y=0x0, obj_x=0x0, obj_y=0x0, w=0xbfffe5c0, bufp=0x0, closest=0x0,
modeline_closest=0x0, obj1=0x0, obj2=0x0) at events.c:1747
#8 0x80836cc in Fevent_window (event=139220156) at events.c:1881
#9 0x807bb94 in Ffuncall (nargs=2, args=0xbfffe638) at eval.c:3175
#10 0x805be99 in execute_optimized_program (
program=0x850d618 "ю\t!╝\003б \eд\t!\035ф\t!\211\036\a╜\004х\t!\211\036\t╜\006йк\016\a\"\036\f\016\a╜\t\016\t?╜\004м\t!\211\036\016╚\nо\016\016\016\aп#╝\f\016\t╜\bо\016\t\016\fя#\036\022с\t!\211\036\024╜\tу\016\024!╜\003\016\024\211\036\026╚\fв\016\026ь\"╚\005\016\026╝\031\016\016╚\nо\016\016\016\aь#╝\f\016\t╜\bо\016\t\016\fь#\211\036\031╜\fу\016\031!╜\006в\016\031ь\"\036\032ш\t!\036\034\016\026╚\fв\016\026я\"╚\005\016\026╝'\016\034╚\013щ\016\034!╚\005\016\034╝\031\016\016╚\nо\016\016\016\aя#╝\f\016\t╜\bо"..., stack_depth=5,
constants_data=0x8372a08) at bytecode.c:747
#11 0x805bb64 in funcall_compiled_function (fun=137823968, nargs=1,
args=0xbfffe734) at bytecode.c:516
#12 0x807bd0f in Ffuncall (nargs=2, args=0xbfffe730) at eval.c:3210
#13 0x807eb4c in call1 (fn=137830916, arg0=139220156) at eval.c:3824
#14 0x809d6d9 in execute_internal_event (event=139220156)
at event-stream.c:3043
#15 0x809c8c0 in Fnext_command_event (event=139220156, prompt=136080356)
at event-stream.c:2398
#16 0x807bcc0 in Ffuncall (nargs=1, args=0xbfffe7fc) at eval.c:3196
#17 0x805be99 in execute_optimized_program (
program=0x8232698 "ю\211\031\032ц \022\f╛\rе\nф \"╚\006гхю\"\210и\n!\021й\n!\210\t╚Д\t*\207g", stack_depth=3, constants_data=0x8279990) at bytecode.c:747
#18 0x805bb64 in funcall_compiled_function (fun=136775548, nargs=0,
args=0xbfffe8f0) at bytecode.c:516
#19 0x807bd0f in Ffuncall (nargs=1, args=0xbfffe8ec) at eval.c:3210
#20 0x805be99 in execute_optimized_program (
program=0x8509070 "ю\tб цZ\f\r\t^фгх !ий\211\211\211\211\036\013\036\f\036\r\036\016\036\017\036\020\036\021\036\022\035\036\023\036\024\036\025\036\026\212в\016\030!q\210ы\016\032P\026\eэ \210\016\035╚＠чъ╠\002\210\016\035╚%i\016\035＠G\\ц\\Ю V╚\tАc\210\016\025T\026\025\016\035＠Б╠\002\210\016\035A\211\026\035╛щЦД╠\002\210\016\025\016\023╚\004Е╙\002Ф\\\026\025\016\023╚Yi\016\023＠G\\\016\026ГV╚\004Е╙\002и\\Х\\Ю V╚\fИc\210\016\025T\211\026\025╙\003\016\025\016\024W╚/\016\026\016\022s╚\017Й\016\026T!\026\026\016\020T\026\020╙ЛК\016\026Л"...,
stack_depth=14, constants_data=0x84cee98) at bytecode.c:747
#21 0x805bb64 in funcall_compiled_function (fun=139252416, nargs=5,
args=0xbfffea0c) at bytecode.c:516
#22 0x807bd0f in Ffuncall (nargs=6, args=0xbfffea08) at eval.c:3210
#23 0x805be99 in execute_optimized_program (
program=0x85081c0 "ю\211\031\032\013╖╛\003д\023е\016\006\016\a\"\210х\016\006!\210\016\t＠й\230╚У\016\tA\237\026\t\016\013\204ф\001\016\t\203а\001л\016\t＠\t\013#\211\022\203╜\001\n<\203╗\001м\016\016\016\017\\\nA＠\\!\n＠Gм\016\020!м\016\016!ю\211\036\021\036\022\036\023\036\024\036\025\211\036\026b\210в \210\016\025\016\026\\b\210в \210\016\026b\210в \210\016\025`\\ь\n＠\016\025`\\ы#\210`U╛\rзшэP\n＠щ\016\026!#\210\016\036╚\035ъ\nAA＠\nAAA＠\n＠щ\016\026!\016\025щ\016\026!\\%\026\021╙\004Ю\213\210\016\026b\210\016\021╚.\016\021<╚)\016"..., stack_depth=9,
constants_data=0x84ce900) at bytecode.c:747
#24 0x805bb64 in funcall_compiled_function (fun=139253116, nargs=2,
args=0xbfffeb14) at bytecode.c:516
#25 0x807bd0f in Ffuncall (nargs=3, args=0xbfffeb10) at eval.c:3210
#26 0x805be99 in execute_optimized_program (
program=0xbfffeb68 "\bb\210а\nц д \rа\036\006\036\a\036\b\036\t\032\036\n\016\013лa╚\020а\022м\016\016＠\016\016A＠\016\a#\026\aа\036\017пя!\210)р\016\b\016\023т#╚\026уж\224ж\225\"\026\006\016\t`\016\006GZа\223\210\bb\210а\036\017пв\016\030╝\002ы\"\210)\016\032\016\023а\223\210\016\e\204\223", stack_depth=7,
constants_data=0x84ce5e8) at bytecode.c:747
#27 0x805dcbd in Fbyte_code (instructions=138583476, constants=139257304,
stack_depth=15) at bytecode.c:2404
#28 0x807b39b in Feval (form=138424468) at eval.c:2975
#29 0x807f817 in Fprogn (args=138430468) at eval.c:766
#30 0x805c743 in execute_rare_opcode (stack_ptr=0xbfffeeb4,
program_ptr=0x846a4b4 "\210\016\f?╜\006\016\r╝\002н*\207",
opcode=Bsave_window_excursion) at bytecode.c:1240
#31 0x805bceb in execute_optimized_program (
program=0x846a490 "\b╛\004а \210б\216\212цд\reU╚\013\016\006dU╚\005г ╙\002х\016\t╝\002й#\210к\213\210\016\f?╜\006\016\r╝\002н*\207", stack_depth=4,
constants_data=0x84ce698) at bytecode.c:657
#32 0x805bb64 in funcall_compiled_function (fun=139252836, nargs=2,
args=0xbfffefac) at bytecode.c:516
#33 0x807bd0f in Ffuncall (nargs=3, args=0xbfffefa8) at eval.c:3210
#34 0x805be99 in execute_optimized_program (program=0x8475bc8 "юed\"\207",
stack_depth=3, constants_data=0x84cea30) at bytecode.c:747
#35 0x805bb64 in funcall_compiled_function (fun=139253172, nargs=0,
args=0xbffff030) at bytecode.c:516
#36 0x807b5c5 in Feval (form=138104140) at eval.c:3034 #37 0x80e56b6 in readevalloop (readcharfun=139039040, sourcename=138184300,
evalfun=0x807ae20 <Feval>, printflag=0) at lread.c:1448
#38 0x80e4847 in Fload_internal (file=138184300, no_error=136080356,
nomessage=136080380, nosuffix=136080356, codesys=136080356,
used_codesys=136080356) at lread.c:736
#39 0x807bc03 in Ffuncall (nargs=7, args=0xbffff340) at eval.c:3175
#40 0x805be99 in execute_optimized_program (
program=0x82bdb68 "ю\t\n\013\fе\211&\006\207'\bТi\037\b(", stack_depth=7,
constants_data=0x8315788) at bytecode.c:747
#41 0x805bb64 in funcall_compiled_function (fun=137426336, nargs=3,
args=0xbffff444) at bytecode.c:516
#42 0x807bd0f in Ffuncall (nargs=4, args=0xbffff440) at eval.c:3210
#43 0x805be99 in execute_optimized_program (
program=0x8499120 "\b\211A\020＠\031бц\t!!╚\005ц\t!\021д\tеф#)\207",
stack_depth=4, constants_data=0x8303938) at bytecode.c:747
#44 0x805bb64 in funcall_compiled_function (fun=137327216, nargs=1,
args=0xbffff538) at bytecode.c:516
#45 0x807bd0f in Ffuncall (nargs=2, args=0xbffff534) at eval.c:3210
#46 0x805be99 in execute_optimized_program (program=0x8499008 "\b╛>\t?\205Ж",
stack_depth=8, constants_data=0x8304dc8) at bytecode.c:747
#47 0x805bb64 in funcall_compiled_function (fun=137327608, nargs=0,
args=0xbffff63c) at bytecode.c:516
#48 0x807bd0f in Ffuncall (nargs=1, args=0xbffff638) at eval.c:3210
#49 0x805be99 in execute_optimized_program (
program=0x8424fc8 "\bA\031бц\034\035ф\t!\021гх!╚\004и \210\016\n╚\020\016\013╛\fлмн\016\n!оQ! \210п \210*я \210р \210rст!q\210у \210жв!\210\016\030ыa╚\005\016\032 \210)ш эa╚\bк ╛\004щ \210ч \210в\026\037к ╜\004Юц!)\207a\001",
stack_depth=4, constants_data=0x8304cb8) at bytecode.c:747
#50 0x805bb64 in funcall_compiled_function (fun=137327412, nargs=0,
args=0xbffff730) at bytecode.c:516
#51 0x807bd0f in Ffuncall (nargs=1, args=0xbffff72c) at eval.c:3210
#52 0x805be99 in execute_optimized_program (
program=0x8215d68 "\b╚\005аб!\207ц\020д \211\035╚\030\rG\016\006GW╚\020г\016\006!г\r!k╚\006х\r!\026\006)и\016\006!\026\006й \210к \210\016\f╝\aмн!╜\002ц\036\fо\016\020\016\021\"\026\022\016\f╚\nсту\016\022\"ж\"\210\016\022╛\006в \210╙\016ь\016\022\016\031\016\032\016\e\016\f%\210э \210)\016\035╛\022\016\036╚\016ъЮА\016\"!\016\036\"Цц#\210\016\035╛\024\016\032╛\006Д\016%!\210Д\016&!\210Д\016'!\210Х\216И )\207\224К \b9", stack_depth=7, constants_data=0x8304308)
at bytecode.c:747
#53 0x805bb64 in funcall_compiled_function (fun=137327356, nargs=0,
args=0xbffff7c4) at bytecode.c:516
#54 0x807b5c5 in Feval (form=137355824) at eval.c:3034
#55 0x807f5fb in condition_case_1 (handlers=136080452, bfun=0x807ae20 <Feval>,
barg=137355824, hfun=0x8062d80 <cmd_error>, harg=136080356) at eval.c:1629
#56 0x80634f9 in top_level_1 (dummy=136080356) at cmdloop.c:202
#57 0x807f4df in internal_catch (tag=136152164, func=0x80634d0 <top_level_1>,
arg=136080356, threw=0x0) at eval.c:1304
#58 0x8062ecc in initial_command_loop (load_me=136080356) at cmdloop.c:281
#59 0x80771e7 in xemacs_21_2_b31_i686_pc_linux (argc=4, argv=0xbffffb34,
envp=0xbffffb48, restart=0) at emacs.c:1879
#60 0x8078b29 in main (argc=4, argv=0xbffffb34, envp=0xbffffb48)
at emacs.c:2305
#61 0x402eb1eb in __libc_start_main (main=0x8078a28 <main>, argc=4,
argv=0xbffffb34, init=0x804e24c <_init>, fini=0x8158600 <_fini>,
rtld_fini=0x4000a610 <_dl_fini>, stack_end=0xbffffb2c)
at ../sysdeps/generic/libc-start.c:90
-------------------------------------------------------------------------------
This crash seems to be font specific, so I picked the font name for crash:
(face-font-name 'buffers-tab)
==> "-*-courier-medium-i-*-*-*-120-*-*-*-*-iso8859-*"
bash$ xlsfonts -fn "-*-courier-medium-i-*-*-*-120-*-*-*-*-iso8859-*"
-adobe-courier-medium-i-normal--12-120-75-75-m-0-iso8859-1
-adobe-courier-medium-i-normal--12-120-75-75-m-0-iso8859-2
-adobe-courier-medium-i-normal--12-120-75-75-m-0-iso8859-3
-adobe-courier-medium-i-normal--12-120-75-75-m-0-iso8859-9
-bitstream-courier-medium-i-normal--12-120-75-75-m-0-iso8859-1
-bitstream-courier-medium-i-normal--12-120-75-75-m-0-iso8859-1
-bitstream-courier-medium-i-normal--12-120-75-75-m-0-iso8859-2
-bitstream-courier-medium-i-normal--12-120-75-75-m-0-iso8859-9
Xemacs does not crash when the font is
"-cronyx-courier-medium-o-*-*-*-100-100-100-*-*-koi8-*"
bash$ xlsfonts -fn "-cronyx-courier-medium-o-*-*-*-100-100-100-*-*-koi8-*"
-cronyx-courier-medium-o-normal--14-100-100-100-m-0-koi8-r
-cronyx-courier-medium-o-normal--14-100-100-100-m-80-koi8-r
-------------------------------------------------------------------------------
Nick.
- 1 participants
- 0 comments
buffer tabs background
25 years
Giacomo Boffi
Giacomo Boffi
i have
% xrdb -q | grep 'Emacs.*ack'
Emacs*Background: mycolor4
Emacs*Tabs*background: rosybrown2
Emacs*XlwScrollBar.Background: mycolor3
Emacs*XlwScrollBar.bottomShadowColor: black
Emacs*backgroundToolBarColor: mycolor3
Emacs*dialog*Background: mycolor3
Emacs*menubar*Background: mycolor3
Emacs*popup*Background: mycolor4
Emacs.default.attributeBackground: mycolor4
%
but
1. the buffer tabs background is unmistakenly mycolor4 (a very dark
blue) when i specified rosybrown2
also,
2. i can set the tabs bg color with editres, but when emacs gains the
focus the tabs are redrawn with mycolor4 (i.e., generic bg color)
3. if i set the borderwith of the tabs, they are clipped in the bottom
4. tabs aren't visually pleasing if they have a dark bg, and there are
no/botton shadow pixel resources to modify, to get a better look
---------------------------- details under this line -------------------
uname -a: Linux boffi95.stru.polimi.it 2.2.12-20 #1 Mon Sep 27 10:25:54 EDT 1999 i586 unknown
./configure '--extra-verbose' '--with-athena=3d' '--with-modules' '--error-checking=none' '--debug' '--use-union-type'
XEmacs 21.2-b31 "Iris" configured for `i586-pc-linux'.
Where should the build process find the source code? /home/jim/src/xemacs
What installation prefix should install use? /usr/local
What operating system and machine description files should XEmacs use?
`s/linux.h' and `m/intel386.h'
What compiler should XEmacs be built with? gcc -g -O3 -Wall -Wno-switch -Wpointer-arith -Winline -Wmissing-prototypes -Wshadow
Should XEmacs use the GNU version of malloc? yes
(Using Doug Lea's new malloc from the GNU C Library.)
Should XEmacs use the relocating allocator for buffers? no
What window system should XEmacs use? x11
Where do we find X Windows header files? /usr/X11R6/include
Where do we find X Windows libraries? /usr/X11R6/lib
Athena library to link: Xaw3d
Athena header include path: X11/Xaw3d
Compiling in support for XAUTH.
Compiling in support for XPM images.
Compiling in support for PNG image handling.
Compiling in support for (builtin) GIF image handling.
Compiling in support for JPEG image handling.
Compiling in support for TIFF image handling.
Compiling in support for X-Face message headers.
Compiling in native sound support.
Compiling in support for Berkeley DB.
Compiling in support for ncurses.
Compiling in support for GPM (General Purpose Mouse).
Compiling in support for proper WM_COMMAND handling.
Using Lucid menubars.
Using Lucid scrollbars.
Using Athena native widgets.
Using Athena dialog boxes.
Compiling in dynamic shared object module support.
movemail will use "dot-locking" for locking mail spool files.
Using the union type for Lisp_Objects.
Compiling in extra code for debugging.
- 3 participants
- 4 comments
different customization for faces
25 years
Giacomo Boffi
Giacomo Boffi
i'm on 21.2.31; i have done
M-x customize-face RET RET
and then i noted that the face specification for "default" is an
editable lisp expression, while the other ones are the usual stuff,
with "Attribute" buttons and various editable fields
i may be mistaken, but the face specification for "default" used to be
no different from the other ones
- 1 participants
- 0 comments
Re: Buffer tabs still flickering
25 years
Hrvoje Niksic
Hrvoje Niksic
Andy Piper <andy(a)xemacs.org> writes:
> At 12:37 PM 2/24/00 +0100, Hrvoje Niksic wrote:
> >Specifically, whenever I press SPC or DEL in the Summary buffer in
> >order to scroll the current article by one page, the tabs flicker.
> >Even if nothing really happen, as when I press DEL and I'm already at
> >the beginning of the article.
> >
> >Is this a known bug that's supposed to be fixed, or does it happen
> >only for me?
>
> Async updates are supposed to fix this. i.e. tabs only get updated
> when redisplay gets called. If this is still happening it would be
> nice to know why.
Could the "window-excursion" code be guilty here?
> >P.S. Did I mention that it would be _really_ cool if the tabs
> >could somehow respect the background pixmap? The gutter looks very
> >ugly when the rest of the frame is pixmapized.
>
> You did, and I replied that it was currently impossible.
The question was rhetorical. Still, I wonder if background support
could be added to the widget itself (there is something called
XPM-Athena apparently able to do these things).
Could widget backgrounds work under Windows?
- 1 participants
- 0 comments
Re: Dynamic size spec for widgets
25 years
Hrvoje Niksic
Hrvoje Niksic
Martin Buchholz <martin(a)xemacs.org> writes:
> Hrvoje> For instance, `gcc -O2' (or, for that matter, `gcc -O')
> Hrvoje> doesn't inline any functions, but it does inline the ones
> Hrvoje> specifically requested. `gcc -O3' inlines all it can, but
> Hrvoje> was reported as buggy under some architectures.
>
> Whatever you do, `inline' will never be more than a hint to the
> compiler.
Whatever. Gcc for one has respected that hint whenever I tried it.
- 2 participants
- 1 comments