Re: [Libreoffice] http://libreoffice.boldandbusted.com/ cppcheck report jobs stalled... no longer! :)
Hi again *, After a long hiatus, this service is back on the air. I swapped out the bad RAM for some good RAM, and hooray, we've got a fresh cppcheck report at http://libreoffice.boldandbusted.com/ . I also hacked in sortable.js for clickable, sortable column headings. My hope is that this is useful to you! There were discussions (with Julien and others) debating using either git master or released versions of cppcheck, but since this machine is stable now, I'll keep cppcheck on released versions (e.g. 1.49) until something really annoying pops up in the report that should be eliminated. I'm still on the hunt for some kind of easy script which makes a usable diff of HTML pages, to be used to highlight new or removed cppcheck findings with each run. If anyone has ideas in this vein, I'd love to hear them. :) I see the excellent Tinderbox work is going strong. If my report isn't really useful anymore due to work elsewhere, please let me know. Time moves on, and perhaps this kind of thing is no longer useful or wanted. If you have suggestions to make it easier or more useful, and they're not too hard/expensive, I'll do what I can to make it better. Anyway, Viva Libreoffice! :) Cheers, Jesse Adelman ilikelinux Consulting/Bold and Busted LLC http://www.ilikelinux.com/ http://www.boldandbusted.com/ Brisbane, CA P.S. FYI, the reports seem to take a bit longer to run - 8 hours or so. On 03/28/11 14:10, some...@boldandbusted.com wrote: Hi *. Sorry to say that it appears a hardware problem (bad RAM) has put a stop to cppcheck's 5 hour report runs that get pushed to http://libreoffice.boldandbusted.com/ . I'm RMA-ing the RAM today, and hopefully we'll see the replacements in a few weeks, if not sooner. Sorry for not writing sooner. The current report will stay available (the machine which does cppcheck runs is separate from the web server which presents the results). I hope it is still valuable as a reference until this problem is repaired. I'll write again to the list when I have an update for you on major changes to the status of this service. Cheers, Jesse Adelman ilikelinux Consulting/Bold and Busted LLC Brisbane, CA http://www.ilikelinux.com/ http://www.boldandbusted.com/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] http://libreoffice.boldandbusted.com/ cppcheck report jobs stalled
Hi *. Sorry to say that it appears a hardware problem (bad RAM) has put a stop to cppcheck's 5 hour report runs that get pushed to http://libreoffice.boldandbusted.com/ . I'm RMA-ing the RAM today, and hopefully we'll see the replacements in a few weeks, if not sooner. Sorry for not writing sooner. The current report will stay available (the machine which does cppcheck runs is separate from the web server which presents the results). I hope it is still valuable as a reference until this problem is repaired. I'll write again to the list when I have an update for you on major changes to the status of this service. Cheers, Jesse Adelman ilikelinux Consulting/Bold and Busted LLC Brisbane, CA http://www.ilikelinux.com/ http://www.boldandbusted.com/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] cppcheck report service updates
Howdy *, So, if you browse to http://libreoffice.boldandbusted.com/ to see the cppcheck run, you'll notice a few things: * Less CSS. * Sortable columns! Odd problems: * You may notice some blanks in the source code links, like this: http://libreoffice.boldandbusted.com/680.html#line-462 . I believe this is due to this error received from cppcheck, which I didn't notice in earlier versions of cppcheck: Bailing out from checking ./ure/sal/osl/os2/debug.c: Too many configurations. Recheck this file with --force if you want to check them all. I'll add --force for the next run and judge the impact on report run time. I hope that folks are still using this service and find it useful. Cheers, Jesse Adelman ilikelinux Consulting, a division of Bold and Busted LLC http://ilikelinux.com/ http://boldandbusted.com/ Brisbane, CA ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] cppcheck headers problem? (was 'Question about cppcheck unused private')
On 02/16/11 12:43, Caolán McNamara wrote: On Sat, 2011-02-12 at 13:26 +0100, Julien Nabet wrote: Hello With the last git version of cppcheck, I've got in the master branch writer/sw/source/ui/dbui this : [./dbmgr.cxx:222]: (style) Unused private function 'SwConnectionDisposedListener_Impl::disposing' I don't understand these errors and so how to correct them. If it's a false positive cppcheck, I don't understand why. So, this is basically one of a bunch of problems that cppcheck shows because it's not able to find all the headers and so it can't tell that the thing that dbmgr.cxx inherits from defines a public virtual void disposing(); so it hopes for the best and notices that the disposing here is in a private section and lets us know that from all cppcheck can tell this is a private method that isn't called. Reduced test-case attached if you want to report it. But this is poor stylistically anyway so probably best to just fix it in dbmgr.cxx by adding a public: before disposing and/or moving disposing after private: C. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice Hi Caolán, So cppcheck can't find the headers it needs? Is this a bug in cppcheck, or LO's construction of header file paths? And how many examples of cppcheck false positives due to this problem are present? Does a clear example of where cppcheck *should* find the headers but *doesn't* exist? Is there a way to prevent this particular problem for cppcheck? Cheers, Jesse Adelman Linux Systems Consultant http://ilikelinux.com/ http://www.boldandbusted.com/ Brisbane, CA USA ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] Fwd: Auto Reply: Now with extra cppcheck FRESHNESS
Please stop setting up autoreplies that reply to mailing lists... Dr. Frank Peters. :) ---BeginMessage--- I am currently travelling with limited access to email and will read your message when I return on Dec 16. Regards Frank Peters -- Dr. Frank Peters | Documentation and Learning Manager Phone: +49 40 23646500 Oracle Office GBU ORACLE Deutschland B.V. Co. KG | Nagelsweg 55 | 20097 Hamburg ORACLE Deutschland B.V. Co. KG Hauptverwaltung: Riesstr. 25, D-80992 München Registergericht: Amtsgericht München, HRA 95603 Komplementärin: ORACLE Deutschland Verwaltung B.V. Rijnzathe 6, 3454PV De Meern, Niederlande Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697 Geschäftsführer: Jürgen Kunz, Marcel van de Molen, Alexander van der Ven Oracle is committed to developing practices and products that help protect the environment ---End Message--- ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Now with extra cppcheck FRESHNESS
On 12/14/10 12:13, some...@boldandbusted.com wrote: Hi all, http://libreoffice.boldandbusted.com/ is running cppcheck 1.46. No segfaults so far. As much as folks want it to run the git version, the segfault party wasn't fun, sorry. Cheers, Jesse Adelman Bold and Busted LLC http://www.boldandbusted.com/ P.S. The current report has 1.45 listed as the cppcheck version. Ignore that; it is indeed output generated from 1.46. The next run or so should have that corrected. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice Just a FYI: With the new 1.46 version of cppcheck, the report generation takes around 4 hours to complete once the process starts. This is up from a little over 2 hours with 1.45. Dunno if that's a feature or a bug. :) I leave about 1-2 hours between runs so I can use the box for other things, so expect that new reports should be created and posted about every 6 hours. Cheers, Jesse Adelman Bold and Busted LLC http://www.boldandbusted.com/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] help.libreoffice.org MediaWiki DB snapshot to play with?
Hi, all. I read part of the thread LibreOffice WikiHelp and recognized that there are a large body of MediaWiki Extensions that might help. However, rather than ask to try it out on your systems, I'd like to try them on my own, against the MediaWiki database backing help.libreoffice.org. Wikipedia offers their MySQL gzipped dump snapshots, and I'm hoping that I can get a copy of yours. One Extension that has some promise is http://www.mediawiki.org/wiki/Extension:Hierarchy . I'd like to try it and see how easy, hard or impossible it would be, and if it could help to present the Help in a more chapter/book-like form. Oh, and having specific versions of MediaWiki software and any existing extensions would rock, so I can replicate the real site better. :) Cheers, Jesse Adelman Bold and Busted LLC Brisbane, CA USA http://www.boldandbusted.com/ Home of http://libreoffice.boldandbusted.com/; ;) ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] Fwd: Auto Reply: ... please un-subscribe this person
Uh, can you un-subscribe/filter this person until he returns or asks to re-subscribe? I got this auto reply directly after posting my previous message to the list... :/ He says he won't be back until the 15th... Thanks. This must be getting sent to everyone who posts? Or maybe I'm special. ---BeginMessage--- I'm currently not in my office and not reading any mail. Your mail has reached my inbox, and been placed in a queue, which I'll probably start processing on December, 15th, 2010. Due to the sheer amount of mails which this queue might contain by then, I may decide for some mails that they're worth being deleted without detailed reading. If the issue because of which you contacted me still requires my attention on December, 20th, 2010, please do not hesitate to re-send your mail then, if I did not yet reply. - Ich bin zur Zeit nicht im Büro und lese keinerlei Mails. Ihre Mail ist in meinem Eingangskorb angekommen, und wurde damit auf die zu-bearbeiten-Liste gesetzt, welche ich am 15. Dezember 2010 abzuarbeiten beginnen werde. Auf Grund der schieren Menge an bis zu diesem Zeitpunkt eingetroffenen Mails ist es möglich, dass ich entscheiden werde, dass Dinge, die bis dahin ohne meine Mitwirkung funktionierten, meiner Aufmerksameit nicht mehr bedürfen. Kurz: Es mag sein, dass ich einige Mails löschen werde, ohne sie im Detail zu lesen. Wenn das Anliegen, wegen dessen Sie mich kontaktiert haben, meine auch am 20. Dezember 2010 noch meine Aufmerksamkeit erfordert, zögern Sie bitte nicht, Ihre Mail dann erneut zu senden, falls ich noch nicht geantwortet habe. ---End Message--- ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] http://libreoffice.boldandbusted.com/ cppcheck report server problem
On 11/27/10 23:47, some...@boldandbusted.com wrote: Ugh. I was wonder why the report hadn't updated in a while, so I looked at dmesg, and... [769748.123672] cppcheck[3299]: segfault at bf12dff8 ip 080b6cb4 sp bf12dff0 error 6 in cppcheck[8048000+c4000] [770896.363343] cppcheck[6124]: segfault at bf12dff8 ip 080b6cb4 sp bf12dff0 error 6 in cppcheck[8048000+c4000] Yay. Well, it is the git version, and I feared that stuff would Just Break... :/ So, reports won't update until I figure out what went wrong. (But I really want to watch Stargate: Universe tonight...) Interestingly, these segfaults left the cppcheck controlling process alive, so fcron doesn't think it's dead. So, I'll kill that and read the entrails. Cheers, Jesse Adelman Bold and Busted LLC http://www.boldandbusted.com/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice OK, so bumping to the latest git cppcheck didn't help, it still segfaults. So, unfortunately, just to get updated reports against LO code, I'm reverting cppcheck to the 1.45 version until further notice. Yeah, there will be re-emergence of some false positives, but it's the best I can do right now. cppcheck does list that mid-December is their target for 1.46, so there's hope there, too. For reference, here's where it fails: 9417/11627 files checked 80% done Checking ./libs-gui/vcl/source/glyphs/graphite_serverfont.cxx... Checking ./libs-gui/vcl/source/glyphs/graphite_serverfont.cxx: WNT... 9418/11627 files checked 81% done Checking ./libs-gui/vcl/source/glyphs/graphite_textsrc.cxx... 9419/11627 files checked 81% done Checking ./libs-gui/vcl/source/helper/canvasbitmap.cxx... then segfault-zombie-process-land. Cheers, Jesse Adelman Bold and Busted LLC http://www.boldandbusted.com/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] http://libreoffice.boldandbusted.com/ cppcheck report server problem
On 11/28/10 03:00, Julien Nabet wrote: Hello Jesse, I git updated cppcheck and it succeeded to scan the whole vcl directory but above all, i noticed this in the logs : ser...@serval:~/cppcheck/cppcheck$ git log commit 00da0adf25b122fcfb7a2f892497f1785b01f43a Author: Daniel Marjamäki daniel...@spray.se Date: Sun Nov 28 11:48:06 2010 +0100 Fixed #2236 (False positive: Assignment to itself) commit ea405d95c6cf9b56e52d43192b4b1bdbe1d10f46 Author: Daniel Marjamäki daniel...@spray.se Date: Sun Nov 28 07:35:42 2010 +0100 *Fixed #2241 (Segfault checking a file)* If you have time, after Stargate Universe of course :-), could you try to cppcheck the vcl directory for test ? Julien. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice Hi Julien, I'll give it a shot once the currently running cppcheck cron job succeeds. Thanks for spot-testing! :) Cheers, Jesse Adelman Bold and Busted LLC San Francisco, CA http://www.boldandbusted.com/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] question about cppcheck for libreoffice.boldandbusted.com
Hi Julien, It is the git version of cppchcek, which I checkout every few days via Portage. If you find false positives, you should let the cppcheck folks know, and they'll remove it or otherwise correct it (or tell you that it isn't a false positive ;) ). Which tracker are you referencing? cppcheck's bugtracker or LO's? I'll bump cppcheck today. Cheers, Jesse Adelman Bold and Busted LLC http://www.boldandbusted.com/ On Sat, 27 Nov 2010 22:44 +0100, Julien Nabet serval2...@yahoo.fr wrote: Hello, libreoffice.boldandbusted.com is a great idea, but what's the version cppcheck used for libreoffice.boldandbusted.com ? I ask this because cppcheck has sometimes false positives. For example, lately i had opened a tracker (#2235: false Resource leak) and today it's corrected. It could be useful to know the date of the last update at the beginning of the report. Julien. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] question about cppcheck for libreoffice.boldandbusted.com
I've added some code to my report generation scripts to insert the cppcheck git sha1 hash in the title of the report. I had to do a bit of shell trickery to get Gentoo's Portage to give me the hash of the installed cppcheck. It is in the middle of a report run now, so probably in 4-6 hours from this writing will the git sha1 hash show up. I'd love it if the cppcheck-htmlreport was made more flexible (the title/header is getting mighty ugly and ungainly, and I just *love* the HTML in the TITLE tag...), but when/if I have time I'll see if I can hack that to work better and add options. Cheers, Jesse Adelman Bold and Busted LLC http://www.boldandbusted.com/ On Sat, 27 Nov 2010 14:02 -0800, some...@boldandbusted.com wrote: Hi Julien, It is the git version of cppchcek, which I checkout every few days via Portage. If you find false positives, you should let the cppcheck folks know, and they'll remove it or otherwise correct it (or tell you that it isn't a false positive ;) ). Which tracker are you referencing? cppcheck's bugtracker or LO's? I'll bump cppcheck today. Cheers, Jesse Adelman Bold and Busted LLC http://www.boldandbusted.com/ On Sat, 27 Nov 2010 22:44 +0100, Julien Nabet serval2...@yahoo.fr wrote: Hello, libreoffice.boldandbusted.com is a great idea, but what's the version cppcheck used for libreoffice.boldandbusted.com ? I ask this because cppcheck has sometimes false positives. For example, lately i had opened a tracker (#2235: false Resource leak) and today it's corrected. It could be useful to know the date of the last update at the beginning of the report. Julien. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] [EasyHacks] cppcheck of entire code at http://libreoffice.boldandbusted.com/
Howdy. To help with EasyHack cppcheck cleanliness, I've set up automated reporting on http://libreoffice.boldandbusted.com/ . Here will live a report generated from a complete scan of the entire LO codebase, generated every 4-6 hours, against a fresh update from the various git repos with LO code. Right now, the report contains both style and error cppcheck issue types (via --enable=all passed to cppcheck). Later, I may make a front page which leads into distinct reports for each cppcheck issue types. (I haven't done this yet because that would require a new full code scan, which takes about 2-3 hours, just to create each report type; I'm hoping to figure out a way that minimizes generation time.) This was done with the advice and help of hoonteke (who got me on this path), dtardon, kohei_, caolan and shm_get on #libreoffice (and others who looked at my alpha reports over the weekend). I think there might have even been some bug squashing already as a result of this report. Yay! My next improvements may be: * Implement some sort of HTML/XML visual diff * Archive reports over time, and provide some way of viewing them via HTTP * Tailor the CSS for LO's purposes * Run code scans and reports on cppcheck's development branch to help cppcheck's devs to improve their software So, this will be two EasyHacks I've helped with! :) Being a Linux SysAdmin/Architect, my expertise is with systems, not large application coding, so I'm happy to help in these sorts of areas. More janitorial work, rather than corner office work that you real coders are doing. ;) Cheers, Jesse Adelman Bold and Busted LLC http://www.boldandbusted.com/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] [EasyHacks] cppcheck of entire code at http://libreoffice.boldandbusted.com/
I should also caution you that, at least for my Firefox, this page may make your browser creak under its weight. Another reason to crush bugs! :) Cheers, Jesse Adelman Bold and Busted LLC Brisbane, CA USA On Sun, 21 Nov 2010 19:38 -0800, some...@boldandbusted.com wrote: Howdy. To help with EasyHack cppcheck cleanliness, I've set up automated reporting on http://libreoffice.boldandbusted.com/ . Here will live a report generated from a complete scan of the entire LO codebase, generated every 4-6 hours, against a fresh update from the various git repos with LO code. Right now, the report contains both style and error cppcheck issue types (via --enable=all passed to cppcheck). Later, I may make a front page which leads into distinct reports for each cppcheck issue types. (I haven't done this yet because that would require a new full code scan, which takes about 2-3 hours, just to create each report type; I'm hoping to figure out a way that minimizes generation time.) This was done with the advice and help of hoonteke (who got me on this path), dtardon, kohei_, caolan and shm_get on #libreoffice (and others who looked at my alpha reports over the weekend). I think there might have even been some bug squashing already as a result of this report. Yay! My next improvements may be: * Implement some sort of HTML/XML visual diff * Archive reports over time, and provide some way of viewing them via HTTP * Tailor the CSS for LO's purposes * Run code scans and reports on cppcheck's development branch to help cppcheck's devs to improve their software So, this will be two EasyHacks I've helped with! :) Being a Linux SysAdmin/Architect, my expertise is with systems, not large application coding, so I'm happy to help in these sorts of areas. More janitorial work, rather than corner office work that you real coders are doing. ;) Cheers, Jesse Adelman Bold and Busted LLC http://www.boldandbusted.com/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] [EasyHacks] cppcheck of entire code at http://libreoffice.boldandbusted.com/
On Sun, 21 Nov 2010 19:38 -0800, some...@boldandbusted.com wrote: Howdy. To help with EasyHack cppcheck cleanliness, I've set up automated reporting on http://libreoffice.boldandbusted.com/ . Here will live a report generated from a complete scan of the entire LO codebase, generated every 4-6 hours, against a fresh update from the various git repos with LO code. Right now, the report contains both style and error cppcheck issue types (via --enable=all passed to cppcheck). Later, I may make a front page which leads into distinct reports for each cppcheck issue types. (I haven't done this yet because that would require a new full code scan, which takes about 2-3 hours, just to create each report type; I'm hoping to figure out a way that minimizes generation time.) This was done with the advice and help of hoonteke (who got me on this path), dtardon, kohei_, caolan and shm_get on #libreoffice (and others who looked at my alpha reports over the weekend). I think there might have even been some bug squashing already as a result of this report. Yay! My next improvements may be: * Implement some sort of HTML/XML visual diff * Archive reports over time, and provide some way of viewing them via HTTP * Tailor the CSS for LO's purposes * Run code scans and reports on cppcheck's development branch to help cppcheck's devs to improve their software So, this will be two EasyHacks I've helped with! :) Being a Linux SysAdmin/Architect, my expertise is with systems, not large application coding, so I'm happy to help in these sorts of areas. More janitorial work, rather than corner office work that you real coders are doing. ;) Cheers, Jesse Adelman Bold and Busted LLC http://www.boldandbusted.com/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice On Sun, 21 Nov 2010 20:38 -0800, some...@boldandbusted.com wrote: I should also caution you that, at least for my Firefox, this page may make your browser creak under its weight. Another reason to crush bugs! :) Cheers, Jesse Adelman Bold and Busted LLC Brisbane, CA USA Also, one other request. By request of folks in #cppcheck, please note in your commit messages (or mailing list message) that you've fixed bugs based on the output of the cppcheck reports I've put up (or even your own cppcheck runs). They have a hunter's gallery there of bugs fixed with cppcheck. It's at http://sourceforge.net/apps/mediawiki/cppcheck/index.php?title=Found_bugs , and I'm sure LibreOffice would be a fine addition to their display. I'll occasionally make a search through the mailing list message bodies to see if cppcheck shows up, and pass on the good news to them. It's only fair that we pay them back for their work! :) Cheers, Jesse Adelman Bold and Busted LLC Brisbane, CA USA http://www.boldandbusted.com/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] [SCRIPT, EASYHACK] add-modelines, a script to add modelines to source files
On Tue, 12 Oct 2010 12:37 +0200, Sebastian Spaeth sebast...@sspaeth.de wrote: On 2010-10-11, some...@boldandbusted.com wrote: However, the script as I last sent it (version 0.7) works to cover the original EasyHack spec. I ran v07 on the various git repos and attached the resulting git patches at https://bugs.freedesktop.org/show_bug.cgi?id=30794 Please someone (I assigned to Kendy as per IRC discussion, so that would be him :-)) apply these patches. The script is fine, but my /bin/sh did not like set -o posix so I made it run as /bin/bash. Also the -z option would not add new modelines but really only overwrite existing ones spewing out lots of mv... file not found errors which puzzled me a lot. Otherwise it's an excellent piece of work :-). Please apply before the patches get old :). Sebastian Hi Sebastian, Sweet! Glad I could help. A couple questions: * What shell environment were you running the script under which gave you the -z option sadness? * Did you commit my original unchanged version to git, then commit your changes, or only commit the version with your changes (awk removal, etc.) and not the original I posted? (I'd like to know that my original version, warts and all, was committed for posterity. :) ) * Yah, sorry about the extra spaces. I actually meant to remove that. I had that in so I could be sure that I wasn't damaging other data. * If you see that set -o posix thing again, just remove it to run under /bin/sh. The set -o posix actually makes Bash behave like /bin/sh. I didn't know that /bin/sh would barf on it, so I'll consider this command a debugging command. Cheers, Jesse Adelman San Francisco, CA Bold and Busted LLC http://www.boldandbusted.com/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Wiki developper page
On Mon, 11 Oct 2010 20:43 -0500, Norbert Thiebaud nthieb...@gmail.com wrote: Ok so I don't have a blog... but We have a brand new wiki... So I started a page, intended to help prospective developper to get acquainted with the build and with git... This is quite fresh in my mind... since I've learn that in the past few days. But I may be wrong, so a reviewed by more senior developpers (and anyone else for that matter) is welcome. http://wiki.documentfoundation.org/Developper_Corner Norbert ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice Norbert, Yay, MediaWiki! :) How can I add info about my submissions (add-modelines)? Will the wiki write-access be restricted to devs with commit rights? Cheers, Jesse Adelman Bold and Busted LLC San Francisco, CA http://www.boldandbusted.com/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Wiki developper page
On Mon, 11 Oct 2010 19:10 -0700, some...@boldandbusted.com wrote: On Mon, 11 Oct 2010 20:43 -0500, Norbert Thiebaud nthieb...@gmail.com wrote: Ok so I don't have a blog... but We have a brand new wiki... So I started a page, intended to help prospective developper to get acquainted with the build and with git... This is quite fresh in my mind... since I've learn that in the past few days. But I may be wrong, so a reviewed by more senior developpers (and anyone else for that matter) is welcome. http://wiki.documentfoundation.org/Developper_Corner Norbert ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice Norbert, Yay, MediaWiki! :) How can I add info about my submissions (add-modelines)? Will the wiki write-access be restricted to devs with commit rights? Cheers, Jesse Adelman Bold and Busted LLC San Francisco, CA http://www.boldandbusted.com/ ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice Ah, nevermind. I'm signing up for an account now... :) ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
