IRC channel logs


back to list of logs

<pkill9>raingloom: have you saved the module to "mininet.scm" and have GUIX_PACKAGE_PATH set to the directory that mininet.scm is in?
<nixo_>wowowo I reached the check phase :D julia-1.1.0 is coming
<wednesday>Is there a better way I could be doing this before I think about formatting it into a patch?
<wednesday>I had to add python as an input to the package for that, so wondering if I can do it without adding that new input
<apteryx>wednesday: no, any referenced package must be part of the inputs, unless they are part of the build system
<apteryx>I would have though the #!/usr/bin/env python to be patched automatically by one of the build phases
<raingloom>pkill-9[m]: yes... or at least i'm 99% sure. and it's defined with define-public.
<apteryx>raingloom: check that you Guile module hierarchy matches the file-system hierarchy
<apteryx>e.g., (my own packages) should appear under my/own/packages
<raingloom>....oh. thanks! I had no idea that had to match >_>
<raingloom>oh, it's in the footnotes...
<wednesday>apteryx: well that one file wasn't, and that stops you using gtags with python, so I might submit that tomorrow or something
<apteryx>wednesday which package is that?
<wednesday>global in code.scm
<apteryx>wednesday: the patch-source-shebangs in (guix build gnu-build-system) should have taken care of it, as long as python is part of the inputs. Have you tried by simply adding python and not doing anything else?
<wednesday>I'll try that in a second
<apteryx>if you read the build log carefully, it even emits: patch-shebang: ./plugin-factory/ warning: no binary for interpreter `python' found in $PATH
<wednesday>apteryx: Doesn't seem to work with just python as an input
<apteryx>oh, maybe python-wrapper
<apteryx>python alone would give you python3
<apteryx>raingloom: yw! I was bitten by this at first too :-)
<wednesday>apteryx: yea that seems to work
<maddo>Blackbeard[m]: I stopped exporting to latex
<maddo>I mostly export to groff using the mom macros set and a custom stylesheet
<maddo>never looked back
<Blackbeard[m]>maddo: groff?
<Blackbeard[m]>maddo: wow
<Blackbeard[m]>looks beautifull
<Blackbeard[m]>maddo: can you teach me how you did it?
<marusich>groff's mom macro package is pretty great
<Blackbeard[m]>I need this for school so I need to do everything quick
<maddo>groff is actually much more straightforward than LaTeX, man pages are pretty clear actually
<maddo>dunno what you need to do for school tho so can't help much there
<marusich>However, I won't lie: if you just need a rudimentary document, LibreOffice is hard to beat. It's intuitive and easy to do most things in LibreOffice, so if you don't have specific requirements for a document, it's a good bet.
<maddo>It's a matter of habit I think. To be perfectly honest I never really managed to like office in any of its implementations
<maddo>be it the proprietary ones or free ones
<maddo>They just seem so confusing to me compared to good ol' org-mode
<maddo>but then again, it's a matter of preference I guess
<Blackbeard[m]>wow it looks amazing
<marusich>I think the nicest part about mom (and groff in general) is that it is trivial to embed pic diagrams, something that apparently even in Latex is harder to do.
<Blackbeard[m]>maddo: how do you export from org mode to groff
<Blackbeard[m]>this is great
<Blackbeard[m]>it looks fantastic
<maddo> customised this to work with mom
<maddo>I'm not on my main pc tho so I can't link it to you yet
<marusich>I have used mom in the past to write a software design document that incorporated pic diagrams into the document; it was built with a simple Makefile, and it was pretty nice to be able to check it all into source control as readable, editable text files. However, in the end my team wanted Markdown, and I'm sad to say I had to relent :(
<maddo>remind me tonight (it's 10 am right now in my tz)
<Blackbeard[m]>maddo: ok
<maddo>the best part about groff in general is font handling
<Blackbeard[m]>it is 3 am for me
<maddo>TeX font handling is something painful
<maddo>very very painful
<Blackbeard[m]>so in my morning i'll ask
<Blackbeard[m]>maddo: indeed
<Blackbeard[m]>I use the defaults
<Blackbeard[m]>they are ok
<Blackbeard[m]>but not great
<marusich>Well, another benefit for LibreOffice is that it supports languages like Japanese and Chinese better. Groff, as far as I know...kind of doesn't
<marusich>But those pic diagrams!
<maddo>and also references can let your compile time grow very slow very quickly
<marusich>So nice.
<marusich>Amazing what you can do with pic:
<Blackbeard[m]>marusich: i would ovly be worried about spanish accents
<Blackbeard[m]>I hope there isn't a problem with those
<maddo>I'm in Italy and we have accents too, never had problems
<Blackbeard[m]>but after emacs and stumpwm
<Blackbeard[m]>i can't go back to gui's
<marusich>And here's another example using pic for sequence diagrams, so nice!
<maddo>but tbh I think groff has support for unicode
<Blackbeard[m]>maddo: ah wonderful
<maddo>if you have the right fonts and everything
<Blackbeard[m]>what about bibliography like bib files
<maddo>that's the best part
<maddo>bibliographies are much more manageable in groff than in TeX
<maddo>there is refer which is blazing fast
<marusich>Blackbeard[m], I think groff has good support for those kinds of characters.
<Blackbeard[m]>ohhh i just look for it
<Blackbeard[m]>seems more readable
<maddo>and you can convert TeX bibliographies to refer ones with one sed script basically
<maddo>that comes handy when you have to use things like
<maddo>marusich: markdown is fine, albeit sort of limited, if you and your team want *only* HTML output
<maddo>but if you need anything other than HTML you're in for a headache
<Blackbeard[m]>I use org-ref
<maddo>I always used org and made others work with org (even on other editors) because that's the only markup where you can literally output to anything while keeping a nice and clean syntax
<maddo>need a pdf? Org can do that. Need a typesetted pdf? Org can do that. Need markdown for your static website? Org can do that. Need a spreadsheet? Org can still fucking do that
<maddo>Markdown? Crippled HTML depending on what you're using (because there is no standard markdown, every parser has its own quirks and dialects)
<Blackbeard[m]>org mode is wonderful ٩(◕‿◕。)۶
<Blackbeard[m]>Emacs is the best ٩(◕‿◕。)۶
<brendyyn>do you think it would be possible to port orgmode to guile and make a library for using org files?
<marusich>I don't know about guile, but I did see this:
<brendyyn>i mean since guile runs elisp
<maddo>everything is possible the point is: is it useful? The main thing for it to happen is guile-emacs reviving and I don't see that happening anytime
<maddo>there is basically no interest in mailing list
<brendyyn>way too advanced level for me ;)
***harding is now known as harding-quassel
<nixo_>Hello guix, I got julia 1.1.0 working, can anybody help in linting and checking it?
<nixo_>Well I uploaded it here in the meanwhile . It's full of noise and one test that should pass (libgit2) is removed
***apteryx_ is now known as apteryx
<nckx>sneek_: ping botsnack.
<nckx>My underscore hypothesis remains undisproven.
<nly>I am trying to build qtwebengine, failing atm
<nly>error log:
<nckx>o/ ATuin.
<ATuin>hi nckx
<ATuin>i'm a bit confused with "pre-inst-env" script. is it just setting env variables right? the store is the same as when using my normal daemon?
<ATuin>i have run ".configure" and "make". Do I need to run make again if i modified a scm inside gnu/packages?
<ATuin>i want to create an emacs package inside emacs-xyz.scm to learn how to work with it
<nckx>ATuin: Yes, pre-inst-env (‘pre-installation environment’) just makes sure that the guix you built from git finds all the dependencies without being installed.
<nckx>You don't need to run make to apply the changes, but Guile will print a warning and run slightly slower for each uncompiled modified file. So if you (or ‘git pull’) have modified many files you'll want to run make again just to get rid of the warnings and improve performance.
<nckx>(The warning is otherwise harmless.)
<atw>scheme-file seems to have compiled a λ into a ?
<ATuin>nckx: thanks, one more question, do i need to run the daemon using pre-inst-env or is it fine to use my normal daemon
<ATuin>seems that
<ATuin>ops sorry
<ATuin>seems that now (running the daemon using the pre-inst-env script) guix lint can not find my ssl certs
<nckx>ATuin: Not nless you've modified the daemon in your git repository (unlikely).
<ATuin>ahh ok, thanks again. I will run the normal daemon then
<ATuin>ah nice, seems that adding nss-certs to the environment fixed the certs issue :)
<atw>nginx quine:
<reepca-laptop>Hm, trying to build openra but it can't seem to find some executable called "csc" so it thinks mono isn't installed, even though it is... I'm not familiar with C# land, any idea what's up there?