From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Subject: bug#33848: Store references in SBCL-compiled code are "invisible" Date: Wed, 26 Dec 2018 17:07:33 +0100 Message-ID: <87r2e4e0fu.fsf@gnu.org> References: <87r2e8jpfx.fsf@gnu.org> <877eg0i43j.fsf@netris.org> <87d0psi1xo.fsf@gnu.org> <874lb3kin6.fsf@ambrevar.xyz> <87sgynezha.fsf@gnu.org> <87r2e6j1hw.fsf@ambrevar.xyz> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:33686) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gcBj9-0002Pe-PE for bug-guix@gnu.org; Wed, 26 Dec 2018 11:08:12 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gcBj1-0000IF-Ec for bug-guix@gnu.org; Wed, 26 Dec 2018 11:08:08 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:51716) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gcBiz-0000CI-UB for bug-guix@gnu.org; Wed, 26 Dec 2018 11:08:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gcBiz-000179-L6 for bug-guix@gnu.org; Wed, 26 Dec 2018 11:08:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87r2e6j1hw.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Mon, 24 Dec 2018 18:08:59 +0100") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Pierre Neidhardt Cc: 33848@debbugs.gnu.org Pierre Neidhardt skribis: >> Store file names are always ASCII so problems arise when they are stored >> as UTF-16 or UTF-32/UCS-4. > > I understand that most programs stick to ASCII filenames, but what about = the odd > one using non-English, special characters? That=E2=80=99s a separate debate. :-) Essentially this restriction on sto= re file names has always been there in Guix (and Nix before that). If we were to change it, that would raise compatibility issues. >> We did have a problem with Fish but I can no longer find it. Do you >> remember what it was? Something with C++, no? > > I think bug #30265. Oh I see, UCS-4 as well. (I can=E2=80=99t believe this bug is still open g= iven the relatively simple solutions outlined at . :-)) Thanks, Ludo=E2=80=99.