bug#38940: \x1b]8; ; OSC character displayed on hyperlinks shown after calls to `guix describe` or `guix show` on mate-terminal 1.12.1 (Trisquel 8)

2020-01-10 Thread Ludovic Courtès
Hi,

Jack Hill  skribis:

> On Thu, 9 Jan 2020, Ludovic Courtès wrote:
>
>>> 1. Instead of INSIDE_EMACS, the variable name NO_SUPPORT_HYPERLINK or
>>> other seems more meaningful. Maybe?
>>
>> Actually the goal was to remove ‘INSIDE_EMACS’ from there once a
>> widespread-enough Emacs version supports it, which could be within a
>> year.  And since other terminals are supposed to ignore it altogether, I
>> would rather not add a special environment variable.
>
> Which Emacs version support it? I'm using Emacs 26.3 from master, and
> see the escape sequences in eshell. They seem to be correctly ignored
> in M-x 
> shell.

Emacs 26.3 does not support it; all I know is that there’s a patch by
José Marchesi floating around.

Ludo’.





bug#39073: GNU icecat number and # disapears. [pt-br]

2020-01-10 Thread Pablo Ferreira
Desde que eu atualizei o GNU Icecat para a versão 68.4.x eu não consigo
mais ver números na internet. Só acontece no Icecat, então acho que a falha
não é no guix. Sítios que personalizaram suas fontes os números aparecem,
então acho que eu vou tentar mudar a fonte do GNU Icecat. Eu tentei isso no
"preferencias" mas ainda não consegui.


bug#38946: guix import fails for cabal-helper

2020-01-10 Thread Robert Vollmert
It appears that the guix cabal parser (in guix/import/cabal.scm) isn’t aware
of `common` stanzas.

https://www.haskell.org/cabal/users-guide/developing-packages.html#pkg-section-common-common

Note that there’s quite a few issues with the cabal parser, and the format is 
pretty
baroque, to the extent that I wonder whether it wouldn’t be better to delegate 
the
parsing to cabal itself.

E.g.:

https://debbugs.gnu.org/cgi/bugreport.cgi?bug=35743
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=36690

I also remember some issue with braces instead of indentation, but can’t find a 
bug
report right now.






bug#39073: GNU icecat number and # missing.

2020-01-10 Thread Tobias Geerinckx-Rice via Bug reports for GNU Guix

Pablo Ferreira 写道:
Desde que eu atualizei o GNU Icecat para a versão 68.4.x eu não 
consigo

mais ver números na internet.


Solved (over IRC) by installing ‘font-gnu-freefont-ttf’ alongside 
IceCat.


I'm merging this with bug #37345, because this still needs 
documenting if it can't be fixed in a reasonable 
(i.e. non-propagated) manner.


Thank you for the report!

T G-R


signature.asc
Description: PGP signature


bug#39079: SBCL CFFI from Guix unable to find dynamic libraries

2020-01-10 Thread Evan Straw
Hello all,

I have GNU Guix installed on a foreign distro, Ubuntu 19.04. I have the
sbcl and cl-cffi packages installed from this installation of Guix, and
I am attempting to use the CFFI package to load libcurl, as demonstrated
in the CFFI tutorial here:
https://common-lisp.net/project/cffi/manual/html_node/Tutorial_002dLoading.html

However, this fails with a message saying that there is "no such file or
directory," even when I attempt referencing the library by its exact
name, "libcurl.so.4".

There is only one condition in which I can get this to (sort of) work,
and that is when I manually add the path "/usr/lib/x86_64-linux-gnu/" to
the *foreign-library-directories* list, which is initially NIL. Even
then, however, CFFI fails to automatically load any libraries libcurl is
dependent on, unless I manually load them by directly referencing their
full names as well.

This seems like it isn't intended behavior, especially since the CFFI
documentation discourages the use of the *foreign-library-directories*
variable, and claims that the implementation (SBCL in this case) should
be taking care of this. I'm unsure if this is anything to do with Guix
not using a "traditional" FSH or not.

Does anyone have any thoughts on this? This is my first bug report
submitted here, so if I'm missing any needed information, please let me
know and I'll try my best to provide it.

Thanks,
-- Evan


signature.asc
Description: PGP signature


bug#39080: How do language packs work?

2020-01-10 Thread Caleb Herbert
How do language packs work in Guix?  I would like to translate my future
system to Pennsylvania Dutch.
<>

signature.asc
Description: OpenPGP digital signature


bug#39080: How do language packs work?

2020-01-10 Thread Julien Lepiller
Le 10 janvier 2020 22:54:28 GMT-05:00, Caleb Herbert  a 
écrit :
>How do language packs work in Guix?  I would like to translate my
>future
>system to Pennsylvania Dutch.

Hi Caleb,

Thanks for your interest in localisation! I'm unfortunately unable to find a 
language code for your language. That is necessary for software to recognise it 
and speak it. I may not have searched correctly, so maybe you can find the 
correct code? Something like ll_LL (fr_BE for Belgium French) or maybe a code 
like ll-x-something (fr-x-gallo for a minority language in France that doesn't 
have its own iso-639 code, although I'm not sure it is technically accepted by 
software).

Once you have that code, you can use it in the guix system in the locale field 
of your os declaration. If you are on a foreign distro, then check with them 
how to set a language (or set $LANG temporarily).

If your question is how to help translating, and not just how to have software 
speak your language, you'll have to note that we do not translate any of the 
software we package, apart from guix itself: each package upstream is 
responsible for their translations.

To help translate guix, please have a look at the translation project: 
https://translation-project.org

To help translate other projects, you'll have to find what their process is to 
accept translations. Usually you can find this information by navigating from 
their home page, which you can find with the command `guix show the-package`.

In either case, there might already be a community of translators for your 
language. I encourage you to go and find them, they will probably have a lot of 
info, guidelines that will be very helpful to you.

I hope this answered some of your questions.





bug#39080: How do language packs work?

2020-01-10 Thread Caleb Herbert
On 1/10/20 10:31 PM, Julien Lepiller wrote:
> Thanks for your interest in localisation! I'm unfortunately unable to find a 
> language code for your language. That is necessary for software to recognise 
> it and speak it. I may not have searched correctly, so maybe you can find the 
> correct code?

pdc

Examples:
https://pdc.wikipedia.org/wiki/Haaptblatt
https://www.jw.org/pdc/
https://iso639-3.sil.org/code/pdc

> Once you have that code, you can use it in the guix system in the locale 
> field of your os declaration. If you are on a foreign distro, then check with 
> them how to set a language (or set $LANG temporarily).

I highly doubt a locale file for pdc_US exists.  I'd like to make one,
but the file for en_US and yi_US don't show the actual characters.  I
just see "", which I can't read or produce.

> To help translate guix, please have a look at the translation project: 
> https://translation-project.org

Thanks.
<>