You could use search/replace, which works in many editors, including
Frescobaldi.
Sorry to just jump in here, but in Frescobaldi 3.1.3 and still in 3.2
the search and replace does not work properly, at least under Windows.
The entered search term is not colored correctly in the code window, and
replacing it does not work either. It is always marked one character
further to the left, so it is marked offset, which is why I had to use
the editor (=Windows on-board tools). I had also reported this some time
ago on GitHub (https://github.com/frescobaldi/frescobaldi/issues/1366),
because the feature search and replace is very important in my opinion.
Unfortunately, I don't know from which version the error occurred, but
it once worked correctly.
On macOS it seems to work, on Linux I don't know.
Andreas
PS apart from that, Frescobaldi is the very best LilyPond tool in my
humble opinion.
Am 26.07.2022 um 22:47 schrieb Jean Abou Samra:
Le 26 juil. 2022 à 22:46, John Ramsey<[email protected]> a écrit :
So, is this Frescobaldi thing something that can convert the apostrophes that
are scattered throughout the old lyric files I'm working from?
You could use search/replace, which works in many editors, including
Frescobaldi.
On Tue, Jul 26, 2022 at 4:24 PM Jean Abou Samra<[email protected]> wrote:
Le 26 juil. 2022 à 22:16, John Ramsey<[email protected]> a écrit :
Thanks. I was just trying to do what I used to do before version 22. I could
transfer my musical thoughts to a word document anywhere I happened to be, not
just my own computer.
You can edit raw text on any computer. On Windows, the Windows Notepad fits the
bill. On Linux, the default graphical raw text editor varies but is often
Gedit. On macOS, the Textedit app works if I recall correctly.
And what's this? No more LilyPad in 7 months??
Bari
Yes. You’ll need either an editor with support for LilyPond (there are many,
seehttps://lilypond.org/easier-editing.html) or to run LilyPond on the command
line.
Everything’s a tradeoff, and this one gave us an enormously more reliable setup
that allows releases not to be blocked because cross-compilation would not
work, as happened in the past. Also, it produces 64-bit binaries, so they’ll be
faster.
On Tue, Jul 26, 2022 at 4:00 PM Jean Abou Samra<[email protected]> wrote:
2. I do some of my rough drafts in MSWord and transfer the notations to
LilyPad. BUT as of version 22, I have a problem with quotation marks and
apostrophes. MSWord uses curly quote marks and curly apostrophes as a
default, which I would hate to change. And LilyPad is now only recognizing
straight ones. Curly commas are OK, but I have to manually change the
quotes and apostrophes after transferring the text to the .ly document, in
order to prevent strings of weird code. I always miss a couple, which
drives me nuts. (I'm halfway there as it is.) Can this be put back the way
it was?
Simple: don’t use MS Word to edit LilyPond code. A rich text editor is not a
good tool to edit raw text. Taking an analogy, this request sounds a bit as if
you were trying to cut bread with your fingernails and complained that your
nail varnish prevented you from doing that. Just don’t do it that way :-)
Do you have any particular reason not to use LilyPad all way through?
At any rate, LilyPad is gone in 2.23, we now only distribute binaries of
LilyPond, without a minimalistic GUI. Instead, we recommend editors like
Frescobaldi. I strongly recommend you try it, for me it was a relief.
All the best,
Jean
Respectfully submitted,
Bari Ramsey
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
