From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] Allow hiding stashes from vc-dir Date: Fri, 18 Oct 2019 23:19:47 -0400 Message-ID: References: <831rvegnub.fsf@gnu.org> <871rvex9ue.fsf@mail.linkov.net> <87eezdpjh4.fsf@gnus.org> <87ftjqlp7w.fsf@gnus.org> <83imom8m1y.fsf@gnu.org> <83h8468knc.fsf@gnu.org> <83ftjq8cq1.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="89749"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: larsi@gnus.org, juri@linkov.net, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Oct 19 05:20:01 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iLfHc-000N9R-L8 for ged-emacs-devel@m.gmane.org; Sat, 19 Oct 2019 05:20:00 +0200 Original-Received: from localhost ([::1]:47928 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iLfHb-0006Bs-Im for ged-emacs-devel@m.gmane.org; Fri, 18 Oct 2019 23:19:59 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48704) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iLfHV-0006Bm-MK for emacs-devel@gnu.org; Fri, 18 Oct 2019 23:19:54 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iLfHU-0005bZ-NC for emacs-devel@gnu.org; Fri, 18 Oct 2019 23:19:53 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:56892) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iLfHT-0005bF-AY; Fri, 18 Oct 2019 23:19:51 -0400 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 9D5898109E; Fri, 18 Oct 2019 23:19:50 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 5ACDB80726; Fri, 18 Oct 2019 23:19:49 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1571455189; bh=TD/qNQewaq+BkEqePLnhLmCQsx7rFUhVgNI9VfvTb70=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=eTb+9huwj1Lo3Kdl1IEwm4urIfGsmqcXYvdtOAgLl882+Smg0pUL1M1Ix7JqNPwt0 zIx3Xp0o4XZOy517l9EUd/DdBOxaUpWa5Q2DCpSagQNz2FWMhhDQHfd4yHJLt2v4vH Sa90EPhpTV4Y5j/EdHH8vrbNgl88g1+kojbVtTjop2EHiYsNKc0sBqGDg9pjGcPnZc fAKnRG/ewfLIy65oE23vR+AnDlOzBw/9EWF8EQoMb+fcqc+05w7gIgOvQEi9NXiFFj LLIj2QyXFXGuct2olVzcSHnG5GpWb08Hf7OG0ZejVqlou36QCGcQDXeAbRrMU9V1UN uOWqdrjHV6v4g== Original-Received: from pastel (unknown [216.154.15.203]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 18F1D1203AB; Fri, 18 Oct 2019 23:19:49 -0400 (EDT) In-Reply-To: (Robert Pluim's message of "Fri, 18 Oct 2019 15:43:47 +0200") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 132.204.25.50 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:241216 Archived-At: > Eli> Then it sounds like more debugging is needed to understand why > Eli> autoloading seems to not work in this case. > > I don=CA=BCt understand what's going on: Re-read the warning: vc/vc-git.el:1782:1:Warning: the function =E2=80=98cl-subseq=E2=80=99 m= ight not be defined at runtime. It doesn't say cl-subseq is an unknown function, but that it suspects that the cl-subseq function while currently defined (during the compilation) may not be defined when the code will be used. That's because the code that loaded it was wrapped in a `eval-when-compile` so it was labeled as "defined now but maybe not at runtime". Stefan