Logs for #nikola for 2015-06-16

06:32:47 <KwBot> [nikola] shmilee opened issue #1826: nikola help auto, UnicodeEncodeError https://github.com/getnikola/nikola/issues/1826
11:45:00 <KwBot> [nikola] ralsina opened issue #1827: Man page improvement https://github.com/getnikola/nikola/issues/1827
13:44:35 <ChrisWarrick> polyzen: (1) please send your complaints to Logbook and use a dark terminal like everyone should (2) what is navbar-alt?  do you mean navbar-inverse (the dark style of the navbar in bootstrap)?  that would require editing themes, I’m afraid
13:46:55 <polyzen> ChrisWarrick, i use dark terminals after the sun sets :p
13:47:01 <polyzen> -light during day, -dark after dark
13:47:06 <ChrisWarrick> that’s boring
13:47:09 <polyzen> lol
13:47:12 <erdgeist_> ChrisWarrick: Hello. After I created a nikola site with nikola init, is there any need to upgrade its content to what a newer version of nikola would have produced?
13:47:31 <polyzen> no /need/
13:47:41 <ChrisWarrick> erdgeist_: you installed an old version, created a site and upgraded nikola, right?
13:47:57 <polyzen> !g python-logbook
13:47:59 <erdgeist_> Yes
13:48:02 <ChrisWarrick> polyzen: sorry, not implemented
13:48:06 <polyzen> :p
13:48:11 <ChrisWarrick> polyzen: KwBot  is still a very dumb bot, I’m afraid
13:48:22 <ChrisWarrick> erdgeist_: run `nikola build`.  some pages might rebuild. if you get any errors or deprecation warnings, please address them manually.
13:49:14 <polyzen> ChrisWarrick, yes, -inverse
13:49:32 <ChrisWarrick> polyzen: sorry, you need to edit the template for that
13:49:54 <polyzen> wonder why that's the default
13:50:22 <polyzen> edit the template, the nikola theme, or the bootswatch theme? o.o
13:51:26 <ChrisWarrick> cp /PATH/TO/site-packages/nikola/data/themes/bootstrap3/templates/base_helper.tmpl themes/custom/templtes/
13:52:03 <polyzen> thank you
13:53:15 <polyzen> ChrisWarrick, so templates are nikola themes?
13:53:28 <ChrisWarrick> polyzen: I’m not sure if I understand your question
13:53:47 <ChrisWarrick> polyzen: a Nikola theme is a collection of assets and templates.
13:54:16 <polyzen> -now i see
13:57:17 <polyzen> no mention of navbar or -inverse in this file
13:57:22 <polyzen> this is going to be fun :p
13:58:06 <polyzen> base.tmpl has it
13:59:54 <KwBot> [nikola] Kwpolska assigned issue #1826 to Kwpolska: nikola help auto, UnicodeEncodeError https://github.com/getnikola/nikola/issues/1826
14:00:08 <ChrisWarrick> oh, sorry
14:00:38 <erdgeist_> ChrisWarrick: I convinced a friend to use nikola and I gave him access to my site's sources, so he can steal useful modifications. I guess what I really wanted to ask is if there's a way for him to apply some of the diffs without checking out an old version of nikola
14:01:26 <ChrisWarrick> erdgeist_: diffs of what?  your config file or your patches to the nikola source code?
14:04:02 <erdgeist_> I did not patch the source code
14:04:30 <erdgeist_> I guess I need something like a threeway diff between an old empty site, a new one and mine
14:05:09 <ChrisWarrick> now, that is not going to be easy…
14:05:36 <ChrisWarrick> you could try diffing the config files this way and hiring humans to read other files
14:05:37 <erdgeist_> ChrisWarrick: You know, there's a plugin/-directory with a __init__.py. I did not create or touch it.
14:05:44 <ChrisWarrick> erdgeist_: that’s intentional
15:39:15 <ChrisWarrick> gour: still waiting for your route usage ideas: https://github.com/getnikola/nikola/issues/915
15:41:33 <gour> ChrisWarrick: do you believe nikola is flexible like Hugo in this regard? i must admit that the issue was due to seeing example of sites done with Nanoc/Middleman which were more of 'general' nature, while those done with Nikola were/are simple blog-only ones
15:45:19 <ChrisWarrick> gour: I never used hugo and have absolutely no fucking idea what it does
15:47:48 <gour> ChrisWarrick: e.g. http://gohugo.io/content/sections/
15:48:38 <gour> in the meantime i have reduced the need for complexity for my web needs, so I'm sure Nikola can do everything ;)
15:49:25 <ChrisWarrick> gour: please read the most recent comments.  you can also use multiple posts directories, categories (for posts) or story_index (for stories) for indexes
15:49:32 <ChrisWarrick> most recent comments under #915*
15:50:35 <gour> ChrisWarrick: just read them :-)
15:51:08 <gour> having ability to have multi-level hierarchy is all what i want(ed) :-) 
15:52:17 <ralsina> ChrisWarrick: so, it looks like we have had a failure to communicate that Nikola does cool things :-)
15:52:39 <ChrisWarrick> we should write a “getting started” tutorial from scratch
15:52:42 <ralsina> Did we at some point **not** support multiple levels there?
15:52:49 <gour> ralsina: this is shed big light on it: "You can have as many levels as you want there and they will appear in the same place in the output."
15:52:51 <ralsina> ChrisWarrick: yeah.
15:53:02 <gour> *sheds
15:54:10 <gour> that's my point too...Nikola is much more capable than it might look at first site...better examples should prove it ;)
15:55:01 <gour> have to prepare for afk engagement...
15:55:36 <ChrisWarrick> ralsina: they were around in August 2013, at least
15:56:22 <ChrisWarrick> ralsina: before that, either I was too dumb, or they were not there yet
15:56:27 <ralsina> When we were ramping up for v7 I did a series of blog posts showing off new features. Now we need a series of thigns showing OLD features.
15:56:46 <ralsina> Since, AFAIK we don't lack much of anything.
15:57:06 <ralsina> Like, pelican just announced that they can do things like "cache things" and "bind to addresses not localhost"
15:57:29 <ralsina> Also "disabled caching by default because you will get stale objects"
15:58:19 <ChrisWarrick> pelican are really funny
15:58:31 <ChrisWarrick> no idea why they are so popular
15:58:35 <ralsina> with that strange beak and everything
15:58:42 <ralsina> oh, the software, again :-)
15:58:56 <ralsina> because octopress is built on top. Pelican itself is unusable.
15:59:16 <ChrisWarrick> wait, isn’t octopress jekyll (unusable either)?
15:59:46 <ChrisWarrick> I had a jekyll site once, I had to provide my own “RSS” files that iterated over the bloody timeline…
16:00:50 <ChrisWarrick> yeah, octopress == jekyll on steroids
16:01:09 <ralsina> ah, right
16:01:15 <ralsina> ok, no excuse for pelicn then
16:01:41 <ralsina> pelican is the one that's "jekyll in python"?
16:01:49 <ChrisWarrick> not really
16:02:21 <ChrisWarrick> http://docs.getpelican.com/en/3.6.0/
16:02:36 <ralsina> they have one feature we may want in the latest release: "Allow Markdown or reST content in metadata fields other than summary"
16:02:36 <ChrisWarrick> they don’t claim to be jekyll, that is hyde but it does not work either
16:02:52 <ChrisWarrick> that feature is meaningless
16:03:20 <ChrisWarrick> our metadata fields are random strings, most of which does not even need formattingh
16:03:58 <ralsina> yes, we merge them way too late for that to matter
16:04:27 <ChrisWarrick> Also: thanks for indirectly exposing me to reveal.js (via the reveal theme), just made something with it and I love it.  finally sanity in presentations and no ugly powerpoint.
16:04:29 * ralsina goes back to the code-for-money-cave
16:04:44 <ralsina> that was not me, I think
16:04:53 <ralsina> or maybe yes, I may have purged the cache
16:06:16 <ChrisWarrick> I think you made the theme
16:06:27 <ralsina> yay me then? :-)
16:08:52 <ChrisWarrick> also, an excuse not to learn beamer
17:56:20 <KwBot> [nikola] shmilee closed issue #1826: nikola help auto, UnicodeEncodeError https://github.com/getnikola/nikola/issues/1826
18:38:17 <KwBot> [nikola] Kwpolska opened issue #1828: Bootstrap 3.3.5 released https://github.com/getnikola/nikola/issues/1828
18:38:17 <KwBot> [nikola] Kwpolska assigned issue #1828 to Kwpolska: Bootstrap 3.3.5 released https://github.com/getnikola/nikola/issues/1828
19:12:23 <ralsina> ChrisWarrick: in the "pelican is unexplainable" theme: https://github.com/getpelican/pelican/issues/1493#issuecomment-112505558
20:13:01 <erdgeist_> Yep, I'm glad I skipped over pelican after scrolling through the code
20:14:14 <ralsina> erdgeist_: well, nikola's code has some areas that look like manhattan in "Escape from NY"
20:14:28 <ralsina> post.py is a scary neighborhood
20:16:05 <erdgeist_> I plan on migrating a larger site with around 25 years of legacy-pages from a self written ruby cms to nikola
20:16:16 <ralsina> erdgeist_: whoa
20:16:23 <ralsina> erdgeist_: happy to help with that :-)
20:16:47 <erdgeist_> and the only thing that positively is not there is a calendar that supports recurring events :)
20:16:55 <ralsina> so far I think my site is probably oldest and I have only ... 15 years there
20:17:21 <ralsina> erdgeist_: I am interested in how to do calendar things in Nikola, but have no clear ideas
20:17:32 <ralsina> erdgeist_ so feel free to file issues if you do :-)
20:18:02 <erdgeist_> I hand wrote that as native ruby gem in C because the ical implementation in Ruby sucks big times
20:18:48 <erdgeist_> ralsina: Basically it's the web site of the largest hackers organization in Europe and we do have recurring events like radio shows and public lectures and so on
20:20:05 <erdgeist_> the query I implemented was something like "list all occurrences of all repeating/non-repeating events from a date newer than today and limit by X entries"
20:20:34 <erdgeist_> Main problem is of course that it breaks nikolas very efficient dependency management
20:23:51 <ralsina> erdgeist_: oh, but that's where JS saves us :-)
20:23:59 <ralsina> or server-side includes, or something like that
20:24:05 <erdgeist_> correct
20:24:17 <ralsina> erdgeist_: are you ok with loading those via JS? If yes, then it's a rather easy job
20:24:44 <ralsina> alternatively, we'd need a dynamic service that does that bit and we consume its output
20:25:44 <erdgeist_> Well, it's twofold. Creating ical-calendars with the powerful template engine would be cool, too :)
20:26:09 <erdgeist_> hmm, but they don't need to be dynamic
20:29:17 <erdgeist_> I think that javascript has the disadvantage that google does not really fancy it
20:29:37 <ralsina> erdgeist_: please put all your thought process in an issue
20:29:51 <ralsina> then we can discuss it in a persistent manner. Who knows :-)
20:30:38 <erdgeist_> sure will do
20:30:48 <ralsina> erdgeist_: we can always fall back to ... IFRAMES!
20:31:00 <erdgeist_> Btw, how is the web-frontend for nikola getting along? ;)
20:31:02 <ralsina> generate schedule html pages and then frame them in :-)
20:31:14 <ralsina> ChrisWarrick is the one doing it. I think it s awesome
20:33:33 <erdgeist_> I loved the addition of the new dependency detection that work well now with the post-list directive
20:33:45 <erdgeist_> Now I usually type "nikola build && nikola deploy"
20:33:54 <erdgeist_> maybe this is worth a short cut?
20:34:26 <erdgeist_> i.e. conditional deployment only if I broke nothing
20:37:10 <erdgeist_> Now, where I think of the calendar: It would also make a great "my first punk band" website ;) With all gigs and tour dates
20:39:51 <ralsina> a  nikold buildeploy? :-)
20:40:27 <ralsina> alias putonagig= nikola build && nikola deploy
20:45:37 <erdgeist_> Also I need to build permission management with git