[tw5] Re: Export plugin to pluginFolder

I realise this is an old topic, but here is a solution for anyone who finds this topic. Use this command for a tid-formatted plugin file: tiddlywiki --import /path/to/plugin/file application/x-tiddler --savewikifolder /path/to/output/folder or this command for a json-formatted plugin file:

[tw5] Re: Build multi-tiddler json plugin file

Tony, I'm aware it can be done interactively in wiki with Tinka, and have used it extensively. I'm after a way to do it from the command line partly out of curiosity and partly because my plugin workflow has changed - I won't bore you with the details. Like you, I assume there's a way to do it

[tw5] Build multi-tiddler json plugin file

I recently figured out how to use server tiddlywiki to disassemble a multi-tiddler json plugin file into separate tiddler files (see gg post here for details -- spoiler: it involves the --savewikifolder option). Is there any

[tw5] Re: Working examples of <$importvariables> and \import with helper macros

Thanks, Mario, for your response. I actually figured it out myself before checking back with GG. The trick was to put the import pragma *inside* the parent macro before calling the helper macro. I've not previously encountered a pragma command that didn't go at the top of the tiddler. That,

[tw5] Working examples of <$importvariables> and \import with helper macros

I'm experimenting with the use of <$importvariables> and \import to scope helper macros to the tiddler containing the main "parent" macro. So far I haven't even had a glimmer of success getting either to work. Before I even get to the point of posting example tiddlers, can anyone point me to a

[tw5] Re: Unpacking json plugin file - algorithms for creating tiddlywiki.files

. This topic can be closed (the original poster isn't able to!). Regards, David. On Sunday, 22 September 2019 11:00:40 UTC+9:30, David Nebauer wrote: > > I'm playing with a script that unpacks a single json plugin file to > individual tiddler files for installing under a node.js server. The script

[tw5] Unpacking json plugin file - algorithms for creating tiddlywiki.files

I'm playing with a script that unpacks a single json plugin file to individual tiddler files for installing under a node.js server. The script would also create a plugin.info file and, if necessary, a tiddlywiki.files file. (Note that TW is not involved in this process - the script acts

[tw5] Unpack json tiddlers (containing multiple files) on command line

I'm moving plugin files from my nodejs wiki to the system /usr/local/lib/node_modules/tiddlywiki/plugins directory. Is there a command line tool I can use to unpack (or decompose?) a json plugin file, i.e., that contains multiple tiddler files, into its constituent tiddler files? Before you

[tw5] Re: [TW5] Global Keyboard Shortcut for Plugin Simple Search: Shift + Space

Since updating to 5.1.20 on node.js the behaviour of the simple search plugin has changed. When I invoke the search dialog with Shift+Space for the first time after opening a wiki, it behaves normally. When I invoke the search dialog thereafter, the dialog opens *behind* the current tiddler.

[tw5] Re: Daily summaries have stopped

+9:30, David Nebauer wrote: > > I stopped receiving daily summaries of TW GG in my gmail account a few > days ago -- not sure exactly which day. My TW GG email delivery preference > is still set to "Send daily summaries". I see from the GG that posts are > still being m

Re: [tw5] Daily summaries have stopped

Hi Tony, Thanks for your suggestion. I checked every folder, including Spam, and there are no TW GG daily summaries anywhere. Regards, David. On Sat, 29 Jun 2019 at 22:14, TonyM wrote: > Do check its not going to spam or it you have the tabs into another tab. > -- You received this message

[tw5] Daily summaries have stopped

I stopped receiving daily summaries of TW GG in my gmail account a few days ago -- not sure exactly which day. My TW GG email delivery preference is still set to "Send daily summaries". I see from the GG that posts are still being made so something has gone wrong. I am still receiving other

[tw5] Re: Styling and sizing images as buttons

Mario, that worked an absolute treat! Thank you very much -- it really makes it easier to use TW on small form factor devices. Regards. David. On Saturday, 8 June 2019 09:03:34 UTC+9:30, PMario wrote: > > Hi David, > > You can try: .tc-tiddler-controls button svg > > My CSS was meant as an

[tw5] Re: Styling and sizing images as buttons

Hi Mario. I may not be understanding this discussion. I want to enlarge the ViewToolBar and Sidebar buttons in the tiddlywikis on my mobile phone to make them easier to press. I tried your solution -- of altering .tc-image-button using a stylesheet tiddler -- in both standalone and nodejs

[tw5] Re: ANN: New Plugin: embed Fira Code font

Thanks, Scott. Looks great on debian linux in qutebrowser, google-chrome and firefox. [image: fira-gc.png] [image: fira-ff.png] [image: fira-qute.png] Regards, David. On Sunday, 2 June 2019 12:06:30 UTC+9:30, Scott Sauyet wrote: > > There is a new plugin hosted at >

[tw5] An insert-table macro

Thought I'd leave this here in case it's of use to anyone. I was initially looking for a way to standardise table appearance across my wiki, and then I wanted a way to store table content in a data tiddler and insert that data into another tiddler as a table. Here is example dictionary tiddler

Re: [tw5] Re: External image tiddlers and external links require 'files' directory

I've added my own keywords to the bottom of a tiddler. They can > be hidden away in HTML comment tags. > > > > > > > On Tuesday, April 30, 2019 at 7:37:08 AM UTC-7, David Nebauer wrote: >> >> It's taken me a while to transfer my standard image tiddlers to external >>

[tw5] External image tiddlers and external links require 'files' directory

It's taken me a while to transfer my standard image tiddlers to external image tiddlers on a 5.1.19/nodejs installation. The most interesting wrinkle is that my "skinny" image tiddlers display images *only* if the image files are saved to a subdirectory of the wiki root called files. I tried

[tw5] Re: Seeking way to *enlist* but with duplicate preservation

I've been looking further into this feature. The alteration to $tw.utils. parseStringArray to enable it to return a list *with* duplicate items was a contribution from inmysocks, aka Jed Carty, in October 2018 (see TW github pull request 2027

[tw5] Re: Should tobibeer's split:list remove duplicates?

For anyone in the future who stumbles across this topic, I eventually found a solution to my need for an enlist replacement that allows duplicates. See this topic for details. Regards, David. -- You received this message

[tw5] Re: Seeking way to *enlist* but with duplicate preservation

I should add that my real-world project handles duplicate values flawlessly now that it uses enliatallowduplicates instead of enlist. I hope this topic is of assistance to others who have, or will have, the same need as I did. Regards, David. On Friday, 26 April 2019 15:24:05 UTC+9:30, David

[tw5] Re: Seeking way to *enlist* but with duplicate preservation

Solved. In fact, the solution was so simple I'm worried it's a trap! I have created a new filter operator -- enlistallowduplicates -- which differs from enlist by a single parameter. Here is the non-comment part of enlist.js: (function(){ /*jslint node: true, browser: true */ /*global $tw:

[tw5] Re: Seeking way to *enlist* but with duplicate preservation

Thanks, Tony. With your suggestion about incrementing a data tiddler, did you mean something like this for a 3-column table? 1: Row 1 Col 1 value 2: Row 1 Col 2 value 3: Row 1 Col 3 value 4: Row 2 Col 1 value 5: Row 2 Col 2 value 6: Row 2 Col 3 value 7: Row 3 Col 1 value 8: Row 3 Col 2 value 9:

[tw5] Re: Seeking way to *enlist* but with duplicate preservation

Mark S., I'll keep that as a backup strategy. I'm still hoping I'll stumble across a more elegant, less fiddly solution. Regards, David. On Thursday, 25 April 2019 00:27:50 UTC+9:30, Mark S. wrote: > > You'll hate this idea, but you could put a uniqueness enforcer in front of > each row item

[tw5] Seeking way to *enlist* but with duplicate preservation

I'm processing dictionary tiddler rows that each contain a sequence of values I need to handle individually. I'd love to use *enlist* in a filter to break apart each row for consumption by a <$list>. The problem with that approach is the rows may contain duplicate values that need to be

[tw5] Re: Should tobibeer's split:list remove duplicates?

ly to work with tabs and spaces in the same strings when they have different semantic meanings :-) My quixotic quest for a drop in enlist-but-with-duplicate-preservation replacement continues... I'll start a fresh topic about that broader question. Regards, David. On Tuesday, 23 Apr

Re: [tw5] Re: Should tobibeer's split:list remove duplicates?

are doing this but what and why you > are doing this? > > There should be a code work around. > > Regards > Tony > > > On Tuesday, April 23, 2019 at 9:32:28 PM UTC+10, David Nebauer wrote: >> >> This tiddlyscript: >> >> <$set name="H

[tw5] Should tobibeer's split:list remove duplicates?

This tiddlyscript: <$set name="HasDuplicates" value="one two two three [[twenty one]] [[twenty one]] [[forty six]]"> <$list filter="[split:list]"> xXx <$list filter="[enlist]"> results in: one two three

Re: [tw5] Re: Unable to import metadata (fields) from file along with tiddler content

wrote: > > Perhaps it relates to your browser. Using firefox on Xubuntu 18.0.4?? with > TW 5.1.20-prerelease (node) it imports perfectly. I'm not too surprised if > qutebrowser can't do it, since it's billed as a minimalistic browser. > > -- Mark > > On Monday, March 25, 2019 at 7:34:47

Re: [tw5] Re: Unable to import metadata (fields) from file along with tiddler content

I see Mark S. has deleted his post but for people on email who saw it, I'm on Debian Linux running TW5 v5.1.19 on node-js, and have had the same results with both google-chrome and qutebrowser browsers. I had just deleted my import files when I saw your message, but have reconstructed the tid

Re: [tw5] Re: Unable to import metadata (fields) from file along with tiddler content

Hi Jeremy, As I mentioned in my initial post, I'm using the Import ("paperclip") button. Pressing that opens a file selector dialog in which you select a file which is then displayed in a $:/Import tiddler, optionally repeat to nominate multiple files for import, then press the Import button

[tw5] Re: Unable to import metadata (fields) from file along with tiddler content

h tid and meta files at the same time, you get the same effect from the tid file and the meta file is imported to its own tiddler: [image: imported-meta-file.png] Once again, a failure to import metadata. Regards, David. On Monday, 25 March 2019 23:18:02 UTC+9:30, David Nebauer wrote: > &

[tw5] Re: Unable to import metadata (fields) from file along with tiddler content

What *does* work is the "div.tiddler" format. This input file: Content of demo "tiddler-style" tiddler file. results in this tiddler: [image: imported-tiddler-style.png] Success. Regards, David. On Monday, 25 March 2019 23:24:34 UTC+9:30, David Nebauer wrote: >

[tw5] Re: Unable to import metadata (fields) from file along with tiddler content

John Friso tags: Test Demo Import Tid title: Demo Testing Tid-Style Import type: text/vnd.tiddlywiki Content of demo "tid-style" tiddler. you end up with: [image: imported-tid-style.png] Clearly the metadata fields do not import as fields. Regards, David. On Monday, 25 March 2019 08:0

[tw5] Unable to import metadata (fields) from file along with tiddler content

In the process of transferring data into TW5 on node-js, I've been trying to import tiddler files as described in https://tiddlywiki.com/#TiddlerFiles. I have tried including metadata fields at the head of the tiddler file, but they were imported as tiddler text. I tried moving the metadata to

[tw5] Re: Quinoid v0.0.8alpha Downloadable, Configurable Resources

On Sunday, March 17, 2019 at 3:26:53 AM UTC-7, David Nebauer wrote: >> >> >> Only one usability issue to report: when I invoke the "More" dropdown >> from the ViewToolbar, the resulting menu is invisible. >> > -- You received this message because you

[tw5] Re: Quinoid v0.0.8alpha Downloadable, Configurable Resources

Reporting successful install of 190313a on a Pixel 1 running android 9. I was asked for storage permissions -- can't recall at exactly which point, though I think it was when I first opened a tiddlywiki. Only one usability issue to report, aside from my apparently giant fingers sometimes

Re: [tw5] Re: <$list> and duplicate items

Thanks, Mal. I'm a little embarrassed I missed that. Regards, David. On Mon, 4 Mar 2019 at 12:32, Mal wrote: > Actually, the instructions for running the prerelease under nodejs are on > tiddlywiki.com > >

Re: [tw5] Re: <$list> and duplicate items

Genius. That looks exactly like what I need. Is there a release schedule for 5.1.20? Is there any way to install it under nodejs now if you're willing to accept the risk of breakage? Regards, David. On Mon, 4 Mar 2019 at 11:30, Mal wrote: > > If you put the following into the advanced search

[tw5] <$list> and duplicate items

I've read the previous discussions about how filters remove duplicates because they are based on the assumption all they will ever be fed is tiddler titles, and how filters *may* be changed to accept duplicates in the next major, i.e., backwardly incompatible, upgrade. I need to break a string

Re: [tw5] Variable not recognised in filter with enlist operator

Thanks, Tony, for your suggestion and the pointer to your own notes. I see your notes do state after an example of double curly braces in a filter that "no delimiters other than the curly braces; you can not 'concatenate' other values into the filter value here". Regards, David. On Mon, 4 Mar

Re: [tw5] Variable not recognised in filter with enlist operator

That's great, Jeremy. It should help the next person who tries the same thing I did and gets desperate enough to look at the documentation! Regards, David. On Mon, 4 Mar 2019 at 00:04, Jeremy Ruston wrote: > > I've added a clarifying note to the docs. > -- You received this message because

Re: [tw5] Variable not recognised in filter with enlist operator

Hmm, I didn't read the intro to filter notation that way, but I guess it's what the Filter Parameter tiddler is saying. Thanks again. Regards, David. On Sun, 3 Mar 2019 at 23:44, Jeremy Ruston wrote: > The main introduction to filter notation

Re: [tw5] Variable not recognised in filter with enlist operator

Thanks, Jeremy, for providing that solution, and so quickly. It solved my problem. I thought I looked through all the relevant TW documentation when I was troubleshooting, but I missed the bit about not being able to combine the effects of the [, { and < brackets in filters. For future

[tw5] Variable not recognised in filter with enlist operator

The following displays the items from the *myfield* field in the *MyTiddler* tiddler: <$list filter="[enlist{*MyTiddler*!!myfield}]" variable="field-item"> <> This, which I expect to be exactly equivalent, displays nothing: <$set name="datasource" value="MyTiddler"> <$list

Re: [tw5] Test for existence of macro

What you say is correct, Jeremy, and I'm already version controlling my wiki and keeping my personal customisations in plugins, and yet... your comments trigger a couple of thoughts. The first is that TW is "marketed" as a personal notebook as much as a personal wiki. The second sentence at

Re: [tw5] Test for existence of macro

S. S., no problem. I touched on it in a post earlier in the topic. My use case is that I've been using TW for a couple of months now and am starting to include some macros in my tiddlers that are either defined in standalone macro tiddlers or in non-core plugins. One example is Mohammad's <>

Re: [tw5] Test for existence of macro

Okay, in summary, here are two ways of using the [is[variable]] operator to display an error message if a specific variable or macro is undefined. * As a macro: \define check-var-or-macro(var) <$list filter="[[$var$]] +[is[variable]]" emptyMessage="Undefined variable or macro '$var$'"> <> \end

Re: [tw5] Test for existence of macro

Thanks, Mal. Your proposed solution would certainly be a more concise and elegant way to achieve the same outcome. If you don't mind, perhaps you could keep this topic updated with developments and/or include a pointer to the github issue you raise. Regards, David. On Thursday, 28 February

Re: [tw5] Test for existence of macro

Thanks S. S. That does juts what I wanted. I'll call that success. Regards, David. On Thursday, 28 February 2019 11:02:47 UTC+9:30, S. S. wrote: > > This seems to work for me. > > \define variable-test(var) > <$list filter="[[$var$]] +[is[variable]]" emptyMessage="''$var$'' - > Undefined

Re: [tw5] Test for existence of macro

e rest of the tiddlyscript in the tiddler executes. -David On Wednesday, 27 February 2019 16:22:52 UTC+9:30, Mohammad wrote: > > Thanks David! > Added to TW-Scripts. > > --Mohammad > > > > On Wednesday, February 27, 2019 at 5:07:17 AM UTC+3:30, David Nebauer > wrote: >>

Re: [tw5] Test for existence of macro

Thanks very much, Mohammad and Jeremy. For future reference, here is what I was seeking: <$list filter="[[VAR_OR_MACRO_NAME]] +[is[variable]addsuffix[ is a variable]] ~[[Undefined variable or macro 'VAR_OR_MACRO_NAME']]"> <> If anyone else sees the option for marking this topic complete, please

Re: [tw5] Test for existence of macro

>>> >>> [[VAR_NAME]] +[is[variable]addsuffix[ is a variable]] ~[[Undefined >>> variable or macro 'VAR_NAME']] >>> >>> [[currentTiddler]] +[is[variable]addsuffix[ is a variable]] ~[[Undefined >>> variable or macro ‘currentTiddler']] >>> &g

Re: [tw5] Test for existence of macro

Thanks, Jeremy, but I'm still not clear on how to use this. For newbs, i.e., me, what complete line (or lines) would you add to the top of a tiddler to display an error message if a particular macro is undefined, and do nothing if it does exist? My use case is to add this to a tiddler where I

Re: [tw5] Test for existence of macro

thub.com/Jermolene/TiddlyWiki5/commit/36e76429b1a1d4638374d513430393db5693b932 > > Best wishes > > Jeremy. > > > On 25 Feb 2019, at 12:34, David Nebauer > > wrote: > > As I understand it, if you attempt to call an undefined macro the call > fails silently, with no

[tw5] Test for existence of macro

As I understand it, if you attempt to call an undefined macro the call fails silently, with nothing displaying in the tiddler to alert users. This occurs regardless of the calling method, i.e., <> or <$macrocall $name="not-a-real-macro"/> *Is there a technique for checking whether a macro is

[tw5] Re: Tinka and TW 5.1.19+ Issue

Subsequent posts in the thread explain further that the plugin is built successfully despite the javascript error. The same has happened to me (TW5.1.19, Tinka 0.4.0) though the internal javascript error I get is "Uncaught TypeError: Cannot read property 'ownerDocument' of undefined". This has

[tw5] Re: TeX- and LaTeX-related logos

:57:52 UTC+9:30, David Nebauer wrote: > > I wanted to see if I could simulate TeX- and LaTeX-related logos in TW5. I > could not find anything in web searches or in the TW google group, so I > came up with a basic solution using plain html and css. (Credits: TEX and > LATEX logo

[tw5] TeX- and LaTeX-related logos

I wanted to see if I could simulate TeX- and LaTeX-related logos in TW5. I could not find anything in web searches or in the TW google group, so I came up with a basic solution using plain html and css. (Credits: TEX and LATEX logo POSHlets ,

[tw5] Re: [theme] Presenting "Mono" theme

-- only two are showing while seven are hidden. There is an icon almost totally hidden at the top of the screen in the top right. On the plus side, I can see the tiddler titles just fine! A fantastic project! Please keep perfecting it. David On Monday, 4 February 2019 15:50:39 UTC+9:30, David

[tw5] Re: [theme] Presenting "Mono" theme

Very nice, indeed. I did notice that on my work system (Windows 7, IE 11) the top bar (with main icons and search box) covers 3/4 of the title of the top-most tiddler and 1/2 of the view toolbar icons, with no way to scroll down sufficiently to bring those elements into view. David On

[tw5] Re: Can't specify table macros via var/macro/transclusion

ll3 | > |Header|Header|h > |Footer|Footer|f > \end > > > And then invoke like: > > > <$vars myclasses="myclass anotherClass"> > > <> > > > > > Good luck > -- Mark > > > On Wednesday, January 30, 2019 at 3:06:11 PM

[tw5] Can't specify table macros via var/macro/transclusion

I've been unable to specify table classes in the classes pseudo-row from "outside" the table: Can't do it with a variable: <$vars varclasses="myclass1 myclass2"> |<>|k ... Can't do it with a macro: \define macroclasses() myclass1 myclass2 |<>|k ... Can't do it by transcluding from

Re: [tw5] [TW5] Global Keyboard Shortcut for Plugin Simple Search: Shift + Space

I, too, was unaware that Shift+Space scrolled up. I won't miss it and sure appreciate having such an easily accessible search. Great plugin! David. On Friday, 25 January 2019 02:29:41 UTC+9:30, Thomas Elmiger wrote: > > Hej ch, mange tak! > > Better late than never, I will happily consider

Re: [tw5] <$wikify> needs <$text> to honour tilde-based wikilink suppression

> > ! <$list filter="[enlist{!!plugin.names}]" variable="name"><$text > text=<>/><$list filter="[enlist{!!plugin.names}last[]] -[]">, > > > {{!!text}} > > > > Best wishes > > Jeremy. > > On 22 Jan 2019, at 12:39, David

Re: [tw5] Re: <$wikify> needs <$text> to honour tilde-based wikilink suppression

Hi Jeremy, The first thing I do when I delve into an app I am going to both devote significant effort to and customise heavily, is document those customisations so I can rebuild the same environment from scratch. In the case of tiddlywiki I'm naturally documenting my customisations in

Re: [tw5] <$wikify> needs <$text> to honour tilde-based wikilink suppression

Hi Jeremy, You're reinforcing my point that when using a <> with <$wikify> there are too many interactions going on for anyone other than a guru to understand, none of which are documented anywhere. And it appears you have to use different methods to render a heading or suppress wikilinks in

Re: [tw5] <$wikify> needs <$text> to honour tilde-based wikilink suppression

Thanks, Thomas. That is another interesting workaround. It is certainly much more self-descriptive than my solution, so it would be easier to figure out what I did when I revisit this tiddler in six months and can't remember why I needed a workaround in the first place! FYI, <$setvar> is from

Re: [tw5] <$wikify> needs <$text> to honour tilde-based wikilink suppression

There does not appear to be a universal rule such as: "to prevent double wikification, always use a <$text> widget when loading a $ widget from a variable." To show what I mean, consider this variation of Jeremy's test rig where I set the variable to a heading string: <$set name="testVar"

[tw5] Re: <$wikify> needs <$text> to honour tilde-based wikilink suppression

>/> Here is where I needed the to use <$text> to ensure tildes in the field content are honoured. Can the above snippet be simplified? On Sunday, 20 January 2019 22:42:28 UTC+9:30, David Nebauer wrote: > > In playing about with listing tiddlers I discovered that passing a valu

[tw5] <$wikify> needs <$text> to honour tilde-based wikilink suppression

In playing about with listing tiddlers I discovered that passing a value like "~WikiLink" to <$wikify> resulted in it being rendered as a wikilink despite the tilde. However, adding a <$text> widget caused <$wikify> to behave as I expected. Here is an example: <$set name="testVar"

[tw5] Re: New View Toolbar icon details do not show in Control Panel

Thanks, Ton. I had to read over your instructions a few times before the light bulb went off, but then I was able to complete the setup very quickly and the button now appears properly in the Control Panel listing for the View Toolbar. In the end I created five tiddlers as per your

[tw5] Re: How to stop shiraz hiding the view toolbar

That worked a treat. Thanks for the prompt help and for a great plugin -- I'm looking forward to exploring it. On Tuesday, 8 January 2019 22:53:54 UTC+9:30, Mohammad wrote: > > Hack the below css tiddler: > $:/plugins/.mr/shiraz/stylesheet/tw-adjustment > -- You received this message because

[tw5] How to stop shiraz hiding the view toolbar

The shiraz plugin hides view toolbar buttons gracefully when the cursor is not hovering over a tiddler. What is the simplest way to suppress this behaviour? That is, how do I ensure view toolbar buttons are always visible? If anyone is curious why I'd like to suppress this rather tidy

[tw5] Re: External editor works with all new tiddler field except for content field

, David Nebauer wrote: > > The web browser I'm using with TW, qutebrowser > <https://github.com/qutebrowser/qutebrowser> has a mechanism for opening > an external editor when filling in forms fields. When creating a new > tiddler this mechanism works with every e

[tw5] Re: External editor works with all new tiddler fields except for content field [SOLVED]

in this forum and I couln't be more impressed with the response. Regards, David. On Thursday, 3 January 2019 14:16:35 UTC+9:30, David Nebauer wrote: > > The web browser I'm using with TW, qutebrowser > <https://github.com/qutebrowser/qutebrowser> has a mechanism for opening >

[tw5] Re: External editor works with all new tiddler field except for content field

text field will appear down with >>> the other fields (only a bigger box). From that text field box try >>> launching your external editor. >>> >>> Good luck! >>> -- Mark >>> >>> On Wednesday, January 2, 2019 at 8:46:35 PM UTC-8, Da

[tw5] Re: External editor works with all new tiddler field except for content field

a bigger box). From that text field box try > launching your external editor. > > Good luck! > -- Mark > > On Wednesday, January 2, 2019 at 8:46:35 PM UTC-8, David Nebauer wrote: >> >> The web browser I'm using with TW, qutebrowser >> <https://github.com/q

[tw5] Re: External editor works with all new tiddler field except for content field

Thanks for the suggestion, Ton. I did toggle off the editor toolbar but it did not change the behaviour of the content field and external editor. I even restarted the TW server after turning off the toolbar, but it made no difference either. Thanks again, David. On Thursday, 3 January 2019

[tw5] Re: External editor works with all new tiddler field except for content field

tTemplateFields/Visibility/text > > and change the text to "show". Now the text field will appear down with > the other fields (only a bigger box). From that text field box try > launching your external editor. > > Good luck! > -- Mark > > On Wednesday, January 2, 2019

[tw5] Re: External editor works with all new tiddler field except for content field

Astounding, you are "two for two". Disabling the CodeMirror plugins resulted in me being able to sucessfully use an external editor with the new tiddler content field. Then, once I re-enabled the CodeMirror plugins I was again unable to use gvim with the content field. However, typing input

[tw5] External editor works with all new tiddler field except for content field

The web browser I'm using with TW, qutebrowser has a mechanism for opening an external editor when filling in forms fields. When creating a new tiddler this mechanism works with every editable field *except* for the content field, which is