[Peter_Dyballa@Freenet.DE: When in no-window use GNU Emacs clips contents in *Backtrace* buffer]

[Peter_Dyballa@Freenet.DE: When in no-window use GNU Emacs clips contents in *Backtrace* buffer]

[Richard Stallman]

Would someone please fix this and ack?

------- Start of forwarded message -------
X-Spam-Status: No, score=0.0 required=5.0 tests=UNPARSEABLE_RELAY 
	autolearn=failed version=3.1.0
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: emacs-pretest-bug@gnu.org
From: Peter Dyballa <Peter_Dyballa@Freenet.DE>
Date: Sat, 4 Aug 2007 15:15:58 +0200
Subject: When in no-window use GNU Emacs clips contents in *Backtrace* buffer

Hello!

When I launch GNU Emacs as an X client with --debug-init lines in  
*Backtrace* buffer are truncated, so I copy them and paste them into  
*scratch* buffer. Everything's now expanded to full length.

When I try the same in xterm or in Apple's Terminal without windows,  
the truncated lines like in this example

	Debugger entered--Lisp error: (void-variable -)
	  eval-buffer(#<buffer  *load*> nil "/Users/pete/.emacs" nil t)  ;  
Reading at buffer position 2$
	  load-with-code-conversion("/Users/pete/.emacs" "/Users/ 
pete/.emacs" t t)

are not expanded, they seem to be clipped in *Backtrace* buffer. So  
it's not easy to get the buffer position where the error happens ...


In GNU Emacs 22.1.50.1 (powerpc-apple-darwin8.10.0, X toolkit, Xaw3d  
scroll bars)
  of 2007-08-04 on localhost
Windowing system distributor `The XFree86 Project, Inc', version  
11.0.40400000
configured using `configure  '--without-sound' '--without-pop' '-- 
with-x-toolkit=athena' '--with-xpm' '--with-jpeg' '--with-tiff' '-- 
with-gif' '--with-png' '--enable-locallisppath=/Library/Application  
Support/Emacs/calendar22:/Library/Application Support/Emacs'  
'CPPFLAGS=-no-cpp-precomp -I/usr/include/openssl -I/sw/include/ 
pango-1.0 -I/sw/lib/freetype219/include -I/sw/lib/freetype219/include/ 
freetype2 -I/sw/lib/fontconfig2/include -I/sw/include/libpng12 -I/usr/ 
local/include -I/sw/include' 'CXXFLAGS=-no-cpp-precomp -I/usr/include/ 
openssl -I/sw/include/pango-1.0 -I/sw/lib/freetype219/include -I/sw/ 
lib/freetype219/include/freetype2 -I/sw/lib/fontconfig2/include -I/sw/ 
include/libpng12 -I/usr/local/include -I/sw/include' 'LDFLAGS=- 
dead_strip -L/sw/lib/freetype219/lib -L/sw/lib/fontconfig2/lib -L/sw/ 
lib/ncurses -L/usr/local/lib -L/sw/lib' 'CFLAGS=-pipe -bind_at_load - 
fPIC -mcpu=7450 -mtune=7450 -fast -mpim-altivec -ftree-vectorize - 
foptimize-register-move -freorder-blocks -freorder-blocks-and- 
partition -fthread-jumps -fpeephole -fno-crossjumping''

Important settings:
   value of $LC_ALL: nil
   value of $LC_COLLATE: nil
   value of $LC_CTYPE: de_DE.UTF-8
   value of $LC_MESSAGES: nil
   value of $LC_MONETARY: nil
   value of $LC_NUMERIC: nil
   value of $LC_TIME: nil
   value of $LANG: de_DE.UTF-8
   locale-coding-system: utf-8
   default-enable-multibyte-characters: t

Major mode: Debugger

Minor modes in effect:
   shell-dirtrack-mode: t
   show-paren-mode: t
   display-time-mode: t
   desktop-save-mode: t
   tooltip-mode: t
   mouse-wheel-mode: t
   menu-bar-mode: t
   file-name-shadow-mode: t
   global-font-lock-mode: t
   font-lock-mode: t
   blink-cursor-mode: t
   unify-8859-on-encoding-mode: t
   utf-translate-cjk-mode: t
   auto-compression-mode: t
   column-number-mode: t
   line-number-mode: t
   transient-mark-mode: t



- --
Greetings

   Pete

There's no place like ~
                           (UNIX Guru)




_______________________________________________
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
------- End of forwarded message -------

Re: Fwd: When in no-window use GNU Emacs clips contents in *Backtrace* buffer

[Stefan Monnier]

> Would someone please fix this and ack?

I don't see anything that needs fixing here.

> When I launch GNU Emacs as an X client with --debug-init lines in  
> *Backtrace* buffer are truncated, so I copy them and paste them into  
> *scratch* buffer. Everything's now expanded to full length.

> When I try the same in xterm or in Apple's Terminal without windows,  
> the truncated lines like in this example

> 	Debugger entered--Lisp error: (void-variable -)
> 	  eval-buffer(#<buffer  *load*> nil "/Users/pete/.emacs" nil t)  ;  
> Reading at buffer position 2$
> 	  load-with-code-conversion("/Users/pete/.emacs" "/Users/ 
> pete/.emacs" t t)

> are not expanded, they seem to be clipped in *Backtrace* buffer. So  
> it's not easy to get the buffer position where the error happens ...

Try M-x toggle-truncate-lines RET


        Stefan

Re: When in no-window use GNU Emacs clips contents in *Backtrace* buffer

[Peter Dyballa]

Am 05.08.2007 um 07:33 schrieb Stefan Monnier:

>> are not expanded, they seem to be clipped in *Backtrace* buffer. So
>> it's not easy to get the buffer position where the error happens ...
>
> Try M-x toggle-truncate-lines RET

Why is GNU Emacs hiding information? No init file is asking it to  
truncate any lines ...

--
Greetings

   Pete

"America believes in education: the average professor earns more money
in a year than a professional athlete earns in a whole week." – Evan
Esar

Re: When in no-window use GNU Emacs clips contents in *Backtrace* buffer

[Stefan Monnier]

>>> are not expanded, they seem to be clipped in *Backtrace* buffer. So
>>> it's not easy to get the buffer position where the error happens ...
>> Try M-x toggle-truncate-lines RET
> Why is GNU Emacs hiding information? No init file is asking it to  truncate
> any lines ...

Some major modes and packages elect to enable truncate-lines by default in
their buffers because it's deemed more important to keep each logical line
on a single physical line (and let the user scroll-horizontally if she wants
to see more of each line).


        Stefan

Re: When in no-window use GNU Emacs clips contents in *Backtrace* buffer

[Richard Stallman]

    > Try M-x toggle-truncate-lines RET

    Why is GNU Emacs hiding information? No init file is asking it to  
    truncate any lines ...

This is a convenience.  Very long lines in a backtrace make it hard to
see the most important info, which is the sequence of functions.

Re: When in no-window use GNU Emacs clips contents in *Backtrace* buffer

[Miles Bader]

Peter Dyballa <Peter_Dyballa@Freenet.DE> writes:
>> Try M-x toggle-truncate-lines RET
>
> Why is GNU Emacs hiding information? No init file is asking it to
> truncate any lines ...

Backtraces without truncate-lines are often quite unreadable and
probably rather scary for an inexperienced user.

Try this:

    M-x toggle-debug-on-quit RET
    M-x customize-face RET
    ^G
    M-x toggle-truncate-lines

...yikes!

-miles

-- 
The automobile has not merely taken over the street, it has dissolved the
living tissue of the city.  Its appetite for space is absolutely insatiable;
moving and parked, it devours urban land, leaving the buildings as mere islands
of habitable space in a sea of dangerous and ugly traffic.
[James Marston Fitch, New York Times, 1 May 1960]