From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4712 invoked by alias); 12 Jan 2015 18:50:28 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 4696 invoked by uid 89); 12 Jan 2015 18:50:28 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mail-ob0-f172.google.com Received: from mail-ob0-f172.google.com (HELO mail-ob0-f172.google.com) (209.85.214.172) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Mon, 12 Jan 2015 18:50:26 +0000 Received: by mail-ob0-f172.google.com with SMTP id va8so23815748obc.3 for ; Mon, 12 Jan 2015 10:50:25 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=iM3GHRdxGVbMCh6IPxxkjZ+zz0aAK+pMpb2cE1fXKNM=; b=OAwCtJBLy/bMHUYdq7T/qThUikCo4QDK+TDPMg1mQbiQtaGzzBH7F8+nbhnFItH5ml d5tXqfqdzui16TeuiclnphCOtBiZKi5vQ7Kp/K5RMdh/P3mBHto9CV5xiK8D98QHaty4 SoMecFRRirCbkMMKSBUz9w/8usXx2iPXhFOM2DPHi8+NxPH9PWnpnbSxA44vk9i1ALVg 8K9et9MeUK5eo1DWVc2Bfn23LOPZ9Rzra9JLPK2KfHxwECsL1Bvkay3lbzCz+3PGjQtq XrLZXwdWIPxAZDUFIagTI3IUdVs+6V3mGm5FLuq7Qw5gCDyDh/pUs5MmOvL1CaAHd+br Oeyw== X-Gm-Message-State: ALoCoQkQUUe5p/3kXFIW3abuxtvNyh7WPLlaYtpHfrs+CVeLDG3GEgg4G48NFyTVxzH0IME9CubQ MIME-Version: 1.0 X-Received: by 10.182.27.207 with SMTP id v15mr18359286obg.21.1421088624998; Mon, 12 Jan 2015 10:50:24 -0800 (PST) Received: by 10.182.222.98 with HTTP; Mon, 12 Jan 2015 10:50:24 -0800 (PST) In-Reply-To: <83a91r6lbd.fsf@gnu.org> References: <1417094168-25868-1-git-send-email-gbenson@redhat.com> <1417094168-25868-4-git-send-email-gbenson@redhat.com> <20141210122233.GA7299@blade.nx> <21671.20308.262958.475080@ruffy2.mtv.corp.google.com> <20150107084255.GA17867@blade.nx> <21680.36641.315766.209208@ruffy2.mtv.corp.google.com> <83a91r6lbd.fsf@gnu.org> Date: Mon, 12 Jan 2015 18:50:00 -0000 Message-ID: Subject: Re: [PATCH 3/3 v2] Implement completion limiting From: Doug Evans To: Eli Zaretskii Cc: Gary Benson , gdb-patches Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes X-SW-Source: 2015-01/txt/msg00314.txt.bz2 On Sat, Jan 10, 2015 at 1:23 AM, Eli Zaretskii wrote: >> From: Doug Evans >> Date: Fri, 9 Jan 2015 18:32:01 -0800 >> Cc: gdb-patches@sourceware.org >> >> +If the number of possible completions is large, @value{GDBN} will >> +print as much of the list as it has collected, as well as a message >> +indicating that the list may be truncated. >> + >> +@smallexample >> +(@value{GDBP}) b m@key{TAB}@key{TAB} >> +m *** List may be truncated, max-completions reached. *** >> +main >> +<... the rest of the possible completions ...> >> +(@value{GDBP}) b m > > Doesn't the "list may be truncated" message scrolls off the screen, if > the list is long enough? If so, wouldn't it be better to display that > message at the end instead, saying something like > > (More completions follow; max-completions exceeded.) If the user sets a bad height, or if pagination is turned off, possibly. I can put it at the end.