all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: 15749@debbugs.gnu.org
Subject: bug#15749: 24.3.50; reduced font size for *Backtrace* is lost for each step
Date: Tue, 29 Oct 2013 08:32:24 -0700 (PDT)	[thread overview]
Message-ID: <ffa52f02-00d3-402c-a88a-683fcee7fb4f@default> (raw)


emacs -Q

Use `debug-on-entry' for some function, invoke that function, and try to
step through the debugger.

As soon as buffer *Backtrace* is created, use `S-mouse-1' and choose
`Decrease Buffer Text Size'.  OK.

Now step, using `d'.  At the first step, buffer *Backtrace* returns to
the original size text.  This font-size change is supposed to be per
buffer, no matter where the buffer is displayed.

Presumably because Emacs, behind the scene, kills and re-creates buffer
`*Backtrace*', the user-expected behavior is broken.  The debugger
should remember the user-chosen font size and reinstate it when it does
its otherwise user-invisible, behind-the-scene buffer manipulations.

In fact, every user-pertinent setting in effect for buffer *Backtrace*
should be restored, each time the buffer is "updated"/re-created.



In GNU Emacs 24.3.50.1 (i686-pc-mingw32)
 of 2013-10-19 on LEG570
Bzr revision: 114715 rgm@gnu.org-20131019023520-s8mwtib7xcx9e05w
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --enable-checking 'CFLAGS=-O0 -g3' CPPFLAGS=-DGLYPH_DEBUG=1'





             reply	other threads:[~2013-10-29 15:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-29 15:32 Drew Adams [this message]
2018-08-03 18:22 ` bug#15749: 24.3.50; reduced font size for *Backtrace* is lost for each step Gemini Lasswell
2018-08-03 18:57   ` Drew Adams
2018-08-03 19:21     ` Gemini Lasswell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ffa52f02-00d3-402c-a88a-683fcee7fb4f@default \
    --to=drew.adams@oracle.com \
    --cc=15749@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.