Graham Percival wrote Wednesday, January 27, 2010 6:43 PM
On Wed, Jan 27, 2010 at 06:12:14PM -, Trevor Daniels wrote:
Neil Puttock wrote Wednesday, January 27, 2010 5:38 PM
There's nothing in the documentation policy for \context block
formatting,
The patch is being written by James
Carl Sorensen wrote Sunday, January 24, 2010 1:49 PM
On 1/23/10 11:10 PM, Mark Polesky markpole...@yahoo.com wrote:
I wrote a little shell script to rebase all my local git
branches at once.
So does the script rebase all branches in a repository? I'm sure
I wouldn't
like that; I have some
Hi Eric
I'm a relative newcomer to Lily development too,
so it's best to keep these questions and answers
on the -devel list. That way others can chip in
to correct anything I say that is wrong and suggest
alternative and probably better ways of achieving
what you want to do.
I've tried to
Mark Polesky wrote Saturday, January 23, 2010 6:45 AM
Carl Sorensen wrote:
My cycle is to
[edit source files]
make (if needed)
You lost me there. How will I know if `make' is needed?
If you modify any source files that have to be
compiled, essentially the c++ files and their
includes
Eric Knapp wrote Thursday, January 21, 2010 2:36 AM
My goal is to determine the fingering
number and the string number
Is there a way to determine the digit
and string-number directly by name? It looks like the
articulations
are a list. Would it be possible to loop through the list and
Marc Hohl wrote Wednesday, January 20, 2010 9:54 AM
Trevor Daniels schrieb:
[...]
I would not worry about this. As Alexander has pointed out,
examples showing the staff lines extending through the sign
and not extending through the sign can be found. It is easy
for a user to move
Marc Hohl wrote Tuesday, January 19, 2010 9:04 AM
Trevor Daniels schrieb:
Marc Hohl wrote Monday, January 18, 2010 8:13 PM
Marc Hohl schrieb:
Neil Puttock schrieb:
2010/1/8 Marc Hohl m...@hohlart.de:
Hmmm - you are right. Is it possible to whiteout this small
part
of the barlines?
I
Marc Hohl wrote Tuesday, January 19, 2010 10:09 AM
Trevor Daniels schrieb:
Marc Hohl wrote Tuesday, January 19, 2010 9:04 AM
Trevor Daniels schrieb:
Marc Hohl wrote Monday, January 18, 2010 8:13 PM
Marc Hohl schrieb:
Neil Puttock schrieb:
2010/1/8 Marc Hohl m...@hohlart.de:
Hmmm
Marc Hohl wrote Monday, January 18, 2010 8:13 PM
Marc Hohl schrieb:
Neil Puttock schrieb:
2010/1/8 Marc Hohl m...@hohlart.de:
Hmmm - you are right. Is it possible to whiteout this small part
of the barlines?
I found out how to define a whiteout stencil, but it seems that it
is placed
Graham Percival wrote Saturday, January 16, 2010 10:26 PM
One idea that I've been considering for over a year is making a
social mailing list for lilypond developers.
Is there any interest in this?
Yeah - sounds fun. I miss the banter between
you and Valentin. And, more importantly,
Reinhold Kainhofer wrote Friday, January 15, 2010 11:01 PM
Am Freitag, 15. Januar 2010 18:24:55 schrieb Joe Neeman:
On Fri, 2010-01-15 at 18:08 +0100, Reinhold Kainhofer wrote:
If you can send us an example of what it looks like (so that we
don't
have to guess which settings you will set
Reinhold Kainhofer wrote Saturday, January 16, 2010 11:32 AM
Here's a file with all different spacings from 2.0 to 4.0...
Looking at some scores with two lyrics lines (mostly oratorios
with two
different language), I would tend to choose 2.8 or 3.0.
2.8 looks good to me.
Trevor
Trevor Daniels wrote Wednesday, January 13, 2010 11:18 AM
John Mandereau wrote Wednesday, January 13, 2010 9:44 AM
Le mercredi 13 janvier 2010 =C3=A0 09:27 +, Trevor Daniels a
=C3=A9crit=
In gitk (in either Unix or Windows) you can only
copy/paste within the fields that you can
Joseph Wakeling wrote Thursday, January 14, 2010 12:11 PM
Sometime soon I must get back onto the Contemporary Music docs.
That would be good! Happy to help when you're ready.
Trevor
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Mark Polesky wrote Wednesday, January 13, 2010 5:52 AM
Trevor Daniels wrote:
I've never had to to do it, as I rarely use the git bash
command line for git work. I can do virtually everything
in git gui or gitk, which cut and paste normally in both
Windows and Unix.
Can you really cut
Mats Bengtsson wrote Tuesday, January 12, 2010 9:41 AM
1) Right-click on the title-bar of the Git Bash window
2) Select Edit Mark
3) Left-click and drag your selection.
4) Press enter to copy it to the clipboard.
I have never tried GIT on Windows, but if the window in question
is a normal
John Mandereau wrote Tuesday, January 12, 2010 10:21 AM
Trevor Daniels wrote
I never did it - with git gui you never need an
editor. It has a pane specifically for displaying,
entering and editing commit messages. It also has
an Amend Last Commit button which was the only
form of rebase -i
John Mandereau wrote Wednesday, January 13, 2010 9:44 AM
Le mercredi 13 janvier 2010 =C3=A0 09:27 +, Trevor Daniels a
=C3=A9crit=
In gitk (in either Unix or Windows) you can only
copy/paste within the fields that you can highlight.
The include only the SHA1 ID and the Find fields, I
Mark Polesky wrote Wednesday, January 13, 2010 6:12 AM
Patrick McCarty wrote:
Most of the time, on GNU/Linux, I copy and paste by
highlighting the text to copy, and then middle-clicking
where I want to paste.
For no explicable reason, I just assumed that wouldn't work
in gitk. But it does
Graham Percival wrote Wednesday, January 13, 2010 12:20 PM
On Wed, Jan 13, 2010 at 8:16 AM, Mark Polesky
markpole...@yahoo.com wrote:
Okay, here's a patch.
- you've reverted some of the ``foo'' - @qq{foo} changes in
essay. Why?
- I'm not positive, but I believe that we put
Thanks Joe
Mark is currently redrafting this section of the CG and it seems
he has picked up and applied your changes in his latest patch.
Is that right, Mark?
Trevor
- Original Message -
From: Joseph Wakeling joseph.wakel...@webdrake.net
To: lilypond-devel lilypond-devel@gnu.org
Mark Polesky wrote Tuesday, January 12, 2010 4:03 AM
Graham Percival wrote:
I think a fair chunk of it will be wasted effort, but it's
*your* effort to waste.
Geez, Graham, sometimes I wish you *would* mince a few words
from time to time! I don't think it's a waste at all. I
remember
Graham Percival wrote Monday, January 11, 2010 11:30 AM
That said, a few more comments:
- if you're going to go to all this effort, please eliminate the
git
on windows section -- for each portion of the (unix-aimed) docs,
just
dump the relevant windows instructions on the bottom of the
Graham Percival wrote Sunday, January 10, 2010 1:35 PM
On Sun, Jan 10, 2010 at 09:36:05AM -, Trevor Daniels wrote:
Graham Percival wrote Saturday, January 09, 2010 10:19 AM
In the past few months, we've had a number of developers being
surprised at some of the build system changes
Mark Polesky wrote Wednesday, January 06, 2010 4:18 AM
Trevor Daniels wrote:
The section headings need to make it clearer what audience
is being addressed. Perhaps
Summary for experienced Unix developers
Full details for new contributors
Then of course there is a lot more to add
Mark Polesky wrote Tuesday, January 05, 2010 8:21 AM
Graham Percival wrote:
I think everybody liked the idea of the intro chapter,
even if there's slight uncertainty over one section of it
(i.e. lily-git). Let's get the part(s) that everybody
agrees with done.
Okay, I've attached a patch
Graham Percival wrote Saturday, January 02, 2010 6:47 AM
Grand LilyPond Input Syntax Stabilization (GLISS)
It's up, such as it is:
http://lilypond.org/~graham/gliss/
Looks promising. Nice overview of the issues.
I'll be happy to be part of the discussions when
they start.
Trevor
Graham Percival wrote Friday, January 01, 2010 2:18 AM
The recent problem with end-of-line in mingw is (believed to be)
fixed;
It is. Thanks Patrick!
In testing I noticed another niggle. Clicking on
the url which now appears in the pdf causes Adobe
Reader to fire up a browser, as it
Carl Sorensen wrote Tuesday, December 29, 2009 6:27 PM
On 12/29/09 8:41 AM, Carl Sorensen c_soren...@byu.edu wrote:
I think I've got a consistent idea now. I think I can add a
property
(probably 'details to avoid namespace pollution, but maybe
timeSignatureDefaults) to the TimeSignature
Hi Graham
With Vista Home Premium and 2.13.10-1.mingw.exe:
Downloaded - OK
Installed - OK
Lilypad - 2 issues
I don't run with administrator privileges
so can't save to /Public/Desktop. Saved in
my 'home' folder. Then OK, except that pdf
does not display the url (Never looked for
this
Reinhold Kainhofer wrote Thursday, December 31, 2009 11:26 AM
Am Donnerstag, 31. Dezember 2009 11:29:14 schrieb Trevor Daniels:
convert-ly - OK, except
Happened to try a file with \version 2.10
This causes a python index error.
Ouch, convert-ly assumed that all version strings always
Carl Sorensen wrote Monday, December 28, 2009 5:25 AM
Oh, I agree that it would have the added benefit of a greater
audience, but
it would also cost more time for Mark to get it into the Git
documentation
instead of into the LilyPond documentation.
[...etc]
Many thanks, Carl. I had
Graham Percival wrote Monday, December 28, 2009 8:09 PM
Why discuss git gui at all? Just give the command-line options.
No. Git GUI and gitk provide a far easier way to work with
branches than the command line. If the intention is to help
people move up to developing why deliberately
Carl Sorensen wrote Monday, December 28, 2009 8:03 PM
Actually, I think it's a three-way split:
* those using lily-git (not lilypond-git, that's the name of the
directory)
This option requires no knowledge of git at all -- just use
the 3
buttons
* those using git gui
* those using
Mark Polesky wrote Sunday, December 27, 2009 2:14 AM
Carl Sorensen wrote:
Have you considered whether Using Git should be an
appendix? To the extent that it's teaching about git,
rather than about LilyPond, it might belong in an
appendix.
Maybe there should be a chapter called something
Carl Sorensen wrote Saturday, December 26, 2009 11:32 PM
On 12/26/09 3:57 PM, Graham Percival gra...@percival-music.ca
wrote:
2009/12/26 John Mandereau john.mander...@gmail.com:
Or just lily-git ? I don't follow the porcelain joke...?
In git terminology, porcelain is what the users
Mark Polesky wrote Saturday, December 26, 2009 3:13 AM
Carl Sorensen wrote:
As I think more about this, I wonder if there should be a
short and sweet summary for experienced Linux developers,
followed by a gentle (and longer) introduction for the
Windows guys.
Actually, I'm thinking there
David Kastrup wrote Saturday, December 26, 2009 9:55 AM
I posted this patch already several days ago without any feedback,
so I
tried uploading it on Rietveld in order to get a better reaction.
A bit
of a nuisance how much work it is to get even trivial doc
improvements
accepted.
Thanks
James Bailey wrote Saturday, December 26, 2009 9:51 AM
Are the ottava symbols an intentional omission from
tabFullNotation? I couldn't find any documentation on the
function.
Not as far as I know. I'll add them (unless
someone shouts quickly).
Trevor
Trevor Daniels wrote Saturday, December 26, 2009 12:24 PM
James Bailey wrote Saturday, December 26, 2009 9:51 AM
Are the ottava symbols an intentional omission from
tabFullNotation? I couldn't find any documentation on the
function.
Not as far as I know. I'll add them (unless
someone
Graham Percival wrote Saturday, December 26, 2009 5:18 PM
I like this idea, but I'm not certain if we all have the same
idea. Here's the idea that I like:
1. introduction
1.1 help us: duplicate material from website
1.2 summary for unix developers: 2-3 paragraphs. We use git, the
docs are
Trevor Daniels Monday, December 21, 2009 1:07 AM
n.putt...@gmail.com, Sunday, December 20, 2009 9:48 PM
On 2009/12/14 12:13:07, t.daniels_treda.co.uk wrote:
So is http://codereview.appspot.com/164063 now ready to go?
The indentation in translation-functions.scm is still a bit
wrong
Mark Polesky wrote Monday, December 21, 2009 3:37 AM
In CG 1.1.6 Other locations for git, this is listed as a
location for the LP repo:
ssh://git.sv.gnu.org/srv/git/lilypond.git
Can only project members pull from it? Or can anyone,
provided SSH is set up properly (whatever that means)?
Mark Polesky wrote Monday, December 21, 2009 1:42 AM
Trevor Daniels wrote:
Actually, I don't think rebase is mentioned in the CG. I
can't see it on a quick trawl. It should be, as a branch
should be rebased before a patch is generated from it if
master has been updated since the branch
Carl Sorensen wrote Monday, December 21, 2009 1:44 PM
You can find out more about ssh on windows by searching for
windows ssh
client.
PuTTY is probably the most common ssh client for Windows, in my
experience.
I never managed to make PuTTY work with savannah and git.
None of the key pairs
Graham Percival wrote Monday, December 21, 2009 2:46 PM
On Mon, Dec 21, 2009 at 12:56:51AM -, Trevor Daniels wrote:
Graham Percival wrote Sunday, December 20, 2009 11:13 PM
git rebase --whitespace=fix master mymods
Can that be written as a universal preference? and added to CG
1.1
Mats, you wrote Monday, December 21, 2009 12:40 PM
I tried it here and it works well.
Try the following:
- Start emacs with the scm file:
emacs myfile.scm
- If Emacs just shows a welcoming screen, press CTRL-g.
- On the status line towards the bottom of the window, it should
say
Graham Percival wrote Monday, December 21, 2009 3:18 PM
On Mon, Dec 21, 2009 at 3:08 PM, Trevor Daniels
t.dani...@treda.co.uk wrote:
Graham Percival wrote Monday, December 21, 2009 2:46 PM
git rebase --whitespace=fix master mymods
If git
can be configured to automatically fix
Carl Sorensen wrote c_soren...@byu.edu
On 12/21/09 8:08 AM, Trevor Daniels t.dani...@treda.co.uk
wrote:
As far as I know it can't. The rebase command rebases
one git branch on another, so you have to be using branches
to take advantage of it.
Rebase combines all the changes between two
Colin Campbell wrote Monday, December 21, 2009 3:33 PM
After building LP 2.13.10 from git, I wanted an HTML copy of the
docs, so I cd to /Documentation and did make doc. The result was a
segfault:
Try make doc in the directory above /Documentation,
whatever you chose to call it.
Trevor
Carl Sorensen wrote Monday, December 21, 2009 4:41 PM
On 12/21/09 9:11 AM, Trevor Daniels t.dani...@treda.co.uk
wrote:
Carl Sorensen wrote c_soren...@byu.edu
so you can do
git rebase --whitespace=fix HEAD^
Hhm. I don't think this works.
The whitespace option is simply passed to apply
Reinhold, you wrote Monday, December 21, 2009 4:37 PM
Please note the ^ in the command, which means the commit
**before** HEAD, so
this command takes all commits since HEAD-1 (i.e. it takes only
the last
patch) and corrects all trailing whitespace in it.
You're right - I'd missed that.
Graham Percival wrote Sunday, December 20, 2009 9:01 PM
There's some git command that removes whitespaces at the end of
lines.
Yes, it's git rebase. That has a --whitespace=fix option.
So if your mods are in branch mymods, say, just enter
git rebase --whitespace=fix master mymods
You'll
Graham Percival wrote Sunday, December 20, 2009 11:13 PM
On Sun, Dec 20, 2009 at 11:05:27PM -, Trevor Daniels wrote:
git rebase --whitespace=fix master mymods
Can that be written as a universal preference? and added to CG
1.1? (I think it's that section; it might have moved
Graham Percival wrote Saturday, December 19, 2009 9:37 PM
On Sat, Dec 19, 2009 at 02:16:19PM +, Ian Hulin wrote:
Trevor did a brilliant job with the Windows section and in some
respects
it's clearer and less forbidding than the material in 1.1 to 1.4.
It
also duplicates a lot of the
Mark Polesky wrote ./autogen.sh question
Do I need to run ./autogen.sh every time I compile?
No. You only need to rerun it if you need to
configure the make files differently, for example
when you wish to retain the debugging info in the
binary.
Trevor
Hi Carl
I've just applied the patch set to check it out,
probably later today. Looks good so far, apart
from a couple of formatting nitpicks. It's
building now. Back soon.
Trevor
- Original Message -
From: Carl Sorensen c_soren...@byu.edu
To: David Kastrup d...@gnu.org
Cc: Lily
Carl,
A question. Does your code require autobeaming
rules to be defined for beams of every possible
duration? I ask because the following example beams
inconsistently, and I'm not sure if this is due to your
code or differences in the autobeaming rules for 4/4 and
2/2 time signatures. With
Graham Percival wrote Friday, December 18, 2009 12:05 PM
(argh, what a painful FAIL with the rainbow example. All those
colors are defined, but they didn't use all notes in the scale in
the output.)
Could somebody change the last line of the notes to:
g8 fis e d g2 |
and then extend the
Graham Percival wrote Friday, December 18, 2009 12:51 PM
On Fri, Dec 18, 2009 at 12:19 PM, Trevor Daniels
t.dani...@treda.co.uk wrote:
Graham Percival wrote Friday, December 18, 2009 12:05 PM
Could somebody change the last line of the notes to:
g8 fis e d g2 |
and then extend the high
Carl, you wrote Friday, December 18, 2009 4:21 PM
On 12/18/09 2:49 AM, Trevor Daniels t.dani...@treda.co.uk
wrote:
A question. Does your code require autobeaming
rules to be defined for beams of every possible
duration? I ask because the following example beams
inconsistently, and I'm
Carl, you wrote Friday, December 18, 2009 12:04 AM
I would like to propose moving one section of the Extending manual
to the
Notation Reference.
I'm happy to go along with this. I think it makes a
useful bridge into the Extending manual.
Trevor
I'm drafting out a new engraver to produce durations above a tab
staff for use in lute tablature, and I've been stumped by a problem
for several hours. Perhaps someone can see something I'm missing.
The problem is this (recast in a simplified form):
If I set the text property in a new grob
Neil Puttock wrote Tuesday, December 15, 2009 11:28 PM
2009/12/15 Trevor Daniels t.dani...@treda.co.uk:
but if I do this:
SCM duration_symbol;
Item *duration_grob;
...
duration_grob = make_item (TabDuration, events_[0]-self_scm
());
...
duration_symbol = ly_string2scm (A);
duration_grob
if the simple default
positioning is not to his taste. Better tools for
manually controlling the positioning might be desirable,
though.
Trevor
- Original Message -
From: Mark Polesky markpole...@yahoo.com
To: Neil Puttock n.putt...@gmail.com; Trevor Daniels
t.dani...@treda.co.uk
Cc: Graham
Thanks Neil
Sorry about the trailing spaces. I was used to my Windows editor
removing
them automatically; gedit can't, AFAICS. However, I've just
discovered that
git rebase --warning=fix will remove them, so as long as I remember
to do
that they should be gone.
I think I've corrected the
Trevor Daniels wrote Monday, December 14, 2009 12:12 PM
Sorry about the trailing spaces. I was used to my Windows editor
removing
them automatically; gedit can't, AFAICS. However, I've just
discovered that
git rebase --warning=fix will remove them,
--whitespace=fix of course!
Trevor
Nicolas Sceaux wrote Saturday, December 12, 2009 3:39 PM
Le 12 déc. 2009 à 14:01, David Kastrup a écrit :
{ G4 g D // | /// // / // | \time 3/4 G g / | D // // | /// // //
| }
Memorizing more than one chord/note (e.g. 3 chords/notes), and
accessing
them using q, qq, qqq, would do it?
John Mandereau wrote 10 Dec 2009
Trevor Daniels wrote 9 Dec2009
Traceback (most recent call last):
File /home/trevor/lilypond-git/scripts/build/out/www_post,
line 67,
in module
map (os.mkdir, [os.path.join (out_root, d) for d in dirs])
OSError: [Errno 2] No such file or directory
Graham Percival wrote Thursday, December 10, 2009 1:40 AM
On Wed, Dec 09, 2009 at 10:59:09PM +, Trevor Daniels wrote:
Traceback (most recent call last):
File /home/trevor/lilypond-git/scripts/build/out/www_post,
line 67,
in module
map (os.mkdir, [os.path.join (out_root, d) for d
I've just posted patch set 3 to Reitveld, after quite
some struggles with juggling regression-testing and
doc-building in a too-small virtual ubuntu system.
See http://codereview.appspot.com/164063
The main change from patch set 2 is to generalise the
input format of the context property
Graham Percival wrote Friday, December 11, 2009 2:24 PM
2.13.9 has been uploaded and should be visible now. Could people
give it a quick spin?
Downloaded mingw and installed fine in Vista.
Tested lilypond-book and lily by compiling notation/pitches.itely -
fine
convert-ly - fine
Dropped
Mark Polesky wrote Wednesday, December 09, 2009 9:05 AM
Wow. It's been just over 94 (and a half) *days* since my last
transmission here. If anyone is curious, I am still alive,
Hi Mark - good to hear it ;)
Which brings me to my question:
Currently there are 11 scripts for which
Due to my ubuntu virtual disk becoming full I had to do a make doc-clean
to free up some space; now I can't compile the docs. The last few lines
in the console are:
echo -e 'AddDefaultCharset utf-8\nAddCharset utf-8 .html\nAddCharset
utf-8 .en\nAddCharset utf-8 .nl\nAddCharset utf-8 .txt\n'
Graham Percival wrote Tuesday, December 08, 2009 8:42 AM
For the THANKS file, we have a policy that people listed as
Developer
aren't listed in the Contributors section. However, what should
we do
about people who are now Developers, but who were merely
Contributors
in the past? Should
From: dem...@suffolk.lib.ny.us Tuesday, December 08, 2009 6:28 PM
I was amused by the recent punctuation fix commit: [...]
BTW, may I remind to have TWO spaces after a full stop,
exclamation
mark and question mark at the end of a sentence.
That is the practice I recall from my time
Dana Emery wrote Sunday, December 06, 2009 9:37 PM
Let the choice of font display a glyph in the proper shape.
Provide the
user with a way to display arbitrary glyphs and ligatures for each
encoded
'stop'. This will be useful for bass stops (/a /b /c... //a
//b //c,
///a) and essential
Carl Sorensen wrote Monday, December 07, 2009 1:51 AM
On Dec 6, 2009, at 5:18 PM, Trevor Daniels
t.dani...@treda.co.uk
wrote:
Carl Sorensen wrote Sunday, December 06, 2009 9:59 PM
. The fretLabels list
wouldn't need to
be characters; they could be markups or stencils, so users could
Carl Sorensen wrote Monday, December 07, 2009 4:20 PM
On 12/6/09 5:18 PM, Trevor Daniels t.dani...@treda.co.uk wrote:
I prefer str to course and string, but if no other ideas
are forthcoming I'll use string_number.
In Scheme files, the variable name should be string-number.
In c++ files
of LilyPond and implementing some rather basic facilities.
Trevor
- Original Message -
From: dem...@suffolk.lib.ny.us
To: Carl Sorensen c_soren...@byu.edu
Cc: Ian Hulin i...@hulin.org.uk; Trevor Daniels
t.dani...@treda.co.uk; lilypond-devel@gnu.org;
re...@codereview.appspotmail.com; tdanielsmu
Graham Percival wrote Sunday, December 06, 2009 12:23 PM
We have a new doc contributor using lilybuntu. Does anybody know:
- what's the default text editor?
- how do you make it wrap at 72 characters per line?
- does it support utf-8? (I had an issue with one patch not
applying cleanly,
Jonathan Kulp wrote Sunday, December 06, 2009 1:20 PM
On Sun, Dec 6, 2009 at 6:41 AM, Trevor Daniels
t.dani...@treda.co.ukwrote:
I'm hardly an expert, having installed ubuntu myself
only a few days ago, but the default editor in ubuntu
from Jonathan's .iso seems to be gedit
Hi Carl
Thanks for taking a look at this.
You wrote Sunday, December 06, 2009 3:23 PM
http://codereview.appspot.com/164063/diff/2001/3008
File scm/translation-functions.scm (right):
http://codereview.appspot.com/164063/diff/2001/3008#newcode393
scm/translation-functions.scm:393:
Carl Sorensen wrote Sunday, December 06, 2009 9:59 PM
On 12/6/09 9:50 AM, Trevor Daniels t.dani...@treda.co.uk
wrote:
I changed it because string is a keyword in Scheme.
It is even used as such in the same few lines of code.
Although string can be used as a variable name I don't
think
Carl Sorensen wrote Friday, December 04, 2009 6:53 PM
On 12/4/09 9:24 AM, David Kastrup d...@gnu.org wrote:
Could you describe in simple words what the behavior is supposed
to
achieve? If you do that, I promise to submit some simple code
that does
that.
Take three text_scripts, all
Carl Sorensen wrote Saturday, December 05, 2009 2:38 PM
On 12/5/09 2:56 AM, Trevor Daniels t.dani...@treda.co.uk
wrote:
Carl Sorensen wrote Friday, December 04, 2009 6:53 PM
Take three text_scripts, all with outside_staff_priority of 450,
and with
script_priorities of 201, 202, 203
I've reworked this patch to make 'whiteout a property of all
grobs. To use it effectively 'layer must also be set
carefully.
I think I've dealt with the other issues.
Patch set 2 is a complete replacement.
Further comments?
http://codereview.appspot.com/164063
Trevor
- Original Message
David Kastrup wrote Friday, December 04, 2009 4:24 PM
I've unwrapped a bit of code of the form
for (a;b;c) {
if (condition)
short something
else {
Large something
}
z
}
into
for (a;b;z,c) {
if (condition) {
short something
continue;
}
Large something
}
which helps a bit
I posted my first patch to Rietveld last night, but nothing seems to
have been cc'd to the list. Not sure what I did wrong. It's at
http://codereview.appspot.com/164063. Here's what it does.
This is the first patch of a series aiming eventually to enable
Baroque lute tablature to be
David Kastrup wrote Wednesday, December 02, 2009 11:15 AM
Trevor Daniels t.dani...@treda.co.uk writes:
I posted my first patch to Rietveld last night, but nothing seems
to
have been cc'd to the list. Not sure what I did wrong. It's at
http://codereview.appspot.com/164063. Here's what
I used git rebase -i to combine several commits into
one for the first time recently. This was in ubuntu.
It threw me for a while because the first editor it
brought up was nano (to edit the list of commits) and
then vi (to edit the commit messages). Not being
familiar with either, the way to
Carl Sorensen wrote Wednesday, December 02, 2009 3:21 PM
On 12/2/09 2:26 AM, Trevor Daniels t.dani...@treda.co.uk
wrote:
I posted my first patch to Rietveld last night, but nothing seems
to
have been cc'd to the list. Not sure what I did wrong. It's at
http://codereview.appspot.com
Hi Jonathan, you wrote Wednesday, December 02, 2009 4:27 PM
On Wed, Dec 2, 2009 at 6:38 AM, Trevor Daniels
t.dani...@treda.co.ukwrote:
I used git rebase -i to combine several commits into
one for the first time recently. This was in ubuntu.
It threw me for a while because the first editor
Carl Sorensen wrote Wednesday, December 02, 2009 3:40 PM
On 12/2/09 2:26 AM, Trevor Daniels t.dani...@treda.co.uk
wrote:
Following a suggestion by Neil I have also made the whiteout
behind
all fret numbers optional. This is controlled by the 'whiteout
property of TabNoteHead
Carl Sorensen wrote Wednesday, December 02, 2009 10:29 PM
In order to do the proper explanation, it seems to me we need to
be clear on
three things:
1) Stacking priority depends on outside-staff-priority if it's
present
2) If not, it depends on script-priority
3) How to decide if objects
Hi Dana
Many thanks for this. It is not only interesting and useful, but
quite a bit _is_ new to me. The variability it exposes is rather
daunting! Makes me wonder how far we shall get along this road, but
we'll proceed one step at a time and hopefully arrive somewhere
useful.
Trevor
Neil Puttock wrote Saturday, November 28, 2009 6:01 PM
2009/11/26 Trevor Daniels t.dani...@treda.co.uk:
Is this a sensible/suitable/best approach? Any other
comments welcome.
I can't see anything wrong with the approach you've outlined
below.
Thanks Neil; that's the encouragement I
I am considering trying to implement a first attempt
at providing a Baroque lute tab facility. This may
turn out to be a bite too large for me, but hey, that's
the way to learn. The first phase would be to implement
a minimal set of facilities which would output something
like Baroque tab in
Carl Sorensen wrote Thursday, November 26, 2009 4:31 PM
On 11/26/09 2:56 AM, Marc Hohl m...@hohlart.de wrote:
Well documented code is crucial in such a project for other
developers
to jump
on the train, so learning by RTF code isn't fun (as mentioned
elsewhere) -
for me, it's annoying,
Having just installed ubuntu, a new git repo and compiled Lily and
the docs for the first time I see that all the entries in out-www
appear as unstaged changes in git.
Should not out-www be included in .gitignore or am I doing something
wrong here?
Trevor
901 - 1000 of 1527 matches
Mail list logo
