Re: fringe bugs and issues (and a couple display margin bugs)

[Alveola Petrofsky]

rms@gnu.org (Richard Stallman) writes:
> 
>     It should be possible to get the emacs 20 behavior of not
>     continuing the line, and placing the cursor in the fringe when
>     point is at the end of such a line.
> 
> This must be a misunderstanding, because Emacs has never done this.

By "fringe", I meant the column containing continuation marks.  Since
at least version 18, emacs has put the cursor in that column if you
are at the end of a line whose display width is equal to the width of
the rest of the window.  The line is not continued.  This is a special
case: for other line lengths, shorter or longer, the cursor is not
placed in the continuation mark column for any of the line's buffer
postions.  The benefit of this feature was that emacs never wasted a
whole row to display an empty continuation line, as emacs 21 X frames
do.

Eli wrote:
> > * Fringes on wrong side of display margins.
> > Fringes should be inside display margins, shouldn't they?
> 
> I'm not sure.  Please tell why do you think so.

Because truncation marks should be adjacent to what is truncated.
Consider:

  foo$nternationaliza$bar

  $foonternationalizabar$

Which makes more sense to you?  (Please pretend that the "$"s are
little bitmaps, since I seem to be the only one who thinks that's
irrelevant to choosing the desired layout :-).)

> > In any case they should be consistent on tty and X frames.
> > Currently the fringes are inside the display margins on ttys and
> > outside on X frames.
> 
> That's because tty's don't support fringes at all.  If you refer to
> the places where continuation and truncation glyphs are displayed as
> the fringe, then the behavior is inconsistent.  But that's not how
> Emacs refers to that.

Emacs is living in denial if she thinks that makes it better.  Forget
I used the word "fringe".  If some frames put truncation marks on the
inside of the display margins, and other frames put them on the
outside, then that is inconsistent behavior.


I understand that the implementation is such that enhancing it to
behave consistently will be difficult, and that you don't consider it
worthwhile.  And, unfortunately, I'm not volunteering to do it myself.
I'm just calling the bugs as I see 'em, for the consideration of
anyone who might work on this.

-al