unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 30243@debbugs.gnu.org, Philipp Stephani <p.stephani2@gmail.com>
Subject: bug#30243: 26.0.91; Infinite recursion in `make-auto-save-file-name' for quoted filenames
Date: Fri, 26 Jan 2018 17:11:17 -0500	[thread overview]
Message-ID: <CAM-tV-9g2mPyEn0Sq6NJH+sEBp9WtbUDGDWGAsGTMAV+RO+ArQ@mail.gmail.com> (raw)
In-Reply-To: <871sichok1.fsf@gmx.de>

On Fri, Jan 26, 2018 at 6:01 AM, Michael Albinus <michael.albinus@gmx.de> wrote:

> Thanks! I've fixed this in filenotify.el (in fact, the underlying watch
> descriptor should not use quoted file names). Patch pushed to the branch.

Ah, makes sense.

>       (equal
>        ("/:/tmp/emacsqk0Dcl~")
>        ("/:/tmp/emacsqk0Dcl.~1~"))

> I guess, it is because I have set `version-control' to t in my .emacs
> (not investigated further).

Hmm, couldn't reproduce here, but it looks like a bug (although not as
severe as the inf loop stuff).

I've tried running the tests on w32, and discovered I missed testing
file-newer-than-file-p with both args quoted. There's also some
apparently w32-specific trouble with dired-compress-file and
insert-directory (although looking at the code, I'm not entirely sure
why dired-compress-file passed on GNU/Linux). I pushed 2 more patches
to fix file-newer-than-file-p and avoid the test w32 errors.

I'm thinking also the massive test needs to be split up, as it's a bit
unwieldy. Having one test per operation almost seems like overkill,
but I think it will make it easier to check we've covered everything,
so I'll probably go with that.





  reply	other threads:[~2018-01-26 22:11 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-24 22:12 bug#30243: 26.0.91; Infinite recursion in `make-auto-save-file-name' for quoted filenames phst
2018-01-24 22:43 ` Philipp Stephani
2018-01-24 23:04   ` Noam Postavsky
2018-01-24 23:25     ` Philipp Stephani
2018-01-25  5:57       ` Noam Postavsky
2018-01-25  9:49         ` Michael Albinus
2018-01-25 14:07           ` Noam Postavsky
2018-01-25 16:36             ` Michael Albinus
2018-01-25 16:46               ` Noam Postavsky
2018-01-26  1:46                 ` Noam Postavsky
2018-01-26 11:01                   ` Michael Albinus
2018-01-26 22:11                     ` Noam Postavsky [this message]
2018-01-28 10:28                       ` Michael Albinus
2018-01-28 14:58                         ` Noam Postavsky
2018-01-28 19:17                           ` Michael Albinus
2018-01-30 13:46                           ` Eli Zaretskii
2018-01-30 16:02                             ` Michael Albinus
2018-01-30 19:22                             ` Philipp Stephani
2018-01-31  0:01                               ` Noam Postavsky
2018-01-31 16:02                                 ` Eli Zaretskii
2018-01-31 18:07                                   ` Michael Albinus
2018-01-31 18:16                                     ` Noam Postavsky
2018-01-31 18:21                                       ` Michael Albinus
2018-02-01 14:01                                       ` Michael Albinus
2018-02-01 16:40                                         ` Philipp Stephani
2018-02-01 18:52                                           ` Michael Albinus
2018-02-02  1:16                                             ` Noam Postavsky
2018-02-02 17:56                                               ` Michael Albinus
2018-02-03 20:34                                                 ` Noam Postavsky
2018-01-31 15:38                               ` Eli Zaretskii
2018-02-16  3:38                   ` bug#30481: 26.0.91; infinite recursion + edebug = memory corruption Noam Postavsky
2018-02-16  8:39                     ` Eli Zaretskii
2018-02-17  3:30                       ` Noam Postavsky

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=CAM-tV-9g2mPyEn0Sq6NJH+sEBp9WtbUDGDWGAsGTMAV+RO+ArQ@mail.gmail.com \
    --to=npostavs@users.sourceforge.net \
    --cc=30243@debbugs.gnu.org \
    --cc=michael.albinus@gmx.de \
    --cc=p.stephani2@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).