Text Editor
A TagSpaces extension allowing editing of text-based documents.
Features
- Opening and editing of text documents
- Syntax highlighting for the following file types: h, c, clj, coffee, coldfusion, cpp, cs, css, groovy, haxe, htm, html, java, js, jsm, json, latex, less, ly, ily, lua, markdown, md, mdx, ml, mli, pl, php, powershell, py, rb, scad, scala, scss, sh, sql, svg, textile, txt, xml
Used Libraries
This extension thankfully relies on the following great libraries:
Installation
This extension is packaged with any new version of TagSpaces.
User Manual
Text Editor
When you edit a plain text file, or any unsupported file format that displays the edit button, the simple text editor will open.
The only extra the text editor offers is basic code highlighting for some common programming languages, and numbered lines.
The text editor will keep the option to print from the plain text viewer.
MarkDown Editor
When you open a MarkDown file for editing from the MarkDown Viewer, it will be opened with the same Text Editor any plain text file would, offering inline highlighting of Markdown syntax.
The difference between MarkDown and plain text editors is the two additional functions in its FAB Overflow Menu: MarkDown Preview (1) and MarkDown Help (2).
The first option will open a popup window, presenting a formatted preview of the MarkDown file, similar to what you would see in the MarkDown viewer.
The second option will offer some basic help about MarkDown syntax and formatting.
Linking Local Files and Images
The Markdown editor will also allow you to link local files and images from within your connected location, using a path relative to your currently active folder. Linked local images will be shown embedded in the current markdown preview, while linked files will open in the default external application defined by your operating system.
For example, the link [link text](images/picture.jpg) will show the file named picture.jpg (located in the images subfolder of the folder your file is located) in the markdown viewer, while [link text](/files/more_files/example.pdf) will open the file named example.pdf (located in the more_files subfolder of the files folder, located in the current folder) in an external PDF viewer.
To enter a relative path, you can usually use UNIX-style slashes (/) in paths, e.g., path/to/file/filename.ext, as node.js, upon which TagSpaces is built, will handle them properly even on Windows. This allows for interoperability across different operating systems. If you only use Windows, however, you can use a backslash (\), e.g., path\to\file\filename.ext, if you prefer, but such paths will not be understood on any other system, including Android.
TagSpaces only understands relative paths. You cannot reference any level above your current folder, or the root of your connected location, but might only link files located in the currently active folder, or in subfolders within.
Source Code
The source code of this extension is freely available on GitHub.
Development
If you want to extend this extension, please follow our general extension development guide.