From: Bruce Korb <bkorb@veritas.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Major usability issue
Date: Tue, 03 Sep 2002 15:46:07 -0700 [thread overview]
Message-ID: <3D753BAF.8D158605@veritas.com> (raw)
In-Reply-To: pB9d9.21$QK1.1819@paloalto-snr1.gtei.net
Barry Margolin wrote:
> >This is a behavioral change not listed in the news.
>
> What change?
If not a change, then I have inadvertently always had the
mini buffer line limit low enough that I never stumbled into
it before. Can't tell anymore. Don't have a 20.x version
access.....
Thanks to all!
next prev parent reply other threads:[~2002-09-03 22:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1030996683.19870.help-gnu-emacs@gnu.org>
2002-09-02 20:04 ` inserting output of shell-command (was: Major usability issue) lawrence mitchell
2002-09-02 20:33 ` Lute Kamstra
2002-09-03 10:22 ` Major usability issue Kai Großjohann
2002-09-03 20:52 ` Bruce Korb
[not found] ` <mailman.1031086444.5149.help-gnu-emacs@gnu.org>
2002-09-03 21:12 ` Barry Margolin
2002-09-03 22:46 ` Bruce Korb [this message]
2002-09-04 1:58 ` Miles Bader
2002-09-03 22:11 ` Kai Großjohann
2002-09-03 13:36 ` Peter Boettcher
2002-09-02 20:01 Bruce Korb
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=3D753BAF.8D158605@veritas.com \
--to=bkorb@veritas.com \
--cc=help-gnu-emacs@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.
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).