From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Heime Newsgroups: gmane.emacs.help Subject: RE: [External] : Continue cycling from a particular element in collection Date: Tue, 22 Aug 2023 21:21:50 +0000 Message-ID: <6ikysmS-qNwmE2xUa6UfijjEq-A_PnqtlDD_jj8IrrpVCCK9mDgkWVzrfkig1sIVNB9DJnbLR3eJB8yHsQprc0kmU3JdhEmsxfUJfIGioF8=@protonmail.com> References: <3UFVadxSsN_hYG9eXZu35vNXUf5Y4Fhyq8x31fG1Ts1sBcw-bmM8Ql0Xptuj64726ZL7GltOIJ1BamUoKWMLoPO9d3_aHHmPWcu_czcDTZ4=@protonmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="15514"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Drew Adams , Heime via Users list for the GNU Emacs text editor To: Heime Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Tue Aug 22 23:22:21 2023 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qYYpQ-0003rw-Q9 for geh-help-gnu-emacs@m.gmane-mx.org; Tue, 22 Aug 2023 23:22:20 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qYYp6-0007tZ-Kk; Tue, 22 Aug 2023 17:22:00 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qYYp4-0007tQ-JZ for help-gnu-emacs@gnu.org; Tue, 22 Aug 2023 17:21:58 -0400 Original-Received: from mail-4324.protonmail.ch ([185.70.43.24]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qYYp2-0006n7-07 for help-gnu-emacs@gnu.org; Tue, 22 Aug 2023 17:21:58 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1692739313; x=1692998513; bh=hMTAM6giRCtEG9vVY1FrzOkPH612aOxlSuPUxpe23Fw=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=dtsqhll14ZJqELH5RzWtb9J3zPaRbZx2uD7Uzqhs3pcPZDSE7LqAMKajPBzS0u/7B ulaUVtn/ahNY+vCDg4OCis5Q6OLh5CJMKHukVNkH9ajMlPEBSN+tsyGkNFeoCjQsDl Pj7+r+KO7urOWVCyLEI2oJKdIFX3vwD2gpOZ6vrHy+pTpvj7f1l7fEMh7j1tHUS7it DQWcBlhgxYBr1Mgn8KT+xWcR8rB/Ysyc/MPvcxlr8mxhThv6raN1CrbGAy4y51J6hU jMqJ3q3bAh5rSQSH4QflF7iPerPBs0d2qrV5Dhjo2CjSzO9xu27ZzBir/Lodd4clt2 PW/91dExR3U3g== In-Reply-To: Feedback-ID: 57735886:user:proton Received-SPF: pass client-ip=185.70.43.24; envelope-from=heimeborgia@protonmail.com; helo=mail-4324.protonmail.ch X-Spam_score_int: -17 X-Spam_score: -1.8 X-Spam_bar: - X-Spam_report: (-1.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, TO_EQ_FM_DIRECT_MX=0.275 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.help:144927 Archived-At: ------- Original Message ------- On Wednesday, August 23rd, 2023 at 9:11 AM, Heime wrote: > ------- Original Message ------- > On Wednesday, August 23rd, 2023 at 9:04 AM, Drew Adams drew.adams@oracle.= com wrote: >=20 >=20 >=20 > > > > > I am using 'completing-read' with INITIAL-INPUT to prefill the > > > > > minibuffer > > > > > with the first entry "alpha". Hew can I then start at index k fro= m > > > > > collection > > > > > as the next entry. > > > >=20 > > > > There is NO "next entry". INITIAL-INPUT is simply a string that get= s > > > > inserted in the minibuffer. It need not correspond to any candidate > > > > provided by argument COLLECTION, meaning that it need not correspon= d to > > > > any completion. > > > >=20 > > > > `completing-read' can be LAX, meaning that, if REQUIRE-MATCH is nil= or > > > > absent then it accepts any text you input - it need not be a comple= tion > > > > candidate. > > >=20 > > > Ok, but can I ask completing-read to start from > > > a different point in collection, rather than > > > from the beginning ? > >=20 > > Dunno. I'm no expert on vanilla Emacs cycling, > > and I'm not sure what kind of cycling ("next entry") > > you have in mind. >=20 >=20 > By 'Next Entry' I mean what shows up after INITIAL-INPUT > is shown after pressing . >=20 > > If you're using argument DEFAULTS to provide a list > > of "entries" then you can of course sort it (or > > truncate it) however you like, to affect the "future > > history". > >=20 > > If you're using a HISTORY variable and cycling the > > (past/real) history then I suppose you could sort > > (or truncate) its value. > >=20 > > But entries in neither DEFAULTS nor HISTORY need be > > elements of COLLECTION. > >=20 > > If you meant the "future history" elements that are > > provided by the misfeature of automatically adding > > everything in COLLECTION to that pseudo-history, > > then no, AFAIK there's no way to filter, sort, or > > truncate the elements from COLLECTION that get added. > >=20 > > But maybe there will be now, since I think they're > > considering adding some option that may help here - > > dunno. > >=20 > > Maybe someone else will have a useful suggestion. It is a deficiency on the part of completing-read that makes INITIAL-INPUT unaware of COLLECTION and of REQUIRE-MATCH.