From: Richard Stallman <rms@gnu.org>
Cc: miles@gnu.org
Subject: Re: gdba probs
Date: Wed, 11 Dec 2002 12:45:16 -0500 [thread overview]
Message-ID: <E18MAv6-000280-00@fencepost.gnu.org> (raw)
In-Reply-To: <200212101414.gBAEEws31564@rum.cs.yale.edu> (monnier+gnu/emacs@rum.cs.yale.edu)
Their meaning is indeed obvious when they're not empty.
When they're empty, the buffer name gives a good hint, but I'm not
sure it's enough to make it "obvious".
When they are empty of real contents, they should instead display some
text that explains what the window is for and how to use it.
Agreed. Only displaying them when there's something to display would
also solve the above "problem".
Many users will like that feature, but I think it would be good to
implement the help text also.
next prev parent reply other threads:[~2002-12-11 17:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-05 20:40 gdba probs Nick Roberts
2002-12-05 21:49 ` Stefan Monnier
2002-12-07 2:38 ` Nick Roberts
2002-12-07 3:10 ` Miles Bader
2002-12-09 15:46 ` Stefan Monnier
2002-12-10 14:19 ` Stefan Monnier
[not found] ` <15862.30022.647969.267154@nick.uklinux.net>
[not found] ` <200212111411.gBBEBUn03805@rum.cs.yale.edu>
2002-12-11 22:27 ` Nick Roberts
2002-12-11 22:48 ` Stefan Monnier
2002-12-12 0:05 ` Nick Roberts
2002-12-12 13:49 ` Stefan Monnier
2002-12-12 14:13 ` Miles Bader
2002-12-13 22:21 ` Richard Stallman
2002-12-12 1:24 ` Miles Bader
2002-12-12 10:22 ` Kim F. Storm
2002-12-15 0:36 ` Nick Roberts
2002-12-07 21:25 ` Richard Stallman
2002-12-08 1:55 ` Nick Roberts
2002-12-09 20:21 ` Richard Stallman
2002-12-10 21:39 ` Nick Roberts
2002-12-10 23:44 ` Kim F. Storm
2002-12-11 20:40 ` Richard Stallman
2002-12-08 2:27 ` Miles Bader
2002-12-10 14:14 ` Stefan Monnier
2002-12-11 17:45 ` Richard Stallman [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-05 6:19 Miles Bader
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=E18MAv6-000280-00@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=miles@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).