LGTM, please push directly to staging
http://codereview.appspot.com/5505059/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On Sat, 2010-06-19 at 12:00 -0400, lilypond-devel-requ...@gnu.org wrote:
> From: Laura Conrad
> Subject: Re: How to develop Emacs mode?
> To: Nicolas Sceaux
> Cc: David Kastrup , lilypond-devel@gnu.org
> Message-ID: <87wrtvazky@laymusic.org>
> Content-Type: text
Nicolas Sceaux writes:
> Le 19 juin 2010 à 16:15, David Kastrup a écrit :
>
>> Nicolas Sceaux writes:
>>
>>> Le 19 juin 2010 à 14:23, David Kastrup a écrit :
>>>
It would appear that you work on MacOSX or so. Can you check whether
some variation of the Midi test code using make-seri
Le 19 juin 2010 à 16:15, David Kastrup a écrit :
> Nicolas Sceaux writes:
>
>> Le 19 juin 2010 à 14:23, David Kastrup a écrit :
>>
>>> It would appear that you work on MacOSX or so. Can you check whether
>>> some variation of the Midi test code using make-serial-process I posted
>>> recently c
Nicolas Sceaux writes:
> Le 19 juin 2010 à 14:23, David Kastrup a écrit :
>
>> It would appear that you work on MacOSX or so. Can you check whether
>> some variation of the Midi test code using make-serial-process I posted
>> recently could be made to work on your setup? If it did, this would b
> "Nicolas" == Nicolas Sceaux writes:
Nicolas> Several years ago, I used a midi keyboard to enter the notes: one
hand
Nicolas> on the midi keyboard, and one hand on the computer keyboard, to set
Nicolas> durations, because I'm a lame keyboard player. But it turned out
that
patible with your plans
> (which may include copyright assignment) to have a full-featured
> Lilypond mode eventually appear upstream in Emacs, I'd just try joining
> forces with you.
I'm not protective about this emacs mode. Just interested in having
something as effective as p
Nicolas Sceaux writes:
> Le 17 juin 2010 à 17:31, David Kastrup a écrit :
>
>> Carl Sorensen writes:
>>
>>> On 6/17/10 8:59 AM, "David Kastrup" wrote:
>>>
I have a question about developing Emacs input and major modes for
Lilypond. What would be the right way to go forward for me?
Le 17 juin 2010 à 17:31, David Kastrup a écrit :
> Carl Sorensen writes:
>
>> On 6/17/10 8:59 AM, "David Kastrup" wrote:
>>
>>>
>>>
>>> Hi,
>>>
>>> I have a question about developing Emacs input and major modes for
>>> Lilypond. What would be the right way to go forward for me?
>>>
>>> I
Graham Percival writes:
> On Thu, Jun 17, 2010 at 09:08:35AM -0600, Carl Sorensen wrote:
>>
>> On 6/17/10 8:59 AM, "David Kastrup" wrote:
>> > Moving existing Lilypond mode stuff into Emacs upstream will require
>> > copyright assignments to the FSF. A fast hunch whether authors of the
>> > cu
On Thu, Jun 17, 2010 at 09:08:35AM -0600, Carl Sorensen wrote:
>
> On 6/17/10 8:59 AM, "David Kastrup" wrote:
> > Moving existing Lilypond mode stuff into Emacs upstream will require
> > copyright assignments to the FSF. A fast hunch whether authors of the
> > current Lilypond mode can be determ
Carl Sorensen writes:
> On 6/17/10 8:59 AM, "David Kastrup" wrote:
>
>>
>>
>> Hi,
>>
>> I have a question about developing Emacs input and major modes for
>> Lilypond. What would be the right way to go forward for me?
>>
>> I want to make use of current Emacs features (like semantic parsing
On 6/17/10 8:59 AM, "David Kastrup" wrote:
>
>
> Hi,
>
> I have a question about developing Emacs input and major modes for
> Lilypond. What would be the right way to go forward for me?
>
> I want to make use of current Emacs features (like semantic parsing and
> similar). I also want to c
Hi,
I have a question about developing Emacs input and major modes for
Lilypond. What would be the right way to go forward for me?
I want to make use of current Emacs features (like semantic parsing and
similar). I also want to create input methods for inputting on the
keyboard in chromatic bu
Well, now that lilypond can compile a file in emacs, I've been looking
around, getting myself acquainted with the various options.
Apparently, the 2tex option calls lilypond as lilypond -b tex
filename.ly The version of lilypond that I have installed says that
should be -f tex (assuming I'm
Milan Zamazal wrote:
"NS" == Nicolas Sceaux <[EMAIL PROTECTED]> writes:
NS> Using in Emacs 22.0.50.1, I applied the following patch.
The following additional patch seems to be needed to avoid an error in
post-command-hook:
-
> "NS" == Nicolas Sceaux <[EMAIL PROTECTED]> writes:
NS> Using in Emacs 22.0.50.1, I applied the following patch.
The following additional patch seems to be needed to avoid an error in
post-command-hook:
--- lilypond0/lilypond-font-lock.el 2005-10-13 11:12:36.0 +0200
+++ lilypond
On 12/10/05, Heikki Johannes Junes <[EMAIL PROTECTED]> wrote:
On Tue, 11 Oct 2005 21:42:37 +0200 Jan Buchal <[EMAIL PROTECTED]> wrote:Seems like 21.4 is the current stable release, and I have not used CVS Emacs.Therefore, patches for LilyPond's Emacs files are welcome. The type of changes
needed be
Heikki Johannes Junes <[EMAIL PROTECTED]> writes:
> On Tue, 11 Oct 2005 21:42:37 +0200 Jan Buchal <[EMAIL PROTECTED]> wrote:
>
>> Hello,
>>
>> we develop Free Software for blind and we have several blind users
>> who use Emacs Lilypond mode.
>
> This is a good thing.
>
>> Now we have problem wit
> "HJJ" == Heikki Johannes Junes <[EMAIL PROTECTED]> writes:
HJJ> On Tue, 11 Oct 2005 21:42:37 +0200 Jan Buchal <[EMAIL PROTECTED]>
wrote:
>> Hello,
>>
>> we develop Free Software for blind and we have several blind
>> users who use Emacs Lilypond mode.
HJJ> This is
On Tue, 11 Oct 2005 21:42:37 +0200 Jan Buchal <[EMAIL PROTECTED]> wrote:
> Hello,
>
> we develop Free Software for blind and we have several blind users
> who use Emacs Lilypond mode.
This is a good thing.
> Now we have problem with Lilypond mode
> and CVS Emacs. In Emacs 22.xx are changed som
how the emacs- lilypond mode works for recent versions
(Lily:2.6 -emacs:21.3)?
information I got through searches are quite old..
what should I do to have it working under winXP
Best Regards,
Mehmet Okonsar, pianist-composer
www.okonsar.com
___
lilypon
> Here is another patch. This one also changes the defaults
> for LilyPond-command-master: it makes sure that a command
> doesn't get run needlessly, by checking the filestamps
> (of the buffer and the master file).
>
> Greetings,
Applied. Thanks.
BTW, should that lilypond
>
> If there are any questions, feel free to ask.
>
Applied. Thanks for the patch.
Comparing Emacs and XEmacs, I found that braces { and } have different colors. Would
it be
possible to force them (non-bold) red?
Greetings,
Heikki Junes
_
On Thu, 06 May 2004 01:19:29 +0200 (CEST) [EMAIL PROTECTED] wrote:
> Hello everybody,
> (Ik neem aan dat deze lijst in het engels is)
>
> Thanks for the great work.
> I have made some improvements to the emacs lisp files.
> Basicly the following:
>
> ...
>
> Here is the patch. (I am
Hello everybody,
(Ik neem aan dat deze lijst in het engels is)
Thanks for the great work.
I have made some improvements to the emacs lisp files.
Basicly the following:
- removed font-lock-warning-face
(it looks really bad in my xemacs, and should anyway only be
used for warnings).
- added a
Also, for all people installing from RPM:s, Debian packages or
some other prepackaged form of Lilypond, the package will
hopefully install the files in some directory that's already
included in the load-path, which makes the suggested instruction
less relevant. Probably, the people who build and
[EMAIL PROTECTED] writes:
>
> The part of documentation which deals how to install Emacs-mode for
> LilyPond could be shorter and more informative for an user. The following
> is needed to install it as a user:
Well, you have CVS access now, so you can fix it :-). Your proposal i
> "Heikki" == Heikki Johannes Junes <[EMAIL PROTECTED]> writes:
Heikki> Copy lilypond-mode.el, lilypond-font-lock.el and
Heikki> lilypond-indent.el to ~/site-lisp/ and lilypond-init.el to
Heikki> ~/site-lisp/site-init.d/.
What I did was add my CVS lilypond directory to load-path,
The part of documentation which deals how to install Emacs-mode for
LilyPond could be shorter and more informative for an user. The following
is needed to install it as a user:
Add "~/site-lisp" to load-path with the following line in ~/.emacs:
(setq load-path (append (list (expand
> It Would Be Nice if the emacs mode also was adapted to the new LaTeX
> mode.
>
> (And if applicable, the manual. Haven't checked.)
??? What new LaTeX mode? I've always used AUCTeX for editing
LaTeX in emacs.
/Mats
___
It Would Be Nice if the emacs mode also was adapted to the new LaTeX
mode.
(And if applicable, the manual. Haven't checked.)
Any takers?
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.cs.uu.nl/~hanwen
___
Lilypond-devel ma
> I have a tiny annoyance in the emacs mode which usually makes revert
> to the command line: when I have lily-tex-xdvi'd a file, I usually
> make some edits to the .ly file. When I press C-c C-c I would expect
> the emacs mode to detect the edits, and suggest that I run
I have a tiny annoyance in the emacs mode which usually makes revert
to the command line: when I have lily-tex-xdvi'd a file, I usually
make some edits to the .ly file. When I press C-c C-c I would expect
the emacs mode to detect the edits, and suggest that I run LilyPond
again. Currently
[EMAIL PROTECTED] writes:
>
> Just for fun, I made the following interface for Emacs which saves some
> keystrokes when you write a sequence of notes.
added.
--
Han-Wen Nienhuys | [EMAIL PROTECTED]| http://www.cs.uu.nl/~hanwen/
___
Lilypon
[EMAIL PROTECTED] writes:
>
> Just for fun, I made the following interface for Emacs which saves some
> keystrokes when you write a sequence of notes.
thanks, put it in.
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.cs.uu.nl/~hanwen
___
Just for fun, I made the following interface for Emacs which saves some
keystrokes when you write a sequence of notes.
Index: VERSION
===
RCS file: /home/lilypond/lilypond/VERSION,v
retrieving revision 1.399
diff -p -u -r1.399 VERSI
On Fri, 19 Apr 2002, Rune Zedeler wrote:
> Strange. I opgraded to emacs 21.2.1 - and now (hjj5) the multiline
> scheme is completely out of order - doesn't even work after C-c f... :-/
>
> -Rune
>
There would be a better way to recognize scheme which would work more
reliably than regexps: Simp
Heikki Johannes Junes wrote:
> After the last patch sent by me (-hjj5) fontifying works with Emacs
> version 21.1.1 and helps _a lot_ to find out typos. As already mentioned,
> font-locking could be implement a more clever way.
Strange. I opgraded to emacs 21.2.1 - and now (hjj5) the multiline
> Heikki, I don't think there's any need for those complicated regexps for
> matching strings and comments. If you remove "font-lock-keywords-only",
> the fontification works perfectly well using just the syntax table, and
> it recognises strings within strings, comments within comments...
Hmm. B
On Tue, Apr 16, 2002 at 10:01:12PM +0200, Rune Zedeler wrote:
> Chris Jackson wrote:
>
> >Because they're recognised by the syntax table, and don't need a
> >multi-line regexp to match them. As they should in lilypond...
>
> How comes that c++ comments are easier to recognise than
> lilypond-c
Chris Jackson wrote:
> Because they're recognised by the syntax table, and don't need a
> multi-line regexp to match them. As they should in lilypond...
How comes that c++ comments are easier to recognise than
lilypond-comments...???
-Rune
___
Lil
Heikki Johannes Junes wrote:
>>Hmmm, then why does C-mode multi line comments work?
> Hmmm. You are right.
> + Set 'font-lock-multiline' true.
What should that do?
I get no difference...
-Rune
___
Lilypond-devel mailing list
[EMAIL PROTECTED
On Tue, Apr 16, 2002 at 08:36:20PM +0200, Rune Zedeler wrote:
> Heikki Johannes Junes wrote:
>
> >>When the mode is invoked (when a file is read or with M-x LilyPond-mode)
> >>then all multi-line schemes and multi-line comments are correctly
> >>parsed. But if you edit any of those - or create
> Hmmm, then why does C-mode multi line comments work?
Hmmm. You are right.
Index: VERSION
===
RCS file: /home/lilypond/lilypond/VERSION,v
retrieving revision 1.385
diff -u -p -r1.385 VERSION
--- VERSION 16 Apr 2002 11:58:57 -
Heikki Johannes Junes wrote:
>>When the mode is invoked (when a file is read or with M-x LilyPond-mode)
>>then all multi-line schemes and multi-line comments are correctly
>>parsed. But if you edit any of those - or create a new one - then the
>>colouring gets wrong.
> Yes. This is problem of
[EMAIL PROTECTED] writes:
>
> The patch helps to proof-read the source by using colors (for example,
> erronous "a,." now easier to see by an eye). Further comments within.
>
> This patch is against latest CVS. I consider my earlier patch (-hjj2),
> which was sent to HWN, not merged.
I had som
There was a copy paste-error. Below is the correct patch. Now menus work
the right way.
Index: lilypond-mode.el
===
RCS file: /home/lilypond/lilypond/lilypond-mode.el,v
retrieving revision 1.33
diff -p -u -r1.33 lilypond-mode.el
--
>Well, I hope that the emacs mode will end up being able to fully cope
>with multi line comments and multiline scheme.
>When the mode is invoked (when a file is read or with M-x LilyPond-mode)
>then all multi-line schemes and multi-line comments are correctly
>parsed. But if
Well, I hope that the emacs mode will end up being able to fully cope
with multi line comments and multiline scheme.
When the mode is invoked (when a file is read or with M-x LilyPond-mode)
then all multi-line schemes and multi-line comments are correctly
parsed. But if you edit any of those
The patch helps to proof-read the source by using colors (for example,
erronous "a,." now easier to see by an eye). Further comments within.
This patch is against latest CVS. I consider my earlier patch (-hjj2),
which was sent to HWN, not merged.
Index: VERSION
[EMAIL PROTECTED] writes:
>
> Is the following idea correct ?
> - Block comments can have also ordinary comments inside.
You can have lines starting with % in %{ %}, but they are not treated
especially.
--
Han-Wen Nienhuys | [EMAIL PROTECTED]| http://www.cs.uu.nl/~hanwen/
__
Is the following idea correct ?
- Block comments can have also ordinary comments inside.
For me it seems reasonable.
Index: VERSION
===
RCS file: /home/lilypond/lilypond/VERSION,v
retrieving revision 1.381
diff -p -u -r1.381 VERSIO
This fixes a silly bug in Emacs indentation (open new .ly file,
type \score { , and get an error message)
--
chris
Index: ChangeLog
===
RCS file: /home/lilypond/lilypond/ChangeLog,v
retrieving revision 1.62
diff -p -u -r1.62 Chan
Inspired by LaTeX-mode, there is now new grouping in menus which separates
commands which execute something outside Emacs ("Command"-menu) and
commands which edit the buffer ("LilyPond"-menu"). New feature is
un-comment-region.
--- VERSION.~1.375.~Mon Apr 8 23:51:12 2002
+++ VERSION Tue
I've been playing with elisp again. This patch restores the blinking of
matching open parentheses, which broke when I did the indentation stuff.
Blinking should work for ) } > and ], with warnings when } and > are
unbalanced. Although I haven't emulated the fancy 'show-paren-mode'
(which highlight
Here is an update for font-lock-keywords in Emacs-mode. It covers most new
keywords added to LilyPond. I also removes some non-keywords.
In manual, at Articulation page:
http://lilypond.org/development/Documentation/user/out-www/lilypond/Articulations.html#Articulations
there are non-visible
> Citat Chris Jackson <[EMAIL PROTECTED]>:
>
> > comments). A similar problem occurs with () meaning either Scheme or
> > a
> > phrasing-slur, depending on context, and the emacs syntax table
> > doesn't understand context.
>
> Well, I don't think it matters whether a paren is a slur or a sche
Citat Chris Jackson <[EMAIL PROTECTED]>:
> comments). A similar problem occurs with () meaning either Scheme or
> a
> phrasing-slur, depending on context, and the emacs syntax table
> doesn't understand context.
Well, I don't think it matters whether a paren is a slur or a scheme-paren, does
i
On Mon, Mar 18, 2002 at 01:28:07PM +0100, Rune Zedeler wrote:
> Finally I installed the new emacs-mode.
> The worst thing is that it only matches the curly brackets (and not '[]'
> '()' or '<>').
> Please fix at least '<>' before 1
Finally I installed the new emacs-mode.
The worst thing is that it only matches the curly brackets (and not '[]'
'()' or '<>').
Please fix at least '<>' before 1.6
-Rune
___
Lilypond-devel mailin
Chris Jackson <[EMAIL PROTECTED]> writes:
> OK - the patch below (relative to my previous patch) sorts out some of the
> speed problems, and replaces a bloated and inefficient function... It can
> still struggle with .ly files over 20K, though.
Ok, thanks.
Jan.
--
Jan Nieuwenhuizen <[EMAIL PR
Chris Jackson <[EMAIL PROTECTED]> writes:
> The problem comes when I have largish source files, looking like, say,
>
> thing = \notes {
> (20 lines)
> }
>
> nextthing = \notes {
> (20 lines)
> }
>
> ... (about 10 of these)
>
> and I select the block at the bottom of the file and run indent-regi
On Thu, Jan 24, 2002 at 11:20:42AM +0100, Jan Nieuwenhuizen wrote:
> I must say that the speed is not too bad. On my fairly old G3/233MHz,
> it feels comparable with c-mode's indenting speed.
OK - the patch below (relative to my previous patch) sorts out some of the
speed problems, and replaces
On Thu, Jan 24, 2002 at 11:20:42AM +0100, Jan Nieuwenhuizen wrote:
> Chris Jackson <[EMAIL PROTECTED]> writes:
>
> > OK - The code below is a first attempt at indentation for lilypond-mode.
>
> Wow. That first attempt seems to work quite well, at first try!
Excellent.
> > The problem with th
acke@@gmx.de, Bjoern Jacke}
German glossary stuff.
+@item @email{chris@@fluffhouse.org.uk, Chris Jackson},
+Emacs mode indentation, directed arpeggios.
@item @email{nj104@@cus.cam.ac.uk, Neil Jerram}.
parts of Documentation/Vocab*
@item @email{heikki.junes@@hut.fi, Heikki Junes}.
>
rman glossary stuff.
+ * Chris Jackson <[EMAIL PROTECTED]> Emacs mode indentation,
+ directed arpeggios
+
* Neil Jerram <[EMAIL PROTECTED]>. parts of
Documentation/Vocab*
diff -purN lilypond-1.5.28/lilypond-font-lock.el
lilypond-1.5.28-new/lilypond-font-lock.el
_LEVEL=hjj2
# use the above to send patches: MY_PATCH_LEVEL is always empty for a
# released version.
--- CHANGES~Wed Oct 10 01:33:39 2001
+++ CHANGES Thu Oct 11 03:44:01 2001
@@ -1,5 +1,7 @@
-1.5.16.hjj1
+1.5.16.hjj2
===
+
+* Emacs-mode: Inserting tags
* Enable python2.1/Pyt
[EMAIL PROTECTED] writes:
>
> Here is a patch which makes the typesetting with Emacs nicer for an eye.
> Identifiers are separated from keywords and some dynamics are included in
> the font-locking. I make a forecast that this patch makes typing with
> Emacs even a bit more fun!
thanks. I put in
.hjj1
+1.5.9.hjj2
==
-* Emacs-mode: Keyboard shortcuts
+* Emacs-mode: Keyboard shortcuts, separated identifiers from keywords
+and spacing not necessary in font-locking.
1.5.8.uu1
=
--- lilypond-1.5.9.patched/lilypond-font-lock.elMon Sep 3 16:40:14 2001
+++ lilypond
Sorry about the misspelling.
--- lilypond-1.5.9.patched/lilypond-mode.el Wed Sep 12 02:39:51 2001
+++ lilypond-1.5.9.NEW/lilypond-mode.el Wed Sep 12 02:40:27 2001
@@ -422,7 +422,7 @@
(define-key LilyPond-mode-map "\C-c\C-c" 'LilyPond-command-master)
(define-key LilyPond-mode-map "\C-c\
I made keyboard shortcuts for Emacs-mode. The keyboard bindings are shown
shown in the "Command"-menu. This was inspired by long-time experience of
LaTeXing with Emacs. Here is the patch...
--- lilypond-1.5.9/CHANGES Sat Sep 8 21:11:09 2001
+++ lilypond-1.5.9.NEW/CHANGES Wed Se
72 matches
Mail list logo
