all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: occitan@esperanto.org, 12419@debbugs.gnu.org
Subject: bug#12419: Mouse click changes layout
Date: Sat, 15 Sep 2012 14:14:39 +0300	[thread overview]
Message-ID: <83627ftu5c.fsf@gnu.org> (raw)
In-Reply-To: <50545AE1.4020609@gmx.at>

> Date: Sat, 15 Sep 2012 12:39:29 +0200
> From: martin rudalics <rudalics@gmx.at>
> CC: occitan@esperanto.org, 12419@debbugs.gnu.org
> 
>  >> You see no problem with minibuffer window resizing not restoring the
>  >> initial configuration?
>  >
>  > When the minibuffer window's growth absolutely must resize windows
>  > other than the lowest one, no.  IMO, it's better than Emacs 23's
>  > punting and displaying only a portion of the echo-area message.
> 
> Where do you see that?  Can you give an example?

Try the recipe I showed earlier in this thread with Emacs 23.3, but
use 1000 instead of 380, and you will see that only the last part of
the echo-area message is shown.

>  >>  >> I use ediff with the control panel on the bottom of the frame.  How can
>  >>  >> I resize the minibuffer in this case?
>  >>  >
>  >>  > Why, by resizing the window above the control panel, of course.
>  >>
>  >> And how would you size the minibuffer back?
>  >
>  > I don't understand the problem you obviously have in mind.
> 
> Then put a one-line window at the bottom of your frame and resize the
> minibuffer.  At the time it sizes back the one-line window has grown.

OK, but why is that a problem grave enough to be concerned about?
Using Ediff in such a way is non-standard, so won't be a problem for
most users.  And even in this configuration, what is so bad about
this?

>  > If the lowest window is large enough, why not show more of
>  > the echo-area message, instead of always showing only the last N lines?
> 
> I don't understand you.  As far as minibuffer resizing is concerned, you
> can show any number of lines in the minibuffer as long as you don't try
> to delete other windows.  So the N lines restriction you see must come
> from somewhere else.

Maybe it does, but I tried that with "emacs -Q", so the number of such
other places is severely limited ;-)

AFAICS, with your patch the minibuffer is never resized to show more
than 9 lines, with the default size of the frame which can show 33
text lines.  This is so even if I do _not_ split the frame into 2
windows, one below the other, but instead invoke 'message' from the
original window configuration displayed by "emacs -Q", where there's a
single window showing the "*scratch*" buffer.  Try this:

  emacs -Q
  (message (make-string 1000 ?a))
  C-x C-e

How many lines and how many a's do you see in the echo area?





  reply	other threads:[~2012-09-15 11:14 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-11 22:04 bug#12419: Mouse click changes layout Daniel Pfeiffer
2012-09-12  2:59 ` Eli Zaretskii
2012-09-12  8:09 ` martin rudalics
2012-09-13 20:41   ` Daniel Pfeiffer
2012-09-14  9:00     ` martin rudalics
2012-09-14 10:36       ` Eli Zaretskii
2012-09-14 13:38         ` martin rudalics
2012-09-14 14:10           ` Drew Adams
2012-09-14 15:08             ` martin rudalics
2012-09-14 16:18               ` Drew Adams
2012-09-14 19:14                 ` martin rudalics
2012-09-14 19:40                   ` Drew Adams
2012-09-15  9:51                     ` martin rudalics
2012-09-15 10:31                       ` martin rudalics
2012-09-14 14:53           ` Eli Zaretskii
2012-09-14 15:16             ` martin rudalics
2012-09-14 16:20               ` Drew Adams
2012-09-14 19:14                 ` martin rudalics
2012-09-14 16:56               ` Eli Zaretskii
2012-09-14 19:15                 ` martin rudalics
2012-09-14 20:16                   ` Eli Zaretskii
2012-09-15  9:54                     ` martin rudalics
2012-09-15 10:23                       ` Eli Zaretskii
2012-09-15 10:39                         ` martin rudalics
2012-09-15 11:14                           ` Eli Zaretskii [this message]
2012-09-15 12:44                             ` martin rudalics
2012-09-15 13:35                               ` Eli Zaretskii
2012-09-15 14:34                                 ` martin rudalics
2012-09-14 15:45             ` Stefan Monnier
2012-09-14 19:14               ` martin rudalics
2012-09-14 19:56                 ` Stefan Monnier
2012-09-15  9:51                   ` martin rudalics
     [not found]       ` <5055D769.1060804@t-online.de>
2012-09-16 17:45         ` martin rudalics
2012-09-22 20:29           ` Daniel Pfeiffer
2012-09-23  9:21             ` martin rudalics
2012-09-23 21:56               ` Daniel Pfeiffer
2012-09-24  8:17                 ` martin rudalics
2012-09-24 14:33                   ` Eli Zaretskii
2012-09-25  9:58                     ` martin rudalics
2012-09-25 12:09                       ` Eli Zaretskii
2012-09-25 14:12                         ` martin rudalics
2012-09-26  8:22                           ` Eli Zaretskii
2012-09-26 11:03                             ` martin rudalics
2012-09-26 11:55                               ` Eli Zaretskii
2012-09-26 12:43                                 ` martin rudalics
2012-09-26 13:17                                   ` Eli Zaretskii
2012-09-26 13:44                                     ` martin rudalics
2012-09-26 13:57                                       ` Eli Zaretskii
2012-09-24 22:20                   ` Daniel Pfeiffer
2012-09-25  6:32                     ` Eli Zaretskii
2012-09-25  9:58                     ` martin rudalics
2020-09-13 17:06               ` Lars Ingebrigtsen
2020-12-07 16:43                 ` Lars Ingebrigtsen

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=83627ftu5c.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=12419@debbugs.gnu.org \
    --cc=occitan@esperanto.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 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.