It is in the links aggregator.
I don’t really understand what it adds to the editing experience. Why do you want to save and re-open a tiddler? Is it just in case you accidentally type <escape> ?
Right. IMO it is likely a less common use case. Maybe working on something big over a lot of time? Where you don’t want to lose anything? Also with saving with backup you do get a crude fallback versioning system for code.
Just FYI, my interest in @telmiger’s neat button set was in “Save & Close”.
Regarding availability. Yes, it is on “Links”. Top notch stuff, thanks much to you.
But, TBH, regarding the query by @jypre I often think we need, in addition to Links, a few “curated guides” to plugins available that address simple questions raised here?
Just a side comment (hat-off 
)
TT
I have two use cases. 1) Sometimes a tiddler is in edit mode for hours while I search for other tiddlers, collect information on the web and so on. And sometimes I experience a browser crash. 2) While coding in a tiddler and viewing the preview at the same time TW might get in an undesired condition so it becomes difficult to save.
I use single file Wikis mostly and I abuse my browser with 5 to 10 windows open and 3 to 20 tabs in each. So I blame myself for crashing it every second week or so.
That’s why I am happy with save and reopen. And also happy with autosave every 200 characters I type or copy-paste.
Cheers, Thomas
1 Like
First of all, I have to say that I find TW to be a technological marvel. Combining code, layout and data into a single file that can be taken/synced anywhere, but still have everything cleanly separated and simply customizable is pretty genius.
The one thing that frustrates me to this day as a wikitext programmer is the lack of a dedicated if-then-else widget. So, so often, when misusing $list for conditionals, I forget to add the variable parameter so that currentTiddler gets borked. It used to take me ages to find this mistake because syntactically the code was correct. By now I figure it out pretty fast. Plus, I’ve started using $reveal instead where it makes sense semantically and functionality-wise.
I’ve been using TW5 since version 5.1.7 in early 2015, and the variable thing just happened to me again yesterday. Maybe I’m just getting old, but TW should be for old people, too! 
Have a mnemonic day
Yaisog
2 Likes
First let me quote @Yaisog, because I could not say it better:
What I miss the most in TW5 is a simple, efficient, wikitext-syntax-coloured editor out-of-the-box. That would be so much in the spirit of a Quine!
Fred
1 Like
I don’t understand, why you want to use a complicated workflow if an easy one exists.
Screenshot utilities usually have a “save function” or even automatic naming and save functions.
- After you captured your screen-shot
- save it with your capture utility as eg: test.png
- in a subdirectory where your wiki is eg:
images
- in a subdirectory where your wiki is eg:
- In the wiki you can use it with.
[img[./images/test.png]]
If you want to add some metadata to your image create a tiddler and use the _canonical_uri mechanism that is described at: https://tiddlywiki.com/#ExternalImages
But I think the first possibility already goes a long way.
If I need to create a lot of screenshots I use IrfanView program for windows. It has an option to automatically create unique file-names and it has an option for a hotkey, to activate the capture process. … I use it for ages and it works very well for me.
Since browsers also have a capture function now, I also start to use them from time to time.
I made mention of and showed some current and future options There is no emptyValue for the view widget - #7 by TW_Tones
I get a lot from Snagit (I pay) but snapshots go into an editor where you can save, annotate and drag and drop from. Later I want my wikis on a local platform where I can use the file uploads plugin and all my images will be saved within a wiki with all the organisation and search facilities I need. I would never need to name the image files because snagit makes them unique and tiddlywiki tiddlers will be what I name and categorise.
For bulk image processing, I also recommend TW-Scripts: Create External Images from A Directory
ShareX - The best free and open source screenshot tool for Windows (getsharex.com) is an open source free software which is excellent tool for screen capture. It saves all screenshots in a dedicated folder or can upload silently to a folder on the cloud like Google Drive. Thne you can have these images in your Tiddlywiki as explained in TW-Scripts (above link)
One can automate the process if he/she has alot of images …
1 Like
I wanted to come back to the OP and comment …
In reality, as a user, my difficulties with using TW are often nothing to do with TW itself.
They are to do with CSS, SVG, HTML and (the horror!) JS.
To fully leverage TW for fluent escalation you need to understand a lot of things that TW combines skilfully. But often I find I need to ask myself how do those work?
Best, TT
1 Like
In my previous post I indicated that, IMO, TW is the least of the issues one faces.
Regarding the OP I’d guess a differentiation between “developing a TW” and “end-user experience of a TW” matters most?
What I mean is … the TW you author may be difficult, sometimes, to achieve as you want. But maybe the real test is whether end-users (with no involvement in TW making) get what they need … ???
The implication here is: If end-consumers can do what thy need, then RELAX on frustration??? 
Just a thought
TT
I will tell you what the worst feature of Tiddlywiki is. It is spending days or even weeks re-creating the hacks learned from a lifetime working with less elegant technologies, and then suddenly realizing that three lines of code and a shift in perspective makes all of that unnecessary.
This is also Tiddlywiki’s best feature. 
10 Likes
a syntax colored editor would also help a lot in finding many typos. A real time saver!!!
4 Likes
I would love to work on converting my VSCode TW5-Syntax plugin to something that TW itself could use in an editor-plugin. Still dealing with the fallout of losing the job unexpectedly, but it’s on my list! (Lol)
2 Likes
I don’t really understand what it adds to the editing experience. Why do you want to save and re-open a tiddler? Is it just in case you accidentally type
<escape>?
Another good feature is that you can save, see the results and easily undo with ctrl-z.
2 Likes
@joshuafontany you could use the VS code editor as an external editor for text area fields as a stop gap.
Can you provide a link to your VSCode TW5-Syntax plugin. I was thinking of adopting the VS studio IDE etc… for other reasons.
Here is a not recently tested by me, edit in external editor for firefox Browser’s external editor
At the same time I discovered the External Application Button (WebExtension) which I would like to see ported into tiddlywiki so we could open local programs to edit images etc…
Both of these add-ons require installing another helper application that is platform specific. I currently use GitHub - fooqri/uri-handler: A uri protocol router for macOS that allows protocols to be handled by simple scripts. , defining a custom uri handler that enables me to open file using a link such as this in Sublime Text.
subl://open/?file=~/Desktop/docs/Dropbox/file.txt
Although I have not really looked too much into this beyond macOS, the advantage of using a uri is there is no need to install a separate extension, just need to write a link.
@markkerrigan appropriately you have inspired another response in me to this threads OT The Worst Feature of Tiddlywiki.
The Worst Feature of Tiddlywiki is; Something that never lasts for long, at least until I discover another. Because I am always able to fix it, or at least find a work around, or someone else fixes it.
Amongst the many bright ideas tiddlywiki has inspired in response to a perceived problem is one I call “protocol handler” unlike the “helper application” that @markkerrigan mentioned, it checks field content on current tiddlers for a set of predefined prefixes such as http https mailto file etc and handles each as I choose. In this case I expose a link with the name of the field it was found in, at the bottom of the tiddler.
I have not published it yet, but I should get used to publishing “viable products” before perfection.
My latest realisation, and rabbit hole, was links are never “space delimited” so we could follow any link value with one or more space delimited keyword=value pairs. I thought I could get tricky and add to my protocol handler, the ability to pass any parameter into the link using these eg target="tiddlywiki.com" or tooltip="Link about xyz".
Why have I not built it myself yet?, because I expect the code to already exists somewhere in tiddlywiki, I just want to find it (waiting for me). This code needs to handle spaces inside the value part of the keyword value pairs.
Of course when ever I see the opportunity to leverage tiddlywiki and develop new features, I try hard to find generic solution others can make use of as well.
Just FYI I thought your VSCode thing excellent!
In a way it is an interesting issue whether it is better to do a native TW version or not?
Practically: I don’t care . Meaning there is a compounding issue in that browsers are quite locked-down now so invocation of the VSCode tool directly from TW is (unless you are Bob, Timimi [old version] or TiddlyDesktop) is off-limits.
What is my point? – Simply here is an issue where the browser get’s in the way.
As far as I grasp it, there is, finally, a new API for browsers in development that looks like it might give us back what we lost (basically invocation of programs) a few years ago??
Whilst a TW syntax highlighter would be neat, I think, for folk hot on that, are likely to be using external tools anyway???
Eek! I hope you come back to your former good!
Just comments, TT
Not really. VSCode is a web-app, that can run entirely in the browser.
github did enable it in a very simple way to work with code. So it’s intended for developers and you have to have a good online connection. To start it, it transfers about 40+MByte of code.
My TW5 repo is at github(dot)com … The VSCode editor can be started with github(dot)dev
If we would like to add about 40MB to a single file wiki, this could be done too … Just joking. …
I do prefer the codemirror editor which can be used already and has nice code highlighting. Also for TW syntax. IMO we should use the possibilities we have.