all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: 5540@debbugs.gnu.org
Subject: bug#5540: 23.1.92; failed to access zip inside zip when not using tramp
Date: Tue, 09 Feb 2010 23:16:12 +0200	[thread overview]
Message-ID: <87ocjy155v.fsf@mail.jurta.org> (raw)
In-Reply-To: <87vde9m7dn.fsf@mail.jurta.org> (Juri Linkov's message of "Sun, 07 Feb 2010 19:01:56 +0200")

> I currently don't understand the decision to use archive-remote=t
> for nested archives (this is an old decision), but perhaps they
> should be distinguished from remote archives with a new variable
> or a new value of `archive-remote'?

Actually for remote archives `archive-remote' is 0 and for nested
archives `archive-remote' is t.  But this difference doesn't matter.

The following patch creates the directories for nested archives:

=== modified file 'lisp/arc-mode.el'
--- lisp/arc-mode.el	2010-02-04 19:54:46 +0000
+++ lisp/arc-mode.el	2010-02-09 21:12:51 +0000
@@ -850,6 +850,11 @@ (defun archive-unique-fname (fname dir)
 	  ;; reconstructed in the temporary directory.
 	  (make-directory (file-name-directory tmpfile) t)
 	  (make-temp-file tmpfile))
+      ;; Maked sure all the leading directories in `fullname' exist
+      ;; under archive-tmpdir.  This is necessary for nested archives
+      ;; (`archive-extract' sets `archive-remote' to t in case
+      ;; an archive occurs inside another archive).
+      (make-directory (file-name-directory fullname) t)
       fullname)))
 
 (defun archive-maybe-copy (archive)

-- 
Juri Linkov
http://www.jurta.org/emacs/






  reply	other threads:[~2010-02-09 21:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-07 17:01 bug#5540: 23.1.92; failed to access zip inside zip when not using tramp Juri Linkov
2010-02-09 21:16 ` Juri Linkov [this message]
2010-02-12 19:45   ` Juri Linkov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ocjy155v.fsf@mail.jurta.org \
    --to=juri@jurta.org \
    --cc=5540@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.