all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: abdo.haji.ali@gmail.com, 49711@debbugs.gnu.org
Subject: bug#49711: 27.2; Deleting a directory called ~ deletes home directory
Date: Sat, 24 Jul 2021 16:18:15 +0200	[thread overview]
Message-ID: <87eebn3ie0.fsf@gnus.org> (raw)
In-Reply-To: <83fsw3zxz5.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 24 Jul 2021 15:40:30 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> Do you mean "~/foo"?  That works the same as before.
>
> Does it?  And what gets recorded in the trash info -- "~/foo" or its
> expansion?  If the latter, where does that expansion happen?
>
> And what about relative file names, as in "foo/bar" -- what gets
> recorded in trash info then?

Nothing has changed about the source file handling -- only the
construction of the path name in the trash can has changed.

> Btw, the implementation of directory-append is sub-optimal: it
> allocates space for the combined string twice.  It is better to create
> an uninit Lisp string first, and then fill its data with the right
> contents.

Good idea.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2021-07-24 14:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-23 15:03 bug#49711: 27.2; Deleting a directory called ~ deletes home directory Al Haji-Ali
2021-07-23 16:07 ` Lars Ingebrigtsen
2021-07-23 17:08   ` Al Haji-Ali
2021-07-24 11:37     ` Lars Ingebrigtsen
2021-07-24 12:17       ` Eli Zaretskii
2021-07-24 12:27         ` Lars Ingebrigtsen
2021-07-24 12:40           ` Eli Zaretskii
2021-07-24 14:18             ` Lars Ingebrigtsen [this message]
     [not found]       ` <b5a28a7b-8705-41b1-8b48-4b042569b387@Spark>
2021-07-24 15:24         ` Lars Ingebrigtsen

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=87eebn3ie0.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=49711@debbugs.gnu.org \
    --cc=abdo.haji.ali@gmail.com \
    --cc=eliz@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.