=== MaNL is now known as MaNI\ [06:59] nlsthzn you wanted to see my zsh, right? https://asciinema.org/a/2mc1k5cv43uj5yrh5b11f6ebx === MaNI\ is now known as MaNI [08:23] well it wasn't me theblazehen I just mentioned I had used fish before :) but it looks sweet [08:24] nlsthzn ty. May have been nsnzero then [08:40] maaz tell nsnzero https://asciinema.org/a/2mc1k5cv43uj5yrh5b11f6ebx zsh [08:40] theblazehen: Okay, I'll tell nsnzero on freenode [10:31] * theblazehen wishes there was some kind of abstraction between code and how it's viewed. Basically like having a reverse lexer? That way people don't have to worry about tabs vs spaces, how many spaces per level of indentation, K&R style vs Allman style braces, etc. [10:31] Lexing would be the right stepp in the process, right? Or would it be at the parsing level? [10:34] if everyone followed some or other standard 100% that would be possible - and already is - but the problem comes in that there are always edge cases where the styling standard doesn't make sense, and then people want to deviate from it, and that part then gets lost when auto formatting [10:35] MaNI got examples? [10:35] How would the golang people handle it? Since they use gofmt etc [10:36] I can't comment on golang, but for C++ there is e.g. clang-format [10:37] * theblazehen is referring to example edge cases [10:37] it is perfectly possible to set git or svn up to automatically do `clang-format ` on all commits, and to do `clang-format ` on checkouts [10:38] I guess [10:39] https://i.imgur.com/wG51k7v.png :( [10:39] well, lets say comments are always a single space, followed by a '//' followed by a space, and then text - maybe 95% of the comments are like this, but somewhere in my code there is bound to be a place where it is desired for the comments at the end of multiple different lines to line up with one another - so a different number of spaces at the start [10:40] Ah, yes. That's a good case. Forgot that not everything in the source is code [10:41] I like how TempleOS does the seperation of code and documentation [10:42] The OS is by a crazy guy, but I like how HolyC handles documentation, embedded data (eg sprites) etc [10:42] http://theblazehen.com/templeos.vdi 1024x512 try it with an older virtualbox version or something. It used to work [10:45] ahoy ZA! [10:45] a hey theblazehen :p [10:45] hi pavlushka [10:46] theblazehen: you haven't used ssl for your site I see :p [10:46] wow, thats one disturbing wikipedia article [10:47] pavlushka yeah, that's on my old server. Still migrating to home where my reverse proxy does ssl [10:48] aha [10:49] hey chesedo :) [10:57] linx.home.theblazehen.com <- with SSL with my reverse proxy pavlushka [10:57] chesedo: where's your re-verification application? [10:58] got it [11:01] removed myself as ubuntu member from the page :/ oh well onward and upward and all that shenanigans... [11:25] is it a bad line "even if you had a bad day at work, join #ubuntu-za on IRC and they might even cheer you up :). " ? [11:26] *they will cheer you up ;) [11:28] nlsthzn: ha ha ha, yes, that's correct :) [11:37] you have failed me for the last time Unity 7.blablabla [11:37] grrrr [11:38] * nlsthzn goes and wrangles a geeko [13:00] I've added a bit from me for https://wiki.ubuntu.com/ZATeam/ReVerificationApplication2016 [13:02] * andrewlsd goes away again for a bit. [13:15] does anybody here use snaps ( http://snapcraft.io/ ) - just wanted to gauge the average linux users opinion on them. Would you be okay if some package you wanted only came in snap form, or do you expect to also have it in the main repo? Do you like the idea of snaps or hate it? etc. === MaNL is now known as MaNI [13:18] MaNI: I use some snaps [13:18] I prefer repo for "stable" apps [13:18] and 'snap' for dev/testing stuff. [13:18] because then I don't have to install tons of dev/incompatible shared libraries. [13:19] obviously, snaps have a size overhead, which can hurt those on slow/limited_cap connections [13:20] the idea of using snaps to update parts in _embedded systems_ looks very good. (again, snap app size needs to somehow be dealt with as many embedded devices have very limited storage) [13:21] current snaps installed: [13:21] anatine ; canonical-livepatch ; lnks ; qownnotes ; toilet ; ubuntu-core ; vlc [13:22] MaNI: if doing "Electron" apps, check out AppImage. (nice for native apps too.) [13:22] AppImage are portable apps, and work on pretty much any distro. [13:22] but... they don't have the sandbox protection of snaps or FlatPack [13:23] after checking out Appimage.org, have a look at https://dl.bintray.com/probono/AppImages/ for some ready-to-use .AppImage software. [13:24] ... following on on the dev/testing via snap: I like it for ease of total removal. [13:24] s/it/snaps/ [13:25] so I think of snaps as "local-only" application containers. [13:25] hope that helps MaNI [13:29] I'm thinking about it from this viewpoint [13:34] stable internet would be fantastic === MaNL is now known as MaNI [13:38] 1) I'm maintaining a cross platform app that the linux version of currently just ships as a zip file with some binaries in [13:38] 2) People seem to be confused about how to install this, ideally it would be nice if they could just install it through a package manager or something [13:39] 3) I don't really have the time or energy to deal with trying to get into an actual package manager, plus probably extra grief because debian may not like the licensing, plus I want to support a lot of other distros [13:39] so I'm wondering if putting up a snap is a good way around that (works on multiple distros) or if most users have never run into snaps and won't know what to do with them [13:41] I could also do some kind of .run style thing I guess - but people never seem to have been fans of those, wondering if it's similar with snaps or if people are a bit more receptive of those [13:42] MaNI: AppImage is probably the right way for you then. [13:43] no "install", just double-click to run. [13:43] AppImage does have a mechanism for creating .Desktop files, so that the gui shell (gnome/kde/unity) will have application launchers [13:44] benefit of snaps: updates are possible [13:44] drawback: only usable by default on Ubuntu. Any other distros would require the user to first manually install the snap framework [13:45] benefit of AppImage: truly portable Linux app. [13:45] Or just put it in docker /s [13:45] drawback: no internal update framework. Update app by downloading and replacing it. [13:45] docker not so much fun for GUI app. [13:45] but true [13:46] MaNI: is it a GUI app? [13:46] yes [13:46] andrewlsd How easy it to to build appimage etc? /me created a .desktop entry to run acrobat reader in docker etc [13:46] another benefit of AppImage, no root privileges required. Snap currently requires root, since it really installs [13:46] docker, gross [13:46] AppImage is easy to build. has IDE hooks too. [13:46] andrewlsd hmm. Might check it out [13:46] theblazehen: AppImage.org [13:47] and MaNI: https://github.com/probonopd/AppImageKit/blob/master/README.md [13:48] andrewlsd and do you need to build anything specially for it? Eg acrobat reader isn't open source [13:48] theblazehen: "An AppImage is an ISO 9660 file with zisofs compression containing a minimal AppDir (a directory that contains the app and all the files that it requires to run which are not part of the targeted base operating systems) and a tiny runtime executable embedded into its header. Hence, an AppImage is both an ISO 9660 file (that you can mount and examine) and an ELF executable (that you can execute)." [13:48] app image, somewhat interesting, though unless users are familiar with it, it doesn't solve the whole "where do I put it" question [13:49] ~/Downloads [13:49] andrewlsd cool [13:49] MaNI: but true. but to solve "where do I put it" requires root. [13:49] yeah - but what I mean is there will be a constant bombardment of people asking where it should go - it's the number 1 asked question for the current scheme (tar with binaries in) [13:49] in which case, snap or flatpack may help. [13:50] MaNI: and could be solved by a "FAQ" [13:50] haha, users that read that would be a first [13:50] tru dat [13:50] something like snap handles that part, but then it's an issue for distros where they first have to install snap system [13:50] hrm [13:50] are your end users "enterprise" environment, or home end-users. [13:51] home end-users [13:51] If you want multi-distro, then AppImage. [13:51] ... otherwise you'll have to still build .rpm .deb or .snap for each supported distribution [13:52] check out the "Appimage updater" too. [13:52] okay [13:53] thanks will have a look [13:53] theblazehen: https://github.com/probonopd/AppImages for recipes for bundling real-world apps [13:53] theblazehen: check if you can put Acrobat Reader into one of those. would be fantastic. [13:57] theblazehen: I see AcroReader is a 32-bit app. Not sure how AppImage would handle that. [13:58] andrewlsd sure. You can see the docker in our salt if you like [13:59] yeah, am looking at it [14:05] going to try get all the required libs via: `lxc launch ubuntu:x/i386 xenial386` [14:08] theblazehen: https://github.com/mciverza/docker-acroread [14:11] andrewlsd that's where I grabbed it from iirc [14:12] not sure how far I'll get since it's 32-bit. so a docker/lxc might remain the best option. [14:12] ^ pretty nice use-case. [14:13] ie, install some crappy, unmaintained application without drastically compromising your system [14:14] so far: 69% of image retrieved by `lxc launch ubuntu:x/i386 xenial386` [14:14] maybe I should do this on Digital Ocean. [14:17] * andrewlsd heads away from here for a few hours === pavlushka is now known as The_Doctorman === The_Doctorman is now known as pavlushka [16:09] HELP [17:03] good evening all [17:07] hi nsnzero [17:07] hi everyone else as well too [17:07] what a long day [17:07] hi Kilos , how are you ? [17:07] from 5 am till now travelling and sitting at hospital [17:07] im ok ty and you [17:08] got a ton of meds [17:08] might be like a goofball for a moth [17:08] month [17:11] thats medication - fix 1 problem create 2 more [17:14] theblazehen: awesome zsh theme = i am impressed [17:29] hi inetpro superfly MaNI theblazehen Xethron [17:31] hi Kilos [17:33] superfly [17:33] sup nsnzero [17:35] trying to copy theblazehen zsh config [18:32] superfly can you and paddatrapper put a few links to debconf in https://trello.com/c/nW7ephrM/118-need-list-of-all-activities-held-in-last-two-years-under-the-flag-of-ubuntu-za [18:33] plese [18:33] under list of all activities [18:33] please as well [18:34] hi Kilos. nsnzero ty :) http://linx.home.theblazehen.com/zshrc.ext just remove the unapplicable bits etc [18:34] sjoe 71 blazehens [18:34] can start a chicken coop soon [18:35] Kilos sorry? [18:36] theblazehen71 here more [18:36] Ah. Right. Other irc bouncer [18:36] so 71 plus you is 72 of them hens [18:36] heh [18:36] aw they left [18:36] heh [18:37] Kilos: will do [18:39] ty paddatrapper [18:40] and maybe something saying fly is leaving south africa the next day but never ubuntu-za [18:40] oh thats for you to say superfly [19:07] hi inetpro [19:07] inetpro ping [19:07] id like to say good morning before i say night [19:37] night all, sleep tigh [19:37] tighter than that