unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Arthur Miller <arthur.miller@live.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Rodrigo Morales <moralesrodrigo1100@gmail.com>, 48659@debbugs.gnu.org
Subject: bug#48659: Escapes are deleted after executing "dired-toggle-read-only" in *Find* buffer
Date: Sat, 29 May 2021 08:29:26 +0200	[thread overview]
Message-ID: <AM9PR09MB4977F0125D20A111E3DCF63E96219@AM9PR09MB4977.eurprd09.prod.outlook.com> (raw)
In-Reply-To: <837djkac8x.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 27 May 2021 10:04:30 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Rodrigo Morales <moralesrodrigo1100@gmail.com>
>> Cc: 48659@debbugs.gnu.org
>> Date: Wed, 26 May 2021 18:55:14 -0500
>> 
>> > Can anyone else reproduce this strange problem?  I don't see how we
>> > could debug this without being able to reproduce.
>> 
>> Here you have two recordings that might make things clearer. Perhaps, I
>> wasn't clear enough in the first messaage I sent and that's why you are
>> not able to reproduce it, so I hope these recordings will present more
>> context regarding this "possible bug".
>> 
>> In the following GIF, you can see that spaces are removed after having
>> finished editing the dired buffer through "dired-toggle-read-only". This
>> can be seen in the output of the "watch" command that is shown in the
>> running shell at the right side.
>
> I believe you.  I just don't see this in the GNU/Linux system where I
> tried this (and also on MS-Windows, FWIW).  In my testing the file
> names remain intact after "C-x C-q", including the space characters.
>
> So either the recipe is not complete, or I somehow didn't follow it
> 100%, or something else is at work on your system that doesn't happen
> on mine.  Thus my question whether someone else sees that who could
> then debug the problem.

If it is of any worth, I am using 27.1 on Win 10 and 28.0.50 compiled on
27th march on Arch Linux and I can't reproduce either. Spaces in names
seems correctly preserved on my machine.





  reply	other threads:[~2021-05-29  6:29 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-25 20:40 bug#48659: Escapes are deleted after executing "dired-toggle-read-only" in *Find* buffer Rodrigo Morales
2021-05-26 12:14 ` Eli Zaretskii
2021-05-26 15:16   ` Rodrigo Morales
2021-05-26 17:18     ` Eli Zaretskii
     [not found]       ` <871r9tdp99.fsf@gmail.com>
2021-05-27  7:04         ` Eli Zaretskii
2021-05-29  6:29           ` Arthur Miller [this message]
2021-05-27  9:14       ` Robert Pluim
2021-05-27  9:34         ` Eli Zaretskii
2021-05-27 13:50         ` Michael Heerdegen
2021-05-27 14:01   ` Michael Heerdegen
2021-05-27 14:04     ` Eli Zaretskii
2021-05-27 14:16       ` Michael Heerdegen
2021-05-27 14:48         ` Andreas Schwab
2021-05-27 15:04         ` Andreas Schwab
2021-05-27 15:31           ` Michael Heerdegen
2021-05-27 15:38       ` Andreas Schwab
2021-05-27 15:47         ` Michael Heerdegen
2021-05-27 15:57           ` Andreas Schwab
2021-05-27 15:56         ` Andreas Schwab
2021-05-27 18:49         ` Michael Heerdegen
2021-05-27 19:11           ` Andreas Schwab
2021-05-27 20:38             ` Michael Heerdegen
2021-05-29 13:39 ` Andreas Schwab
2021-05-29 23:09   ` Michael Heerdegen

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=AM9PR09MB4977F0125D20A111E3DCF63E96219@AM9PR09MB4977.eurprd09.prod.outlook.com \
    --to=arthur.miller@live.com \
    --cc=48659@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=moralesrodrigo1100@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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).