Le jeudi 14 janvier 2010 à 08:36 +, Trevor Daniels a écrit :
> Unlike copying from the SHA1 ID and Find fields, cntl-c
> cannot be used to copy to the clipboard from this pane.
>
> In Windows you have to press enter.
>
> In gitk running under ubuntu even this does not work. The field
> to be
Le jeudi 14 janvier 2010 à 12:52 +, Graham Percival a écrit :
> 3) this is a presentation issue, not a content issue. As long as it
> compiles, push it, then let other people work on the presentation.
>
> Based on your description, I gather that there's yet another bug in
> lilypond-texi2html
Mark Polesky wrote:
> Yep. Thanks Joe!
Brilliant. There's probably plenty more that can be added -- see all
the info on the Wine wiki linked to -- but this seems to be the really
_essential_ stuff. Maybe also a link to where to get dos2unix ... ?
__
Suggestions:
1) stop sticking everything in the same thread; it makes it very hard
to keep track of what's happening.
2) I can't reproduce with some tests on programming-work.itexi based
on your description, so further debugging would be tricky for me.
3) this is a presentation issue, not a conte
Unfortunately, there's a hierarchy problem with the
@subsubheading Technical details
thing that had previously escaped my notice. I'm finding
this really confusing so I'll try to be clear. And I could
be wrong on some detail... Any instance of
@unnumberedsubsubsec foo
that comes immediat
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 highlig
On Wed, Jan 13, 2010 at 08:32:28AM -0800, Mark Polesky wrote:
> Graham Percival wrote:
> > - elsewhere in the docs, we use "foo -- bar", not
> > "foo---bar". I don't pretend to be authoritative about
> > the difference, though.
>
> I've read that the typographical ideal is:
>
> word, hair-spac
On Wed, Jan 13, 2010 at 02:24:58PM +0100, John Mandereau wrote:
> Le mercredi 13 janvier 2010 à 12:20 +, Graham Percival a écrit :
> > Also, please
> > use @q{} in the @section name.
> > ... actually, could we just sidestep the whole issue by removing the
> > quotes entirely? "@node Using li
Trevor Daniels wrote:
> 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?
Yep. Thanks Joe!
- Mark
___
lilypond-devel mailing list
lily
Graham Percival wrote:
> Looks mostly good.
>
> - you've reverted some of the ``foo'' -> @qq{foo} changes
> in essay. Why?
Freaky. I didn't touch essay. How did that happen? I see
Trevor has some theories... Oh, I see now that Francisco
was doing some work there. I must not have rebased at t
Graham Percival wrote Wednesday, January 13, 2010 12:20 PM
On Wed, Jan 13, 2010 at 8:16 AM, Mark Polesky
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 punctuation outside
@q{}
brack
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
Le mercredi 13 janvier 2010 à 12:20 +, Graham Percival a écrit :
> - I'm not positive, but I believe that we put punctuation outside @q{}
> brackets. If you want to change this policy, we can discuss it, but
> please don't just go changing things inside the hu/ translation.
Indeed; Mark, diff
On Wed, Jan 13, 2010 at 8:16 AM, Mark Polesky wrote:
> Okay, here's a patch. Obviously, there's more work to be done,
> but it might be good to get the re-structuring stuff out of the
> way. `make' succeeded and `make doc' is still going, but I'm off
> to bed.
Looks mostly good.
- you've rever
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
thin
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
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
Le mercredi 13 janvier 2010 à 09:27 +, Trevor Daniels a écrit :
> 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
> think.
You can also copy (but not paste) from the commit content su
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/paste
On 2010-01-12, Mark Polesky wrote:
> 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 indeed.
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 indeed. Thanks.
Incidentally, have you guys seen gitg?
On 2010-01-12, Mark Polesky wrote:
> 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/paste in g
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/paste in gitk on Unix? I can't seem to.
Right-clicking in
Le mardi 12 janvier 2010 à 14:49 +, Graham Percival a écrit :
> For unstable, yes. But they're not all that cheap for stable -- I
> mean, I'd expect many users to update to a new stable version. But
> there's absolutely no functional difference between 2.12.3 and the
> hypothetical 2.12.4. T
2010/1/12 John Mandereau :
> Le mardi 12 janvier 2010 à 12:31 +, Graham Percival a écrit :
>> now that John's
>> updated stable, I need to drop that work and start figuring out how to
>> get GUB to make 2.12.3-2.
>
> Why not releasing a 2.12.4 instead? Revision numbers (third number of
> the v
Le mardi 12 janvier 2010 à 12:31 +, Graham Percival a écrit :
> now that John's
> updated stable, I need to drop that work and start figuring out how to
> get GUB to make 2.12.3-2.
Why not releasing a 2.12.4 instead? Revision numbers (third number of
the version number) are cheap, aren't they
On Tue, Jan 12, 2010 at 4:03 AM, Mark Polesky wrote:
> 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.
...
> *Th
On Tue, Jan 12, 2010 at 4:03 AM, Mark Polesky wrote:
> Graham Percival wrote:
> Of the two, I prefer "top...".
Ok. I suggest dropping the "sometimes"; let's make sure it's *always*
referred to as the "top source directory". Even if people never get
start touching the build system, using the ex
Le mardi 12 janvier 2010 à 09:09 +, Trevor Daniels a écrit :
> I don't
> use Cygwin, so I don't know if it shares a
> clipboard with Windows.
IIRC there is an option in Cygwin to share the clipboard between Windows
and XWindow applications, but if you just use Cygwin as a Windows
application i
Trevor Daniels wrote:
Now that I'm back home I don't have access to a Schmindows
machine, so I forget the details. But I do remember it
being a pain. Something like
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
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 was
Graham Percival wrote:
> Don't use $ in front of examples. It makes it impossible
> to cut&paste!
Well, not impossible. Besides, it's good to differentiate
the input from the output when quoting the output.
> Don't bother quoting the output.
Right.
> I think a fair chunk of it will be wasted
Graham Percival wrote:
> Don't use $ in front of examples. It makes it impossible
> to cut&paste!
Well, not impossible. Besides, it's good to differentiate
the input from the output when quoting the output.
> Don't bother quoting the output.
Right.
> I think a fair chunk of it will be wasted
>Original Message
>From: markpole...@yahoo.com
>Date: 11/01/2010 20:20
>To: "lilypond-devel", "pound...@lineone.net"
>Subj: Re: CG chapter 2, first draft
>
>pound...@lineone.net wrote:
>> I was just re-reading this section of the CG wh
pound...@lineone.net wrote:
> I was just re-reading this section of the CG when this
> arrived. For me, the balance is just right.
>
> Particularly useful for me was:
>
> 1 - The extra explanation in "Organization of remote
> branches" is useful when the terminology is new
>
> 2 - The reassurance a
>Original Message
>From: markpole...@yahoo.com
>Date: 11/01/2010 7:23
>To: "lilypond-devel"
>Subj: CG chapter 2, first draft
>
>Hey everyone. Here's a first draft of my idea for the new
>CG chapter 2. I left out some obvious things to save spa
Hi Mark, Trevor, Graham,
On 11/01/10 12:29, Trevor Daniels wrote:
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, jus
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 pag
(sorry, re-sending to list as well)
On Mon, Jan 11, 2010 at 7:23 AM, Mark Polesky wrote:
> Hey everyone. Here's a first draft of my idea for the new
> CG chapter 2.
Don't use $ in front of examples. It makes it impossible to
cut&paste! This is an abomination that probably started in printed
Hey everyone. Here's a first draft of my idea for the new
CG chapter 2. I left out some obvious things to save space.
And of course there are unfinished spots, but it's a preview
of (I hope) the new Git chapter. I say "I hope" because I
worry that some of you might think it's too much?
Well, we
40 matches
Mail list logo
