Hello,
Status update: I have extended my trip to California (I'm visiting my
employer's client) until June 6th, and I'm very busy with my day job. I
should be able to resume work on LilyDev by June 13th - I hope that delay
is not a problem.
Anyway, I think that the proof of concept that I've
Hello,
I have an alpha version of LilyDev built with Vagrant and Ansible ready for
demonstration.
To try it, you need VirtualBox (https://www.virtualbox.org/) and Vagrant (
https://www.vagrantup.com/) installed, and the LilyDev Vagrant box (which
you can download here:
PS don't install Vagrant with apt-get, the version in official repositories
is *ancient* and probably won't work - install using files from the website.
2015-05-12 21:38 GMT-07:00 Janek Warchoł janek.lilyp...@gmail.com:
Hello,
I have an alpha version of LilyDev built with Vagrant and Ansible
2015-05-05 3:10 GMT+02:00 Paul Morris p...@paulwmorris.com:
Automatic formatting/indenting of C++ files currently doesn't work out of
the box” and there’s no easy way to manually get it to work. Artistic
Style 2.02 is required for LilyPond’s fixcc.py but LilyDev3 has 2.01, which
is the
2015-05-04 20:41 GMT+02:00 Carl Sorensen c_soren...@byu.edu:
On 5/4/15 11:19 AM, Federico Bruni fedel...@gmail.com wrote:
So I'd rather put a script to download the repository when the user logs
in
for the first time.
What do you think?
Isn't that the way it works right now? If not, it
2015-05-06 22:47 GMT+02:00 Janek Warchoł janek.lilyp...@gmail.com:
I'll wait for your prototype, even if it looks like a work duplication
already.
Why not improving what's already available? Which advantages have the
tools
you are using?
I _am_ going to improve what's already
On 5/7/15 3:49 PM, Wols Lists antli...@youngman.org.uk wrote:
Basically, what I'm saying is don't assume everyone is using Debian
and/or lilydev when you revamp the CG, because that's where that quote
makes it look you're heading.
Thanks for the reminder. I hope we won't head that way. I agree
On 04/05/15 23:35, Carl Sorensen wrote:
On 5/4/15 4:25 PM, Dan Eble d...@faithful.be wrote:
But anyways, the main point of this email is to point out that pushing
debian could cost you developers - I don't know how many people like me
there are out there, but if I have to use a debian-based
Am 06.05.2015 um 07:34 schrieb Federico Bruni:
2015-05-06 7:19 GMT+02:00 Janek Warchoł janek.lilyp...@gmail.com:
as I've already mentioned, I've already started working on a new
LilyDev. I'm going to use tools that should make it easy to build
different versions of LilyDev (e.g. 32-bit and
Federico Bruni fedel...@gmail.com writes:
2015-05-04 20:29 GMT+02:00 Phil Holmes m...@philholmes.net:
Years ago I started by (accidentally) using it as a live OS. It's a
useless way of trying to use it. I wouldn't bother to try to support it.
I totally agree. In my experience a live OS
On 06/05/15 10:55, Urs Liska wrote:
Am 06.05.2015 um 07:34 schrieb Federico Bruni:
2015-05-06 7:19 GMT+02:00 Janek Warchoł janek.lilyp...@gmail.com:
as I've already mentioned, I've already started working on a new
LilyDev. I'm going to use tools that should make it easy to build
2015-05-06 11:55 GMT+02:00 Urs Liska u...@openlilylib.org:
As a side note: What would be the amount of work to provide a lily-dev
metapackage that could be used by people who are already using a Linux
distribution? As a Linux user I would prefer modifying my own system over
using a
Hi,
2015-05-05 22:34 GMT-07:00 Federico Bruni fedel...@gmail.com:
2015-05-06 7:19 GMT+02:00 Janek Warchoł janek.lilyp...@gmail.com:
as I've already mentioned, I've already started working on a new
LilyDev. I'm going to use tools that should make it easy to build
different versions of
Hi all,
as I've already mentioned, I've already started working on a new
LilyDev. I'm going to use tools that should make it easy to build
different versions of LilyDev (e.g. 32-bit and 64-bit, possibly also
based on different distros).
In order to reduce work duplication, I suggest to wait
2015-05-04 20:29 GMT+02:00 Phil Holmes m...@philholmes.net:
Years ago I started by (accidentally) using it as a live OS. It's a
useless way of trying to use it. I wouldn't bother to try to support it.
I totally agree. In my experience a live OS makes sense only when you must
fix something
2015-05-06 7:19 GMT+02:00 Janek Warchoł janek.lilyp...@gmail.com:
as I've already mentioned, I've already started working on a new
LilyDev. I'm going to use tools that should make it easy to build
different versions of LilyDev (e.g. 32-bit and 64-bit, possibly also
based on different
Hi Paul, thanks for the suggestions.
As Debian Jessie was released few days ago, I was thinking about a new
LilyDev.
I think I'll first upgrade to a more recent version of live-build and then
add the modifications you are suggesting.
2015-05-04 0:09 GMT+02:00 Paul Morris p...@paulwmorris.com:
2015-05-04 18:32 GMT+02:00 Federico Bruni fedel...@gmail.com:
As Debian Jessie was released few days ago, I was thinking about a new
LilyDev.
I think I'll first upgrade to a more recent version of live-build and then
add the modifications you are suggesting.
I have a question: does anybody
- Original Message -
From: Federico Bruni fedel...@gmail.com
To: Paul Morris p...@paulwmorris.com
Cc: LilyPond Development Team lilypond-devel@gnu.org
Sent: Monday, May 04, 2015 6:19 PM
Subject: Re: Improving the Contributors Guide and LilyDev
2015-05-04 18:32 GMT+02:00 Federico Bruni
On 5/4/15 11:19 AM, Federico Bruni fedel...@gmail.com wrote:
So I'd rather put a script to download the repository when the user logs
in
for the first time.
What do you think?
Isn't that the way it works right now? If not, it certainly should.
There should be a script that configures git
On May 3, 2015, at 6:15 PM, David Kastrup d...@gnu.org wrote:
CG 3.3.4 Making Patches
git format-patch origin doesn't work if you type it in literally,
but gives ambiguous argument 'origin' message.
Shouldn't happen unless you managed to create either a local branch
named origin or a
Hi Federico,
On May 4, 2015, at 12:32 PM, Federico Bruni fedel...@gmail.com wrote:
Hi Paul, thanks for the suggestions.
As Debian Jessie was released few days ago, I was thinking about a new
LilyDev.
Hey, that’s great timing!
I think I'll first upgrade to a more recent version of
On May 3, 2015, at 11:02 PM, Carl Sorensen c_soren...@byu.edu wrote:
I think that it would be great to have you prepare patches for the CG.
The CG is the least-reviewed manual in our set, so it's probably the
easiest manual for which to get patches approved.
Will do, once this discussion
Wols Lists antli...@youngman.org.uk writes:
On 04/05/15 04:02, Carl Sorensen wrote:
2. Compiling with LilyDev (2.3) and Compiling (4.x)
2.3 is about getting it set up with LilyDev. 4.x is about general work
whether with or without LilyDev. We are much stronger about recommending
the use of
On 5/4/15 4:25 PM, Dan Eble d...@faithful.be wrote:
But anyways, the main point of this email is to point out that pushing
debian could cost you developers - I don't know how many people like me
there are out there, but if I have to use a debian-based system my
reaction is likely to be thanks
But anyways, the main point of this email is to point out that pushing
debian could cost you developers - I don't know how many people like me
there are out there, but if I have to use a debian-based system my
reaction is likely to be thanks but no thanks. (That said, I think a
The data point
On 04/05/15 04:02, Carl Sorensen wrote:
2. Compiling with LilyDev (2.3) and Compiling (4.x)
2.3 is about getting it set up with LilyDev. 4.x is about general work
whether with or without LilyDev. We are much stronger about recommending
the use of LilyDev than we were when the CG was
On 04/05/15 22:39, Wols Lists wrote:
On 04/05/15 04:02, Carl Sorensen wrote:
2. Compiling with LilyDev (2.3) and Compiling (4.x)
2.3 is about getting it set up with LilyDev. 4.x is about general work
whether with or without LilyDev. We are much stronger about recommending
the use of LilyDev
On May 4, 2015, at 9:10 PM, Paul Morris p...@paulwmorris.com wrote:
They both have highlighting for c++, .css, and .py files,
gedit also has it for .scm, .itexi, .itely, and .make files,
but geany doesn’t have it for these.
(And neither has it for .ly files.)
This was from the default
Hello dev list,
Below are some notes I made as I worked with the contributor’s guide and
LilyDev in recent months. This started with minor things and grew from there.
They represent my view as a novice who is basically learning git and the
command line as I go. I found the learning curve
Two notes:
Paul Morris p...@paulwmorris.com writes:
CG 3.3.4 Making Patches
git format-patch origin doesn't work if you type it in literally,
but gives ambiguous argument 'origin' message.
Shouldn't happen unless you managed to create either a local branch
named origin or a file with that
Am 04.05.2015 um 00:15 schrieb David Kastrup:
CG 3.3.4 git-cl configuration
add how to set the EDITOR variable for git cl, namely:
export EDITOR=/usr/bin/nano
Nano does not offer point-and-click in connection with LilyPond I think.
I don't think so either. But I don't see why that should
On Mon, May 04, 2015 at 03:02:32AM +, Carl Sorensen wrote:
A. Suggestions for LilyDev3:
All of these suggestions would actually probably be for LilyDev4. I'm not
sure that we will make another release of LilyDev3. But if we did, I'm
still happy to host it.
If somebody is available and
On 5/3/15 4:09 PM, Paul Morris p...@paulwmorris.com wrote:
I think that it would be great to have you prepare patches for the CG.
The CG is the least-reviewed manual in our set, so it's probably the
easiest manual for which to get patches approved.
A. Suggestions for LilyDev3:
All of these
34 matches
Mail list logo
