00:50.41 | *** join/#maemo-ssu FIQ|n900 (~FIQ@unaffiliated/fiq) |
02:30.01 | *** join/#maemo-ssu BCMM (~BCMM@unaffiliated/bcmm) |
03:51.27 | *** join/#maemo-ssu amiconn_ (amiconn@rockbox/developer/amiconn) |
04:04.02 | *** join/#maemo-ssu DocScrutinizer06 (~HaleBopp@openmoko/engineers/joerg) |
05:18.10 | *** join/#maemo-ssu jade (~jade@Jade.broker.freenet6.net) |
05:18.10 | *** join/#maemo-ssu jade (~jade@unaffiliated/jade) |
07:04.13 | *** join/#maemo-ssu dhbiker (~dhbiker@APN-123-32-135-gprs.simobil.net) |
07:31.19 | *** join/#maemo-ssu LaoLang_cool (~LaoLang_c@221.226.175.139) |
07:48.44 | *** join/#maemo-ssu sourav (~user@1.38.26.118) |
08:00.11 | *** part/#maemo-ssu sourav (~user@1.38.26.118) |
10:02.13 | *** join/#maemo-ssu NIN101 (~NIN@p5DD28567.dip0.t-ipconnect.de) |
11:18.19 | *** join/#maemo-ssu Estel_ (~Estel@178235127192.piaseczno.vectranet.pl) |
11:18.19 | *** join/#maemo-ssu Estel_ (~Estel@Maemo/community/contributor/Estel-) |
11:19.17 | *** join/#maemo-ssu jonwil (~jonwil@27-33-137-199.static.tpgi.com.au) |
11:19.41 | jonwil | ~seen pali |
11:19.44 | infobot | pali <~pali@Maemo/community/contributor/Pali> was last seen on IRC in channel #maemo-ssu, 3d 23h 59m 32s ago, saying: 'freemangordon, do you know state of portrait keyboard?'. |
11:28.07 | *** join/#maemo-ssu jon_y (~enforcer@2002:7c52:3c94::7c52:3c94) |
11:29.30 | *** join/#maemo-ssu freemangordon (~freemango@130-204-50-168.2074221835.ddns.cablebg.net) |
11:56.02 | *** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu) |
12:04.41 | *** join/#maemo-ssu FIQ|n900 (~FIQ@unaffiliated/fiq) |
12:14.26 | *** join/#maemo-ssu arcean (~Arcean@aafq143.neoplus.adsl.tpnet.pl) |
12:50.57 | *** join/#maemo-ssu toxaris (~toxaris@s83-180-246-172.cust.tele2.se) |
12:57.39 | chem|st | happy armageddon2.0 |
12:58.36 | FIQ|n900 | chem|st: too late, it happened 11 days ago ;) |
12:59.54 | chem|st | we are 70 years ahead because some king wanted to have his birthday on a century shift... |
13:00.17 | chem|st | what was 1.0 if not the maya one? |
13:01.17 | freemangordon | chem|st: happy http://www.youtube.com/watch?v=iJVztkKHUW0 |
13:01.19 | FIQ|n900 | lol @ birthday |
13:01.26 | FIQ|n900 | chem|st: y2k |
13:03.08 | chem|st | well y2k was some nerd telling that his server clock will reset... to 1970.. |
13:03.14 | FIQ|n900 | 3.0 will be y2k38 |
13:03.33 | FIQ|n900 | chem|st: heh |
13:03.34 | chem|st | still fun :) |
13:03.57 | chem|st | nvm |
13:08.46 | FIQ|n900 | hmm |
13:09.29 | FIQ|n900 | is there any way to, in case of a boot issue @ maemo, drop to a shell instead of simply rebooting (which wont really solve stuff)? |
13:11.51 | kerio | FIQ|n900: automatically? eeeh |
13:12.22 | FIQ|n900 | guess not |
13:12.25 | kerio | i suppose that you could start a shell if the bootreason is a certain one |
13:39.14 | *** join/#maemo-ssu LaoLang_cool (~LaoLang_c@221.226.175.139) |
14:04.03 | *** join/#maemo-ssu FredrIQ|n900 (~FIQ@unaffiliated/fiq) |
14:15.07 | *** join/#maemo-ssu kolp (~quassel@212.255.21.247) |
14:28.13 | *** join/#maemo-ssu arcean_ (~Arcean@aael45.neoplus.adsl.tpnet.pl) |
15:18.32 | *** join/#maemo-ssu amiconn (amiconn@rockbox/developer/amiconn) |
15:23.57 | DocScrutinizer05 | I guess we already fixed that issue for H-D respawn triggering reboot |
15:24.47 | DocScrutinizer05 | for the very reason of "won't really solve stuff" |
15:24.59 | DocScrutinizer05 | I been the one pushing it |
15:25.39 | DocScrutinizer05 | we should do same for other reboot-on-respawn configs as well |
15:25.58 | DocScrutinizer05 | e.g friggin bme |
15:26.05 | *** join/#maemo-ssu FIQ|n900 (~FIQ@unaffiliated/fiq) |
15:26.15 | DocScrutinizer05 | or browserd |
15:27.37 | DocScrutinizer05 | or TADAAAA we could redefine general semantics of dsmetool -t to dsmetool -f |
15:28.18 | freemangordon | do we have the sources? |
15:28.20 | DocScrutinizer05 | since dsmetool -t and dsmetool -r are basically brainfuck |
15:28.31 | DocScrutinizer05 | wrapper script, freemangordon |
15:28.39 | freemangordon | hmmm |
15:29.02 | freemangordon | could work, but is hackish |
15:29.14 | DocScrutinizer05 | sure, I love hackish |
15:29.19 | DocScrutinizer05 | it's tasty |
15:29.27 | DocScrutinizer05 | or was that haeggis |
15:29.32 | freemangordon | :) |
15:29.43 | freemangordon | ham and eggs? |
15:30.13 | DocScrutinizer05 | ~wiki heaggis |
15:30.21 | DocScrutinizer05 | hmm |
15:30.47 | DocScrutinizer05 | ~wiki haggis |
15:31.04 | merlin1991 | is back from the lands of no internet |
15:31.08 | merlin1991 | anybody miss me? :D |
15:31.15 | freemangordon | who were you? |
15:31.17 | DocScrutinizer05 | you bet we did |
15:31.23 | freemangordon | :D |
15:31.40 | freemangordon | merlin1991: seems we 'll need zlib on gitorious |
15:31.52 | freemangordon | if you don't mind |
15:32.14 | merlin1991 | did you find a real adavantage? |
15:32.35 | merlin1991 | or is still not clear if it's faster :D |
15:32.36 | DocScrutinizer05 | >>As the 2001 English edition of the Larousse Gastronomique puts it, "Although its description is not immediately appealing, haggis has an excellent nutty texture and delicious savoury flavour".<< |
15:32.41 | freemangordon | luf said there is. i'll benchmark when there are source |
15:32.50 | freemangordon | *s |
15:33.25 | merlin1991 | https://gitorious.org/community-ssu/zlib |
15:33.33 | freemangordon | merlin1991: BTW in case you've missed it NEONized libpng is ~ 33% faster on decoding |
15:33.51 | merlin1991 | that IS a speedup :) |
15:33.57 | DocScrutinizer05 | yup |
15:34.02 | freemangordon | yeah :) |
15:34.11 | merlin1991 | how far did you have to go with the versions to get that? or did you just backport a patch? |
15:34.16 | DocScrutinizer05 | any 'issues' known? like instabilities or sth? |
15:34.30 | freemangordon | last 1.2 libpng with backported patch |
15:34.36 | freemangordon | DocScrutinizer05: none so far |
15:34.45 | freemangordon | 1.2.49 |
15:35.21 | freemangordon | merlin1991: BTW microb is using 1.213 or smthng, we should upgrade that too |
15:35.23 | DocScrutinizer05 | so I guess it's save to assume Nokia just didn't have that patch available when they built fremantle |
15:35.32 | freemangordon | yep |
15:35.50 | freemangordon | it is pretty new, a couple of months old |
15:35.54 | DocScrutinizer05 | then I don't think it's a big deal to slowly and carefully introduce it to CSSU |
15:36.29 | freemangordon | merlin1991: or even better - add apng suppor to libpng and compile microb with system libpng and libzlib |
15:36.44 | merlin1991 | apng? |
15:37.01 | freemangordon | ~wiki apng |
15:37.01 | merlin1991 | freemangordon: the mircob libpng was witihn the microb-engine sources right? |
15:37.07 | freemangordon | yep |
15:37.38 | freemangordon | the same for libzlib |
15:38.22 | freemangordon | apng is an extension to png made by mozilla. patches exist for every libpng version |
15:40.22 | freemangordon | though luf said it is better to do the stuf step by step, i'd rather do it in one step - libpng+APNG+NEON, zlib+NEON and microb compiled with the former |
15:40.36 | freemangordon | libs |
15:41.26 | merlin1991 | btw is microb statically linked against the lib or is it just using a private version? |
15:41.42 | freemangordon | statically linked against its private version |
15:41.46 | freemangordon | aiui |
15:42.22 | merlin1991 | wonders if there was another reason for that besides having a fixed library version |
15:42.34 | freemangordon | apng |
15:42.48 | merlin1991 | well they could have simply added that to the system lib |
15:43.07 | freemangordon | and there are some comments for zlib "don;t use system zlib because some problems with linking" |
15:43.41 | freemangordon | but I was able to build it with system zlib yesterday, NP at all |
15:43.57 | freemangordon | (with 4.7.2, didn;t try 4.2.1) |
15:45.01 | DocScrutinizer05 | fekkin wikipedia pictores on top of HTML text |
15:45.03 | freemangordon | merlin1991: maybe we should check if there is anu patch for libpng in microb |
15:45.38 | merlin1991 | freemangordon: we should that for sure |
15:46.46 | *** join/#maemo-ssu FIQ|n900 (~FIQ@unaffiliated/fiq) |
15:48.40 | DocScrutinizer05 | I guess infobot using lynx or sth to render the wikipedia HTML, and there the URL tags like {{other uses}} show up on top for such pages. I'll pester TimRiker to filter out {{.*}} shit |
15:51.10 | DocScrutinizer05 | particularly filter out {{other uses}} and {{Infobox.*}} (the latter not particularly easy for embedded other {{BS-links}}) |
15:53.51 | DocScrutinizer05 | could somebody come up with a counting RE that matches anny number of nested {} pairs? |
15:55.06 | freemangordon | merlin1991: can't find patches to libpng in microb |
15:57.39 | DocScrutinizer05 | hmmmm s/{{(^[{{]){{^[}}]*}}(^[}})}}/{{\1\2}}/ |
15:58.04 | DocScrutinizer05 | RE clearly are write-once/read-never |
15:58.31 | DocScrutinizer05 | ugh |
15:59.23 | DocScrutinizer05 | hmmmm s/{{(^[{{]*){{^[}}]*}}(^[}}]*)}}/{{\1\2}}/ |
15:59.53 | DocScrutinizer05 | or sth like that |
16:08.15 | DocScrutinizer05 | I.E repeatedly eliminate the most inner pair of {{.*}} until nothing left over |
16:10.23 | kerio | DocScrutinizer05: REs can't parse nested parentheses |
16:11.13 | kerio | you need pushdown automata for that |
16:15.24 | *** join/#maemo-ssu luf (~luf@ip-89-102-208-114.net.upcbroadband.cz) |
16:22.34 | luf | merlin1991: We're glad you returned from universe :D |
16:23.00 | luf | BTW I need patched libxml2 first :) Can you accept the merge request? |
16:23.23 | luf | freemangordon: come on I wrote you where you can find the sources. |
16:23.43 | luf | merlin1991.at/~luf/zlib/source/ |
16:23.54 | DocScrutinizer05 | kerio: but you can recursively solve nested stuff from inside out |
16:24.21 | luf | And I'm not sure it's using neon as no problem with tests in sb ... |
16:24.26 | DocScrutinizer05 | since RE can detect a pattern inside another pattern |
16:25.19 | DocScrutinizer05 | or rather, an RE can match a {} pair that does NOT contain another { inside |
16:26.10 | DocScrutinizer05 | which is clearly the definition of most inner nesting level, and once you eliminate that, you get the next outer nesting level as most inner one and can eliminate it as well |
16:26.35 | kerio | yeah but it's not just a RE then |
16:26.42 | DocScrutinizer05 | repeat until you got a non-nested structure |
16:27.09 | DocScrutinizer05 | repeated application of same RE is a known feature though |
16:28.25 | DocScrutinizer05 | usually you mark those as /g |
16:28.39 | kerio | it's not "applied repeatedly", is it |
16:28.45 | kerio | it's "don't stop at the first match" |
16:28.50 | DocScrutinizer05 | not sure |
16:29.01 | kerio | so at best you can remove all the lowest layers |
16:29.18 | DocScrutinizer05 | you might be right for /g, however shell expansion is recursive for example |
16:30.17 | DocScrutinizer05 | if $x expands to "$y" and $y expands to A then shell expansion of $x will result in A |
16:31.37 | DocScrutinizer05 | so it's a known principle to do repeated expansion/transformation until the result doesn't change anymore |
16:34.33 | luf | merlin1991: are again in non-internet universe? |
16:34.54 | merlin1991 | no worries, I'll do the merge request :D |
16:36.43 | luf | :D |
16:48.02 | *** join/#maemo-ssu Martix (~martix@ip-62-245-106-78.net.upcbroadband.cz) |
16:53.01 | DocScrutinizer05 | kerio: http://en.wikipedia.org/wiki/Regular_expression#Perl-derived_regular_expressions >>Other examples of functionality possible with Perl [...] and recursive patterns<< |
16:53.27 | kerio | when you add backtracking you get out of the realm of REs |
16:53.40 | DocScrutinizer05 | since infobot is coded in perl afaik, I'd think this issue I came from will be solvable with PERL-RE |
16:55.04 | DocScrutinizer05 | and actually no, backtracking is an indispensable component of solving RE greedy RE |
16:55.59 | DocScrutinizer05 | greedy is default for RE |
16:57.06 | DocScrutinizer05 | in fact backtracking is what makes RE slow and resource-hungry |
16:58.47 | kerio | oh sorry, the issue is that if you add backreferences |
16:58.57 | kerio | then it's not really a RE anymore, in the formal sense |
16:59.36 | kerio | also, REs aren't slow and resource-hungry if you know the theory: http://swtch.com/~rsc/regexp/regexp1.html |
17:00.08 | DocScrutinizer05 | how does knowing the theory change runtime behaviour? ;-P |
17:00.28 | kerio | because once you know the theory, you go "oh, this is a piece of crap", and use a different RE engine |
17:01.05 | DocScrutinizer05 | o.O |
17:01.16 | DocScrutinizer05 | lost me |
17:03.14 | kerio | (yes, you also need to do some changes, you don't just have to study to magically make your existing programs run faster) |
17:07.08 | *** join/#maemo-ssu toxaris (~toxaris@s83-180-246-172.cust.tele2.se) |
17:13.37 | *** join/#maemo-ssu arcean (~Arcean@aacu118.neoplus.adsl.tpnet.pl) |
17:15.13 | DocScrutinizer05 | anyway I referred to real existing RE implementations, not to the mere theory of clean RE |
17:15.41 | DocScrutinizer05 | and I don't give a **** about perle RE non-clean |
17:17.05 | DocScrutinizer05 | I just pondered how to remove that {{naggedinagg-shit}} from "~wiki whatever" |
17:17.33 | DocScrutinizer05 | since |
17:17.36 | DocScrutinizer05 | ~wiki apng |
17:18.06 | DocScrutinizer05 | is basically useless due to {{infobox bla bla bla}} |
17:18.32 | DocScrutinizer05 | and infobot *is* written in perl |
17:32.35 | *** join/#maemo-ssu dhbiker (~dhbiker@95.87.145.172) |
17:42.21 | kerio | look for the first {{, then go from there and start counting {{ and }}s until you get back to zero |
18:00.39 | DocScrutinizer05 | kerio: I'm not senile enough so I had forgotten this design pattern, but it's obviously not simple to integrate into the otherwise probably RE-based infobot wiki HTML parser |
18:04.49 | *** join/#maemo-ssu kolp (~quassel@brmn-4dbcd297.pool.mediaWays.net) |
18:06.48 | DocScrutinizer05 | while a repeated non-greedy s/{{.*{{.*}}.*}}/{{}}/ would reduce nesting to a bare "{{}}", then remove that by s/{{}}// |
18:12.41 | DocScrutinizer05 | as an additional benefit it won't remove simple plain non-nested {{links}} |
18:13.55 | DocScrutinizer05 | and anticipating a max nesting depth you could even unroll the recursion and get away with like 15 lines of simple RE substitutions |
18:17.42 | DocScrutinizer05 | s/HTML parser/lynx plugin/ |
18:25.48 | kerio | it's not a lynx plugin, that's just the wiki syntax |
18:26.09 | kerio | getting the actual html page (from the mobile version of the site, for instance) would be better |
18:33.47 | *** join/#maemo-ssu kolp (~quassel@brmn-4dbcd297.pool.mediaWays.net) |
18:35.31 | *** join/#maemo-ssu FIQ|n900 (~FIQ@unaffiliated/fiq) |
19:09.38 | *** join/#maemo-ssu Wulfe (~wulfe@74.61.223.51) |
19:12.22 | *** part/#maemo-ssu Wulfe (~wulfe@74.61.223.51) |
19:26.18 | *** join/#maemo-ssu Martix (~martix@ip-62-245-106-78.net.upcbroadband.cz) |
20:14.56 | *** join/#maemo-ssu FredrIQ|n900 (~FIQ@unaffiliated/fiq) |
20:24.36 | *** join/#maemo-ssu neilita (4de34a21@gateway/web/freenode/ip.77.227.74.33) |
20:33.16 | *** part/#maemo-ssu neilita (4de34a21@gateway/web/freenode/ip.77.227.74.33) |
21:04.42 | *** join/#maemo-ssu kolp (~quassel@212.255.21.247) |
21:05.15 | DocScrutinizer05 | ooh, you say it gets the edit page? |
21:05.44 | kerio | yep |
21:05.46 | DocScrutinizer05 | indeed |
21:06.02 | DocScrutinizer05 | meh |
21:06.52 | DocScrutinizer05 | yeah, getting the rendered HTML would be much better, though probably magnitudes more demanding regarding code to add to infobot |
21:06.59 | kerio | DocScrutinizer05: are you kidding me |
21:07.00 | kerio | this is perl |
21:07.16 | kerio | there's probably a library in cpan that does exactly what we want |
21:07.30 | DocScrutinizer05 | hehe good point |
21:07.41 | DocScrutinizer05 | toldya no clue about perl here |
21:07.52 | kerio | WWW::Wikipedia - Automated interface to the Wikipedia |
21:08.10 | DocScrutinizer05 | :-o |
21:10.30 | kerio | and entries have a text() method that tries to return the summary, or returns the fulltext if there's no summary |
21:10.57 | DocScrutinizer05 | so what's that? a perl library? |
21:11.00 | kerio | yep |
21:11.02 | kerio | in cpan |
21:11.04 | DocScrutinizer05 | :-D |
21:11.20 | DocScrutinizer05 | friggin smartass stuff |
21:14.01 | DocScrutinizer05 | ~wiki ibm |
21:14.36 | DocScrutinizer05 | look ^^^ - useless |
21:14.42 | kerio | indeed |
21:17.08 | DocScrutinizer05 | seems we should simply grep "}}(.*)==History==" and echo the inner match, unless no match at all when we should display same we do now |
21:17.25 | *** join/#maemo-ssu nox- (noident@freebsd/developer/nox) |
21:17.56 | DocScrutinizer05 | here this would result in >>'''International Business Machines Corporation''' ({{New York Stock Exchange|IBM}}), or '''IBM''', is an American [[Multinational corporation|multinational]] [[technology]] and [[Consultant|consulting]] corporation, with headquarters in [[Armonk, New York|Armonk]], New York, United States. IBM manufactures and markets com...<< |
21:18.26 | DocScrutinizer05 | still friggin ugly |
21:20.11 | DocScrutinizer05 | this WWW::Wikipedia thing sounds mad useful |
21:20.20 | kerio | it outputs html though |
21:20.25 | DocScrutinizer05 | :-/ |
21:20.29 | kerio | but of course, parsing and cleaning html is easy |
21:20.39 | kerio | for instance, HTML::Parser |
21:20.47 | DocScrutinizer05 | mhm |
21:21.00 | kerio | perl is a crappy language, if you must use it at least make use of cpan |
21:21.27 | DocScrutinizer05 | don't you feel an irresistible urge to code a proof of concept perl sniplet? ;-) |
21:21.39 | kerio | nah, i can't do perl |
21:22.50 | kerio | the syntax is awful, the object model is ugly and counterintuitive |
21:22.56 | kerio | and there's a ton of magic |
21:27.52 | FIQ|n900 | and there's always 10 methods of doing things |
21:28.17 | FIQ|n900 | the good way, the decent way, the bad way, the really bad way, the ... |
21:28.28 | FIQ|n900 | oh also perl is ok |
21:28.48 | FIQ|n900 | as by existing it gave me a working IPS patcher on n900 :D |
21:29.50 | kerio | PERL - it's good cuz it exists |
21:30.04 | FIQ|n900 | kerio: well |
21:30.14 | FIQ|n900 | I can't say anything good of it |
21:30.14 | FIQ|n900 | or bad |
21:30.25 | FIQ|n900 | because I've never looked at the syntax, etc |
21:31.27 | DocScrutinizer05 | wtf IPS catcher? |
21:31.34 | DocScrutinizer05 | err patcher |
21:31.39 | FIQ|n900 | catcher lol |
21:31.47 | FIQ|n900 | IPS is a file format |
21:31.54 | DocScrutinizer05 | mhm |
21:32.01 | DocScrutinizer05 | ~wtf ips |
21:32.05 | FIQ|n900 | using for patching files (only use I've seen is rom patching) |
21:32.14 | FIQ|n900 | think romhacks |
21:32.20 | DocScrutinizer05 | mhm |
21:32.25 | kerio | a binary diff format, popular with emulators for some reason |
21:32.30 | FIQ|n900 | yeah |
21:32.39 | FIQ|n900 | exactly :p |
21:32.40 | DocScrutinizer05 | binary diff? sounds friggin useful |
21:32.45 | kerio | nah, it's crap |
21:32.57 | DocScrutinizer05 | :-/ |
21:33.05 | kerio | it's used for hysterical raisins |
21:33.31 | FIQ|n900 | i've not looked into the format so I only care if it works or not :p |
21:33.39 | DocScrutinizer05 | pretty much wants a useful binary diff/patch format. jdiff aka jojo diff might be exactly that, but... jury still out on that one |
21:33.54 | DocScrutinizer05 | the poor raisins |
21:34.37 | DocScrutinizer05 | I looked into the diff, and it been.... binary :-o |
21:35.09 | DocScrutinizer05 | wtf is the use of a diff when you can't read the output? |
21:35.26 | DocScrutinizer05 | of course it's meant to feed it to jpatch |
21:35.36 | FIQ|n900 | also IIRC ips has some kind of size limitation |
21:35.46 | DocScrutinizer05 | but still I want it to be human legible |
21:36.09 | FIQ|n900 | because of what I've heard, the mother 3 translation project romhack couldn't use it so they developed their own format instead |
21:36.25 | FIQ|n900 | so I doubt ips is that good |
21:36.34 | FIQ|n900 | but it works, so.. :p |
21:37.15 | kerio | you can only patch up to 2mb or something |
21:37.27 | FIQ|n900 | hmm ok |
21:37.41 | kerio | i mean MB ofc |
21:37.45 | FIQ|n900 | yeah |
21:37.52 | FIQ|n900 | not millibits :D |
21:38.06 | kerio | it's either 2MB or 16MB |
21:38.24 | kerio | i'm not sure if it's in bits or bytes |
21:38.34 | kerio | but the address of the data to change is 3 bytes |
21:38.39 | kerio | which is fairly ridiculous |
21:38.51 | FIQ|n900 | 3 bytes |
21:39.03 | kerio | 24 bits of information isn't shit |
21:39.26 | FIQ|n900 | so no patching >16MB stuff |
21:40.12 | kerio | hahaha, and you can't patch at address 0x454f46 |
21:40.19 | kerio | because that's "EOF" and it's the end of the IPS file |
21:40.42 | kerio | yeah, it's 16MB |
21:40.54 | kerio | well, 16M - 1 B |
21:40.56 | FIQ|n900 | kerio: brilliant |
21:41.13 | FIQ|n900 | @ 0x454f46 limitation |
21:43.07 | DocScrutinizer05 | dreams of <0Xaddr>:DEL <0Xend-addr>; <0Xaddr>:INS<0Xlength><byte>[<byte>...]; ----:OFFSET <0Xoffsset> <0Xaddr>[,<0Xaddr>...] |
21:44.20 | DocScrutinizer05 | first cuts out bytes, 2nd inserts bytes, 3rd adds an offset to a list of absolute addr location contents |
21:44.49 | DocScrutinizer05 | would make a pretty useful binary diff format |
21:46.20 | DocScrutinizer05 | maybe even add <0Xaddr>:INSfrombuffer <num-of-buffer>, where buffer is a stack filled with last snippets from DEL |
21:47.05 | kerio | DocScrutinizer05: how big are address and length? |
21:47.06 | DocScrutinizer05 | so you could swap |
21:47.14 | DocScrutinizer05 | arbitrary |
21:47.28 | kerio | ok, how do i figure out when they end? |
21:47.56 | kerio | unless you actually have a "<0X" then the number written in ascii then ">" |
21:48.06 | FIQ|n900 | lol |
21:48.11 | DocScrutinizer05 | ooh, between <0Xlength> and <byte> there's a space missing |
21:48.35 | DocScrutinizer05 | otherwise there's : as delimiter |
21:50.30 | DocScrutinizer05 | semantics of <byte><byte><byte> not sufficient for <0Xlength> is repeat and fill |
21:52.04 | DocScrutinizer05 | obviously nothing forbids arbitrary unambiguous base for <length>, for <addr> I don't think allowing base-10 integers would meake much sense but it doesn't hurt either |
21:53.00 | DocScrutinizer05 | in '<0Xaddr>:DEL <0Xend-addr>;' the both addr are first and last byte to cut |
21:53.37 | DocScrutinizer05 | for INS first byte inserted is on the given addr, not after |
21:54.26 | kerio | should CSSU ship the fmtxd modification? |
21:54.38 | DocScrutinizer05 | writing the patch binary for that format looks quite simple, the diff binary gets a tad more tricky if it shall act smart |
21:55.45 | DocScrutinizer05 | kerio: such highly philosophical questions on a day as lame as this one... |
21:56.06 | kerio | a lame day? |
21:56.11 | kerio | it's america's 2013th birthday! |
21:56.13 | kerio | http://i.imgur.com/6bjq7.jpg |
21:56.21 | DocScrutinizer05 | sure, half the world suffers from hangover |
21:56.42 | kerio | well, it still fits, considering we're talking about binary diff formats |
21:56.57 | DocScrutinizer05 | indeed |
21:57.00 | kerio | but you're right, friends don't let friends drink and write specs for binary diffs |
21:57.17 | DocScrutinizer05 | :-D |
21:57.33 | DocScrutinizer05 | I kept pretty sober yesterday |
21:57.46 | kerio | i don't even drink \_o_/ |
21:58.09 | DocScrutinizer05 | o.O how that? |
21:58.27 | kerio | i don't like the taste of alcohol |
21:58.28 | FIQ|n900 | neither do I |
21:58.44 | DocScrutinizer05 | geeks |
21:58.46 | DocScrutinizer05 | ;-P |
21:58.51 | kerio | which is fairly awesome actually, because otherwise i'm pretty sure i'd be an alcoholic |
21:59.39 | FIQ|n900 | :p |
22:00.18 | DocScrutinizer05 | idly wonders if awk... |
22:00.29 | FIQ|n900 | awk binary patching? |
22:00.37 | DocScrutinizer05 | sed is clearly too line oriented |
22:00.46 | FIQ|n900 | super ed |
22:00.47 | DocScrutinizer05 | FIQ|n900: *nod* |
22:01.13 | FIQ|n900 | (I know what sed is, just not what the s part of it means) |
22:01.35 | DocScrutinizer05 | dunno if awk could get configured to use one-byte "lines" |
22:01.48 | DocScrutinizer05 | serial afaik |
22:01.52 | DocScrutinizer05 | or stream |
22:02.28 | DocScrutinizer05 | since it basically doesn't do any skip-back on input |
22:03.08 | DocScrutinizer05 | so movin last line of sourcefile to the head of destination file is a tad cimbersome with sed |
22:03.25 | DocScrutinizer05 | cumber* |
22:03.51 | DocScrutinizer05 | unlike ed where you could actually do that |
22:04.15 | DocScrutinizer05 | hmmm, ed |
22:10.25 | *** join/#maemo-ssu macmaN (~chezburge@138.167.190.90.dyn.estpak.ee) |
22:11.36 | DocScrutinizer05 | I wish there was a hex_ed which doesn't work on lines but byte adresses, and not displays raw text but hex reprentation |
22:12.06 | FIQ|n900 | make it! |
22:12.20 | DocScrutinizer05 | already pondering it |
22:12.25 | DocScrutinizer05 | can't be hard |
22:13.43 | DocScrutinizer05 | read in from <file> to buffer assumes/fakes a \n after very byte, and the most basic print command converts each "char" to a 2char hex representation |
22:16.20 | jon_y | DocScrutinizer05: speaking of \n, here's the perl bq2k query script |
22:16.24 | jon_y | http://paste.debian.net/220910/ |
22:16.37 | DocScrutinizer05 | :-) |
22:16.57 | DocScrutinizer05 | I'll add it to my host, if you allow |
22:17.13 | jon_y | host? |
22:18.15 | jon_y | well, just take it, it is your script |
22:18.45 | DocScrutinizer05 | I'd like to add your (C) to the header however |
22:19.11 | jon_y | oh, sure, thanks |
22:24.37 | kerio | it should be 27x00 then |
22:26.59 | DocScrutinizer05 | jon_y: what author name shall I use for your (c)? |
22:31.19 | *** join/#maemo-ssu FIQ|n900 (~FIQ@unaffiliated/fiq) |
22:35.09 | DocScrutinizer05 | hmm, hope that's ok: http://maemo.cloud-7.de/maemo5/usr/local/sbin/bq27k-detail-perl |
23:15.35 | *** join/#maemo-ssu Sc0rpius (~naikel@190.79.197.57) |
23:18.07 | kerio | freemangordon: have you noticed a regression with whatever is responsible for phone notifications since a bit ago? |
23:31.16 | DocScrutinizer05 | phone notifications? |
23:32.44 | DocScrutinizer05 | could it be that rotation stuff got way more laggy for dialer in forced portrait mode, since last (2) update(s) of CSSU-T? |
23:33.27 | DocScrutinizer05 | (dialer is the only thing in portrait mode on my IroN900, always been) |
23:33.38 | kerio | nah, i'm talking about hildon-home taking up 100% of cpu |
23:33.52 | DocScrutinizer05 | ouch |
23:33.58 | kerio | and hildon-desktop locking up when you try to access the tasknav |
23:34.07 | kerio | possibly because of ^ |
23:34.18 | DocScrutinizer05 | sure |
23:34.31 | kerio | but i couldn't even pull up the power key menu |
23:34.44 | DocScrutinizer05 | o.O |
23:34.54 | DocScrutinizer05 | and that's all the time? |
23:35.08 | kerio | i've had a slowdown and a lockup in two separate occasions |
23:35.23 | kerio | both after i didn't answer a call |
23:35.29 | kerio | (left it ring, didn't hang up) |
23:35.31 | DocScrutinizer05 | :nod: |
23:36.22 | DocScrutinizer05 | I always thought that's due to recaller writing a new file and tracker going mad in indexing, when call gets finished |
23:37.48 | DocScrutinizer05 | but since last update which for me been basically 2 in 1, it feels a lot more laggy on start of ringing, with rotating dialer to portrait mode. It takes like 5..10s now, while former lag was only ~1s |
23:39.13 | DocScrutinizer05 | it might be a singular event, maybe caused by HAM or whatever still active in background |
23:39.34 | DocScrutinizer05 | maybe rsync backup was active |
23:40.09 | DocScrutinizer05 | anyway it sucked, and I hope it's not a regression in latest (2) update(s) |
23:40.25 | kerio | as a sidenote: is it normal that i don't get a name for a number in multiple contacts? |
23:50.52 | *** join/#maemo-ssu Sc0rpius (~naikel@190.79.197.57) |
23:52.43 | DocScrutinizer05 | alas yes |
23:52.46 | arcean | DocScrutinizer05: rotation should be slightly faster with the latest h-d |
23:53.15 | DocScrutinizer05 | arcean: then I give it the benefit of doubt until it happens again |
23:53.39 | DocScrutinizer05 | who knows what's going on in this little phone all the time ;-D |
23:54.05 | DocScrutinizer05 | might actually been HAM still active |
23:54.24 | DocScrutinizer05 | and we all know HAM brings *everything* to a grinding halt |
23:54.26 | arcean | yeah, sometimes strange things happens |
23:55.27 | DocScrutinizer05 | kerio: the resolving of number->name is not very smart, actually it sucks donkeyballs |
23:56.05 | DocScrutinizer05 | since it doesn't tolerate any small differences in number to match |
23:56.31 | DocScrutinizer05 | and also fails completely when same number is in multiple contacts |
23:56.42 | kerio | i kinda like the fact that if a number is associated to multiple contacts, it doesn't just choose one at random |
23:57.31 | DocScrutinizer05 | I'd prefer some unambiguous priority thing, like maybe wildcards in numbers or sth |
23:58.17 | DocScrutinizer05 | or a dedicated numerical priority field |
23:59.11 | DocScrutinizer05 | or a simple selector popping up when same number gets added to a second (third...) contact, to select which one is primary contact now |
23:59.41 | kerio | foreign keys without enforcing will end up in a giant mess |
23:59.48 | kerio | *enforcement |