From: Tim Visher <tim.visher@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 16668@debbugs.gnu.org
Subject: bug#16668: 24.3; Feature Request: Face to indicate lines displayed in window that are not part of the buffer.
Date: Mon, 10 Feb 2014 12:07:41 -0500 [thread overview]
Message-ID: <CAHa53uxyA9ETKhWPPp9YcfEBDuatdDjr7=oLhuHY_iNBw9Fxtw@mail.gmail.com> (raw)
In-Reply-To: <834n4cz1uj.fsf@gnu.org>
On Thu, Feb 6, 2014 at 10:40 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Tim Visher <tim.visher@gmail.com>
>> Date: Thu, 6 Feb 2014 09:33:15 -0500
>>
>> I'd like some visual indication of where the contents of the buffer
>> ends. I've always thought it would be nice to have a different color
>> for the space beneath the buffer in the window.
>>
>> So if I have a buffer with
>>
>> ```
>> this is the last line of text in the file
>>
>>
>> ``` note the 2 blank lines at the bottom of the file
>>
>> displayed in a window that looks like
>>
>> ```
>> snth
>> satoe
>> this is the last line of text in the file
>>
>>
>>
>>
>> ``` Note the 2 extra blank lines
>>
>> I'd like:
>>
>> ```
>> Normal Faces
>> Normal Faces
>> Normal Faces
>> Normal Faces
>> Normal Faces
>> Face indicating not part of buffer
>> Face indicating not part of buffer
>> ```
>>
>> Or something similar.
>
> A great introductory exercise for anyone who would like to gain
> experience in hacking the Emacs display engine. Volunteers are most
> welcome.
Sounds intriguing. Could you perhaps point me to a couple places to
start? I wouldn't mind gaining said experience. :)
next prev parent reply other threads:[~2014-02-10 17:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 14:33 bug#16668: 24.3; Feature Request: Face to indicate lines displayed in window that are not part of the buffer Tim Visher
2014-02-06 15:40 ` Eli Zaretskii
2014-02-10 17:07 ` Tim Visher [this message]
2014-02-10 17:48 ` Eli Zaretskii
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='CAHa53uxyA9ETKhWPPp9YcfEBDuatdDjr7=oLhuHY_iNBw9Fxtw@mail.gmail.com' \
--to=tim.visher@gmail.com \
--cc=16668@debbugs.gnu.org \
--cc=eliz@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 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.