Given all of the discussion, and based upon desiring the capability to use
.ly files as stylesheets, I propose to add two predefineds for
point-and-click:
pointAndClickOff = #(define-music-function (parser location) ()
(ly:set-option 'point-and-click #f)
on 2008-07-15 at 09:52 Palmer, Ralph wrote:
>Also, I hope the tenor of the discussion stays civil.
i'm sure we all wish the same.
>I'm on a PC running XP SP3 now, others are on Macs, and many seem to
>be running some version of Linux, so I would assume that not all
>software is useable by all o
Perhaps I should try again, but when I tried using JEdit about a year ago (with
LilyPondTool, I think - is JEdit normally used without LilyPondTool?), it took so long to
load JEdit, that I said, "Forget it - I'm going back to ConTEXT." ConTEXT is
not perfect, but it works and works quickly f
Message: 7
> Date: Tue, 15 Jul 2008 01:33:01 +0200
> From: Bertalan Fodor <[EMAIL PROTECTED]>
> Subject: Re: nopc -- Proposed Predefines
> To: Trevor Daniels <[EMAIL PROTECTED]>
> Cc: lilypond-user@gnu.org, Carl Sorensen <[EMAIL PROTECTED]>
> Message-ID: <[EMAI
on 2008-07-14 at 23:20 Trevor Daniels wrote:
>> Non-command-line people should be using jedit anyway
>
>No I shouldn't. I have a text editing environment that has all the
>features I need for editing all my text files, and I have no intention
>of learning to use another just so I can turn off po
Trevor Daniels wrote:
Bertalan Fodor wrote
Yes, it has a quite impressive list of highlighters, also syntax
checking for php and html via plugins
(http://jedit.org/index.php?page=features). I must note however, that
jedit's highlighter configuration is regular-expression based, so it
doesn'
Bertalan Fodor wrote
Yes, it has a quite impressive list of highlighters, also syntax
checking for php and html via plugins
(http://jedit.org/index.php?page=features). I must note however, that
jedit's highlighter configuration is regular-expression based, so it
doesn't have such power that
Currently JEdit with LilyPondTool is the only editor for LilyPond
that provides syntax checking and autocompletion of tweaks. I
consider those such crucial features I can't image how other people
can work without it. So it may worth learning to use another. That
will be the last, I'm sure. Th
Am Dienstag, 15. Juli 2008 schrieb Bertalan Fodor:
> Currently JEdit with LilyPondTool is the only editor for LilyPond that
> provides syntax checking and autocompletion of tweaks. I consider those
> such crucial features I can't image how other people can work without
> it.
Apparently, you haven
Reinhold Kainhofer wrote:
Am Dienstag, 15. Juli 2008 schrieb Bertalan Fodor:
Currently JEdit with LilyPondTool is the only editor for LilyPond that
provides syntax checking and autocompletion of tweaks. I consider those
such crucial features I can't image how other people can work without
it.
Bertalan Fodor wrote
This argument is like: "I have all the predefined commands I need for
editing all my LilyPond files".
Not really. Using a *single* editor with which
I am very familiar and which has macros, easily
editable highlighers for most languages automatically
selected by file exte
This argument is like: "I have all the predefined commands I need for
editing all my LilyPond files".
Currently JEdit with LilyPondTool is the only editor for LilyPond that
provides syntax checking and autocompletion of tweaks. I consider those
such crucial features I can't image how other peo
Graham Percival wrote Monday, July 14, 2008 11:01 PM
I've never actually used jedit myself, but I'm quite impressed
with the screenshots and video showing off the advanced commands
(auto-completion, docs, etc). I think that most people *would*
be better served by using lilypondtool.
Perhaps
Graham Percival wrote Monday, July 14, 2008 6:40 PM
Non-command-line people should
be using jedit anyway, so they get the three-click toggle that Bert was
talking about.
No I shouldn't. I have a text editing environment that has all the features
I need for editing all my text files, and I ha
On Mon, 14 Jul 2008 23:39:31 +0200
Reinhold Kainhofer <[EMAIL PROTECTED]> wrote:
> Am Montag, 14. Juli 2008 schrieb Graham Percival:
> > On Mon, 14 Jul 2008 14:25:09 + (UTC)
> >
> > Given this difference, I'm not convinced that this predef is
> > really needed. Looking at the docs and finding
I don't think it's about forcing to use a specific editor. Personally I
love all editors that provide shortcuts, macros or whatever to ease
lilypond development. Unfortunately there is not many of them.
So I have the following points:
- put as many features into editors as you can
- put as many
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Montag, 14. Juli 2008 schrieb Graham Percival:
> On Mon, 14 Jul 2008 14:25:09 + (UTC)
>
> Carl Sorensen <[EMAIL PROTECTED]> wrote:
> > However, if we need to emphasize the
> > difference (that you can't have point and click on in part of your
>
On Mon, 14 Jul 2008 14:25:09 + (UTC)
Carl Sorensen <[EMAIL PROTECTED]> wrote:
> However, if we need to emphasize the
> difference (that you can't have point and click on in part of your
> music and off everywhere else), then perhaps it's better to have an
> entirely different construct, so \n
Valentin Villenave a écrit, Monday, July 14, 2008 7:25 PM,
2008/7/14 Trevor Daniels <[EMAIL PROTECTED]>:
Two good points. So why do we need \pointAndClickOn?
John Mandereau (whom I've just met with) has just given me an example
of a case where one would need a \pointAndClickOn:
suppose y
James E. Bailey wrote:
> personally, I like having predefined commands. I don't know how to
> say \key fis \major in scheme, and I don't want to know. Leaving
> that kind of predefined command to the editor forces everyone to use
> an (or /the/) editor that can send that kind of information. The
>
2008/7/14 Trevor Daniels <[EMAIL PROTECTED]>:
> Two good points. So why do we need \pointAndClickOn?
John Mandereau (whom I've just met with) has just given me an example
of a case where one would need a \pointAndClickOn:
suppose you have a default stylesheet file, called e.g. "layout.ly",
that
Trevor Daniels treda.co.uk> writes:
>
> Mark Knoop wrote Monday, July 14, 2008 9:56 AM
>
> > On Mon, 2008-07-14 at 02:21 +, Carl Sorensen wrote:
> >> Mats Bengtsson ee.kth.se> writes:
> >> OK, I'll bite.
> >>
> Two good points. So why do we need \pointAndClickOn?
> It is on by default,
Le 14 juil. 08 à 14:19, Bertalan Fodor (LilyPondTool) a écrit :
Well, the fun is that it seems that Scheme creators like predefined
commands as well. Think of the commands
cadr, caddr, cadddr, which are essentially:
(car (list-tail mylist 2)) (car (list-tail mylist 3)) (car (list-
tail mylis
Well, the fun is that it seems that Scheme creators like predefined
commands as well. Think of the commands
cadr, caddr, cadddr, which are essentially:
(car (list-tail mylist 2)) (car (list-tail mylist 3)) (car (list-tail
mylist 4))
In SRFI-1, the first extension of the Scheme language even inc
Am 14.07.2008 um 12:28 schrieb Carl D. Sorensen:
On 7/14/08 3:24 AM, "Nicolas Sceaux" <[EMAIL PROTECTED]> wrote:
Le 14 juil. 08 à 04:21, Carl Sorensen a écrit :
I propose some new predefined functions:
\pointAndClickOn
pointAndClickOn = #(ly:set-option 'point-and-click #t)
and
\point
On 7/14/08 3:24 AM, "Nicolas Sceaux" <[EMAIL PROTECTED]> wrote:
> Le 14 juil. 08 à 04:21, Carl Sorensen a écrit :
>
>> I propose some new predefined functions:
>>
>> \pointAndClickOn
>>
>> pointAndClickOn = #(ly:set-option 'point-and-click #t)
>>
>> and
>>
>> \pointAndClickOff
>>
>> pointAndCli
Mark Knoop wrote Monday, July 14, 2008 9:56 AM
On Mon, 2008-07-14 at 02:21 +, Carl Sorensen wrote:
Mats Bengtsson ee.kth.se> writes:
OK, I'll bite.
I propose some new predefined functions:
\pointAndClickOn
pointAndClickOn = #(ly:set-option 'point-and-click #t)
and
\pointAndClickOff
Le 14 juil. 08 à 04:21, Carl Sorensen a écrit :
I propose some new predefined functions:
\pointAndClickOn
pointAndClickOn = #(ly:set-option 'point-and-click #t)
and
\pointAndClickOff
pointAndClickOff = #(ly:set-option 'point-and-click #f)
These do not do what you think they do.
When the
On Mon, 2008-07-14 at 02:21 +, Carl Sorensen wrote:
> Mats Bengtsson ee.kth.se> writes:
> OK, I'll bite.
>
> I propose some new predefined functions:
>
> \pointAndClickOn
>
> pointAndClickOn = #(ly:set-option 'point-and-click #t)
>
> and
>
> \pointAndClickOff
>
> pointAndClickOff = #(ly:
personally, I like having predefined commands. I don't know how to say
\key fis \major in scheme, and I don't want to know. Leaving that kind
of predefined command to the editor forces everyone to use an (or the)
editor that can send that kind of information. The predefined commands
are a r
Very good point :-) This is my real question as well.
I remember this is not the first time that a new predefined command is
added (or requested) for something that could be better handled with the
editor.
Bert
James E. Bailey wrote:
I don't know if this is really crowding the LilyPond namesp
I don't know if this is really crowding the LilyPond namespace with a
feature that as far as I know is in one tool attached to a specific
editor. I mean, if that's the case, why have any editor features as
predefined commands in the first place?
Am 14.07.2008 um 09:26 schrieb Bertalan Fodor
Yeah, it was very difficult. Exactly 3 clicks in LilyPondTool since
years. (LilyPond > Source editing > Toggle point-and-click)
I don't think we should crowd the LilyPond command namespace with editor
features.
Bert
James E. Bailey wrote:
Am 14.07.2008 um 04:21 schrieb Carl Sorensen:
Mat
Am 14.07.2008 um 04:21 schrieb Carl Sorensen:
Mats Bengtsson ee.kth.se> writes:
James E. Bailey wrote:
in 3.1.3
#(ly:set-option 'point-and-click #f)
The last one is apparently deprecated.
Why? The first two are only interesting if you have your own standard
include file with utility f
2008/7/14 Carl Sorensen <[EMAIL PROTECTED]>:
> OK, I'll bite.
>
> I propose some new predefined functions:
>
> \pointAndClickOn
>
> pointAndClickOn = #(ly:set-option 'point-and-click #t)
>
> and
>
> \pointAndClickOff
>
> pointAndClickOff = #(ly:set-option 'point-and-click #f)
>
>
>
>
> If I get app
Mats Bengtsson ee.kth.se> writes:
>
> James E. Bailey wrote:
>
> >
> > in 3.1.3
> > #(ly:set-option 'point-and-click #f)
> >
> > The last one is apparently deprecated.
>
> Why? The first two are only interesting if you have your own standard
> include file with utility functions. I guess that
36 matches
Mail list logo
