[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: emacs -nw vs. default-indicate-empty-lines
From: |
Dan Jacobson |
Subject: |
Re: emacs -nw vs. default-indicate-empty-lines |
Date: |
Mon, 27 Nov 2006 23:33:44 +0800 |
Markus says:
(defun vi-waves ()
(interactive)
(setq ol (make-overlay (point-min) (point-max) (current-buffer) t t))
(overlay-put ol 'after-string "\n~\n~\n~\n~\n~\n~"))
OK, but that effect (however best it be written) should extend to the
bottom of the screen all in one invocation.
Also indicate-empty-lines,
*Visually indicate empty lines after the buffer end. If non-nil, a
bitmap is displayed in the left fringe of a window on
window-systems.
lacks an action for when not on a window-system. So the vi-waves
effect should be its action in the case of emacs -nw.
Also default-indicate-empty-lines should be t instead of nil by
default. Why not?
So now the user will see a fringe, or tildes if -nw, and all without
adding anything to his .emacs file.
P.S., Shocking discovery: all the vi emulations included with emacs
don't put the tilde waves at the end of the buffer by default, even
when using emacs -nw!
Implementing my suggestions above would fix that too.
I mean even lowly less(1) beats emacs here.