Cool! TBH I've not used point-and-click much, but according to the
documentation it should work both ways:
https://github.com/martineausimon/nvim-lilypond-suite/wiki/2.-Configuration#point-and-click
Roosna & Flak
Contemporary Dance & Music
https://roosnaflak.com
Original Message
On Thu, May 2, 2024 at 1:10 PM Pierre-Luc Gauthier
wrote:
> > {
> > s2...\< s16\! |
> > }
> > ...that I do it almost automatically.
>
> Try that in 12/8 :-)
>
{
\time 12/8
s1*23/16\< s16\! | % ??
}
Yeah, I see your point. ;)
--
Knute Snortum
Sounds like just the VSLilyPond-PDF-Preview extension is not being
maintained. I'll take a look at that tonight...thanks, Federico!
On Thu, May 2, 2024 at 4:41 PM Federico Sarudiansky
wrote:
> Hi Jeff.
>
> I've been using VSLilypond for VSCode for a while now and I found a
> solution for the
No it's only a one way point-and-click from the pdf and not as smooth
and fast as Fresco.
It's not as complete as Fresco but when you're a vim-centric guy on
different project your're looking for interaction with your linux system
and this plugin becomes really helpful for that.
And his
Hi Jeff.
I've been using VSLilypond for VSCode for a while now and I found a
solution for the annoying lack of refresh of the PDF output. It is here:
https://github.com/lhl2617/VSLilyPond-PDF-preview/pull/118
Basically you have to edit a file of the Lilypond PDF preview extension
And while you are about to extend the 'Easier Editing' section: maybe
for the Mac users in particular one might want to add the combination
of TeXShop/LaTeX and Skim/Preview. I had a Mac until about 12 years ago
when I started to use LilyPond. That was on Mac OS 10.4, before I left
the Apple
Le jeu. 2 mai 2024, à 15 h 20, Knute Snortum a écrit :
> I use a different context for all my dynamics and I've gotten so used to
> typing...
I do too. For bowing, nuances, articulations, etc. Btw I use quite a
lot of \quoting and \tagging for that.
> {
> s2...\< s16\! |
> }
> ...that I do
I kicked the tires with VScode and the VSLilypond extension set, and it
worked pretty well. I'm not sure I figured out how to *automagically* update
the PDF display, all I had to do was to close and reopen the file and it
was there. Clicking on a note in the PDF viewer took me right to the text
This looks really good, Ken. I'm going to do a general tidy up on the
Easier Editing page, but I hope to have something up for review in a day
or two. I've installed neovim, but to save a bit of time: is the
point-and-click two-way, like Frescobaldi, or from PDF to code only?
Cheers,
Colin
Well done Kenneth! I don't have anything better to say.Maybe asking
Simon Martineau is thoughts about that.And thanks to Werner for the
proposal.It feels a little bit like I'm a part of the game, haha. I have
more than 20 scores to transpose on lilypond so I'm here to stay a
little longer and
On Thu, May 2, 2024 at 10:31 AM Pierre-Luc Gauthier <
p.luc.gauth...@gmail.com> wrote:
> Le jeu. 2 mai 2024, à 13 h 08, Knute Snortum a écrit
> :
> > Perhaps I'm not getting the need for this command as you could using an
> empty chord at the end of the repeat to do the same thing:
> >
> > {
> >
Maybe one addition:
fromEnd =
#(define-music-function (delta ev mus) (ly:duration? ly:music? ly:music?)
(_i "Add music @var{ev} with a distance of @var{delta} before the end of
@var{ev} is usually a post-event.")
#{
\context Bottom
<<
{
\skip
Thanks Lukas,
Le jeu. 2 mai 2024, à 13 h 29, Lukas-Fabian Moser a écrit :
> fromEnd =
> #(define-music-function (delta ev mus) (ly:duration? ly:music? ly:music?)
>(_i "Add music @var{ev} with a distance of @var{delta} before the end of
>
> @var{ev} is usually a post-event.")
>#{
>
Le jeu. 2 mai 2024, à 13 h 08, Knute Snortum a écrit :
> Perhaps I'm not getting the need for this command as you could using an empty
> chord at the end of the repeat to do the same thing:
>
> {
> <>(\<
> \after 2 \>
> \repeat unfold 8 {e''16 d''} <>)\!|
> }
The above example would not
Hi Pierre-Luc,
Am 02.05.24 um 17:02 schrieb Pierre-Luc Gauthier:
Rambling here :
So, I *love* the simplicity and elegance of the \after command and I
am using it pretty much everywhere.
{
<>(
<>\<
\after 2 \>
\after 16*15 )
\after 16*15 \!
\repeat unfold 8 {e''16 d''} |
}
On 2 May 2024, at 19:08, Knute Snortum wrote:On Thu, May 2, 2024 at 8:04 AM Pierre-Luc Gauthier wrote:Rambling here :
So, I *love* the simplicity and elegance of the \after command and I
am using it pretty much everywhere.
{
<>(
<>\<
\after 2 \>
\after 16*15
Glad to hear that the description is useful for you!
I agree, the website is not great at onboarding new users...
Best,
Kenneth
Raphael Mankin, May 02, 2024 at 20:07:
> This is a much better description of Neovim than exists on any of the
> Neovim web-sites. They all jump straight into detail
On Thu, May 2, 2024 at 8:04 AM Pierre-Luc Gauthier
wrote:
> Rambling here :
>
> So, I *love* the simplicity and elegance of the \after command and I
> am using it pretty much everywhere.
>
> {
> <>(
> <>\<
> \after 2 \>
> \after 16*15 )
> \after 16*15 \!
> \repeat unfold 8 {e''16
This is a much better description of Neovim than exists on any of the
Neovim web-sites. They all jump straight into detail without telling one
what the whole thing is about. I struggled to work out what Neovim is,
or why I should want to use it.
On 02/05/2024 05:33, Kenneth Flak wrote:
OK,
Rambling here :
So, I *love* the simplicity and elegance of the \after command and I
am using it pretty much everywhere.
{
<>(
<>\<
\after 2 \>
\after 16*15 )
\after 16*15 \!
\repeat unfold 8 {e''16 d''} |
}
and since then I often end up doing head math to figure out what I
must add
On Wed, May 1, 2024 at 10:55 PM Robert Garrigos wrote:
> Oh this is a bit embarrassing, such a basic error….. sorry, I never
> realized that the parenthesis needs to be right after the first note.
>
Nothing to be embarrassed about. It takes some getting used to.
--
Knute Snortum
21 matches
Mail list logo