unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-pretest-bug@gnu.org, raman@users.sf.net
Subject: Re: 23.0.50; Cannot run calculator on TTY
Date: Sat, 13 Oct 2007 15:47:54 -0400	[thread overview]
Message-ID: <E1Igmxm-0002Fk-Du@fencepost.gnu.org> (raw)
In-Reply-To: <471089B7.7030503@gmx.at> (message from martin rudalics on Sat, 13 Oct 2007 11:02:47 +0200)

     > One idea that occurs to me is that `window-min-height' could count the
     > header line, if any.

    Do you mean

    "One idea that occurs to me is that the `split-window' could NOT count
    the header line, if any."

We may be trying to say the same thing in two ways.  Basically, my
idea is that the minimum allowed number of lines in a window -- in
every sense -- would not depend on whether one of those lines
is used as a header line.

This might require changes in redisplay as well
in order to function correctly.

    The only drawback I can think of is that splitting may produce a window
    showing a header- and a mode-line only.

Yes, that could happen.  It might be a lesser problem than the one we
now have.  At least it would be comprehensible and would follow a
simple rule.

     > That way, the fact that some buffers have header
     > lines and others don't will not cause any problems for vertical
     > splitting of windows.  In the most usual cases, at least -- but not
     > in all cases, perhaps.
     >
     > Another solution would be to pass a two buffers to `split-window',
     > telling it to select those two buffers, and to calculate based
     > on the assumption that those buffers will be displayed.

    That's what I meant with "provide explicit (optional) parameters for
    `split-window-vertically' and `split-window-horizontally'".  This would
    also mean that the client of these functions (and `split-window') would
    have to set the corresponding (buffer-local) variables _before_ calling
    these.

Then we both had the same idea.  If people like this better, it is
fine with me.

  reply	other threads:[~2007-10-13 19:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-01  2:35 23.0.50; Cannot run calculator on TTY raman
2007-10-01  6:16 ` martin rudalics
2007-10-01 13:17   ` T. V. Raman
2007-10-01 15:41     ` martin rudalics
2007-10-02  3:13       ` T. V. Raman
2007-10-02  7:32         ` martin rudalics
2007-10-02 13:23           ` T. V. Raman
2007-10-02 17:51             ` martin rudalics
2007-10-03  1:49               ` T. V. Raman
2007-10-03  6:21                 ` martin rudalics
     [not found]                   ` <18179.41840.532732.664369@gargle.gargle.HOWL>
     [not found]                     ` <18187.33374.913139.901742@gargle.gargle.HOWL>
2007-10-09 17:07                       ` martin rudalics
2007-10-11  4:21                         ` T. V. Raman
2007-10-11  8:50                           ` martin rudalics
2007-10-11 13:30                             ` T. V. Raman
2007-10-12  9:23                               ` martin rudalics
2007-10-13  0:18                                 ` Richard Stallman
2007-10-13  9:02                                   ` martin rudalics
2007-10-13 19:47                                     ` Richard Stallman [this message]
2007-10-26 21:03                                       ` martin rudalics

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=E1Igmxm-0002Fk-Du@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=raman@users.sf.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 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).