From: Waleed Yousef <wyousef@fcih.net>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: Robert Pluim <rpluim@gmail.com>,
Stefan Kangas <stefankangas@gmail.com>,
42895@debbugs.gnu.org
Subject: bug#42895: 27.1; error when moving files in dired
Date: Mon, 17 Aug 2020 09:30:40 -0700 [thread overview]
Message-ID: <87ft8ltetr.fsf@fcih.net> (raw)
In-Reply-To: <87ft8l9rc5.fsf@gmail.com> (Tino Calancha's message of "Mon, 17 Aug 2020 18:20:42 +0200")
Thanks all;
I downloaded the new dired+.el and had this in my .emacs (so I commented
out the dired-fixups):
(load "~/.emacs.d/loadpath/dired+.el")
;;(require 'dired-fixups)
(require 'dired-tar)
and it works perfect now.
Please, just confirm to me that I no longer need dired-fixups
Tino Calancha <tino.calancha@gmail.com> writes:
> Robert Pluim <rpluim@gmail.com> writes:
>
>>>>>>> On Mon, 17 Aug 2020 08:23:04 -0700, Waleed Yousef <wyousef@fcih.net> said:
>>
>> Waleed> I update the packages almost daily! How do I have the old one?
>>
>> dired+ is not distributed via any of the ELPA systems, updating it
>> must be done manually from the location Tino mentioned.
> Exactly. IIRC, it was distributed within MELPA, as other Drew libs,
> until MELPA baned libs stored at emacswiki.
> I see you have in your .emacs:
>
> (use-package dired+)
>
> Very likely this downloaded an old version from when emacswiki was OK
> for MELPA: you won't get dired+.el updates with that line anymore.
next prev parent reply other threads:[~2020-08-17 16:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 1:52 bug#42895: 27.1; error when moving files in dired Waleed Yousef
2020-08-17 11:35 ` Stefan Kangas
2020-08-17 14:58 ` Waleed Yousef
2020-08-17 15:14 ` Tino Calancha
2020-08-17 15:23 ` Waleed Yousef
2020-08-17 15:27 ` Drew Adams
2020-08-17 15:50 ` Robert Pluim
2020-08-17 16:20 ` Tino Calancha
2020-08-17 16:30 ` Waleed Yousef [this message]
2020-08-17 16:40 ` Drew Adams
2020-08-17 16:41 ` Stefan Kangas
2020-08-17 15:23 ` Drew Adams
2020-08-17 16:19 ` Drew Adams
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=87ft8ltetr.fsf@fcih.net \
--to=wyousef@fcih.net \
--cc=42895@debbugs.gnu.org \
--cc=rpluim@gmail.com \
--cc=stefankangas@gmail.com \
--cc=tino.calancha@gmail.com \
/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.