From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: indicate-buffer-boundaries
Date: Sun, 26 Sep 2004 01:50:49 +0200 [thread overview]
Message-ID: <m3k6uhnc12.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <E1CAzfj-00085a-Ou@fencepost.gnu.org> (Richard Stallman's message of "Fri, 24 Sep 2004 19:40:15 -0400")
Richard Stallman <rms@gnu.org> writes:
> The interface for indicate-buffer-boundaries is really kludgy.
> I cleaned up the doc for it, but I would really rather make
> it simpler.
>
> A good way to make it simpler is to use an alist. Pick four suitable
> symbols, one for each of these icons. I suggest `top', `bottom', `up'
> and `down'. t can serve as a default for all four. In the alist,
> associate these symbols with either `left', `right' or `nil'.
>
> Instead of current (t . right), we would use ((top . left) (t . right))
> or ((top . left) (bottom . right) (up . right) (down . right))
> Instead of current (left . nil), we would use ((top . left) (bottom . left)).
>
> Isn't that clearer? It is much less ad-hoc.
That would be cleaner, yes.
I will change it.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2004-09-25 23:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-24 23:40 indicate-buffer-boundaries Richard Stallman
2004-09-25 23:50 ` Kim F. Storm [this message]
2004-11-14 16:38 ` indicate-buffer-boundaries Lars Hansen
-- strict thread matches above, loose matches on Subject: below --
2004-11-21 17:35 indicate-buffer-boundaries Andreas Schwab
2004-11-21 20:36 ` indicate-buffer-boundaries Lars Hansen
2004-11-21 23:12 ` indicate-buffer-boundaries Andreas Schwab
2004-11-28 0:58 ` indicate-buffer-boundaries Kim F. Storm
2004-11-25 2:21 ` indicate-buffer-boundaries Richard Stallman
2004-11-25 15:35 ` indicate-buffer-boundaries Lars Hansen
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=m3k6uhnc12.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=emacs-devel@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).