From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Mauro Aranda Newsgroups: gmane.emacs.bugs Subject: bug#65089: 30.0.50; shell-command filename completion unexpected behavior change Date: Tue, 15 Aug 2023 19:23:18 -0300 Message-ID: <13457d93-12a0-bf24-22b6-0b9e4e6ca4fa@gmail.com> References: <7e89aab4-41bb-384a-760d-9fd7830ff6b9@gmail.com> <83pm41sqbs.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="19560"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 Cc: Eli Zaretskii , 65089@debbugs.gnu.org, Augusto Stoffel To: Stefan Monnier Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Aug 16 00:24:17 2023 Return-path: Envelope-to: geb-bug-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 1qW2SW-0004oG-S5 for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 16 Aug 2023 00:24:16 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qW2SJ-0008Jz-UM; Tue, 15 Aug 2023 18:24:03 -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 1qW2SI-0008JZ-4w for bug-gnu-emacs@gnu.org; Tue, 15 Aug 2023 18:24:02 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qW2SH-0001yf-T8 for bug-gnu-emacs@gnu.org; Tue, 15 Aug 2023 18:24:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qW2SH-0007zY-Oo for bug-gnu-emacs@gnu.org; Tue, 15 Aug 2023 18:24:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Mauro Aranda Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 15 Aug 2023 22:24:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 65089 X-GNU-PR-Package: emacs Original-Received: via spool by 65089-submit@debbugs.gnu.org id=B65089.169213821230684 (code B ref 65089); Tue, 15 Aug 2023 22:24:01 +0000 Original-Received: (at 65089) by debbugs.gnu.org; 15 Aug 2023 22:23:32 +0000 Original-Received: from localhost ([127.0.0.1]:37033 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qW2Rn-0007yq-SI for submit@debbugs.gnu.org; Tue, 15 Aug 2023 18:23:32 -0400 Original-Received: from mail-oa1-x30.google.com ([2001:4860:4864:20::30]:42136) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qW2Rl-0007yb-1p for 65089@debbugs.gnu.org; Tue, 15 Aug 2023 18:23:30 -0400 Original-Received: by mail-oa1-x30.google.com with SMTP id 586e51a60fabf-1c4cd0f6cb2so1842928fac.0 for <65089@debbugs.gnu.org>; Tue, 15 Aug 2023 15:23:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1692138203; x=1692743003; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=2aaf/Gh0HY2kG0KBNQfJlHE4RhKhPEMMHF2EganHC4g=; b=ABXN+r2gqhCQ+EHym+e/1Q3mTy2KU3DT5dI5OrFeAuAVtmzh/SfUNIeHC/DtFl61Gk wcFaLcV/v7AysJMy+zVbsUBbbX7Ukr5xhr4h7SnVO+oG0ZgjQ/rQP9UgRtEwlbEC+VnM ougJyqQnN0Xyus2lAygJ0tar1cuHJqP97WWrBSirqOnAQMgkYNKw/zQectR9N+wQhHNX +kg1f1B9bhOmaka3SBRXNCZ6SDhkr+zJWdKklyx2j+tsKloIrP1CexPh+lhO59RshQj2 d3rY2DOB/KenERR4byp8cSmtVIK3TMF20IwmerEaIqnbcELfDViPzKt6CXKu8rDCCRSg KLBg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692138203; x=1692743003; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=2aaf/Gh0HY2kG0KBNQfJlHE4RhKhPEMMHF2EganHC4g=; b=HPCUBes5sLZtSajb+9alUMeRfzasYpsHBMqOhQoEky8uEbsY3rRJl71shPP+pkDDRC Dy2BQIHo19wuqB3kt1/iFs/3R3Txmve7Ccg8GHe1tpNoJCJ7Mbg2wbmH4VoQWoyNc0Gb sM+HGP9HRaHU8SuRpTEGrs+0RA8r8+WSZl66kEU1Cg/aHgj/cv588l+kWhwUT4gVz6qS YagtKwEbqbZ6BTa71Gsnfcwk07huNbbJFvNSRji2umhSfzLYU/oR65rigBVUFAEKXweQ PmGvkJNcwMdR8T+2EtKD41PeMTxCKBQv7a2ZArK5YiDagfua1GpZdFYfhyzDrwcvuW8y sgAg== X-Gm-Message-State: AOJu0YynvsDxj9dtl1pcsl2L1LtC8F5kG8MWuzYRmtN4ccBcHYklRFsk m1VwqK3HUKEQjFVapyedaiU= X-Google-Smtp-Source: AGHT+IFo4UvCBQ0ebWV9tlWl4QMmBomk8lk704gNBl3Z0AZkC0xZ0BZX4z5AhHR7va1V4KEQUg3tHQ== X-Received: by 2002:a05:6870:7025:b0:1c4:c354:bd9 with SMTP id u37-20020a056870702500b001c4c3540bd9mr2189177oae.13.1692138203225; Tue, 15 Aug 2023 15:23:23 -0700 (PDT) Original-Received: from [192.168.0.234] ([186.127.128.249]) by smtp.gmail.com with ESMTPSA id ef38-20020a0568701aa600b001c4b8a9ef88sm4854759oab.24.2023.08.15.15.23.21 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 15 Aug 2023 15:23:22 -0700 (PDT) Content-Language: en-US In-Reply-To: X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:267527 Archived-At: Stefan Monnier writes: >>> Now, with emacs -Q: >>> M-! >>> ls ~/bug/bar >>> Put point between "/" and "b" of "bar" and type TAB >>> emacs says "No match", but I expected it to offer completions, foo-1 and >>> foo-2. >>> >>> That was the behavior, at least in Emacs 28. Reverting the following >>> commit, returns this behavior for me: > > The patch below adds yet another heuristic to try and handle the > current case, but really we should rework the pcomplete API so as to > provide us the right info to start with. I see.  Thanks for your explanation.  In the meantime, I confirm that your patch fixes this use case.