unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Denys Mentiei <Denys.Mentiei@tobii.com>
Cc: 59507@debbugs.gnu.org
Subject: bug#59507: 29.0.50; Autoloads generation hangs on Windows and Emacs 29
Date: Wed, 23 Nov 2022 16:33:05 +0200	[thread overview]
Message-ID: <837czlzqou.fsf@gnu.org> (raw)
In-Reply-To: <HE1PR0302MB26030894A38E8EE8434679C1F00D9@HE1PR0302MB2603.eurprd03.prod.outlook.com> (bug-gnu-emacs@gnu.org)

> Date: Tue, 22 Nov 2022 20:13:47 +0000
> From:  Denys Mentiei via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> It looks like "loaddefs-generate--file-load-name" hangs when it receives
> a path starting with "c:/".
>  
> Looking at the code, it seems like the very first loop, which
> eats the path piece by piece with (file-name-directory name) never
> terminates as (file-name-directory-name "c:/") returns "c:/".

Thanks.

I may be missing something, but I fail to see the difference between a
Windows file name starting with "C:/" and a Unix file name starting with
"/", as far as that function is concerned.  Either they both work or they
both fail in the same way, because (file-name-directory "/") returns "/".

So do you have a real-life recipe where loaddefs-generate--file-load-name is
called and infloops?  Can you show such a recipe, preferably in "emacs -Q"?

Alternatively, a recipe which just invokes loaddefs-generate--file-load-name
with file names which cause the loop will also suffice, but in that case
please also describe how did those file names ended up being passed to the
function, i.e. with which file/directory names did the call sequence start.

The reason I'm asking is that I'm not yet sure whether the problem, whatever
it is, is in the function you pointed to or in some other place.





  reply	other threads:[~2022-11-23 14:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-22 20:13 bug#59507: 29.0.50; Autoloads generation hangs on Windows and Emacs 29 Denys Mentiei via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-23 14:33 ` Eli Zaretskii [this message]
2022-11-23 19:36   ` Denys Mentiei via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-26 11:01     ` Eli Zaretskii
2022-11-29  8:58       ` Denys Mentiei via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-29 13:10         ` Eli Zaretskii

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=837czlzqou.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=59507@debbugs.gnu.org \
    --cc=Denys.Mentiei@tobii.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).