unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Cc: Kai Grossjohann <kai@emptydomain.de>,
	emacs-devel@gnu.org, Miles Bader <miles@gnu.org>
Subject: Re: Showing end of buffer
Date: 20 Jan 2004 00:59:18 +0100	[thread overview]
Message-ID: <x5llo3wkvd.fsf@lola.goethe.zz> (raw)
In-Reply-To: <m3hdyrqwnz.fsf@kfs-l.imdomain.dk>

storm@cua.dk (Kim F. Storm) writes:

> But I deliberately didn't want to make them too visible -- it's nice
> they are there, but they are a bit on the noisy side in some cases.
> 
> In any case, I have plans to make the bitmaps customizable (in
> lisp), so eventually you will be able to make them any way you
> like...

Could you customize them in viper-mode to look like
~
~
~
~
~
~
~
~
?

Just kidding.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2004-01-19 23:59 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-21  0:59 Showing end of buffer Richard Stallman
2003-04-21  1:57 ` Miles Bader
2003-04-21  6:05   ` Karl Eichwalder
2003-04-21  8:46     ` Miles Bader
2003-04-21  9:37       ` Karl Eichwalder
2003-04-23  1:00       ` Richard Stallman
2003-04-23  1:35         ` Miles Bader
2004-01-16 20:03       ` Kim F. Storm
2004-01-16 23:12         ` Michael Welsh Duggan
2004-01-17  0:33         ` Kevin Rodgers
2004-01-17  1:29           ` Miles Bader
2004-01-17  1:48           ` Kim F. Storm
2004-01-19 18:27         ` Glenn Morris
2004-01-19 23:51           ` Kim F. Storm
2004-01-19 20:42         ` Kai Grossjohann
2004-01-19 21:42           ` Miles Bader
2004-01-20  0:41             ` Kim F. Storm
2004-01-19 23:59               ` David Kastrup [this message]
2004-01-20  9:42                 ` Kai Grossjohann
2004-01-20  2:22               ` Miles Bader
2004-01-20 10:43                 ` Kim F. Storm
2004-01-19 21:55           ` Robert J. Chassell
2004-01-19 23:48           ` Kim F. Storm
2004-01-20  7:47             ` Kai Grossjohann
2004-01-20 15:31           ` Richard Stallman
2004-01-20 22:39             ` Kim F. Storm
2004-01-21  4:25               ` David Kastrup
2004-01-21 21:09               ` Richard Stallman
2004-01-22  4:55                 ` Michael Welsh Duggan
2004-01-23 18:24                   ` Richard Stallman
2004-01-24  0:12                     ` Kim F. Storm
2004-02-17 23:28             ` Kim F. Storm
2004-01-22 19:04         ` Peter Lee
2003-04-21 10:05     ` Kai Großjohann
2003-04-21 11:03       ` Karl Eichwalder
2003-04-21 12:01     ` Simon Josefsson
2003-04-21 13:28     ` Stefan Monnier
2003-04-21  7:30 ` Werner LEMBERG
2004-01-22 18:11 ` Sam Steingold
2004-01-22 21:25   ` Miles Bader
2004-01-22 21:41     ` Sam Steingold
2004-01-22 22:03       ` Miles Bader
2004-01-23  0:07       ` Kim F. Storm
2004-01-23 10:31         ` Gaute B Strokkenes

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=x5llo3wkvd.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=kai@emptydomain.de \
    --cc=miles@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).