From: "Drew Adams" <drew.adams@oracle.com>
To: "'martin rudalics'" <rudalics@gmx.at>, "'Eli Zaretskii'" <eliz@gnu.org>
Cc: 13154@debbugs.gnu.org
Subject: bug#13154: 24.3.50; emacs_backtrace.txt (different one)
Date: Fri, 14 Dec 2012 07:51:13 -0800 [thread overview]
Message-ID: <C674F90A18474C6BBA479EE26282C750@us.oracle.com> (raw)
In-Reply-To: <50CAFEE1.2080401@gmx.at>
> >> FWIW, it's not clear to me that `w-o-t-t-b' inside `s-e'
> >> is "evil". It might be ineffectual in some contexts,
> >> in the sense that it might not do what some users
> >> mistakenly might expect, but - for my own understanding -
> >> just why do you consider it evil?
> >
> > Martin will probably tell,
>
> It's evil because `with-output-to-temp-buffer' may pop up a new frame
> while `save-window-excursion' gives you the false impression
> that it can cope with that situation.
That's exactly what I meant by "It might be ineffectual in some contexts, in the
sense that it might not do what some users mistakenly might expect."
In practice (IMHO), that is probably more of a problem/annoyance for Emacs Dev,
having to field false-bug reports from users, than it is a real problem for
users. Just one opinion.
> >> * I found an occurrence in my version of
> >> `describe-function', which is based on
> >> the vanilla Emacs 22 version in this respect. It has to
> >> work for 22+, and 22 does not have macro `with-help-window'.
> >>
> >> * I found one other occurrence of
> >> `with-output-to-temp-buffer' inside `save-excursion', but
> >> that code is used only when running Emacs 22, and it is a
> >> copy of the vanilla Emacs 22 code (for
> >> `describe-text-properties'). IOW, the fault is with
> >> vanilla Emacs in this case, and this case cannot be
> >> manifested in Emacs 24 anyway.
>
> `save-window-excursion' and not `save-excursion', I presume.
No, `save-excursion'. It is `save-excursion' that occurs in the vanilla Emacs
22 code, in both cases (vanilla `describe-function' and `describe-variable', for
Emacs 22 and prior). Emacs was "evil" for decades...
> I still don't know whether you are sure that Drew runs some
> code within `window-configuration-change-hook'.
Didn't know I was expected to look for that one. Grepping for
`window-configuration-change-hook' finds the following two occurrences:
1. Inside the definition of command `dired-sort-dialogue' (from Francis Wright's
library dired-sort-menu.el). But I did not invoke this command, AFAIK.
(add-hook 'window-configuration-change-hook
'dired-sort-dialogue-auto-kill-2)
2. In pp-c-l.el. I do use this one.
(add-hook 'window-configuration-change-hook
'refresh-pretty-control-l)
(defun refresh-pretty-control-l ()
"Reinitialize `pretty-control-l-mode', if on, to update the display."
(interactive)
(when pretty-control-l-mode (pretty-control-l-mode t)))
`pretty-control-l-mode' is a global minor mode that does only this:
(walk-windows
(lambda (window)
(let ((display-table (or (window-display-table window)
(make-display-table))))
(aset display-table ?\014
(and pretty-control-l-mode
(pp^L-^L-display-table-entry window)))
(set-window-display-table window display-table)))
'no-minibuf
'visible)
HTH.
next prev parent reply other threads:[~2012-12-14 15:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 5:04 bug#13154: 24.3.50; emacs_backtrace.txt (different one) Drew Adams
2012-12-12 16:54 ` Eli Zaretskii
2012-12-12 17:06 ` Drew Adams
2012-12-12 18:52 ` Eli Zaretskii
2012-12-13 10:29 ` martin rudalics
2012-12-13 17:08 ` Eli Zaretskii
2012-12-13 21:16 ` Drew Adams
2012-12-14 7:47 ` Eli Zaretskii
2012-12-14 10:26 ` martin rudalics
2012-12-14 15:51 ` Drew Adams [this message]
2012-12-14 16:13 ` martin rudalics
2012-12-14 16:18 ` Drew Adams
2012-12-14 16:35 ` martin rudalics
2012-12-14 16:46 ` Drew Adams
2013-02-23 1:13 ` Glenn Morris
2014-02-10 4:36 ` Lars Ingebrigtsen
2012-12-14 15:25 ` Drew Adams
2012-12-14 16:13 ` martin rudalics
2012-12-14 16:18 ` Drew Adams
2012-12-14 10:24 ` martin rudalics
2012-12-14 15:27 ` Drew Adams
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C674F90A18474C6BBA479EE26282C750@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=13154@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rudalics@gmx.at \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).