Frescobaldi 3.0.0 not saving templates

[Kevin Cole]

I'm on Pop!_OS 20.04 (roughly the same as Ubuntu 20.04) and using the Debian package.

When I create a new template, it appears in the list of templates, along with the two built-in templates, but if I close the template dock, the template disappears. If I exit Frescobaldi, the template disappears. It seems to disappear a lot.

How can I get the templates I make to stick around and be reusable?

P..S I tried the 3.1.3 flatpak, but that's completely broken. I'd like to stick to a .deb if possible.

[Kevin Cole]

P.S. In digging, I found that ~/.config/frescobaldi/frescobaldi.conf
has a [snippets] stanza with my snippet in it, but it is completely
ignored by and invisible to a running Frescobaldi instance.

[Federico Bruni]

On Tue, Jan 25 2022 at 23:08:10 -0500, Kevin Cole <dc....@gmail.com>
wrote:

> P.S. In digging, I found that ~/.config/frescobaldi/frescobaldi.conf
> has a [snippets] stanza with my snippet in it, but it is completely
> ignored by and invisible to a running Frescobaldi instance.
>

Your desktop environment is GNOME?
If you have both the deb package and the flatpak package, I think that
GNOME shell will list only one application when you search Frescobaldi;
or maybe it will list two identical icons and you won't know what you
started actually.
This is a problem, since the flatpak package stores the conf file in a
different place:
~/.var/app/org.frescobaldi.Frescobaldi/config/frescobaldi/frescobaldi.conf

If you want to debug your problems you should launch Frescobaldi using
the command line, so you're sure you're running the deb package.

[Federico Bruni]

On Tue, Jan 25 2022 at 19:36:10 -0800, Kevin Cole <dc....@gmail.com>
wrote:

> I'm on Pop!_OS 20.04 (roughly the same as Ubuntu 20.04) and using the
> Debian package.
>
> When I create a new template, it appears in the list of templates,
> along with the two built-in templates, but if I close the template
> dock, the template disappears. If I exit Frescobaldi, the template
> disappears. It seems to disappear a lot.
>
> How can I get the templates I make to stick around and be reusable?
>

I cannot reproduce it using the 3.1.3 flatpak.

This is similar to an issue with keyboard shortcuts (which I cannot
reproduce):
https://github.com/frescobaldi/frescobaldi/issues/1396

> P..S I tried the 3.1.3 flatpak, but that's completely broken. I'd
> like to stick to a .deb if possible.

It works great here.
What is broken exactly? I suspect that you cannot access some folders
to open files, right? If that's the case, you may miss some knowledge
about how flatpak works. Quick workaround is installing Flatseal
application and grant full system access to Frescobaldi.

[Kevin Cole]

I didn't have both installed simultaneously. When the Debian package wouldn't do what I wanted, I uninstalled it and installed the flatpak which was at version 3.1.3. Nothing happened when I clicked the flatpak icon. After about three minutes, I got a pop-up warning me that Frescobaldi was running in the background and that Pop!_OS thought that might be a problem, giving me the choice to "allow" it or cancel it. I chose "allow" thinking it might just be hellishly slow for some reason. After another six minutes, I killed the process, uninstalled the flatpak and reinstalled the Debian package.

[Federico Bruni]

Il giorno mer 26 gen 2022 alle 08:10:07 -0500, Kevin Cole
<dc....@gmail.com> ha scritto:

> I didn't have both installed simultaneously. When the Debian package
> wouldn't do what I wanted, I uninstalled it and installed the flatpak
> which was at version 3.1.3. Nothing happened when I clicked the
> flatpak icon. After about three minutes, I got a pop-up warning me
> that Frescobaldi was running in the background and that Pop!_OS
> thought that might be a problem, giving me the choice to "allow" it
> or cancel it. I chose "allow" thinking it might just be hellishly
> slow for some reason. After another six minutes, I killed the
> process, uninstalled the flatpak and reinstalled the Debian package.

Mmmmh, running in background doesn't make sense for Frescobaldi.
Anyway, you were too hasty... and I can't help you, sorry.

[Knute Snortum]

Have you tried downloading the 3.1.3 deb version from GitHub?

https://github.com/frescobaldi/frescobaldi/releases

You can also install from the source code. It's a bit of a pain to
get setup, but once you do, it's snap to use. And you can then get
the latest development version too.

--
Knute Snortum

[Kevin Cole]

TL;RL: I missed whatever documentation mentioning the magic incantation:

"-*- template; template-run;"

----

So. I went with the git version and got the same results as before: My
template "disappears"...

However... going back to the Debian package (because I really prefer
having a single package manager that checks for updates over having
more than I can keep track of), I note that it's not that the template
doesn't get stored; it's that the template doesn't get stored as a
template.

Restarting Frescobaldi and going to [File->New], my template is not
listed. Going to [File-> New->Manage Templates...], my template is
still not listed. Going to [Snippets->Manage Snippets...], lo and
behold, I find my template.

Digging into the source, and finding .../snippet/builtin.py, I notice
that the first lines of the builtin templates are actually "-*-
template; template-run;".

Adding that to the top of my template fixed everything.

[Federico Bruni]

On Wed, Jan 26 2022 at 13:56:21 -0500, Kevin Cole <dc....@gmail.com>
wrote:

> TL;RL: I missed whatever documentation mentioning the magic
> incantation:
>
> "-*- template; template-run;"
>
> ----
>
> So. I went with the git version and got the same results as before: My
> template "disappears"...
>
> However... going back to the Debian package (because I really prefer
> having a single package manager that checks for updates over having
> more than I can keep track of), I note that it's not that the template
> doesn't get stored; it's that the template doesn't get stored as a
> template.

You should have saved it as a template using File>Save>Save as template
and that line would have been added automatically by Frescobaldi.

[Kevin Cole]

I feel dumb. I missed that entirely. I was using "File->Manage Templates..." followed by the "+" to add a new template. 

It seems confusing to have the menu choice "Manage Templates..." now. It should be made clearer that the "Manage Templates..." is really -- I guess -- "Manage a subset of snippets" and that the "+" means "Add a new snippet".  Perhaps removing "Manage Templates..." and adding some filtering under "Manage Snippets.." would be better.

[Wilbert Berendsen]

Op Thu, 27 Jan 2022 08:14:50 -0500
Kevin Cole <dc....@gmail.com> schreef:

> I feel dumb. I missed that entirely. I was using "File->Manage
> Templates..." followed by the "+" to add a new template.
>
> It seems confusing to have the menu choice "Manage Templates..." now.
> It should be made clearer that the "Manage Templates..." is really --
> I guess -- "Manage a subset of snippets" and that the "+" means "Add
> a new snippet". Perhaps removing "Manage Templates..." and adding
> some filtering under "Manage Snippets.." would be better.

Good point!

Or make + automatically add the template line when the filter filters
only templates...

--
Wilbert Berendsen (www.wilbertberendsen.nl)

[Kevin Cole]

On Thu, Jan 27, 2022 at 11:16 AM Wilbert Berendsen <w...@xs4all.nl> wrote:

> > It seems confusing to have the menu choice "Manage Templates..." now.
> > It should be made clearer that the "Manage Templates..." is really --
> > I guess -- "Manage a subset of snippets" and that the "+" means "Add
> > a new snippet". Perhaps removing "Manage Templates..." and adding
> > some filtering under "Manage Snippets.." would be better.
>
> Good point!
>
> Or make + automatically add the template line when the filter filters
> only templates...

Actually, your suggestion makes better sense to me: It seems simple,
and end-users would not see a change in the way things work. No
changes to menus, etc.

[Sigismund Neukomm]

I still see the same problem under Linux Mint 21.2 Victoria and in Frescobaldi 3.3.0 and was struggling with it for at least half an hour. Thank God I stumbled upon this conversation here! Adding those correct "incatations" from /snippets/builtin.py did the trick on my Frescobaldi as well. Added it to my toolbox and thanks a lot for that hint! 

Maybe also the description in the manual in the corresponding section could be clearer as well by maybe adding one basic example. Tried to follow the instructions there, but I must somehow have missed something, because it did not work as expected.