Re: Code formatter

[using cc-mode for automatically formatting C++ code of lilypond] >> IIRC, you mentioned this before; I think it's to do with (your) >> emacs expecting a colon at the end of the macro (which isn't >> strictly necessary). > > D'oh. I mean semicolon of course. :) In case we are going to automatic

Re: [PATCH] Allow nested properties to be set with \tweak

> Please review this patch: > > http://codereview.appspot.com/152127/show Very nice! Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Code formatter

Graham Percival wrote Saturday, November 14, 2009 12:10 AM On Sat, Nov 14, 2009 at 12:03:52AM +, Neil Puttock wrote: 2009/11/13 Graham Percival : > Oh, and there's lots of > MAKE_SCHEME_CALLBACK (Axis_group_interface, print, 1) > -SCM > + SCM My emacs doesn't do this. :) Joy of joys..

Re: anybody know apache? (dir structure of docs)

On Thu, Nov 12, 2009 at 11:06:54PM +0100, Reinhold Kainhofer wrote: > Here's the updated snippet for the .htaccess file: Thanks! Evidently Jan has already added that to the web server. (please bear with me for this question; I know I could answer it myself by spending between 10 and 60 minutes r

Re: [PATCH] Allow nested properties to be set with \tweak

On Fri, Nov 13, 2009 at 9:41 PM, Neil Puttock wrote: > Hi everybody, > > Please review this patch: > > http://codereview.appspot.com/152127/show > Shouldnt this be something recursive? I thought properties could nest beyond one level. -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all

Re: Code formatter

On Sat, Nov 14, 2009 at 12:03:52AM +, Neil Puttock wrote: > 2009/11/13 Graham Percival : > > > Oh, and there's lots of > >  MAKE_SCHEME_CALLBACK (Axis_group_interface, print, 1) > > -SCM > > +  SCM > > My emacs doesn't do this. :) Joy of joys... gperc...@sapphire:~$ emacs --version GNU Emacs

Re: Code formatter

2009/11/14 Neil Puttock : > IIRC, you mentioned this before; I think it's to do with (your) emacs > expecting a colon at the end of the macro (which isn't strictly > necessary). D'oh. I mean semicolon of course. :) ___ lilypond-devel mailing list lil

Re: Code formatter

2009/11/13 Graham Percival : > Oh, and there's lots of >  MAKE_SCHEME_CALLBACK (Axis_group_interface, print, 1) > -SCM > +  SCM My emacs doesn't do this. :) IIRC, you mentioned this before; I think it's to do with (your) emacs expecting a colon at the end of the macro (which isn't strictly neces

Re: Code formatter

On Fri, Nov 13, 2009 at 04:52:48PM -0700, Carl Sorensen wrote: > On 11/13/09 4:42 PM, "Graham Percival" wrote: > > > I'm amused that formatting everything in lily/*.cc with emacs > > produces a 127 Kb diff. > > Actually, that doesn't sound too bad to me, given the amount of code in > lily/*.cc a

Re: Code formatter

On 11/13/09 4:42 PM, "Graham Percival" wrote: > I'm amused that formatting everything in lily/*.cc with emacs > produces a 127 Kb diff. Actually, that doesn't sound too bad to me, given the amount of code in lily/*.cc and the lack of janitorial work we've had on the code. Thanks, Carl __

Re: Code formatter

On 11/13/09 4:24 PM, "Ian Hulin" wrote: > Hi Carl and list, > > Carl Sorensen wrote: >> >> >> On 11/13/09 9:59 AM, "Trevor Daniels" wrote: >> >>> >>> Chris Snyder wrote Friday, November 13, 2009 4:35 PM Graham Percival wrote: > I know that you're thinking "this is ridiculous", b

Re: Code formatter

I'm amused that formatting everything in lily/*.cc with emacs produces a 127 Kb diff. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Code formatter

On Fri, Nov 13, 2009 at 11:24:15PM +, Ian Hulin wrote: > Hi Carl and list, > > Carl Sorensen wrote: >> >> Do whatever emacs does. > > In which case we need to understand, note and detail "whatever emacs > does" in the CG, so users of other editors can set their environment up > not to get into

[PATCH] Allow nested properties to be set with \tweak

Hi everybody, Please review this patch: http://codereview.appspot.com/152127/show Cheers, Neil ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Code formatter

On 11/13/09 4:36 PM, "Neil Puttock" wrote: > 2009/11/13 Graham Percival : > >> Would it be worth adapting _ as an alternative to spaces inside >> illustrations inside comments, just to avoid this problem? >> Stating that the code style is "whatever emacs does, as long as >> you manually rever

Re: Code formatter

2009/11/13 Graham Percival : > Would it be worth adapting _ as an alternative to spaces inside > illustrations inside comments, just to avoid this problem? > Stating that the code style is "whatever emacs does, as long as > you manually revert its formatting in areas X Y and Z" is getting > really

Re: Code formatter

On Fri, Nov 13, 2009 at 07:46:59PM +, Neil Puttock wrote: > 2009/11/13 Graham Percival : > > > If you could choose one such example, and add it somewhere to the > > CG similar to this: > > http://lilypond.org/doc/v2.13/Documentation/contributor/Sectioning-commands > > (bottom of the page) > >

Re: Code formatter

Hi Carl and list, Carl Sorensen wrote: On 11/13/09 9:59 AM, "Trevor Daniels" wrote: Chris Snyder wrote Friday, November 13, 2009 4:35 PM Graham Percival wrote: I know that you're thinking "this is ridiculous", but unless somebody does it, newbies will continue to face this difficulty. Th

Re: Issue #768 - chord repetition shortcut: patch for review

Hi David, OTOH, something like { 8-. -^ }*2 is not doable with the q approach. Of course it is: \repeat unfold 2 { 8-. q-^ } Cheers, Kieren. ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-de

Re: Make doc failure

On Fri, Nov 13, 2009 at 09:36:44PM +, Neil Puttock wrote: > > I guess I could test this tomorrow. > > Doesn't work for me unfortunately: > > WARNING: Unable to find node 'Scheme tutorial' in book learning. > cp /home/neil/lilypond/Documentation/css/*.css out-www/contributor/ > cp /home/neil/l

Re: Make doc failure

2009/11/13 Graham Percival : > I guess I could test this tomorrow. Doesn't work for me unfortunately: WARNING: Unable to find node 'Scheme tutorial' in book learning. cp /home/neil/lilypond/Documentation/css/*.css out-www/contributor/ cp /home/neil/lilypond/Documentation/css/*.css out-www/notati

Re: Make doc failure

On Fri, Nov 13, 2009 at 10:08:36PM +0100, Matthias Kilian wrote: > On Fri, Nov 13, 2009 at 08:31:34PM +, Carl Sorensen wrote: > > @@ -146,8 +146,8 @@ local-WWW-1: $(OUT_TEXINFO_MANUALS) > > $(PDF_FILES) info > > > > local-WWW-2: txt-to-html $(OUT_HTML_FILES) $(DEEP_HTML_FILES) > > $(source

Re: Make doc failure

On Fri, Nov 13, 2009 at 08:31:34PM +, Carl Sorensen wrote: > @@ -146,8 +146,8 @@ local-WWW-1: $(OUT_TEXINFO_MANUALS) > $(PDF_FILES) info > > local-WWW-2: txt-to-html $(OUT_HTML_FILES) $(DEEP_HTML_FILES) > $(source-links) $(OM > # fix links from other manuals to general > - fi

Re: Make doc failure

raham Percival percival-music.ca> writes: > > On Thu, Oct 22, 2009 at 07:34:18AM -0600, Carl Sorensen wrote: > > # fix links from other manuals to general > > find ./out-www -name "*.html" | xargs sed -i 's/\.\.\/general\//\.\.\//' > > sed: 1: "./out-www/All.html": invalid command code . > > M

Re: Fixes issue 786, "Extenders in lyrics stop prematurely if a single underscore is found."

Hi Chris, Thanks for working on these issues. I've applied your patch to master. Cheers, Neil http://codereview.appspot.com/150067 ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Code formatter

On 11/13/09 12:39 PM, "Graham Percival" wrote: > On Fri, Nov 13, 2009 at 08:18:04PM +0100, Nicolas Sceaux wrote: >> Le 13 nov. 2009 à 20:01, Werner LEMBERG a écrit : >> >>> Then, for goodness' sake, why not write a small elisp program to use >>> Emacs in batch mode on the command line (yes, t

Re: Code formatter

2009/11/13 Graham Percival : > If you could choose one such example, and add it somewhere to the > CG similar to this: > http://lilypond.org/doc/v2.13/Documentation/contributor/Sectioning-commands > (bottom of the page) > > that would be awesome. It's already there in section 8.5.5 (you added it

Re: Code formatter

On 11/13/09 12:35 PM, "Graham Percival" wrote: > On Fri, Nov 13, 2009 at 11:23:55AM -0700, Carl Sorensen wrote: >> Jan believes that code formatting standards should be no more restrictive >> than the GNU standards. > > By the way, if somebody has a compelling argument why we should > differ

Re: Code formatter

On Fri, Nov 13, 2009 at 08:18:04PM +0100, Nicolas Sceaux wrote: > Le 13 nov. 2009 à 20:01, Werner LEMBERG a écrit : > > > Then, for goodness' sake, why not write a small elisp program to use > > Emacs in batch mode on the command line (yes, this is possible) to > > format one or more files? Emacs

Re: Code formatter

On Fri, Nov 13, 2009 at 11:23:55AM -0700, Carl Sorensen wrote: > Jan believes that code formatting standards should be no more restrictive > than the GNU standards. By the way, if somebody has a compelling argument why we should differ from the GNU standards, I'm willing to go up against Jan. But

Re: Code formatter

On Fri, Nov 13, 2009 at 01:17:43PM -0500, Chris Snyder wrote: > You're approaching this as if it's a technical issue. As of now, it's > not. I don't have the standing in the community to resolve the social > issues that must be dealt with first. ... you didn't learn anything from the long emai

Re: Code formatter

Le 13 nov. 2009 à 20:01, Werner LEMBERG a écrit : > >> The rules are already defined (albeit unsatisfactorily in my opinion): >> >> Do whatever emacs does. > > Then, for goodness' sake, why not write a small elisp program to use > Emacs in batch mode on the command line (yes, this is possible)

Re: Code formatter

On Fri, Nov 13, 2009 at 08:01:41PM +0100, Werner LEMBERG wrote: > > > The rules are already defined (albeit unsatisfactorily in my opinion): > > > > Do whatever emacs does. > > Then, for goodness' sake, why not write a small elisp program to use > Emacs in batch mode on the command line (yes, th

Re: Code formatter

> The rules are already defined (albeit unsatisfactorily in my opinion): > > Do whatever emacs does. Then, for goodness' sake, why not write a small elisp program to use Emacs in batch mode on the command line (yes, this is possible) to format one or more files? Emacs runs on Windows too, and n

Re: Issue #768 - chord repetition shortcut: patch for review

>> OTOH, something like >> { 8-. -^ }*2 >> >> is not doable with the q approach. > > Why not? > > \repeat unfold 2 { 8-. q-^ } > > Please stop trying to overload the * operator. Well, David has a point here IMHO: The `\repeat unfold' really is neither elegant nor intuitive nor quickly to type

Re: Code formatter

On 11/13/09 9:59 AM, "Trevor Daniels" wrote: > > > Chris Snyder wrote Friday, November 13, 2009 4:35 PM >> > >> Graham Percival wrote: >>> I know that you're thinking "this is ridiculous", but unless >>> somebody does it, newbies will continue to face this difficulty. >>> This job won't ge

Re: Issue #768 - chord repetition shortcut: patch for review

Le 13 nov. 2009 à 13:25, David Kastrup a écrit : Kieren MacMillan writes: Since the patch (as I understand it) ensures that q does not duplicate anything except the notes, q allows for 8-. q-^ q-. q-^ etc., right? Obviously, this would *not* be possible with something like 4*8

Re: Code formatter

Graham Percival wrote: Whatever. You're giving up. All this time I've spent trying to help you on this was wasted. I'm sure that more experienced developers list are either laughing at me, or shaking their heads sadly... "oh that Graham, he's trying to help the beginners, but he still doesn't

Re: Code formatter

Forget the tool. Astyle is very configurable, but we still could need our own formatter (though I wouldn't like that). Developing C++ code on Windows is practically impossible, but can be well done with the VirtualBox pc for which I host the ISO (see the CG :)) So it doesn't matter whether the t

Re: Issue #768 - chord repetition shortcut: patch for review

At 13:25 on 13 Nov 2009, David Kastrup wrote: > Kieren MacMillan writes: > > > Hi, > > > >> Could it be an option to make 4*8 do the obvious thing? > >> Or even { 4 }*8 ? > >> That would be so much more natural. The first already does > >> something, but not something which I would call useful.

Re: [PATCH] Strings as markup arguments in music functions

Le 12 nov. 2009 à 23:02, Neil Puttock a écrit : Hi all, Though strings are valid markup objects according to the type predicate `markup?', the parser only recognizes full_markup objects as valid for music functions, which means it's currently impossible to pass both strings and markups unless u

Re: Code formatter

On Fri, Nov 13, 2009 at 04:59:20PM -, Trevor Daniels wrote: > > Chris Snyder wrote Friday, November 13, 2009 4:35 PM >> Graham Percival wrote: >>> I know that you're thinking "this is ridiculous", but unless >>> somebody does it, newbies will continue to face this difficulty. >>> This job won't

Re: new abc2ly files not distributed

Am Freitag, 13. November 2009 15:30:21 schrieb Graham Percival: > Trying to build GUB: > > file from VC not distributed: > lilypond-2.13.8/input/regression/abc2ly/GNUmakefile > file from VC not distributed: > lilypond-2.13.8/input/regression/abc2ly/clefs.abc file from VC not > distributed: lilyp

Re: Code formatter

Chris Snyder wrote Friday, November 13, 2009 4:35 PM Graham Percival wrote: I know that you're thinking "this is ridiculous", but unless somebody does it, newbies will continue to face this difficulty. This job won't get done by itself. Yes, I do think it's ridiculous. As I understand, yo

Re: Code formatter

- which set of options in astyle produces the smallest possible diff with our existing code? (don't answer the questions on the list -- go investigate them) That is not interesting at all, as formatting rules should be introduced incrementally. __

Re: Code formatter

Graham Percival wrote: I know that you're thinking "this is ridiculous", but unless somebody does it, newbies will continue to face this difficulty. This job won't get done by itself. Yes, I do think it's ridiculous. As I understand, you're saying, "go find a tool that makes the code conform t

lilypond frogs

In case people missed it, here's the website for the Frogs: http://frogs.lilynet.net It has stuff like the easy-to-use lilypond git gui that Carl's working on. Again, this will be better publicized in the new website. Cheers, - Graham ___ lilypond-d

Re: Code formatter

(sorry if it's a duplicate; email problems) On Fri, Nov 13, 2009 at 10:44:54AM -0500, Chris Snyder wrote: > Graham Percival wrote: >> 1) running astyle will change lines of code. This makes the >> history harder to look at... if we want to know who wrote a >> particular line (say, "there seems to

Re: Code formatter

On Fri, Nov 13, 2009 at 10:44:54AM -0500, Chris Snyder wrote: > Graham Percival wrote: >> 1) running astyle will change lines of code. This makes the >> history harder to look at... if we want to know who wrote a >> particular line (say, "there seems to be a bug here; hey Joe, why >> did you write

Re: Code formatter

Yes, code formatting involves fascism. - Someone, a lead architect should decide upon rules. - Then a tool must be used to force these rules. It shouldn't be the tool's rules, but the tool should support the rules defined by the lead developer. - You should NOT run it on all existing files. -

Re: Code formatter

Graham Percival wrote: 1) running astyle will change lines of code. This makes the history harder to look at... if we want to know who wrote a particular line (say, "there seems to be a bug here; hey Joe, why did you write "if (x = 3)" ?"), then it will appear that *you* were the last person to

Re: Code formatter

On Fri, Nov 13, 2009 at 08:41:06AM -0500, Chris Snyder wrote: > There is one thing that bugs me about this discussion (and others) - it > seems like sometimes improvements are rejected as being "not good > enough," even if they're still an incremental improvement. Wouldn't > running all of th

new abc2ly files not distributed

Trying to build GUB: file from VC not distributed: lilypond-2.13.8/input/regression/abc2ly/GNUmakefile file from VC not distributed: lilypond-2.13.8/input/regression/abc2ly/clefs.abc file from VC not distributed: lilypond-2.13.8/input/regression/abc2ly/grace.abc file from VC not distributed: lilyp

Re: Code formatter

Graham Percival wrote: I'm afraid that you won't get many positive responses until you look at the previous discussion about this issue. Again, the main developers have been bitten by people in the past asking many questions, spending hours explaining things to them, but then ultimately giving u

Re: BOM mark from Windows notepad

On 13 Nov 2009, at 12:25, Bertalan Fodor (LilyPondTool) wrote: {BOM_UTF8}/.* { if (this->lexloc->line_number () != 1 || this->lexloc->column_number () != 0) { LexerError (_ ("stray UTF-8 BOM encountered").c_str ()); exit (1); Also, the conditions and the stuff following might possibl

Re: BOM mark from Windows notepad

On 13 Nov 2009, at 12:25, Bertalan Fodor (LilyPondTool) wrote: Hehe, we've got this: {BOM_UTF8}/.* { if (this->lexloc->line_number () != 1 || this->lexloc->column_number () != 0) { LexerError (_ ("stray UTF-8 BOM encountered").c_str ()); exit (1); That means, we correctly parse th

Re: Issue #768 - chord repetition shortcut: patch for review

On 11/13/09 5:27 AM, "David Kastrup" wrote: > Marc Hohl writes: > >> David Kastrup schrieb: >>> [...] >>> But *4 is _logical_. You can guess what it does without looking it up >>> in the manual. >>> >> No. Since it looks like a multiplication, it treats the number, not >> the notes (at le

Re: Issue #768 - chord repetition shortcut: patch for review

Kieren MacMillan writes: >> Why couldn't you write >> 4 s4*3 >> or similar? > > I might be able to... but with your suggested "fix" of the * symbol, > > R1*8 > > would end up as > > R1 R1 R1 R1 R1 R1 R1 R1 > > and potentially not compress. Depends on the details of implementing * I guess. >

Re: Issue #768 - chord repetition shortcut: patch for review

Graham Percival writes: > On Fri, Nov 13, 2009 at 11:33:55AM +0100, David Kastrup wrote: >> In fact, I was quite surprised at what 4*4 does currently. Makes >> no sense to me. Can't imagine what it would be good for. > > \time 5/8 > R8*5 > > I used it all the time. For rests, yes. In particul

Re: Issue #768 - chord repetition shortcut: patch for review

Marc Hohl writes: > David Kastrup schrieb: >> [...] >> But *4 is _logical_. You can guess what it does without looking it up >> in the manual. >> > No. Since it looks like a multiplication, it treats the number, not > the notes (at least for me). So < c e g>4*4 could be interpreted as > < c e

Re: Issue #768 - chord repetition shortcut: patch for review

Kieren MacMillan writes: > Hi, > >> Could it be an option to make 4*8 do the obvious thing? >> Or even { 4 }*8 ? >> That would be so much more natural. The first already does something, >> but not something which I would call useful. > > I use it all the time, actually. > >> The second bombs out

Re: Issue #768 - chord repetition shortcut: patch for review

Hi David, Why couldn't you write 4 s4*3 or similar? I might be able to... but with your suggested "fix" of the * symbol, R1*8 would end up as R1 R1 R1 R1 R1 R1 R1 R1 and potentially not compress. This unwanted behaviour along with the loss of (e.g.) 4 q8-. q8-> ~ q2 would be unf

Re: Issue #768 - chord repetition shortcut: patch for review

On Fri, Nov 13, 2009 at 11:33:55AM +0100, David Kastrup wrote: > In fact, I was quite surprised at what 4*4 does currently. Makes > no sense to me. Can't imagine what it would be good for. \time 5/8 R8*5 I used it all the time. Cheers, - Graham ___

Re: Issue #768 - chord repetition shortcut: patch for review

Kieren MacMillan writes: > Hi, > >> In fact, I was quite surprised at what 4*4 does currently. >> Makes >> no sense to me. Can't imagine what it would be good for. > > I use it all the time to write piano music which looks like it has > multiple voices, but without all the complexity of actually

Re: Issue #768 - chord repetition shortcut: patch for review

At 06:23 on 13 Nov 2009, Kieren MacMillan wrote: > Hi, > > > Could it be an option to make 4*8 do the obvious thing? > > Or even { 4 }*8 ? > > That would be so much more natural. The first already does > > something, but not something which I would call useful. > > I use it all the time, actuall

Re: BOM mark from Windows notepad

2009/11/13 Bertalan Fodor (LilyPondTool) : > Hehe, we've got this: > > {BOM_UTF8}/.* { >  if (this->lexloc->line_number () != 1 || this->lexloc->column_number () != > 0) >   { >     LexerError (_ ("stray UTF-8 BOM encountered").c_str ()); >     exit (1); > > That means, we correctly parse the BOM,

Re: Issue #768 - chord repetition shortcut: patch for review

Hi, In fact, I was quite surprised at what 4*4 does currently. Makes no sense to me. Can't imagine what it would be good for. I use it all the time to write piano music which looks like it has multiple voices, but without all the complexity of actually writing multiple voice constructs

Re: BOM mark from Windows notepad

Hehe, we've got this: {BOM_UTF8}/.* { if (this->lexloc->line_number () != 1 || this->lexloc->column_number () != 0) { LexerError (_ ("stray UTF-8 BOM encountered").c_str ()); exit (1); That means, we correctly parse the BOM, but exit if it is not the first char. Hans Aberg wro

Re: Issue #768 - chord repetition shortcut: patch for review

Hi, Could it be an option to make 4*8 do the obvious thing? Or even { 4 }*8 ? That would be so much more natural. The first already does something, but not something which I would call useful. I use it all the time, actually. The second bombs out. In contrast, q feels rather hackish. Sinc

Re: Issue #768 - chord repetition shortcut: patch for review

David Kastrup schrieb: [...] But *4 is _logical_. You can guess what it does without looking it up in the manual. No. Since it looks like a multiplication, it treats the number, not the notes (at least for me). So < c e g>4*4 could be interpreted as < c e g >16, which is not what we want. I

Re: developers developers developers

Graham Percival writes: > On Thu, Nov 12, 2009 at 04:25:40PM +0100, Bertalan Fodor (LilyPondTool) wrote: >>Good visual debugger for both scheme and C++, running well on Windows and >>Linux. > > That'll take... oh, 200 hours? Sorry, but that would probably > take all the lilypond programm

Re: Issue #768 - chord repetition shortcut: patch for review

Marc Hohl writes: > David Kastrup schrieb: >>> > This is great! >>> I've chosed arbitrary defaults, which may be changed: >>> - the shortcut is `q'; >>> - the function copying the previous chord only copies the chord pitches, >>> and removes all other decorations. >>> Both are customizable,

Re: BOM mark from Windows notepad

On 13 Nov 2009, at 10:08, Bertalan Fodor (LilyPondTool) wrote: I think changing the LilyPond parser to support BOM in the middle (ie not at the beginning) of the file is very hard. Actually if it is not at the beginning, then it should be treated as a regular character, which might not be p

Re: BOM mark from Windows notepad

On 13 Nov 2009, at 02:27, Patrick McCarty wrote: Please keep on touch until I get a sample again from one of my students. Perhaps they created it in another encoding, and the filled the file with UTF-8? No, I just used Windows Notepad (on Windows XP) to create the file, and saved it with UTF

Re: Issue #768 - chord repetition shortcut: patch for review

David Kastrup schrieb: Nicolas Sceaux writes: Hi, Here is patch implementing the chord repetition shortcut that has been discussed a few times, for review: This is great! I've chosed arbitrary defaults, which may be changed: - the shortcut i

Re: BOM mark from Windows notepad

I think changing the LilyPond parser to support BOM in the middle (ie not at the beginning) of the file is very hard. Actually if it is not at the beginning, then it should be treated as a regular character, which might not be present just anywhere in the file. Francisco Vila wrote: 2009/11/1

Re: BOM mark from Windows notepad

2009/11/13 Francisco Vila : > Here, suppose the user unexpectedly inserted a blank > before the BOM. > % > And no PDF.  Attached for your convenience. Comments? Following unicode.org[1], one could well handle it as a ZWNBSP. I mean, BOM is there for a reason, and if it is supported, that shou

Re: BOM mark from Windows notepad

Hello again, Still looking for a test case which reproduces the error; anyway, here is another case, IIRC not exactly what I encountered, but a case in which I think the expureous BOM could well be ignored for the sake of a happy ending. Here, suppose the user unexpectedly inserted a blank before

Re: Patch: remove Ottava_spanner_engraver from \TabStaff

Neil Puttock schrieb: 2009/11/9 Marc Hohl : I added another version of my patch without these comments; I tried to fill the [DOCME] in the description tag with something more useful. Cheers, it's applied. Thank you! Marc Regards, Neil

Re: Issue #768 - chord repetition shortcut: patch for review

Nicolas Sceaux writes: > Hi, > > Here is patch implementing the chord repetition shortcut that has been > discussed a few times, for review: > > > > I've chosed arbitrary defaults, which may be changed: > - the shortcut is `q'; > - the function copying the