From: Richard Stallman <rms@gnu.org>
Cc: storm@cua.dk, eliz@is.elta.co.il, emacs-devel@gnu.org
Subject: Re: Weird frame/buffer interaction
Date: Wed, 6 Mar 2002 19:30:03 -0700 (MST) [thread overview]
Message-ID: <200203070230.g272U3Y02066@wijiji.santafe.edu> (raw)
In-Reply-To: <37D24D4FFB26F74D8F4C82CF039354F1013883C4@xch-stl-08.mw.nos.boeing.com> (michael.p.broida@boeing.com)
I appreciate the effort that you are making to explore the envelope of
this bug, but that is not an effective way to get to the bottom of
things. Information about the envelope of the bug will never lead us
to the cause of the problem. That is not the way problems are found.
What would in fact help is a test case that we can really try. I
cannot try the test case that was sent because I can't do anything
with such a tall frame. Can you find a test case which uses
an ordinary size frame?
I suggest you read the Bugs section in the Emacs manual, which
explains what information will actually help find the bug.
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-03-07 2:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-05 17:19 Weird frame/buffer interaction EXT-Broida, Michael P
2002-03-07 2:30 ` Richard Stallman [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-07 19:32 EXT-Broida, Michael P
2002-03-07 18:31 EXT-Broida, Michael P
2002-03-07 17:28 EXT-Broida, Michael P
2002-03-05 17:07 EXT-Broida, Michael P
2002-03-05 17:02 EXT-Broida, Michael P
2002-03-07 2:30 ` Richard Stallman
2002-03-04 18:31 EXT-Broida, Michael P
[not found] <3C7EB0A2.D73F6CD4@boeing.com>
[not found] ` <3C7F1FA6.2105F03E@is.elta.co.il>
2002-03-01 15:50 ` Kim F. Storm
2002-03-04 4:07 ` Richard Stallman
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=200203070230.g272U3Y02066@wijiji.santafe.edu \
--to=rms@gnu.org \
--cc=eliz@is.elta.co.il \
--cc=emacs-devel@gnu.org \
--cc=storm@cua.dk \
/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.