<davexunit>you will want to add $HOME/.guix-profile/bin to your path, for one thing.
<davexunit>additionally, you will likely want to use the environment variables output by 'guix package --search-paths'
<sirgazil>But, say I have inkscape installed with apt and I install it again but using Guix... If I add my guix profile bin to PATH, what inkscape I'd be running? (sorry, I don't usually deal with env variables manually)
<mark_weaver>sirgazil: if you run /usr/bin/inkscape, you'll run the inkscape from Debian. if you run ~/.guix-profile/bin/inkscape, you'll run the one from Guix.
<mark_weaver>sirgazil: if you just run "inkscape", it'll run the one that is found first in $PATH
<Sleep_Walker>quick question - I have multiline description, sentence is ending on a line, should that be followed by two spaces even it is in the end of line? should that be on beginning of first line? or should I just ommit it?
<Sleep_Walker>(uh, again my english - with "it" I mean two spaces separator between sentences)
<davexunit>Sleep_Walker: Omit it, since it would be trailing whitespace.
<davexunit>it's how M-x fill-paragraph does it in Emacs
<civodul>so eventually we should just arrange to have ISO-8859-1/UTF-8 transformations built-in
<mark_weaver>no need to apologize. sometimes it's better to get something working and then fix it up later. if it were me, my perfectionism probably would have prevented me from ever getting something like guix off the ground :)
<mark_weaver>if we assume that pti->encoding_mode is SCM_PORT_ENCODING_MODE_UTF8 (which I'm not yet sure), then the UTF-8 from the file will be converted to ISO-8859-1 in the string internal buffer, and then regexp-exec will interpret that ISO-8859-1 as UTF-8, which is certainly likely to fail.
<mark_weaver>so these are old problems that have been hidden for a long time.