all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 44059@debbugs.gnu.org, larsi@gnus.org
Subject: bug#44059: 28.0.50; Trash files cannot be deleted properly if delete-by-moving-to-trash is set
Date: Wed, 28 Oct 2020 14:42:49 +0300	[thread overview]
Message-ID: <X5lZOZRjb1EpWIVn@protected.rcdrun.com> (raw)
In-Reply-To: <83r1pkeprs.fsf@gnu.org>

* Eli Zaretskii <eliz@gnu.org> [2020-10-26 22:44]:
> > There is no big problem. If delete-by-moving-to-trash is set then
> > Tramp says it was trashed, which is confusing.
> 
> And this is yet another, almost unrelated, issue.
> 
> Can we please stay focused in each thread on the topic of that thread,
> and nothing more?

Actually exactly that was my intended original message for this
bug. That variable should not affect remote systems and Tramp should
not assume neither seek remote trash if that variable is set, it
should remain local.






  reply	other threads:[~2020-10-28 11:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-18  9:27 bug#44059: 28.0.50; Trash files cannot be deleted properly if delete-by-moving-to-trash is set Jean Louis
     [not found] ` <handler.44059.B.16030132896481.ack@debbugs.gnu.org>
2020-10-18  9:32   ` bug#44059: Acknowledgement (28.0.50; Trash files cannot be deleted properly if delete-by-moving-to-trash is set) Jean Louis
2020-10-19  9:54 ` bug#44059: 28.0.50; Trash files cannot be deleted properly if delete-by-moving-to-trash is set Lars Ingebrigtsen
2020-10-19 11:30   ` Jean Louis
2022-02-12  8:05     ` Lars Ingebrigtsen
2020-10-19 14:54   ` Eli Zaretskii
2020-10-19 15:13     ` Stefan Kangas
2020-10-26 16:03     ` Jean Louis
2020-10-26 19:44       ` Eli Zaretskii
2020-10-28 11:42         ` Jean Louis [this message]
2020-10-28 15:36           ` Eli Zaretskii
2020-10-28 17:39             ` Jean Louis
2020-10-26 20:07       ` Michael Albinus

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=X5lZOZRjb1EpWIVn@protected.rcdrun.com \
    --to=bugs@gnu.support \
    --cc=44059@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.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.