Showing git commit hash (or other revision number) - Revision history

Lemzwerg: New category

2025-11-21T23:30:05Z

New category

← Older revision		Revision as of 23:30, 21 November 2025
Line 35:		Line 35:
	[[Category:Really simple]]		[[Category:Really simple]]
	[[Category:Text]]		[[Category:Text]]
	[[Category:Scheme]][[Category:Snippet]]		[[Category:Scheme]]
			[[Category:Snippet]]

Lemzwerg at 23:00, 21 November 2025

2025-11-21T23:00:11Z

← Older revision		Revision as of 23:00, 21 November 2025
Line 35:		Line 35:
	[[Category:Really simple]]		[[Category:Really simple]]
	[[Category:Text]]		[[Category:Text]]
	[[Category:Scheme]]		[[Category:Scheme]][[Category:Snippet]]

Jean Abou Samra: Replace version="2.24.0" with version="2.24" now that the LilyWiki extension supports auto-selecting the latest release in a stable series

2025-11-16T18:53:51Z

Replace version="2.24.0" with version="2.24" now that the LilyWiki extension supports auto-selecting the latest release in a stable series

← Older revision		Revision as of 18:53, 16 November 2025
Line 5:		Line 5:
	Please ignore the displayed output of the snippet. It's there because all snippets need to produce output. The interesting stuff is in the file itself.		Please ignore the displayed output of the snippet. It's there because all snippets need to produce output. The interesting stuff is in the file itself.

	<lilypond version="2.24.0">		<lilypond version="2.24">
	%% http://lsr.di.unimi.it/LSR/Item?id=567		%% http://lsr.di.unimi.it/LSR/Item?id=567

Jean Abou Samra: Import snippet from LSR

2025-10-26T22:43:43Z

Import snippet from LSR

New page

Git is a distributed version-control system. Lilypond itself is developed using Git. It's useful to keep your .ly files in a Git repository: it ensures you can get back old versions of your files if you take a piece in the wrong direction, it makes it easy to share your work with others and incorporate each other's changes, and it lets you look back to see when you made particular changes. But if you're printing out your Lilypond parts, it's easy to get confused about which is the latest version, or what source a print-out was generated from.

The usual workaround is to use the date, but this only tells you when the PDF was generated, not when the source was written. This snippet is some trivial Scheme code that declares a <code>\commit</code> variable containing the current HEAD of the Git repository. (It's simple to change it to show the hash of the file, or the date of the HEAD commit, or the revision number from Subversion, CVS, or whatever else you use. It just runs a command and expects the output to be one line.)

Please ignore the displayed output of the snippet. It's there because all snippets need to produce output. The interesting stuff is in the file itself.

<lilypond version="2.24.0">
%% http://lsr.di.unimi.it/LSR/Item?id=567

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% This is the code. Paste it into a file you can \include. It's commented out
% because it won't run in the LSR's sandbox.

%{
#(use-modules (ice-9 popen))
#(use-modules (ice-9 rdelim))
commit =
#(let* ((port (open-pipe* OPEN_READ "git" "show" "--pretty=format:%H" "--quiet"))
(str (read-line port)))
(close-pipe port)
str)
%}

% and I use that command like this:
%\header {
% tagline = \commit
%}

% This is just to give LSR something to compile. It doesn't like empty files.

{ c''4 c'' c'' c'' }
</lilypond>

[[Category:Scheme]]
[[Category:Really simple]]
[[Category:Text]]
[[Category:Scheme]]