Combining vim-template and nautilus document templates naming conventions

[iagomosqueira]

I am trying to unify the template files used by vim-template and those available with Nautilus "New document" context menu. I have pointed both vim-template and Nautilus to the same folder when looking for template files, but I haven't found a way of merging both naming conventions.

Nautilus wants filed to be named R\ file.R to show as "R file" in the context menu, but vim-template expects a common filename and only different extensions, say file.R.

Is there any way of specifying g:templates_global_name_prefix to achieve this? Would I need to modify every time this variable is used to create the right string by pasting the extension and a space before g:templates_global_name_prefix?

[muff1nman]

Interesting. Do you have a reference that describes the nautilus document templates in greater detail?

[iagomosqueira]

Not a full Nautilus reference, found out through these links

http://gnome-look.org/content/show.php?content=39317

http://askubuntu.com/questions/208291/how-to-create-a-new-blank-file-in-nautilus-3-6-and-above

and testing it myself. Could not find anything about changing Nautilus naming convention.

[muff1nman]

The one thing I can think of that may work for you is specifying an empty prefix: let g:templates_global_name_prefix = "". Then you would have templates named like txt without any prefix.

[iagomosqueira]

I am not sure that will work with Nautilus. But if no easy solution is
available I do not think it is worth too much effort.

On 27/11/15 09:27, muff1nman wrote:

The one thing I can think of that may work for you is specifying an empty prefix: let g:templates_global_name_prefix = "". Then you would have templates named like txt without any prefix.

---

Reply to this email directly or view it on GitHub:
#91 (comment)

[muff1nman]

I thought I tested it and had it working, but other than that I cannot think of an easy solution.

[iagomosqueira]

Thanks. Not such an essential feature.

On 13/12/15 01:41, muff1nman wrote:

I thought I tested it and had it working, but other than that I cannot think of an easy solution.

---

Reply to this email directly or view it on GitHub:
#91 (comment)