From debbugs-submit-bounces@debbugs.gnu.org Tue Dec 17 02:15:36 2019 Received: (at submit) by debbugs.gnu.org; 17 Dec 2019 07:15:36 +0000 Received: from localhost ([127.0.0.1]:40651 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ih74x-000602-UU for submit@debbugs.gnu.org; Tue, 17 Dec 2019 02:15:36 -0500 Received: from lists.gnu.org ([209.51.188.17]:41007) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ih74w-0005zu-4U for submit@debbugs.gnu.org; Tue, 17 Dec 2019 02:15:34 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:32952) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ih74u-0007dJ-Kc for bug-gnu-emacs@gnu.org; Tue, 17 Dec 2019 02:15:34 -0500 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on eggs.gnu.org X-Spam-Level: X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_50,FREEMAIL_FROM autolearn=disabled version=3.3.2 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ih74t-0006W2-D4 for bug-gnu-emacs@gnu.org; Tue, 17 Dec 2019 02:15:32 -0500 Received: from mail-pf1-x442.google.com ([2607:f8b0:4864:20::442]:38126) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ih74t-0006UW-4F for bug-gnu-emacs@gnu.org; Tue, 17 Dec 2019 02:15:31 -0500 Received: by mail-pf1-x442.google.com with SMTP id x185so7036408pfc.5 for ; Mon, 16 Dec 2019 23:15:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:date:message-id:mime-version; bh=vAP0a0405SyeS3Pwm7H62sXsO84DLT8N4L3LFk1pBwM=; b=OwL8vuoPwLKhO3O1TRjuvWUx4E/LeV+kDy+dYCe1DVvXKkZEpi5puEeaYzNdNFHcnN iy0zT//lTfKHGlvLdyftWfPetGFDFQZbvniaJiepl67Pr1KfZuqjdIScKi9jJGM9WRUI YjLhCSM/M+Gi3OeSgSlJiueOut1WovgjRtlgX6QSmDsQBMK9/zLXoF+aW7WfPwNN/F1v V1F1vuzz7HChL2WglW6UTtktb8ZPPWtOiKVa4mmYS33kvpaKzO5APPRVZ51XiMv7tN+f pv5FGsrbVe1T8ZPG7c1+qqvPNvf+6oLPZe4VaMWVL9hAi6LX+btxTe0Q35CGc7+Nnnbq Yejg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:mime-version; bh=vAP0a0405SyeS3Pwm7H62sXsO84DLT8N4L3LFk1pBwM=; b=LlA4E565nUAytHypcqjWeQK4t+qJRpVNMuQOAsSVcbg2Ny48OnG4g8kI+LVJNG5F7n iUm3095SJYiueR+Lg1GOlWTN6UrY6AtoghqEXimgEnmRmfBJNBw1CQ0cFQ/SAPpFdCPD F9lVXYKxSfXlLYlRpg/JQBOYSWPev4xjh3h1VWeZIIb1ihzf7scjnIktNSq0Ribw+6pP Ejn4HENK8lSvWbW3JUbENisbOjBzRI2lRM2UD4imxh0AOOiCLXwTCO5K7qTxeUdhT2Ae cXg7E317YIn22WOz1ioO+VTkQA/Bq+O6ryfpiZWna+RYO4v01B1LqJlpinAZFQwQ2EZ0 A9kg== X-Gm-Message-State: APjAAAVCgjpUR/8e/tPcEKOgAgdI3KbI0EhF/cqhr0OnHcsEdU3f4f+i ViDSMgyrNvNMO0COOyEEoqlBHMod X-Google-Smtp-Source: APXvYqyV8IJgDJrwkbBFpjLTfkbasUB+tLid+NeChhL6+bZeDb1dmGpqabFmLqaAweXB2mEBeW4aBg== X-Received: by 2002:a63:1953:: with SMTP id 19mr23021721pgz.157.1576566929608; Mon, 16 Dec 2019 23:15:29 -0800 (PST) Received: from HP (east42-p111.eaccess.hi-ho.ne.jp. [219.121.173.112]) by smtp.gmail.com with ESMTPSA id v16sm24838757pfn.77.2019.12.16.23.15.28 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 16 Dec 2019 23:15:29 -0800 (PST) From: ynyaaa@gmail.com To: bug-gnu-emacs@gnu.org Subject: 26.3; image-next-file does not consider archived images Date: Tue, 17 Dec 2019 16:15:23 +0900 Message-ID: <86pngno22c.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:4864:20::442 X-Spam-Score: 0.7 (/) X-Debbugs-Envelope-To: submit X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -2.3 (--) When viewing archived images(zip or tar) with image-mode, typing 'n' does not show the next image in the archive. Similar for 'p'. In GNU Emacs 26.3 (build 1, x86_64-w64-mingw32) of 2019-08-29 built on CIRROCUMULUS Repository revision: 96dd0196c28bc36779584e47fffcca433c9309cd Windowing system distributor 'Microsoft Corp.', version 6.3.9600 Recent messages: Configured using: 'configure --without-dbus --host=x86_64-w64-mingw32 --without-compress-install 'CFLAGS=-O2 -static -g3'' Configured features: XPM JPEG TIFF GIF PNG RSVG SOUND NOTIFY ACL GNUTLS LIBXML2 ZLIB TOOLKIT_SCROLL_BARS THREADS LCMS2 Important settings: value of $LANG: JPN locale-coding-system: cp932 Major mode: Lisp Interaction Minor modes in effect: tooltip-mode: t global-eldoc-mode: t eldoc-mode: t electric-indent-mode: t mouse-wheel-mode: t tool-bar-mode: t menu-bar-mode: t file-name-shadow-mode: t global-font-lock-mode: t font-lock-mode: t blink-cursor-mode: t auto-composition-mode: t auto-encryption-mode: t auto-compression-mode: t line-number-mode: t transient-mark-mode: t Load-path shadows: None found. Features: (mode-local find-func thingatpt help-fns radix-tree cl-print debug ispell network-stream nsm starttls tls gnutls mailalias smtpmail auth-source cl-seq eieio eieio-core cl-macs eieio-loaddefs misearch multi-isearch help-mode pp shadow sort mail-extr emacsbug message rmc puny seq byte-opt gv bytecomp byte-compile cconv cl-loaddefs cl-lib dired dired-loaddefs format-spec rfc822 mml easymenu mml-sec password-cache epa derived epg epg-config gnus-util rmail rmail-loaddefs mm-decode mm-bodies mm-encode mail-parse rfc2231 mailabbrev gmm-utils mailheader sendmail rfc2047 rfc2045 ietf-drums mm-util mail-prsvr mail-utils elec-pair time-date mule-util japan-util tooltip eldoc electric uniquify ediff-hook vc-hooks lisp-float-type mwheel dos-w32 ls-lisp disp-table term/w32-win w32-win w32-vars term/common-win tool-bar dnd fontset image regexp-opt fringe tabulated-list replace newcomment text-mode elisp-mode lisp-mode prog-mode register page menu-bar rfn-eshadow isearch timer select scroll-bar mouse jit-lock font-lock syntax facemenu font-core term/tty-colors frame cl-generic cham georgian utf-8-lang misc-lang vietnamese tibetan thai tai-viet lao korean japanese eucjp-ms cp51932 hebrew greek romanian slovak czech european ethiopic indian cyrillic chinese composite charscript charprop case-table epa-hook jka-cmpr-hook help simple abbrev obarray minibuffer cl-preloaded nadvice loaddefs button faces cus-face macroexp files text-properties overlay sha1 md5 base64 format env code-pages mule custom widget hashtable-print-readable backquote threads w32notify w32 lcms2 multi-tty make-network-process emacs) Memory information: ((conses 16 122843 37538) (symbols 48 21555 3) (miscs 40 70 379) (strings 32 36407 1382) (string-bytes 1 934688) (vectors 16 17296) (vector-slots 8 601335 15884) (floats 8 57 548) (intervals 56 805 0) (buffers 992 17)) From debbugs-submit-bounces@debbugs.gnu.org Tue Dec 17 11:20:51 2019 Received: (at 38647) by debbugs.gnu.org; 17 Dec 2019 16:20:51 +0000 Received: from localhost ([127.0.0.1]:42285 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ihFac-0000mj-S8 for submit@debbugs.gnu.org; Tue, 17 Dec 2019 11:20:51 -0500 Received: from eggs.gnu.org ([209.51.188.92]:37689) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ihFab-0000mK-3h; Tue, 17 Dec 2019 11:20:49 -0500 Received: from fencepost.gnu.org ([2001:470:142:3::e]:53512) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ihFaW-0006QU-0L; Tue, 17 Dec 2019 11:20:44 -0500 Received: from [176.228.60.248] (port=4368 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1ihFaV-0004Ad-5e; Tue, 17 Dec 2019 11:20:43 -0500 Date: Tue, 17 Dec 2019 18:20:31 +0200 Message-Id: <83d0cm53g0.fsf@gnu.org> From: Eli Zaretskii To: ynyaaa@gmail.com In-reply-to: <86pngno22c.fsf@gmail.com> (ynyaaa@gmail.com) Subject: Re: bug#38647: 26.3; image-next-file does not consider archived images References: <86pngno22c.fsf@gmail.com> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 38647 Cc: 38647@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) severity 38647 wishlist thanks > From: ynyaaa@gmail.com > Date: Tue, 17 Dec 2019 16:15:23 +0900 > > > When viewing archived images(zip or tar) with image-mode, > typing 'n' does not show the next image in the archive. > Similar for 'p'. Sounds like a missing feature which would be good to have, thanks. Any takers? From debbugs-submit-bounces@debbugs.gnu.org Sun Aug 02 05:49:24 2020 Received: (at 38647) by debbugs.gnu.org; 2 Aug 2020 09:49:25 +0000 Received: from localhost ([127.0.0.1]:41723 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1k2AcO-0006N9-NA for submit@debbugs.gnu.org; Sun, 02 Aug 2020 05:49:24 -0400 Received: from quimby.gnus.org ([95.216.78.240]:59976) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1k2AcM-0006Mv-Rf for 38647@debbugs.gnu.org; Sun, 02 Aug 2020 05:49:23 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date: References:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=Q1WqFdSZcvNseyBZGaiHzPnELwWd2WugCYD8COaWP0Y=; b=CxTpBnDctTFwyPqqzbinHVKoOl jlvZRz4mrd68m0MqKWSqoHaqpuomfnZp/yI0Zdex76USgcCglQQuWl6ZJWfjOKX7E8xO1X0FZs6OJ YzkTT2RolYOTRevBesQERZTGoRepn9JOZglSz8gG0PGFF3YvRK3UPrQliPwW1i7eS/W8=; Received: from cm-84.212.202.86.getinternet.no ([84.212.202.86] helo=xo) by quimby with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k2AcC-0007sd-O4; Sun, 02 Aug 2020 11:49:16 +0200 From: Lars Ingebrigtsen To: Eli Zaretskii Subject: Re: bug#38647: 26.3; image-next-file does not consider archived images References: <86pngno22c.fsf@gmail.com> <83d0cm53g0.fsf@gnu.org> Date: Sun, 02 Aug 2020 11:49:11 +0200 In-Reply-To: <83d0cm53g0.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 17 Dec 2019 18:20:31 +0200") Message-ID: <87d049js2w.fsf@gnus.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Report: Spam detection software, running on the system "quimby.gnus.org", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see @@CONTACT_ADDRESS@@ for details. Content preview: Eli Zaretskii writes: >> When viewing archived images(zip or tar) with image-mode, >> typing 'n' does not show the next image in the archive. >> Similar for 'p'. > > Sounds like a missing feature which would be good to hav [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 38647 Cc: 38647@debbugs.gnu.org, ynyaaa@gmail.com X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) Eli Zaretskii writes: >> When viewing archived images(zip or tar) with image-mode, >> typing 'n' does not show the next image in the archive. >> Similar for 'p'. > > Sounds like a missing feature which would be good to have, thanks. > > Any takers? There's some difficulty knowing how to approach this -- the different archive modes do so many different odd things. For instance, if you open the file "guide.png" from a zip buffer, buffer-file-name ends up being: "/home/larsi/tmp/images.zip:guide.png" In a tar file buffer, you end up with: "/home/larsi/tmp/images.tgz!./guide.png" So that has to be regularised first... but will that break stuff? Secondly, there doesn't seem to be any general "what's the next file in this archive buffer" function? Or am I missing something? This seems like a trivial request, but I'm not sure we have the infrastructure to make it happen... -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no From debbugs-submit-bounces@debbugs.gnu.org Mon Aug 03 20:58:57 2020 Received: (at 38647) by debbugs.gnu.org; 4 Aug 2020 00:58:57 +0000 Received: from localhost ([127.0.0.1]:46393 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1k2lI8-0003m1-VJ for submit@debbugs.gnu.org; Mon, 03 Aug 2020 20:58:57 -0400 Received: from relay10.mail.gandi.net ([217.70.178.230]:57137) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1k2lI6-0003lh-Hc for 38647@debbugs.gnu.org; Mon, 03 Aug 2020 20:58:55 -0400 Received: from mail.gandi.net (m91-129-102-47.cust.tele2.ee [91.129.102.47]) (Authenticated sender: juri@linkov.net) by relay10.mail.gandi.net (Postfix) with ESMTPSA id 2DAF1240004; Tue, 4 Aug 2020 00:58:46 +0000 (UTC) From: Juri Linkov To: Lars Ingebrigtsen Subject: Re: bug#38647: 26.3; image-next-file does not consider archived images Organization: LINKOV.NET References: <86pngno22c.fsf@gmail.com> <83d0cm53g0.fsf@gnu.org> <87d049js2w.fsf@gnus.org> Date: Tue, 04 Aug 2020 02:50:12 +0300 In-Reply-To: <87d049js2w.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 02 Aug 2020 11:49:11 +0200") Message-ID: <87d047cjzv.fsf@mail.linkov.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: -0.7 (/) X-Debbugs-Envelope-To: 38647 Cc: 38647@debbugs.gnu.org, Eli Zaretskii , ynyaaa@gmail.com X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.7 (-) >>> When viewing archived images(zip or tar) with image-mode, >>> typing 'n' does not show the next image in the archive. >>> Similar for 'p'. >> >> Sounds like a missing feature which would be good to have, thanks. >> >> Any takers? > > There's some difficulty knowing how to approach this -- the different > archive modes do so many different odd things. > > For instance, if you open the file "guide.png" from a zip buffer, > buffer-file-name ends up being: > > "/home/larsi/tmp/images.zip:guide.png" > > In a tar file buffer, you end up with: > > "/home/larsi/tmp/images.tgz!./guide.png" > > So that has to be regularised first... but will that break stuff? > > Secondly, there doesn't seem to be any general "what's the next file in > this archive buffer" function? Or am I missing something? > > This seems like a trivial request, but I'm not sure we have the > infrastructure to make it happen... All this indicates that instead of using 'directory-files', 'image-next-file' should rely on 'archive-next-line' if the file is opened from an archive, and on 'dired-next-line' otherwise. When using 'dired-next-line' the image navigation order will be exactly the same as the file sorting order in the dired buffer, thus allowing the users to change the image order from dired. Also this means that if there is no corresponding dired buffer already visited, then 'image-next-file' should create an internal dired buffer just for the sake of file image navigation. From debbugs-submit-bounces@debbugs.gnu.org Tue Aug 04 04:05:58 2020 Received: (at 38647) by debbugs.gnu.org; 4 Aug 2020 08:05:58 +0000 Received: from localhost ([127.0.0.1]:46709 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1k2rxO-0005nK-4O for submit@debbugs.gnu.org; Tue, 04 Aug 2020 04:05:58 -0400 Received: from quimby.gnus.org ([95.216.78.240]:53112) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1k2rxM-0005n4-NP for 38647@debbugs.gnu.org; Tue, 04 Aug 2020 04:05:57 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date: References:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=cEA0OsNew5Teo6sdBrkNjzaaIzTgMJZMmqN5Puz4eYI=; b=u9682sFZh+KJjXz7sfzhVVUf+b f/tv0G0ZzOtWJAZ4+yuQ3w2ZZvtCvx66TTg1zHSkw7uswv/Lr9CJVq01jOo5pzAup5+OmACbXZqlb nfVSbYzogsdbb4YjW0lR7UDYbHaw9Hp+c5WNzoTtGLQ7J75QgNftG2KOkntLYAIDKdvM=; Received: from cm-84.212.202.86.getinternet.no ([84.212.202.86] helo=xo) by quimby with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k2rxD-0005XB-8C; Tue, 04 Aug 2020 10:05:50 +0200 From: Lars Ingebrigtsen To: Juri Linkov Subject: Re: bug#38647: 26.3; image-next-file does not consider archived images References: <86pngno22c.fsf@gmail.com> <83d0cm53g0.fsf@gnu.org> <87d049js2w.fsf@gnus.org> <87d047cjzv.fsf@mail.linkov.net> Date: Tue, 04 Aug 2020 10:05:45 +0200 In-Reply-To: <87d047cjzv.fsf@mail.linkov.net> (Juri Linkov's message of "Tue, 04 Aug 2020 02:50:12 +0300") Message-ID: <87zh7au97q.fsf@gnus.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Report: Spam detection software, running on the system "quimby.gnus.org", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see @@CONTACT_ADDRESS@@ for details. Content preview: Juri Linkov writes: > All this indicates that instead of using 'directory-files', > 'image-next-file' should rely on 'archive-next-line' if the file > is opened from an archive, and on 'dired-next-line' otherwise. Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 38647 Cc: 38647@debbugs.gnu.org, Eli Zaretskii , ynyaaa@gmail.com X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) Juri Linkov writes: > All this indicates that instead of using 'directory-files', > 'image-next-file' should rely on 'archive-next-line' if the file > is opened from an archive, and on 'dired-next-line' otherwise. `archive-next-line' isn't used in tar mode buffers -- that's the problem: There's no unified interface across the different archive modes. (Although perhaps there's just two? arc-mode and tar-mode? > When using 'dired-next-line' the image navigation order will be > exactly the same as the file sorting order in the dired buffer, > thus allowing the users to change the image order from dired. Yeah, that would be nice. > Also this means that if there is no corresponding dired buffer > already visited, then 'image-next-file' should create an internal > dired buffer just for the sake of file image navigation. Hm. I think that makes sense... but it would perhaps be a bit surprising? -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no From debbugs-submit-bounces@debbugs.gnu.org Tue Aug 04 20:25:01 2020 Received: (at 38647) by debbugs.gnu.org; 5 Aug 2020 00:25:01 +0000 Received: from localhost ([127.0.0.1]:49367 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1k37Er-0002HU-Dr for submit@debbugs.gnu.org; Tue, 04 Aug 2020 20:25:01 -0400 Received: from relay7-d.mail.gandi.net ([217.70.183.200]:40603) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1k37Eq-0002Gw-3b for 38647@debbugs.gnu.org; Tue, 04 Aug 2020 20:25:00 -0400 X-Originating-IP: 91.129.102.47 Received: from mail.gandi.net (m91-129-102-47.cust.tele2.ee [91.129.102.47]) (Authenticated sender: juri@linkov.net) by relay7-d.mail.gandi.net (Postfix) with ESMTPSA id 266A820002; Wed, 5 Aug 2020 00:24:51 +0000 (UTC) From: Juri Linkov To: Lars Ingebrigtsen Subject: Re: bug#38647: 26.3; image-next-file does not consider archived images Organization: LINKOV.NET References: <86pngno22c.fsf@gmail.com> <83d0cm53g0.fsf@gnu.org> <87d049js2w.fsf@gnus.org> <87d047cjzv.fsf@mail.linkov.net> <87zh7au97q.fsf@gnus.org> Date: Wed, 05 Aug 2020 02:47:44 +0300 In-Reply-To: <87zh7au97q.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 04 Aug 2020 10:05:45 +0200") Message-ID: <87lfiuq6w7.fsf@mail.linkov.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: -0.7 (/) X-Debbugs-Envelope-To: 38647 Cc: 38647@debbugs.gnu.org, Eli Zaretskii , ynyaaa@gmail.com X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.7 (-) >> All this indicates that instead of using 'directory-files', >> 'image-next-file' should rely on 'archive-next-line' if the file >> is opened from an archive, and on 'dired-next-line' otherwise. > > `archive-next-line' isn't used in tar mode buffers -- that's the > problem: There's no unified interface across the different archive > modes. (Although perhaps there's just two? arc-mode and tar-mode? Yep, there's just two - these twins are going hand in hand, for example, in image-mode.el in image-toggle-display-image: (not (and (boundp 'archive-superior-buffer) archive-superior-buffer)) (not (and (boundp 'tar-superior-buffer) tar-superior-buffer)) >> Also this means that if there is no corresponding dired buffer >> already visited, then 'image-next-file' should create an internal >> dired buffer just for the sake of file image navigation. > > Hm. I think that makes sense... but it would perhaps be a bit > surprising? Maybe when not requested, such Dired buffer should be killed afterwards, or its name should start with a space. From debbugs-submit-bounces@debbugs.gnu.org Wed Aug 05 05:09:20 2020 Received: (at 38647) by debbugs.gnu.org; 5 Aug 2020 09:09:20 +0000 Received: from localhost ([127.0.0.1]:49723 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1k3FQG-0004WZ-3B for submit@debbugs.gnu.org; Wed, 05 Aug 2020 05:09:20 -0400 Received: from quimby.gnus.org ([95.216.78.240]:37930) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1k3FQE-0004WN-Ll for 38647@debbugs.gnu.org; Wed, 05 Aug 2020 05:09:19 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date: References:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=xmY/Ah+ZtHI9HII/rsKbhaG2VwdxtpfHjDrAthkOF0s=; b=MOENCY7w2zjFYEVxtKI4dTQxJD I0lCcxFPN8dhVlqUwspwezV1SBkJQvjOWtbm7C5+SPCauTM3pl0gysAzbTpprJgK7IuD3GXHYjj0i O+Qg/HCbsEnyjhnHSWfA34hi3PBWVfHJMq7bc/ohSpf+nbnInvW4yeEl1jt/MVMG85Vs=; Received: from cm-84.212.202.86.getinternet.no ([84.212.202.86] helo=xo) by quimby with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k3FQ2-0002ot-J8; Wed, 05 Aug 2020 11:09:11 +0200 From: Lars Ingebrigtsen To: Juri Linkov Subject: Re: bug#38647: 26.3; image-next-file does not consider archived images References: <86pngno22c.fsf@gmail.com> <83d0cm53g0.fsf@gnu.org> <87d049js2w.fsf@gnus.org> <87d047cjzv.fsf@mail.linkov.net> <87zh7au97q.fsf@gnus.org> <87lfiuq6w7.fsf@mail.linkov.net> Date: Wed, 05 Aug 2020 11:09:04 +0200 In-Reply-To: <87lfiuq6w7.fsf@mail.linkov.net> (Juri Linkov's message of "Wed, 05 Aug 2020 02:47:44 +0300") Message-ID: <87v9hxe9xr.fsf@gnus.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Report: Spam detection software, running on the system "quimby.gnus.org", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see @@CONTACT_ADDRESS@@ for details. Content preview: Juri Linkov writes: > Yep, there's just two - these twins are going hand in hand, > for example, in image-mode.el in image-toggle-display-image: > > (not (and (boundp 'archive-superior-buffer) > archive-superior-buffer)) [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 38647 Cc: 38647@debbugs.gnu.org, Eli Zaretskii , ynyaaa@gmail.com X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) Juri Linkov writes: > Yep, there's just two - these twins are going hand in hand, > for example, in image-mode.el in image-toggle-display-image: > > (not (and (boundp 'archive-superior-buffer) > archive-superior-buffer)) > (not (and (boundp 'tar-superior-buffer) > tar-superior-buffer)) If there's just two, that's indeed manageable. I imagined there were a dozen of these modes, which seemed hopeless... OK, I think the way forward here is probably to create a couple of helper functions to abstract away the underlying movement/selection stuff. So something like image-mode--{next,prev}-file that will do the right thing in dired/tar/arc buffers, and also respect the sorting in those buffers. I think that should be pretty easy to implement (he said without actually having looked at it *theme music from Jaws starts playing*). >>> Also this means that if there is no corresponding dired buffer >>> already visited, then 'image-next-file' should create an internal >>> dired buffer just for the sake of file image navigation. >> >> Hm. I think that makes sense... but it would perhaps be a bit >> surprising? > > Maybe when not requested, such Dired buffer should be killed afterwards, > or its name should start with a space. Hm... But what is "afterwards"? Just leaving the image mode buffer? Perhaps we can just make this all less surprising, and still have the functionality, by just notifying the user. (Or query?) That is, if you `n' in an image-mode buffer, and there's no dired (etc) buffer parent, then just message "Opened dired buffer for " when doing so? And... bury it? Or not? Many UX things to tweak. -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no From debbugs-submit-bounces@debbugs.gnu.org Wed Aug 05 20:15:22 2020 Received: (at 38647) by debbugs.gnu.org; 6 Aug 2020 00:15:22 +0000 Received: from localhost ([127.0.0.1]:52443 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1k3TZ4-0007DL-BX for submit@debbugs.gnu.org; Wed, 05 Aug 2020 20:15:22 -0400 Received: from relay12.mail.gandi.net ([217.70.178.232]:58273) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1k3TZ2-0007Cf-QK for 38647@debbugs.gnu.org; Wed, 05 Aug 2020 20:15:21 -0400 Received: from mail.gandi.net (m91-129-102-47.cust.tele2.ee [91.129.102.47]) (Authenticated sender: juri@linkov.net) by relay12.mail.gandi.net (Postfix) with ESMTPSA id BB8CD200004; Thu, 6 Aug 2020 00:15:13 +0000 (UTC) From: Juri Linkov To: Lars Ingebrigtsen Subject: Re: bug#38647: 26.3; image-next-file does not consider archived images Organization: LINKOV.NET References: <86pngno22c.fsf@gmail.com> <83d0cm53g0.fsf@gnu.org> <87d049js2w.fsf@gnus.org> <87d047cjzv.fsf@mail.linkov.net> <87zh7au97q.fsf@gnus.org> <87lfiuq6w7.fsf@mail.linkov.net> <87v9hxe9xr.fsf@gnus.org> Date: Thu, 06 Aug 2020 02:50:20 +0300 In-Reply-To: <87v9hxe9xr.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 05 Aug 2020 11:09:04 +0200") Message-ID: <87tuxgprib.fsf@mail.linkov.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: -0.7 (/) X-Debbugs-Envelope-To: 38647 Cc: 38647@debbugs.gnu.org, Eli Zaretskii , ynyaaa@gmail.com X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.7 (-) >> Maybe when not requested, such Dired buffer should be killed afterwards, >> or its name should start with a space. > > Hm... But what is "afterwards"? Just leaving the image mode buffer? I thought that after every typing of `n'. > Perhaps we can just make this all less surprising, and still have the > functionality, by just notifying the user. (Or query?) That is, if you > `n' in an image-mode buffer, and there's no dired (etc) buffer parent, > then just message "Opened dired buffer for " when doing so? > And... bury it? Or not? Or optionally pop up a new Dired buffer on image navigation. Or use commands from image-dired.el. So many options... From debbugs-submit-bounces@debbugs.gnu.org Thu Aug 06 05:52:45 2020 Received: (at 38647) by debbugs.gnu.org; 6 Aug 2020 09:52:45 +0000 Received: from localhost ([127.0.0.1]:53172 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1k3cZp-0002zv-Fn for submit@debbugs.gnu.org; Thu, 06 Aug 2020 05:52:45 -0400 Received: from quimby.gnus.org ([95.216.78.240]:51824) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1k3cZm-0002zc-Sf for 38647@debbugs.gnu.org; Thu, 06 Aug 2020 05:52:43 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date: References:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=5lhAOm1n4xfMlOW7BexbO9BLdaPPq18ngbumAtypE5U=; b=VAfprzzpCRTgZDjn9gj5sSNEY7 ptfud5ttbDiXuYFiXPAoYW+ZK0tEVuk9+7MSZUzWlAF5CH9oJh0km+xXXrvLMnFEqDIyaXytkSCD3 erR7abnguspozf76kvu7nUEwmT9l2RsO6EfV1AYz+DwwXoaZOMvRWVYv0WAxl46ms+98=; Received: from cm-84.212.202.86.getinternet.no ([84.212.202.86] helo=xo) by quimby with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k3cZc-0008Ow-0Y; Thu, 06 Aug 2020 11:52:34 +0200 From: Lars Ingebrigtsen To: Juri Linkov Subject: Re: bug#38647: 26.3; image-next-file does not consider archived images References: <86pngno22c.fsf@gmail.com> <83d0cm53g0.fsf@gnu.org> <87d049js2w.fsf@gnus.org> <87d047cjzv.fsf@mail.linkov.net> <87zh7au97q.fsf@gnus.org> <87lfiuq6w7.fsf@mail.linkov.net> <87v9hxe9xr.fsf@gnus.org> <87tuxgprib.fsf@mail.linkov.net> Date: Thu, 06 Aug 2020 11:52:30 +0200 In-Reply-To: <87tuxgprib.fsf@mail.linkov.net> (Juri Linkov's message of "Thu, 06 Aug 2020 02:50:20 +0300") Message-ID: <878sesf6e9.fsf@gnus.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Report: Spam detection software, running on the system "quimby.gnus.org", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see @@CONTACT_ADDRESS@@ for details. Content preview: Juri Linkov writes: >> Perhaps we can just make this all less surprising, and still have the >> functionality, by just notifying the user. (Or query?) That is, if you >> `n' in an image-mode buffer, and there's no dired [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 38647 Cc: 38647@debbugs.gnu.org, Eli Zaretskii , ynyaaa@gmail.com X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) Juri Linkov writes: >> Perhaps we can just make this all less surprising, and still have the >> functionality, by just notifying the user. (Or query?) That is, if you >> `n' in an image-mode buffer, and there's no dired (etc) buffer parent, >> then just message "Opened dired buffer for " when doing so? >> And... bury it? Or not? > > Or optionally pop up a new Dired buffer on image navigation. > Or use commands from image-dired.el. So many options... I just made it message. I've now implemented this, and it seems to work for me in normal buffers, as well as archive mode and tar mode buffers. I had to add a couple helper functions to the latter two modes. -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no From debbugs-submit-bounces@debbugs.gnu.org Thu Aug 06 05:52:51 2020 Received: (at control) by debbugs.gnu.org; 6 Aug 2020 09:52:51 +0000 Received: from localhost ([127.0.0.1]:53175 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1k3cZu-00030D-Rb for submit@debbugs.gnu.org; Thu, 06 Aug 2020 05:52:51 -0400 Received: from quimby.gnus.org ([95.216.78.240]:51836) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1k3cZs-0002zn-Lu for control@debbugs.gnu.org; Thu, 06 Aug 2020 05:52:48 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Subject:From:To:Message-Id:Date:Sender:Reply-To:Cc: MIME-Version:Content-Type:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=kMXx60VBj/i0EH2HIzkw1cdl8XGbJletROTDOS4/OiU=; b=qswxHStp9ZzMc+GPvdDLe8F7EA xfqjJ+M3EXgjd89ghgP1CS0J/J/TD7jmEUocraBmszHZ+YdY0bYf5lMr62WHN9MnckpAJTEYiVyz6 +3FBWoey11VsVzLWQZ7ZB+idqMNzm1IjjEsSxauf2PK1JR2brPrftK4DefjVmlPbv7RE=; Received: from cm-84.212.202.86.getinternet.no ([84.212.202.86] helo=xo) by quimby with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k3cZk-0008P8-Ga for control@debbugs.gnu.org; Thu, 06 Aug 2020 11:52:42 +0200 Date: Thu, 06 Aug 2020 11:52:39 +0200 Message-Id: <877ducf6e0.fsf@gnus.org> To: control@debbugs.gnu.org From: Lars Ingebrigtsen Subject: control message for bug #38647 X-Spam-Report: Spam detection software, running on the system "quimby.gnus.org", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see @@CONTACT_ADDRESS@@ for details. Content preview: tags 38647 fixed close 38647 28.1 quit Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: control X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) tags 38647 fixed close 38647 28.1 quit From unknown Sat Aug 16 16:18:27 2025 Received: (at fakecontrol) by fakecontrolmessage; To: internal_control@debbugs.gnu.org From: Debbugs Internal Request Subject: Internal Control Message-Id: bug archived. Date: Thu, 03 Sep 2020 11:24:07 +0000 User-Agent: Fakemail v42.6.9 # This is a fake control message. # # The action: # bug archived. thanks # This fakemail brought to you by your local debbugs # administrator