Comments for Yngve's blog

Comment on Latexdiff and git by Making the diff-erence in using LaTeX – WeST Blog (University of Koblenz-Landau) | WeST Blog

Mon, 15 Apr 2013 14:00:35 +0000

[...] in the folder. You can get additional information in how to use git with latexdiff by reading the blog post of Yngve and the tex.stackexchange [...]

Comment on Tip of the day: partial git log by Darby

Darby — Thu, 04 Apr 2013 05:15:42 +0000

How can you get all BUT a certain folder?

Comment on Latexdiff and git by Vinicius

Vinicius — Sun, 31 Mar 2013 01:32:48 +0000

Great work!
Also, for brazilians or other accent-like languages with bibtex errors

“Warning–I didn’t find a database entry for …”

your .bib files cannot contain direct accents, e.g. “é”, “ó”, replace with “\’e”, “\’o”

Took me a half an hour to find out… =)

Comment on Latexdiff and git by dynetrekk

dynetrekk — Thu, 28 Mar 2013 13:56:11 +0000

It probably will under Cygwin, assuming you’ve got all those tools (sed, bash, pdflatex, bibtex, etc) on your %PATH%. Also, you will need to make an if/else clause replacing the “xdg-open” command with “cygstart”.

Comment on Latexdiff and git by Yngve I. Levinsen

Yngve I. Levinsen — Thu, 28 Mar 2013 12:56:38 +0000

This script is using extensively unix tools. On Windows I do not believe you have e.g. ‘pdflatex’ or ‘bibtex’ installed and available in the shell. Hence I do not believe it will work. If anyone feels like writing the script so it works also on Windows feel free to submit patches. I do not have a Windows machine available, nor the need to develop this script for Windows myself. Sorry.

Comment on Latexdiff and git by flwe

flwe — Tue, 26 Mar 2013 14:38:56 +0000

Hi, I have a real beginners question: How do I execute the “latexbatchdiff.sh”? Do I use the Windows Commandtool CMD or what else? The provided examples could not help. I have perl installed.

Comment on Get bug tracker for your gitorious repository by Ben Givens

Ben Givens — Fri, 22 Feb 2013 18:47:28 +0000

Hello,
I recently released a new open-source bug tracker that was funded via Kickstarter, and we are looking for people to try it out. I saw you wrote about bug trackers previously and wanted share our new app. It’s free and open source, we would love any feedback.
http://www.bugkick.com

If you want to share it with anyone, let me know and we’ll give you and your friends free pro accounts (normally $108 a year).

Best,
Ben

Comment on Hello World cmake+openmpi by Yngve I. Levinsen

Yngve I. Levinsen — Mon, 04 Feb 2013 13:37:15 +0000

Quite interesting, I also get a similar memory leak. However, I get precisely the same memory leak regardless of whether I use cmake to build or the wrappers. Are you sure the wrappers are from the same MPI version as the one cmake finds on your system? You can have several installed…

Edit: You might find more information about this issue here: http://www.open-mpi.org/faq/?category=debugging#valgrind_clean

Comment on Hello World cmake+openmpi by lumberJack

lumberJack — Mon, 04 Feb 2013 13:17:10 +0000

If i use your “# Require MPI for this project: ….. ” CMakeLists.txt, valgrind says by executing this simple program

int main()
{
MPI::Init();
MPI::Finalize();
return 0;
}

==8546== LEAK SUMMARY:
==8546== definitely lost: 22,215 bytes in 39 blocks
==8546== indirectly lost: 6,967 bytes in 28 blocks
==8546== possibly lost: 22,593 bytes in 598 blocks
==8546== still reachable: 116,620 bytes in 113 blocks
==8546== suppressed: 0 bytes in 0 blocks
==8546== Rerun with –leak-check=full to see details of leaked memory

If i use the MPI compiler wrappers, valgrind says:

==8583== LEAK SUMMARY:
==8583== definitely lost: 0 bytes in 0 blocks
==8583== indirectly lost: 0 bytes in 0 blocks
==8583== possibly lost: 0 bytes in 0 blocks
==8583== still reachable: 21,606 bytes in 1 blocks
==8583== suppressed: 0 bytes in 0 blocks
==8583== Rerun with –leak-check=full to see details of leaked memory

Whats going on?

Im using open MPI 1.6.3.

Comment on Latexdiff and git by Pål Ellingsen

Pål Ellingsen — Thu, 22 Nov 2012 09:45:48 +0000

I would agree that I didn’t state the problem well, so I’ll try again.
My setup is such that I have a main file, which includes several other files. I wanted to be able to compare changes for the main file and all of the included files in one, getting out one pdf with all the changes.
In order to do this I tried to call you script first with only my main file, this only gave me the changes in this file (as expected), I than called it with the main file, and ‘*.tex’, such that it would diff all my files, though this didn’t result in a pdf with all the changes.
I the looked at latexdiff, which takes the optional argument –flatten, which also takes the diff for the included files (note that in my latexdiff there is a bug, such that you can’t have commented includes in the main file). I set this in my -hgrc file as an option, though I didn’t work as the extdiff tool in hg creates an folder in tmp, which only holds the changed files, and therefore latexdiff couldn’t find all of the included files. I tried it both with and without your script.
My solution for this, is to instead of using ‘hg extdiff’ I use ‘hg archive’ into a folder, and then run latexdiff on that folder (which contains a copy of the repository at a given revision).
I don’t know if git has the same problem, but I know that in hg diff is optimised for speed and therefore doesn’t copy over unchanged files.

Hope this was a better explanation