Hi again Fennel,
I tried to install oil.nvim to see if it messed with completion, but everything
worked as it should out of the box. I'm strongly suspecting there's something
fishy going on with how and/or from where your dictionaries are being pulled.
Best,
Kenneth
Fennel, Jun 06, 2024 at
Excellent. That looks like what I want. it's a little more
sophisticated coding wise than I would have come up with... but I can
hide that in an include file.
I will give this a try this weekend and how it work on a full piece and
when I add the chord names above the tab staff.
Thanks,
PS forgot to include the output pdf.
On Thu, Jun 6, 2024 at 5:12 PM ming tsang wrote:
> Dear Valentin,
>
> The "%\rouded-box" is a misplaced typo. Once I delete the \rounded-box
> trom the code you sent me, it works A-ok. Your code answers my two
> questions.
> I might try to put a rounded-box
Dear Valentin,
The "%\rouded-box" is a misplaced typo. Once I delete the \rounded-box trom
the code you sent me, it works A-ok. Your code answers my two questions.
I might try to put a rounded-box on the two markups.
On Thu, Jun 6, 2024 at 4:26 PM Valentin Petzel wrote:
> Hello,
>
> Do you
Hello,
Do you mean something like this:
\version "2.24.3"
\markup\line {
\circle" 1. "
\box \override #'(line-width . 40) \fill-line { "\t\musicglyh \tlsr?" } %
\rounded-box
}
\markup \vspace #0.75
Cheers,
Valentin
Am Donnerstag, 6. Juni 2024, 23:16:51 MESZ schrieb ming tsang:
> Dear
Hello Walt,
rather than switching between staves with different tunings, why not simply
hide Staff lines if not required?
Use \stopStaff and \startStaff to change line positions. See the appended file
for details.
Cheers,
Valentin
Am Donnerstag, 6. Juni 2024, 19:25:45 MESZ schrieb Walt
I was playing around with drawing regular polygons, which led to
creating a new markup command with several configurable options. (Some
of these options are inherited via the built-in \polygon command.)
There might be a few things to tighten up, but I believe it is in a
pretty workable
Dear Lilyponders,
I have two markups printed in two lines.
questions:
1.. How to print the two markups side-by-side on one line
2.. How to shorten the fill-line or have an arg to determine the width.
Here is the lily markup code:
\version "2.24.3"
\markup\circle" 1. "
\markup \box \fill-line {
Well... I'm getting closer.
I got the alignment to work by adding two dummy string values at the
top. That looks like it makes the result line up without showing the two
dummy lines at the top.
Now if I could just the get lines to show for the two low strings on the
notes that need them to
Hello everyone,
these are really a lot of suggestions, I will try them out and then get
back to you.
Am Do., 6. Juni 2024 um 11:05 Uhr schrieb Kenneth Flak <
kennethf...@protonmail.com>:
> This issue seems related:
>
> https://github.com/uga-rosa/cmp-dictionary/issues/58
>
> Fennel, Jun 06, 2024
This issue seems related:
https://github.com/uga-rosa/cmp-dictionary/issues/58
Fennel, Jun 06, 2024 at 11:51:
> It seems like cmp-dictionary doesn’t play nice with oil.nvim, and I
> am not
> removing that to make this work unfortunately. Here’s a stack trace if
> you’re
> interested:
>
> Error
I stopped using oil.nvim some time ago, as it started getting all buggy and
weird
on me... My new favorite file manager is yazi, which also has an nvim plugin :-)
https://yazi-rs.github.io/
How does your cmp-dictionary setup look like?
Fennel, Jun 06, 2024 at 11:51:
> It seems like
It seems like cmp-dictionary doesn’t play nice with oil.nvim, and I am not
removing that to make this work unfortunately. Here’s a stack trace if you’re
interested:
Error executing luv callback:
...vim/lazy/cmp-dictionary/lua/cmp_dictionary/dict/trie.lua:43: bad argument
#1 to 'decode'
I’m using analysis brackets as shown in the snippet below:
\version "2.24.3"
\layout {
\context { \Voice \consists Horizontal_bracket_engraver } }
\relative c' {c1 \startGroup | \break
c1 \stopGroup
}
which produces the following output:
[image.png]
I would like for the bracket
Hi Fennel,
I'm using the cmp-dictionary approach, which works fine for me. I wasn't aware
that it's archived, which is a shame... In order for it to work I did have to
specify an absolute path to the dictionaries, though:
local basepath =
ok - here is a made up example. Code and screenshot are below.
Let's say I had a very short piece of 5 bars.
4 bars can be played fine on the upper six strings.
But there is one bar that dips down into a couple of lower notes needing
to be played on 7th and 8th strings.
If this were a
The plugin that Kenneth mentions (which I am also using at the moment) is
rather quite broken as far as Emacs or Frescobaldi-style autocompletion is
concerned.
[nvim-lilypond-suite](https://github.com/martineausimon/nvim-lilypond-suite)
strongly recommends the use of `coc.nvim`, which is not
Walt North writes:
> I occasionally write out Tab notation parts for 6 or 8 string lap
> steel guitar. I have created tuning entries for these and it works
> well using Minimum fret and max fret difference values. Here is my
> question. 90% of the time I only need the upper six strings and just
18 matches
Mail list logo
