From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#47718: Fix epa-file-insert-file-contents substring error Date: Mon, 12 Apr 2021 16:23:10 +0300 Message-ID: <83h7kb3add.fsf@gnu.org> References: <8735vv2a39.fsf@gnus.org> <83o8ej3ebk.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="19125"; mail-complaints-to="usenet@ciao.gmane.io" Cc: larsi@gnus.org, 47718@debbugs.gnu.org To: juntaka Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Apr 12 15:24:12 2021 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 1lVwY0-0004ae-ER for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 12 Apr 2021 15:24:12 +0200 Original-Received: from localhost ([::1]:48830 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lVwXz-00048l-EW for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 12 Apr 2021 09:24:11 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53026) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lVwXq-000458-Ae for bug-gnu-emacs@gnu.org; Mon, 12 Apr 2021 09:24:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:45325) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lVwXq-0008Lg-2l for bug-gnu-emacs@gnu.org; Mon, 12 Apr 2021 09:24:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1lVwXp-0007Aq-Td for bug-gnu-emacs@gnu.org; Mon, 12 Apr 2021 09:24:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 12 Apr 2021 13:24:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 47718 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: fixed Original-Received: via spool by 47718-submit@debbugs.gnu.org id=B47718.161823381327534 (code B ref 47718); Mon, 12 Apr 2021 13:24:01 +0000 Original-Received: (at 47718) by debbugs.gnu.org; 12 Apr 2021 13:23:33 +0000 Original-Received: from localhost ([127.0.0.1]:56871 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lVwXM-0007A2-Sx for submit@debbugs.gnu.org; Mon, 12 Apr 2021 09:23:33 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:40260) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lVwXK-00079n-TY for 47718@debbugs.gnu.org; Mon, 12 Apr 2021 09:23:31 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:54289) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lVwXF-0007wX-H7; Mon, 12 Apr 2021 09:23:25 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:2875 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1lVwXE-00045t-Kr; Mon, 12 Apr 2021 09:23:25 -0400 In-Reply-To: (message from juntaka on Mon, 12 Apr 2021 12:57:28 +0000) 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" Xref: news.gmane.io gmane.emacs.bugs:203898 Archived-At: > Date: Mon, 12 Apr 2021 12:57:28 +0000 > From: juntaka > Cc: Lars Ingebrigtsen , "47718@debbugs.gnu.org" <47718@debbugs.gnu.org> > > In my use case, I'm writing an elisp to show the first line of each file on dired. > It does not need to visit and read entire file. So I just try to limit by (window-width). > But if Emacs try to decrypt GPG files, then I got such error. Doesn't that mean the problem is in your application code?