Feature Request:
capability to import and export SuperAbbrev sets in XML (or some other human-editable
format).
Reasons:
- transfer sets from one system to another
- backup in case of corruption, errors, etc.
- global definition edits, e.g. using jEdit search & replace on multiple terms
| Submitted | phipster - 2009-06-17 - 20:53:25z | Assigned | shlomy |
|---|---|---|---|
| Priority | 5 | Category | None |
| Status | Open | Group | None |
| Resolution | None | Visibility | No |
| 2012-11-27 - 16:30:51z |
+1 All the cases are valid. How is one to share abbreviations with colleagues and internets? something simpler than xml could be better.. like velocity templates with ##template= ... like: ##name=func mode=javascript function $1($2){ $3 } |
|---|---|
| 2012-11-27 - 18:33:11z jojaba_67 |
I absolutely agree with that, so +1 also for me. |
| 2013-02-20 - 16:09:43z |
https://bitbucket.org/nateskulic/satool feel free to integrate into superabbrevs! i couldnt get jedit to build. |
| 2013-10-24 - 16:28:18z shlomy |
Would INI format be good enough? http://en.wikipedia.org/wiki/INI_file The abbreviations can be specified as the key of each property in the INI file, while the expansion would be the value. I think INI file suits better than XML here. |
| 2013-10-24 - 17:11:52z phipster |
Concur with INI format |
| 2013-10-25 - 05:43:12z jojaba_67 |
OK with ini files (simple enough to be edit by everyone) Is it possible to keep the tabulations and line wrap in this case ? Can you please give a template example ? Thanks |