all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: kai@emptydomain.de, emacs-devel@gnu.org
Subject: Re: Showing end of buffer
Date: Wed, 21 Jan 2004 16:09:23 -0500	[thread overview]
Message-ID: <E1AjPbH-0003FD-5L@fencepost.gnu.org> (raw)
In-Reply-To: <m3fzeai6rw.fsf@kfs-l.imdomain.dk> (storm@cua.dk)

    > That's what I would expect, too.  Lines don't necessarily come near
    > the right margin, so the indicator in the right margin can be far
    > away from the text.  They should all be on the left.

    But there may be a continuation glyph there if the last line is a
    continuation of the previous line.  

That is an annoying problem.  But I still think it should go on
the left.  We should not let that obscure case make us handle 

    Where should the up and down arrows go?  In the left fringe as well?

What do the up and down arrows mean?
(I have not seen this code running as of yet.)

  parent reply	other threads:[~2004-01-21 21:09 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1AjPbH-0003FD-5L@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=kai@emptydomain.de \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.