unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Márton Marczell" <dalokmarcinak@gmail.com>
Cc: 30755@debbugs.gnu.org
Subject: bug#30755: 25.3; Encoding of load-file-name wrong when path toworking dir does not contain accented letter
Date: Wed, 09 May 2018 20:28:08 +0300	[thread overview]
Message-ID: <83fu30pwlz.fsf@gnu.org> (raw)
In-Reply-To: <CAChNUDE1RMe2SM9m0UJ2QdVYgCuewo_MWVhbPWKadd6pPm65=Q@mail.gmail.com> (message from Márton Marczell on Wed, 9 May 2018 11:01:26 +0200)

> From: Márton Marczell <dalokmarcinak@gmail.com>
> Date: Wed, 9 May 2018 11:01:26 +0200
> Cc: 30755-done@debbugs.gnu.org
> 
> This bug has reappeared and I have investigated its conditions further. The conditions appear to be the
> following:
>  - Emacs is started with a working directory with only ASCII characters in the path (no accented letters)
>  - There is at least one "multi-file package" in ~/.emacs.d/elpa/
> This latter requirement is satisfied even with an empty package (only a "foo" folder with a foo-pkg.el containing
> only the necessary define-package and nothing else.)

Can you provide all the necessary files and a procedure to reproduce
this problem?  Given that the problem is so elusive, I think having a
recipe to reproduce exactly what you do and with the same data will
allow us to investigate much more efficiently.

Thanks.





  parent reply	other threads:[~2018-05-09 17:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-09 11:22 bug#30755: 25.3; Encoding of load-file-name wrong when path to working dir does not contain accented letter Márton Marczell
2018-03-09 13:46 ` Eli Zaretskii
     [not found]   ` <5aa2ff79.c786df0a.cebf4.23cd@mx.google.com>
2018-03-11 16:09     ` Eli Zaretskii
2018-03-17 14:19       ` bug#30755: 25.3; Encoding of load-file-name wrong when path toworking " Márton Marczell
2018-03-17 14:58         ` Eli Zaretskii
     [not found]           ` <CAChNUDE1RMe2SM9m0UJ2QdVYgCuewo_MWVhbPWKadd6pPm65=Q@mail.gmail.com>
     [not found]             ` <CAChNUDE+Et1DtkgS_4-f3EKVvvxbo4PVxPVgGuGP=rScUH=qng@mail.gmail.com>
2018-05-09  9:06               ` Márton Marczell
2018-05-09 17:28             ` Eli Zaretskii [this message]
2018-05-10 22:23               ` bug#30755: 25.3; Encoding of load-file-name wrong when pathtoworking " Márton Marczell
2018-05-15 17:22                 ` Eli Zaretskii
2018-05-16  7:42                   ` bug#30755: 25.3; Encoding of load-file-name wrong whenpathtoworking " Márton Marczell
2018-05-16  8:07                     ` Eli Zaretskii
2018-05-17 14:54                       ` bug#30755: 25.3; Encoding of load-file-name wrongwhenpathtoworking " Márton Marczell
2018-05-17 15:19                         ` Eli Zaretskii
2018-05-18 13:06                           ` Márton Marczell
2018-05-18 13:38                             ` 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=83fu30pwlz.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=30755@debbugs.gnu.org \
    --cc=dalokmarcinak@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).