From: Ken Hori <fplemma@gmail.com>
To: bug-gnu-emacs@gnu.org
Subject: bug#5445: term.el: term-height is off by 1 or 2 if header-line is present
Date: Thu, 21 Jan 2010 22:36:30 -0800 [thread overview]
Message-ID: <d0dc7c8f1001212236x42d2aa5dp120a4cd65b1f9a1b@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 325 bytes --]
Because term-height is off somewhat,
$ less <filename> # and then press 'k'
hides the first 1 or 2 lines of <filename> content.
Steps to reproduce:
1. emacs -q
2. M-x term <RET> <RET>
3. less FILENAME
4. press 'k'
Observed version: GNU Emacs 23.1.90.1 (x86_64-unknown-linux-gnu, GTK+
Version 2.18.3)
bzr revision 99310.
[-- Attachment #2: Type: text/html, Size: 420 bytes --]
next reply other threads:[~2010-01-22 6:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 6:36 Ken Hori [this message]
2012-06-20 8:35 ` bug#5445: term.el: term-height is off by 1 or 2 if header-line is present Chong Yidong
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=d0dc7c8f1001212236x42d2aa5dp120a4cd65b1f9a1b@mail.gmail.com \
--to=fplemma@gmail.com \
--cc=bug-gnu-emacs@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).