From: David De La Harpe Golden <david@harpegolden.net>
To: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Yesterdays observation of lower left fringe
Date: Tue, 23 Sep 2008 19:43:44 +0100 [thread overview]
Message-ID: <48D938E0.3010001@harpegolden.net> (raw)
In-Reply-To: <48D93120.4030308@gmail.com>
Lennart Borgman (gmail) wrote:
>
> If the last line has an ending newline char then place the fringe symbol
> one line down (and let it be the same symbol). What about that?
>
>
That would make the normal case where there is a terminating newline
present*, kind of ugly IMO. I'd agree that the upper right symbol is
a bit wierd, but better use a different symbol when there's no final
newline, maybe something like |... , not move a line down IMO. i.e. a
dotted horizontal bar on the "L" because the line hasn't been terminated
yet.
* Technically, a bit like C vs. Pascal ';', most programs treat "\n" as
a line terminator, some as a line separator. Having the fringe marker
move another line down for a present final newline would make more sense
if newline were considered a separator, as programs observing that
convention might think there was a new, empty line if the last line in
the file had a newline at the end. But AFAIK considering it a
terminator is far more common than separator.
next prev parent reply other threads:[~2008-09-23 18:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-20 1:30 Yesterdays observation of lower left fringe Lennart Borgman (gmail)
2008-09-23 18:03 ` David De La Harpe Golden
2008-09-23 18:10 ` Lennart Borgman (gmail)
2008-09-23 18:43 ` David De La Harpe Golden [this message]
2008-09-23 18:47 ` Lennart Borgman (gmail)
2008-09-23 19:30 ` David De La Harpe Golden
2008-09-23 19:51 ` Lennart Borgman (gmail)
2008-09-23 20:05 ` David De La Harpe Golden
2008-09-23 20:11 ` Lennart Borgman (gmail)
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=48D938E0.3010001@harpegolden.net \
--to=david@harpegolden.net \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman@gmail.com \
/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).