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: ingo.lohmar@posteo.net, emacs-devel@gnu.org
Subject: Re: set-frame-size should respect line-spacing!?
Date: Mon, 14 Oct 2019 11:06:47 +0300	[thread overview]
Message-ID: <83d0ezkay0.fsf@gnu.org> (raw)
In-Reply-To: <57de2a38-3b9e-4d44-c1a5-a2d1bd988292@gmx.at> (message from martin rudalics on Sun, 13 Oct 2019 19:06:52 +0200)

> Cc: emacs-devel@gnu.org, ingo.lohmar@posteo.net
> From: martin rudalics <rudalics@gmx.at>
> Date: Sun, 13 Oct 2019 19:06:52 +0200
> 
>  > I think the only case where the issues raised by bug#14825 should
>  > matter is when we decide whether a window is too small.  E.g., what
>  > bad things will happen if we interpret window-min-height in terms of
>  > the default face's font set for the buffer shown (or to be shown) in
>  > the window?
> 
> Such an interpretation would cut both ways.  Think of people that use
> 'line-spacing' for ages or have remapped the default face font to
> something higher.  They would be surprised that C-x 2 all of a sudden
> complains that their window is "too small for splitting".

I very much doubt that, since less than 4 lines in a window is hardly
useful.

> Also note that often the buffer to be shown in the new window, for
> example via 'pop-to-buffer', is unknown to 'split-window'.

In that case, let us behave as we do currently.

> I'm not against a fix for Bug#14825.  But doing it in a clean and
> consistent way will be pretty hard.

I'm not going to lament its not being solved; it was you who brought
it into this discussion.  I suggest to proceed with the original
discussion disregarding that bug for now.



      reply	other threads:[~2019-10-14  8:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-11 20:44 set-frame-size should respect line-spacing!? Ingo Lohmar
2019-10-12  7:00 ` Eli Zaretskii
2019-10-12  7:12   ` Ingo Lohmar
2019-10-12  7:48     ` Eli Zaretskii
2019-10-12  8:25       ` martin rudalics
2019-10-12  8:25     ` martin rudalics
2019-10-12  9:45       ` Eli Zaretskii
2019-10-12  9:56         ` Ingo Lohmar
2019-10-12 11:03         ` martin rudalics
2019-10-12 13:11           ` Eli Zaretskii
2019-10-13  8:16             ` martin rudalics
2019-10-13  9:10               ` Eli Zaretskii
2019-10-13 12:15                 ` martin rudalics
2019-10-13 12:18                   ` Eli Zaretskii
2019-10-13 12:51                     ` martin rudalics
2019-10-13 13:20                       ` Eli Zaretskii
2019-10-13 17:06                         ` martin rudalics
2019-10-14  8:06                           ` Eli Zaretskii [this message]

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=83d0ezkay0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=ingo.lohmar@posteo.net \
    --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.