unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Jacobson <jidanni@dman.ddts.net>
Subject: even more(1) tells you how big the file is on the first screen
Date: Sun, 13 Apr 2003 10:34:50 +0800	[thread overview]
Message-ID: <878yufxgz9.fsf@jidanni.org> (raw)

You know, I think it's bad that no matter if we are looking
a giant file, or a little file, the mode line has that "Top"
item, instead of some indication of percent.  "Top" is more closed
mouthed than an Army security officer. 
---1:---F1  some_file (Fundamental)--L1--Top--
We have to move the cursor down to engage the percent mechanism.

RMS, I recall, was pleased, as top was top.  However, I want more for
my money without budging a finger. I.e. we have just done M-x
compile. Does the compile output end just below the screen where we
thought it should, or does it go on for page upon page?

No, don't tell me to rely on the exit condition in the modeline, and
no, don't tell me to set the variable that always makes point equal
the end of the compile buffer.

Do instead break the dumb tradition of Top being top. Let's have emacs
give some clue as to how long the file is without us having to budge
from the first screen, etc.

I mean even the mere wimpy less(1) and even more(1) tell you what
percent you are on right there on the first screen.

Ya ya, I know they are talking about lines and you are talking about
screenfulls or whatever.  But it is your mission, Jim, to get the info
one way or the other, to the user, in the modeline, right there, first
screen, no ifs ands or buts.
-- 
http://jidanni.org/ Taiwan(04)25854780

             reply	other threads:[~2003-04-13  2:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-13  2:34 Dan Jacobson [this message]
2003-04-14  2:36 ` even more(1) tells you how big the file is on the first screen Richard Stallman
2003-04-14 20:57   ` Dan Jacobson
     [not found]   ` <mailman.4612.1050362964.21513.bug-gnu-emacs@gnu.org>
2003-04-15 20:59     ` Alan Mackenzie
2003-04-16  4:09       ` Dan Jacobson
     [not found] ` <mailman.4535.1050287953.21513.bug-gnu-emacs@gnu.org>
2003-04-14 17:11   ` Kevin Rodgers
     [not found] <mailman.4502.1050203467.21513.bug-gnu-emacs@gnu.org>
2003-04-13 10:10 ` David Kastrup

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=878yufxgz9.fsf@jidanni.org \
    --to=jidanni@dman.ddts.net \
    /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).