unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'martin rudalics'" <rudalics@gmx.at>
Cc: 'Chong Yidong' <cyd@stupidchicken.com>, 7533@debbugs.gnu.org
Subject: bug#7533: 24.0.50; `dired-mark-pop-up': delete frame afterwards if `pop-up-frames'
Date: Fri, 17 Dec 2010 07:32:27 -0800	[thread overview]
Message-ID: <FC91B2B91B3B4C02AF17798D6C4CA5D9@us.oracle.com> (raw)
In-Reply-To: <4D0B03EB.4050706@gmx.at>

>  > M-x set-variable RET
>  >  special-display-regexps RET
>  >  ("[ ]?[*][^*]+[*]") RET
> 
> You shouldn't include the buffer in `special-display-regexps' in the
> first place.  Or, write a separate entry for such buffers.

That, my friend, is utterly ridiculous.  Why not just tell me I shouldn't use
Emacs because it inconveniences you?

That's why we have option `special-display-regexps'.  I _want_ such buffers to
be displayed in a separate frame whenever they are displayed.

And no, I do not want to be obliged to specify separately the name of each
buffer that Emacs might decide to use in a temporary dialog to provide info for
a dialog question.

That's just silly.  That you would even bring it up, let alone proclaim it as a
rule ("you shouldn't") suggests bad faith.

The fact that when using `C', `x', etc. in Dired Emacs cannot tell that the
temporary display of a pop-up buffer is no longer needed after you hit RET, and
that Emacs does not remove such a frame like it removes a temporary pop-up
window, is a failing on Emacs's part.

The word "brain-dead" comes to mind (for Emacs, not for you).  The world's best
editor was not built to act like this.  From a user perspective this is a
regression since Emacs 22.  Until release 23 Emacs was completely sane in this
respect - since Day One.

I've mentioned a couple of possible workarounds, the best of which is to just
return to the Emacs 22 behavior.

But ideally the code should be fixed to remove the frame when the Dired command
interaction is finished.  There is no reason to show the buffer after the
operation is done.  That buffer is a list of objects that _will_ be acted on
_if_ you confirm.  After you confirm (or deny) its display has no raison d'etre.

Apparently you think that the proper fix of removing the frame is too hard to
implement for some reason.  In that case I request that we return to the sane
behavior of Emacs 22.

>  > Alternatively, restore the behavior in Emacs 22, where even if
>  > `special-display-regexps' would normally cause the buffer 
>  > to be displayed in a separate frame it is not: it is popped
>  > up in a window of the current frame.
> 
> Not necessarily: Try customizing `dired-shrink-to-fit' to nil.

emacs -Q in Emacs 22 does exactly what I described: it pops up a window, not a
frame, and it removes the window when the user dialog is finished.

(And `dired-shrink-to-fit' should simply be removed.  The only reason it ever
existed was for people on connections less than 1200 baud (300, 900).  See
Richard's comment in the source code.)

Sounds like you are just _searching_ for reasons to defend this regression and
not fix this bug.






  reply	other threads:[~2010-12-17 15:32 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-02 18:35 bug#7533: 24.0.50; `dired-mark-pop-up': delete frame afterwards if `pop-up-frames' Drew Adams
2010-12-02 19:05 ` martin rudalics
2010-12-02 19:22   ` Drew Adams
2010-12-03  8:17     ` martin rudalics
2010-12-03 16:22       ` Drew Adams
2010-12-03 18:16         ` martin rudalics
2010-12-03 18:33           ` Drew Adams
2010-12-03 18:41             ` martin rudalics
2010-12-04 22:44               ` Chong Yidong
2010-12-16 18:27                 ` Drew Adams
2010-12-17  6:32                   ` martin rudalics
2010-12-17 15:32                     ` Drew Adams [this message]
2010-12-17 16:12                       ` martin rudalics
2010-12-17 16:55                         ` Drew Adams
2010-12-17 18:09                           ` martin rudalics
2010-12-17 18:40                             ` Drew Adams
2010-12-21  6:48                           ` Chong Yidong
2010-12-03 20:27       ` Stefan Monnier
2012-04-05 20:23         ` Drew Adams
2012-04-06 14:02           ` martin rudalics
2012-04-06 14:44             ` Drew Adams
2012-04-06 14:53               ` martin rudalics
2012-04-06 15:34                 ` Drew Adams
2012-04-06 15:47                   ` martin rudalics
2012-04-06 16:10                     ` Drew Adams
2012-04-06 16:56                       ` martin rudalics
2012-04-06 17:08                         ` Drew Adams
2012-04-18 14:32                           ` Drew Adams
2012-05-25 20:52                             ` Drew Adams
2012-05-26 17:55                               ` bug#7533: 24.0.50; `dired-mark-pop-up': delete frame afterwards if `pop-up-frames' [PATCH] Drew Adams
2012-05-27 13:21                                 ` martin rudalics
2012-05-27 14:33                                   ` Drew Adams
2011-01-18 22:14 ` bug#7533: 24.0.50; `dired-mark-pop-up': delete frame afterwards if `pop-up-frames' Drew Adams
2012-09-05 14:30 ` martin rudalics
2012-09-05 14:33   ` Drew Adams
2012-10-03  9:11     ` martin rudalics
2012-10-03 15:52     ` 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=FC91B2B91B3B4C02AF17798D6C4CA5D9@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=7533@debbugs.gnu.org \
    --cc=cyd@stupidchicken.com \
    --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).