[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lilypond-auto] Issue 2935 in lilypond: Issue 2935: is_main_input_ s
From: |
lilypond |
Subject: |
Re: [Lilypond-auto] Issue 2935 in lilypond: Issue 2935: is_main_input_ should only be set by \maininput command |
Date: |
Tue, 30 Oct 2012 11:16:25 +0000 |
Updates:
Summary: Issue 2935: is_main_input_ should only be set by \maininput
command
Status: Fixed
Labels: -Patch-review Fixed_2_17_6
Comment #8 on issue 2935 by address@hidden: Issue 2935: is_main_input_ should
only be set by \maininput command
http://code.google.com/p/lilypond/issues/detail?id=2935
Pushed to staging as
commit 7cee59f148669079a68177090fb36e29b2e51f66
Author: David Kastrup <address@hidden>
Date: Tue Oct 30 11:17:22 2012 +0100
Issue 2935: is_main_input_ should only be set by \maininput command
is_main_input reflects the state of being in the reign of the main
input file as opposed to the init file, which corresponds to a drop of
privileges. This drop of privileges is explicitly signified with
\maininput
and should not otherwise be tampered with in order not to restrict the
init file's capabilities. There should be no way to arrive at a lexer
from within LilyPond or Scheme without is_main_input_ set unless one
already has one such lexer to start with.
I'll be offline for a number of hours now, but I don't expect problems.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [Lilypond-auto] Issue 2935 in lilypond: Issue 2935: is_main_input_ should only be set by \maininput command,
lilypond <=