<chrislck>the lack of an easy built-in cross-platform gui toolkit is annoying imo <chrislck>alternatively is it easy to create a standalone text-based ui? <nly>can you tell me how g-golf is supposed to be used in terms of libraries, for example which one is better 1. hard-coding the gobject glib and libgirepository into g-golf at build time 2. dynamically loading gobject glib and gobject-introspection from user profile? <str1ngs>nly: the typical way is to use a standard path like /usr/lib. if not then you can add the library path to LD_LIBRARY_PATH <str1ngs>nly: for guix we substitute which is good for guix. <nly>oh man, given you do everthing right, still it doesn't quite work. Maybe I am looking in the wrong spot for problems? <nly>str1ngs: [appropriate time] greetings! <str1ngs>is this the in regards to the class GdkPixbuf is already registered issue? <nly>guix package -L ./guix -i nomad && nomad <nly>no <application> or something <str1ngs>before <application> error do you get a glib error? <nly>but get this, ./pre-inst-env nomad # the one installed in profile <nly>missing some wrapped path? <nly>1 sec, i'll paste the log <nly>str1ngs: no, it works. haha <str1ngs>guix package -L ./guix -i nomad && nomad work nly? <nly>>guix package -L ./guix -i nomad && nomad <str1ngs>also you might want to use nomad-git <str1ngs>nly: does guix.git environment --ad-hoc nomad-git -- nomad work? <nly>>Typelib file for namespace 'Gdk' (any version) not found <nly>well, yes but actually ran `nomad -Q` <str1ngs>right but you modified the propagates right? <nly>feature-windows: dcd44aa7df68033b16601cc2eb7aaf688ac2f97f <str1ngs>guix.git environment --ad-hoc nomad-git -- nomad works for me <nly>let's trade computers <nly>i have modified nomad pkg in guix, does that affect? <str1ngs>right I asked you if you modified nomad.scm <str1ngs>and guix environment --ad-hoc nomad-git then in the environment echo $GI_TYPELIB_PATH <nly>/gnu/store/dcfwzgcwnipk7c71j51czkb7bjm6svmm-profile/lib/girepository-1.0 <str1ngs>looks good now run nomad same error? <str1ngs>then guix environment --ad-hoc nomad-git -- nomad . should work too <str1ngs>okay I thought you said it didnt work <str1ngs>okay so everything seems to be working now then? <nly>>guix environment --ad-hoc nomad-git -- nomad <str1ngs>I think the issue was you were not using nomad-git? <nly>>guix package -L ./guix -i nomad-git -- nomad <nly>but doesn't work, was the complain <str1ngs>okay so installing to your profile does not work then? <str1ngs>okay with Typelib file for namespace 'Gdk' (any version) not found ? <str1ngs>if so start a new terminal and then run nomad <nly>>if so start a new terminal and then run nomad <str1ngs>seems maybe you ignored hint: Consider setting the necessary environment variables by running ? ***oni_on_ion is now known as oni-on-ion
<nly>echo $GI_TYPELIB_PATH is empty <str1ngs>GI_TYPELIB_PATH should not be empty please start a new terminal <nly>>please start a new terminal <str1ngs>and source ~/.guix-profile/etc/profile && nomad <nly>>source ~/.guix-profile/etc/profile && nomad <str1ngs>your shell is not setup to source ~/.guix-profile/etc/profile <str1ngs>as far as I can see nomad.scm is fine. provided you source ~/.guix-profile/etc/profile <nly>thanks for the patience <str1ngs>one thing to keep in mind is feature-window is a <nly>source ~/.guix-profile/etc/profile <str1ngs>a moving target. that's why I'm using propagates etc. it's mainly only intended for development <str1ngs>also propagates is less likely to cause the cannot register existing type 'GdkPixbuf' issue <str1ngs>later maybe we can wrap nomad and provide GI_TYPELIB_PATH. <str1ngs>if you want to experiment with that. it's possible we can avoid propagates. <str1ngs>but then you might get the cannot register type issue <str1ngs>also we might be able to switch back to using glib-or-gtk-build-system. since libguile-nomad.so guile extention <str1ngs>nly: no problem. if you want to refine nomad.scm that would be helpful. since I mainly work locally for development reasons <str1ngs>nly: also regards to ibuffer I don't think right arrow and left arrow is all that important. for now we could unbind them. or bind them to ibuffer-next-line etc ***oni_on_ion is now known as oni-on-ion
<roptat>Is it possible to do xml->sxml without parsing entities? Basically "<foo>&</foo>" -> (foo "&") <roptat>I managed to do almost that by defining default-entities-handler and entities keywords, but handling & that way raises a [norecursion] broken error <roptat>I'm trying to extract the content of a script element <roptat>Imagine something like <script>var a="&"; console.log(a.length)</script>. The browser shows 4, but I would get 1 in a js interpreter in guile <roptat>Oh if I set a to "<foo>" it's even worse, since the parser thinks the html tags are unbalanced <roptat>So… is there a way to get the correct behavior for the script element? <RhodiumToad>parsing html is a _whole other world_ than parsing xml <RhodiumToad>in xml, or even in xml representation of xml, you'd solve that by putting the script in a CDATA <RhodiumToad>not that I know of, but don't take that as definitive <oni-on-ion>weinholt, yea, i see this recommendation on guile-user mailling list ***Server sets mode: +nt