unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <none@example.invalid>
Subject: Re: even more(1) tells you how big the file is on the first screen
Date: 15 Apr 2003 22:59:17 +0200	[thread overview]
Message-ID: <98ph7b.r5.ln@acm.acm> (raw)
In-Reply-To: mailman.4612.1050362964.21513.bug-gnu-emacs@gnu.org

Dan Jacobson <jidanni@dman.ddts.net> wrote on Tue, 15 Apr 2003 04:57:00 +0800:
>>>>>> "RMS" == Richard Stallman <rms@gnu.org> writes:

> Well, here, a face saving solution: you know those little dots
> etc. that now appear in the very left margin on wrapped lines, and
> after the bottom of the file, when one has indicate-empty-lines=t?

> Well, it turns out that if you add a special mark for the beginning of
> the file in the very left margin, then one does not anymore need to
> rely on "Top" in the modeline to tell us we are on top.

Wouldn't work for those of us using Emacs without fringes.

> Therefore, if the user enables that, then he should also have the
> choice of having the modeline keep on indicating "traditional emacs
> style percents" or "alternative more(1) style percents".

> Anyway, how can we not convey how big the file is on the initial
> screen when even the wimpy more(1) command has for what, 25 years?
> (and less -M)

Dan, I tend to agree with you on the substantive points.  I personally
think the mode line ought to contain the size of the file.  Maybe this
was left out for efficiency reasons when the machines running emacs had
processor speeds measured in kilohertz rather than gigahertz.  But until
(??) Emacs gets this update, try the following in your .emacs:

(defvar mode-line-changed-p nil)
(when (not mode-line-changed-p)
  (setq-default mode-line-format
                (append (butlast default-mode-line-format)
                        '((:eval (format "--P%s/%s" (point)
                                         (save-restriction (widen)
                                                           (point-max)))))
                        (last default-mode-line-format)))
  (setq mode-line-changed-p t))

-- 
Alan Mackenzie (Munich, Germany)
Email: aacm@muuc.dee; to decode, wherever there is a repeated letter
(like "aa"), remove half of them (leaving, say, "a").

  parent reply	other threads:[~2003-04-15 20:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-13  2:34 even more(1) tells you how big the file is on the first screen Dan Jacobson
2003-04-14  2:36 ` 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 [this message]
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=98ph7b.r5.ln@acm.acm \
    --to=none@example.invalid \
    /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).