date:20190129

Fwd: [Frescobaldi] Re: export the user guide to HTML (issue 825)

2019-01-29 Thread Urs Liska

Forwarding this to lilypond-user because I think not all potential 
addressees are also subscribed to the Frescobaldi mailing list ...



 Weitergeleitete Nachricht 
Betreff:[Frescobaldi] Re: export the user guide to HTML (issue 825)
Datum:  Tue, 29 Jan 2019 23:34:24 -0800 (PST)
Von:g...@ursliska.de
Antwort an: frescoba...@googlegroups.com
An: Frescobaldi 



Am Mittwoch, 30. Januar 2019 07:23:45 UTC+1 schrieb Federico Bruni:

   Hi folks

   As you know, the current user guide for Frescobaldi 3 is available only
   within the application. Exporting it to HTML is a long standing issue
   (at least since 2016):
   >

   There's anybody who's willing to work on it? :-)
   It would be great to get this done in the next future, as I'm working
   on the new website for Frescobaldi and it would be good to be able to
   include the HTML user manual.

   You don't have to be acquainted with Frescobaldi code base - Urs told
   me. Here's what he wrote to me:

> When displaying a page in the user guide Frescobaldi converts the
> Markdown file to HTML and then loads that in the text browser
   widget.
> So it should be *fairly* straightforward to write a harvesting tool
> that does that for the whole structure - it's basically about
> *managing*, not about doing the basic work.
> It should be equally possible to implement that within Frescobaldi
> ("Export User Guide") or as a standalone tool. The latter would look
> more natural to me while the former might be easier to do.

   
>


   Any volunteer?


Let me just add that this would be a great way to support Frescobaldi 
development with a medium-commitment contribution ;-)


Urs


   Thanks
   Federico

   PS
   The website I'm working on is generated with Hugo from Markdown
   sources.
   In theory I may add above userguide as a git submodule in a content
   directory and let Hugo convert it to HTML. This would work if the user
   guide files were simple Markdown, but they contain variables and other
   stuff which only Frescobaldi scripts can understand.



--
Frescobaldi homepage: http://www.frescobaldi.org/
Mailing list: http://groups.google.com/group/frescobaldi
Issue tracker: https://github.com/wbsoft/frescobaldi/issues
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Configuration Point & Click

2019-01-29 Thread Federico Bruni

Il giorno mar 29 gen 2019 alle 22:21, foxfanfare
ha scritto:

Hi fellow lilyponders!

I would have need some of your help understanding how the Point &
Click
option works. I switched from Windows to Linux some weeks ago (please
be
gentle with me, I'm still a noob in this world!) and I'm trying to
set-up a
minimalist desktop. I've installed ArchLinux and configured already
some
basic things and I am trying now to set up all my LilyPond
workstation.

What I can do: I can edit my lilypond file with vim (my main editor),
compile it with a shortcut, see at the same time the PDF in another
window

(I've choosen Zathura) which is updated automatically.

What I can't do: set-up the point & click!

I'm sorry, I read the documentation several times, tried a lot of
things,
but I have to admit that I can't figure how this works by myself...
Is there

by any chance someone using a similar configuration who could help me?

What I think I've understood so far:
-LP generate a PDF with URL links which start with textedit:///...
- I should set-up zathura to open those links with
lilypond-invoke-editor

(... I didn't found how yet...)
-lilpypond-invoke-editor should interract properly with vim.

Right now, when I click on the PDF link, the textedit:///... link
goes to

firefox, and I get a message in my vim file at the same time saying
"/usr/bin/xdg-open: line 881: x-www-browser: commande introuvable"
And when I type in the console lilypond-invoke-editor following with
the
textedit link, it opens correctly the vim file, but the cursor isn't
at the

good position...

To make a long story short, I'm lost here!

I have a blog post draft (since some months...) for lilypondblog.org on
this subject. It's not released yet because I had some troubles
configuring Windows and especially Mac. Hopefully I'll finalize it next
week (the last famous words...).

You have two problems:

1. lilypond-invoke-editor doesn't open the correct position because you
did not set the correct vim command in your .bashrc, that is:

export LYEDITOR="vim '+call cursor(%(line)s, %(column)s)'"

This command may be added to LilyPond _in the future_ and then you will
be able to simply set vim:

export LYEDITOR=vim

2. xdg-open error
Configuring Linux should be easy and it's explained in the docs.
Which desktop environment are you using in Arch?
You'll probably have to follow the instructions for GNOME 3.. which I
guess it should work for any Freedesktop.org desktop environment, but I
didn't check.

http://lilypond.org/doc/v2.19/Documentation/usage/configuring-the-system-for-point-and-click#using-gnome-3-for-point-and-click

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

52 matches

Mail list logo