From: martin rudalics <rudalics@gmx.at>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: [davidk@lysator.liu.se: display-buffer change]
Date: Thu, 23 Aug 2007 23:19:59 +0200 [thread overview]
Message-ID: <46CDF9FF.4000305@gmx.at> (raw)
In-Reply-To: <E1IOJkm-0003ce-Co@fencepost.gnu.org>
> Would people please take a look at this issue?
I've tried to contact the author but he didn't respond.
> Was the change made deliberately?
I don't know when and why the change was made but it implements
the behavior documented as for Emacs 21 and 22. The user can
change the behavior by customizing split-height-threshold.
next prev parent reply other threads:[~2007-08-23 21:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-23 20:58 [davidk@lysator.liu.se: display-buffer change] Richard Stallman
2007-08-23 21:19 ` martin rudalics [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-23 18:06 Richard Stallman
2007-06-23 18:26 Richard Stallman
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=46CDF9FF.4000305@gmx.at \
--to=rudalics@gmx.at \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
/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).