Perl 6 - the future is here, just unevenly distributed

IRC log for #darcs, 2015-04-27

| Channels | #darcs index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:00 povman joined #darcs
00:14 c74d joined #darcs
01:01 fr33domlover joined #darcs
01:22 k-u joined #darcs
01:46 ilbot3 joined #darcs
01:46 Topic for #darcs is now http://darcs.net/ | logs: http://irclog.perlgeek.de/darcs/ | darcs 2.10.0 is out http://darcs.net/Releases/2.10
02:47 c74d joined #darcs
03:54 byorgey joined #darcs
05:36 c74d joined #darcs
07:09 IbnFirnas joined #darcs
07:09 IbnFirnas joined #darcs
07:46 fr33domlover joined #darcs
08:00 vikraman joined #darcs
08:02 vikraman joined #darcs
08:02 vikraman joined #darcs
08:04 vikraman joined #darcs
08:08 vikraman joined #darcs
09:32 povman joined #darcs
11:05 povman joined #darcs
11:18 mizu_no_oto joined #darcs
12:27 povman joined #darcs
13:04 gh_ joined #darcs
13:05 gh_ hi
17:06 sm hi gh_
17:07 sm that's weird, you can't access hub.darcs.net :8901 ? (hiding 8901 urls from search bots) It works for me right now
17:09 gh_ sm, hi,  I realized that maybe the university firewall was blocking the port :/
17:10 sm ah.. any ports that would work better ?
17:15 sm I'm wondering why the latest build fails to render that patch, http://hub.darcs.net/simon/darcsden-gh/patch/20150422181943-3c3f9
17:15 gh_ sm, the https port?
17:16 sm we don't have any https support yet IIRC
17:17 gh_ yeah so the port is free?
17:17 sm oh I get you
17:18 sm well, which number do you mean ?
17:18 sm 443 ?
17:19 sm I think I won't use that one
17:19 gh_ 443
17:19 gh_ well for the time being..
17:19 sm well ok what the heck, just briefly
17:19 sm building
17:19 gh_ or you could just upload screenshots
17:19 gh_ of that instance
17:22 sm ok 443 won't work, I have other servers using it
17:23 gh_ or can you show me the bug as a screenshot? you can upload to imgur for instance
17:24 gh_ sm,  between both patches I'm more confident about the max-width one anyway
17:24 sm I'd rather get you access to the test server so you can verify things yourself
17:24 sm I'm not seeing any change yet, I might not have deployed right
17:25 sm the path from a simple css fix to deployment has become overgrown and thorny eh <HACK> <HACK>
17:25 gh_ :)
17:28 sm gh_: do you have a remote machine you could ssh tunnel through, or might there be a list of open ports in your university IT docs ?
17:30 sm how about 992 (try now)
17:31 gh_ sm, smtp is open (25)
17:31 sm I'm certainly using *that* :)
17:31 sm 992 is blocked ?
17:31 gh_ sm, it's blocked :/
17:32 sm how about 110 ?
17:33 sm oh, firefox doesn't like that one
17:33 gh_ now it's firefox who blocks it
17:33 sm right
17:34 sm gh_: unless you find a workable port I guess I'll leave it on 8901 and when you get a chance you can test your fix from somewhere else
17:35 sm I suppose I could also set up a separate hostname
17:36 gh_ sm, yes agreed. the best would be for me to test it locally in fact.
17:36 gh_ sm, in any case the max-width patch alone would be quite useful and trustable to deploy IMO
17:37 sm yes, I just want to see it in action
17:37 sm testing locally is useful too, certainly. HEAD is relatively easy to install with ghc 7.8 or 7.10 now
17:37 sm see http://hub.darcs.net/simon/darcsden/issue/127
17:38 gh_ on the link I passed you privately the max-width setting is quite useful.
17:38 sm gh_: what effect will your change have ?
17:39 gh_ I'm using hub.darcs.net for some lecture notes written in markdown
17:39 sm oh I can look
17:39 gh_ sm, readability . long lines are difficult to read
17:39 sm for me that page looks the same on the test instance
17:39 gh_ sm, d'oh
17:40 gh_ sm, when I change the css manually in firefox I get the desired effect. isn't there a cache issue going one?
17:40 gh_ on*
17:40 sm quite possibly
17:40 sm I don't yet know what you mean about long lines, can you point to an example
17:41 sm if I know what to expect, I'll debug further
17:41 gh_ "If your text is too long – if a line of text is too long the visitor’s eye will have a hard time focusing on the text. This is because the length makes it difficult to get an idea of where the line starts and ends. Furthermore it can be difficult to continue from the correct line in large blocks of text." (from, eg, http://www.benshoemate.com/2013/08/02/optimum-web-readability-max-and-min-width-for-page-text/#sthash.8Pqe2O9J.dpuf)
17:42 gh_ i can upload screenshots in fact
17:42 sm that works
17:47 sm gh_: thanks, I see what you did
17:48 sm am I right in thinkin you changed an upstream bootstrap file, making bootstrap upgrades a bit harder ?
17:49 sm would it be better to override in local style file ?
17:50 gh_ sm, the patch modifies main.css
17:50 gh_ sm, that's the only place where I saw the markdown class
17:50 sm huh, must have misread
17:50 gh_ sm, the other patch does modify another files, for that one I'm less sure about what's going one
17:50 gh_ *on
17:52 sm "make pre and code style more readable" makes some change to bootstrap.min.css, that one I'm still unclear on
17:52 gh_ sm, those are the same changes as the ones of bootstrap.css
17:52 sm oh right
17:53 gh_ sm, I'm not sure why the .min.css is versioned, actually..
17:53 sm so this patch is changing the bootstrap styles, and will be lost next time I upgrade bootstrap
17:53 sm both of those files come from bootstrap
17:53 gh_ oh
17:56 sm style changes are so subjective, they need preview and discussion. I'll figure out how to get your change previewable on 8901. Most efficient of all will be if other devs like you can demo changes on your own instance
18:00 sm ah I see.. a hardcoded assets path
18:04 mal`` joined #darcs
18:17 sm and the manually updated combined.css hub is using
18:26 gh_ sm, to find the files I just looked for css files in darcsden's repo and the css debugger of firefox
18:26 gh_ I thought that combined.css was generated automatically..
18:27 sprang joined #darcs
18:28 sm gh_: it's not, unless I'm confused
18:29 gh_ sm, ouch. then it should probably appear in darcsden's source repo
18:29 sm yes, it was a quick hack for hub. Needs to be automated
18:30 sm found the final problem: some local change (for hub ?) removed the http port from css urls
18:30 sm test server is showing css changes now
18:32 gh_ \o/
18:32 * sm has a lie-down
18:39 sm more next time o/
18:40 gh_ sm, thanks for investigating this, see you!
18:40 sm thanks gh_
19:03 povman joined #darcs
19:17 gh_ talking about darcsden, we're having one GSoC project this year: http://darcs.net/GSoC/2015-Darcsden !
20:06 Riastradh joined #darcs
20:06 sm gh_:great!
20:30 povman joined #darcs
21:08 c74d joined #darcs
21:31 Heffalump sm: I've uploaded ssh 0.3.1, that should work with 7.10 - thanks a lot for the fixes and chasing up pseudomacros
22:05 sprang joined #darcs
22:39 alexei_ joined #darcs
23:14 sprang joined #darcs
23:33 sm Heffalump: great!
23:40 sm Heffalump: I forgot to mention, there are also ghc 7.10 updates in http://hub.darcs.net/simon/redis
23:48 sm I wonder what should be done with the darcsden-ssh and darcsden-post-hook executables
23:49 sm they complicate dependencies, a bit, and I imagine the majority of darcsden installers won't care about them
23:50 sm I don't think they can be optionally built based on a flag - the best one could do is stub them out and skip the dependencies
23:51 sm should they become separate packages ?

| Channels | #darcs index | Today | | Search | Google Search | Plain-Text | summary