[tw5] Re: Render a custom type as text/plain

[springer]

Just a quick follow-up: My memory was wrong -- I'm actually seeing the 
preview pane applying alternate view templates correctly in nearly all 
cases. The exceptions all turned out to involve cascade-conditions that 
referenced things like how the title begins (which are of course disrupted 
by "Draft of..." prefix). 

So, I'm baffled as to why the template specified in your ViewTemplate 
cascade is not working properly in the preview pane while editing.

On Saturday, April 1, 2023 at 11:05:26 PM UTC-4 springer wrote:

> I bet it's possible to have the preview pane give you a preview according 
> to the template you need.
>
> I've just discovered that I can get such an effect within dynamic tables 
> (which can toggle their expanded rows into edit mode). See this thread: 
> https://talk.tiddlywiki.org/t/hacking-tbl-expand-with-templates-in-shiraz-dynamic-tables/5824/7
>
> I suspect part of the explanation has to do with how the preview pane 
> works for "draft of" tiddlers, if/when you haven't specified a different 
> Edit template (via the cascade for edit mode)
>
> There are various plugins that offer editing interfaces that edit without 
> setting up a "draft of" tiddler, and these may help you (or anyone working 
> regularly with templates other than the default one) to see a live preview 
> of your edits in progress as they would appear in their "final" form. 
>
> (Then again, if you're looking for a completely non-wikified mode, is the 
> preview pane doing anything useful for you at all? Wouldn't you just toggle 
> that preview pane off for these tiddlers?)
> On Saturday, April 1, 2023 at 4:29:15 PM UTC-4 Gabriel Montagné 
> Láscaris-Comneno wrote:
>
>> The editor preview is also rendering it as a wiki tiddler, not as code.  
>> I can live with that, but I was hoping there'd be a fundamental "and here 
>> is how you render this type of tiddler" way.
>> Still,  it's incredible how flexible TW is!
>>
>> Cheers,
>> Gabriel
>>
>> On Saturday, April 1, 2023 at 8:35:59 PM UTC+2 Gabriel Montagné 
>> Láscaris-Comneno wrote:
>>
>>> Wonderful :-) Thanks a lot!
>>>
>>> On Saturday, April 1, 2023 at 8:29:50 PM UTC+2 Eric Shulman wrote:
>>>
 Instead of using simple transclusion (i.e., `{{TiddlerTitle}}`) use 
 the `$codeblock` widget, like this:
 `<$codeblock code={{TiddlerTitle}}/>`


 On Saturday, April 1, 2023 at 11:08:53 AM UTC-7 gab...@tibas.media 
 wrote:

> Interestingly, when I transclude the node, it's still rendered as a 
> wiki tiddler, not as code.  I wonder, Eric, if, from the top of your 
> head, 
> you'd know how to work around that?
> Thanks again, Gabriel
>
> On Saturday, April 1, 2023 at 8:02:29 PM UTC+2 Gabriel Montagné 
> Láscaris-Comneno wrote:
>
>> Amazing Eric!  Worked perfectly.  And thanks for the link and 
>> explanation!   I'll use the Discourse server for these type of questions 
>> going forward.
>> Again, 1000 thanks!
>> Cheers,
>> Gabriel
>>
>> On Saturday, April 1, 2023 at 6:35:04 PM UTC+2 Eric Shulman wrote:
>>
>>> Addendum:
>>>
>>> Instead of
>>>
>>> [type[text/x-fountain]then[$:/core/ui/ViewTemplate/body/rendered-plain-text]]
>>>
>>> your cascade definition should be:
>>> [type[text/x-fountain]then[$:/core/ui/ViewTemplate/body/code]]
>>>
>>> The difference is that the first definition will render embedded 
>>> wikitext syntax,
>>> while the second definition simply displays the content as plain 
>>> text without any other processing.
>>>
>>> -e
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/81862ecc-e668-4015-b651-1c11705d9f1fn%40googlegroups.com.

[tw5] Re: Render a custom type as text/plain

[springer]

I bet it's possible to have the preview pane give you a preview according 
to the template you need.

I've just discovered that I can get such an effect within dynamic tables 
(which can toggle their expanded rows into edit mode). See this thread: 
https://talk.tiddlywiki.org/t/hacking-tbl-expand-with-templates-in-shiraz-dynamic-tables/5824/7

I suspect part of the explanation has to do with how the preview pane works 
for "draft of" tiddlers, if/when you haven't specified a different Edit 
template (via the cascade for edit mode)

There are various plugins that offer editing interfaces that edit without 
setting up a "draft of" tiddler, and these may help you (or anyone working 
regularly with templates other than the default one) to see a live preview 
of your edits in progress as they would appear in their "final" form. 

(Then again, if you're looking for a completely non-wikified mode, is the 
preview pane doing anything useful for you at all? Wouldn't you just toggle 
that preview pane off for these tiddlers?)
On Saturday, April 1, 2023 at 4:29:15 PM UTC-4 Gabriel Montagné 
Láscaris-Comneno wrote:

> The editor preview is also rendering it as a wiki tiddler, not as code.  I 
> can live with that, but I was hoping there'd be a fundamental "and here is 
> how you render this type of tiddler" way.
> Still,  it's incredible how flexible TW is!
>
> Cheers,
> Gabriel
>
> On Saturday, April 1, 2023 at 8:35:59 PM UTC+2 Gabriel Montagné 
> Láscaris-Comneno wrote:
>
>> Wonderful :-) Thanks a lot!
>>
>> On Saturday, April 1, 2023 at 8:29:50 PM UTC+2 Eric Shulman wrote:
>>
>>> Instead of using simple transclusion (i.e., `{{TiddlerTitle}}`) use the 
>>> `$codeblock` widget, like this:
>>> `<$codeblock code={{TiddlerTitle}}/>`
>>>
>>>
>>> On Saturday, April 1, 2023 at 11:08:53 AM UTC-7 gab...@tibas.media wrote:
>>>
 Interestingly, when I transclude the node, it's still rendered as a 
 wiki tiddler, not as code.  I wonder, Eric, if, from the top of your head, 
 you'd know how to work around that?
 Thanks again, Gabriel

 On Saturday, April 1, 2023 at 8:02:29 PM UTC+2 Gabriel Montagné 
 Láscaris-Comneno wrote:

> Amazing Eric!  Worked perfectly.  And thanks for the link and 
> explanation!   I'll use the Discourse server for these type of questions 
> going forward.
> Again, 1000 thanks!
> Cheers,
> Gabriel
>
> On Saturday, April 1, 2023 at 6:35:04 PM UTC+2 Eric Shulman wrote:
>
>> Addendum:
>>
>> Instead of
>>
>> [type[text/x-fountain]then[$:/core/ui/ViewTemplate/body/rendered-plain-text]]
>>
>> your cascade definition should be:
>> [type[text/x-fountain]then[$:/core/ui/ViewTemplate/body/code]]
>>
>> The difference is that the first definition will render embedded 
>> wikitext syntax,
>> while the second definition simply displays the content as plain text 
>> without any other processing.
>>
>> -e
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/2fc662a1-b0b3-47a0-a7fe-4c0f770acf07n%40googlegroups.com.

[tw5] Re: SelectWidget: adding separator lines

[Charlie Veniot]

Since I'm finding myself using this separator in many places, it made sense 
to macrofy the thing:

```
\define selectOptionSeparator() ─
```

Example:

```
<>
🥇 Acknowledgements
❤ Support This 
Project
```

On Thursday, March 30, 2023 at 6:43:13 PM UTC-3 Charlie Veniot wrote:

> [image: Screenshot 2023-03-30 6.41.32 PM - Display 2.png]
>
> On Thursday, March 30, 2023 at 6:40:14 PM UTC-3 Charlie Veniot wrote:
>
>> I found a unicode character that gives nicer results:
>>
>> ```
>> ─
>> ```
>>
>> On Thursday, March 30, 2023 at 6:30:47 PM UTC-3 Charlie Veniot wrote:
>>
>>> This works with my Chrome web browser.  I don't know about other web 
>>> browsers.
>>>
>>>
>>>
>>> ```
>>> <$select tiddler='$:/SiteTitle' tooltip='Choose a new site title'>
>>> A Tale of Two Cities
>>> 
>>> A New Kind of Science
>>> —
>>> The Dice Man
>>> 
>>> ```
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/5d8e4da0-e372-4abb-9052-226e090cf714n%40googlegroups.com.

[tw5] FeatherWiki works really well as embedded content

[Charlie Veniot]

For certain things that don't need to be in a TiddlyWiki instance and would 
just clutter up a TiddlyWiki instance ...

If it is the kind of content that fits well in FeatherWiki, it might make 
sense in certains scenarios to manage that content in a small FeatherWiki 
instance and embed it in a TiddlyWiki (or wherever else needed) with an 
iframe.

For example, Sample BASIC Anywhere Machine Programs 

.

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/7eb7735e-6288-4f8b-8ffd-dc1b62890b22n%40googlegroups.com.

[tw5] Tiddler Links showing only in "TiddlyWiki interface" mode

[Charlie Veniot]

The BASIC Anywhere Machine User Guide and Programming Reference 
 by 
default displays a customised interface that hides the natural TiddlyWiki 
interface.

When working on the BAM documentation in the natural interface, I need easy 
access links to anything I see so that I can quickly edit it.

So this requires links that show when in the natural interface, and links 
that hide when in the custom interface.

*The following in the custom interface*
[image: Screenshot 2023-04-01 9.15.53 PM.png]
l*ooks like this in the natural interface:*
[image: Screenshot 2023-04-01 9.14.52 PM.png]
So I can design and test the interface in the natural interface as it would 
look in the custom interface, but with the addition of the tiddler (fish) 
emoji, so that when I select a subject, I can quickly go to the related 
tiddler for editing.

To create the fishy link:
```
{{{ [[$:/temp/currently_showing]get[book]] || fLx }}}
```
The tiddler ```$:/temp/currently_showing``` (```book``` field) holds the 
selection of "Subject".

```fLx``` is a template tiddler.  It has

```
^^
<$list filter="[[$:/state/sidebar]get[text]]+[match[yes]] 
[] +[replace[yes]]">
<$link to={{!!title}}  tooltip={{{ [addprefix[Open 
]addsuffix[ Tiddler]] }}}>🐟^^ 
```

The fishy link only shows when the TW sidebar is showing.  So the benefit 
of two things for the price of one (reduce, reuse, recycle!):  the sidebar 
is hidden when in the custom interface, and I can see exactly how a tiddler 
will look in the custom interface without leaving the natural interface by 
hiding the sidebar.





-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/eb67c2c6-9b30-48a1-a56d-5f426dbf9ae5n%40googlegroups.com.

[tw5] BAM now also available at Tiddlyhost

[Charlie Veniot]

Being a supporter of Neocities ( I think it is good for folk to have a free 
place to build old-school websites), I've been hosting all of my TiddlyWiki 
instances over there,

Of course, Neocities being free and it always having potential of hosting 
sites that might not be appropriate/trustworthy, some environments may 
completely block access to Neocities.

I've just setup https://bam-ide.tiddlyhost.com/ so that anybody interested 
in it but could not access it, now hopefully can give it a spin.

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/caceace7-8394-4cd6-a46b-57ffa0c8c4fdn%40googlegroups.com.

[tw5] Re: Render a custom type as text/plain

[Gabriel Montagné Láscaris-Comneno]

The editor preview is also rendering it as a wiki tiddler, not as code.  I 
can live with that, but I was hoping there'd be a fundamental "and here is 
how you render this type of tiddler" way.
Still,  it's incredible how flexible TW is!

Cheers,
Gabriel

On Saturday, April 1, 2023 at 8:35:59 PM UTC+2 Gabriel Montagné 
Láscaris-Comneno wrote:

> Wonderful :-) Thanks a lot!
>
> On Saturday, April 1, 2023 at 8:29:50 PM UTC+2 Eric Shulman wrote:
>
>> Instead of using simple transclusion (i.e., `{{TiddlerTitle}}`) use the 
>> `$codeblock` widget, like this:
>> `<$codeblock code={{TiddlerTitle}}/>`
>>
>>
>> On Saturday, April 1, 2023 at 11:08:53 AM UTC-7 gab...@tibas.media wrote:
>>
>>> Interestingly, when I transclude the node, it's still rendered as a wiki 
>>> tiddler, not as code.  I wonder, Eric, if, from the top of your head, you'd 
>>> know how to work around that?
>>> Thanks again, Gabriel
>>>
>>> On Saturday, April 1, 2023 at 8:02:29 PM UTC+2 Gabriel Montagné 
>>> Láscaris-Comneno wrote:
>>>
 Amazing Eric!  Worked perfectly.  And thanks for the link and 
 explanation!   I'll use the Discourse server for these type of questions 
 going forward.
 Again, 1000 thanks!
 Cheers,
 Gabriel

 On Saturday, April 1, 2023 at 6:35:04 PM UTC+2 Eric Shulman wrote:

> Addendum:
>
> Instead of
>
> [type[text/x-fountain]then[$:/core/ui/ViewTemplate/body/rendered-plain-text]]
>
> your cascade definition should be:
> [type[text/x-fountain]then[$:/core/ui/ViewTemplate/body/code]]
>
> The difference is that the first definition will render embedded 
> wikitext syntax,
> while the second definition simply displays the content as plain text 
> without any other processing.
>
> -e
>


-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/e9f697e0-603d-4fe8-8b20-7607863af1e3n%40googlegroups.com.

[tw5] Re: Render a custom type as text/plain

[Gabriel Montagné Láscaris-Comneno]

Wonderful :-) Thanks a lot!

On Saturday, April 1, 2023 at 8:29:50 PM UTC+2 Eric Shulman wrote:

> Instead of using simple transclusion (i.e., `{{TiddlerTitle}}`) use the 
> `$codeblock` widget, like this:
> `<$codeblock code={{TiddlerTitle}}/>`
>
>
> On Saturday, April 1, 2023 at 11:08:53 AM UTC-7 gab...@tibas.media wrote:
>
>> Interestingly, when I transclude the node, it's still rendered as a wiki 
>> tiddler, not as code.  I wonder, Eric, if, from the top of your head, you'd 
>> know how to work around that?
>> Thanks again, Gabriel
>>
>> On Saturday, April 1, 2023 at 8:02:29 PM UTC+2 Gabriel Montagné 
>> Láscaris-Comneno wrote:
>>
>>> Amazing Eric!  Worked perfectly.  And thanks for the link and 
>>> explanation!   I'll use the Discourse server for these type of questions 
>>> going forward.
>>> Again, 1000 thanks!
>>> Cheers,
>>> Gabriel
>>>
>>> On Saturday, April 1, 2023 at 6:35:04 PM UTC+2 Eric Shulman wrote:
>>>
 Addendum:

 Instead of

 [type[text/x-fountain]then[$:/core/ui/ViewTemplate/body/rendered-plain-text]]

 your cascade definition should be:
 [type[text/x-fountain]then[$:/core/ui/ViewTemplate/body/code]]

 The difference is that the first definition will render embedded 
 wikitext syntax,
 while the second definition simply displays the content as plain text 
 without any other processing.

 -e

>>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/54077926-1228-4550-b3d3-21c59b10f2d1n%40googlegroups.com.

[tw5] Re: Render a custom type as text/plain

[Eric Shulman]

Instead of using simple transclusion (i.e., `{{TiddlerTitle}}`) use the 
`$codeblock` widget, like this:
`<$codeblock code={{TiddlerTitle}}/>`


On Saturday, April 1, 2023 at 11:08:53 AM UTC-7 gab...@tibas.media wrote:

> Interestingly, when I transclude the node, it's still rendered as a wiki 
> tiddler, not as code.  I wonder, Eric, if, from the top of your head, you'd 
> know how to work around that?
> Thanks again, Gabriel
>
> On Saturday, April 1, 2023 at 8:02:29 PM UTC+2 Gabriel Montagné 
> Láscaris-Comneno wrote:
>
>> Amazing Eric!  Worked perfectly.  And thanks for the link and 
>> explanation!   I'll use the Discourse server for these type of questions 
>> going forward.
>> Again, 1000 thanks!
>> Cheers,
>> Gabriel
>>
>> On Saturday, April 1, 2023 at 6:35:04 PM UTC+2 Eric Shulman wrote:
>>
>>> Addendum:
>>>
>>> Instead of
>>>
>>> [type[text/x-fountain]then[$:/core/ui/ViewTemplate/body/rendered-plain-text]]
>>>
>>> your cascade definition should be:
>>> [type[text/x-fountain]then[$:/core/ui/ViewTemplate/body/code]]
>>>
>>> The difference is that the first definition will render embedded 
>>> wikitext syntax,
>>> while the second definition simply displays the content as plain text 
>>> without any other processing.
>>>
>>> -e
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/2e23c278-cdd7-4b80-995c-d0198c47aab6n%40googlegroups.com.

[tw5] Re: Render a custom type as text/plain

[Gabriel Montagné Láscaris-Comneno]

Interestingly, when I transclude the node, it's still rendered as a wiki 
tiddler, not as code.  I wonder, Eric, if, from the top of your head, you'd 
know how to work around that?
Thanks again, Gabriel

On Saturday, April 1, 2023 at 8:02:29 PM UTC+2 Gabriel Montagné 
Láscaris-Comneno wrote:

> Amazing Eric!  Worked perfectly.  And thanks for the link and 
> explanation!   I'll use the Discourse server for these type of questions 
> going forward.
> Again, 1000 thanks!
> Cheers,
> Gabriel
>
> On Saturday, April 1, 2023 at 6:35:04 PM UTC+2 Eric Shulman wrote:
>
>> Addendum:
>>
>> Instead of
>>
>> [type[text/x-fountain]then[$:/core/ui/ViewTemplate/body/rendered-plain-text]]
>>
>> your cascade definition should be:
>> [type[text/x-fountain]then[$:/core/ui/ViewTemplate/body/code]]
>>
>> The difference is that the first definition will render embedded wikitext 
>> syntax,
>> while the second definition simply displays the content as plain text 
>> without any other processing.
>>
>> -e
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/2fad206b-4b01-4fda-8dbf-453aa2fb5a00n%40googlegroups.com.

[tw5] Re: Render a custom type as text/plain

[Gabriel Montagné Láscaris-Comneno]

Amazing Eric!  Worked perfectly.  And thanks for the link and 
explanation!   I'll use the Discourse server for these type of questions 
going forward.
Again, 1000 thanks!
Cheers,
Gabriel

On Saturday, April 1, 2023 at 6:35:04 PM UTC+2 Eric Shulman wrote:

> Addendum:
>
> Instead of
>
> [type[text/x-fountain]then[$:/core/ui/ViewTemplate/body/rendered-plain-text]]
>
> your cascade definition should be:
> [type[text/x-fountain]then[$:/core/ui/ViewTemplate/body/code]]
>
> The difference is that the first definition will render embedded wikitext 
> syntax,
> while the second definition simply displays the content as plain text 
> without any other processing.
>
> -e
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/7b572e62-0964-4b34-9bb7-7d1204839228n%40googlegroups.com.

[tw5] Re: Render a custom type as text/plain

[Eric Shulman]

Addendum:

Instead of
[type[text/x-fountain]then[$:/core/ui/ViewTemplate/body/rendered-plain-text]]

your cascade definition should be:
[type[text/x-fountain]then[$:/core/ui/ViewTemplate/body/code]]

The difference is that the first definition will render embedded wikitext 
syntax,
while the second definition simply displays the content as plain text 
without any other processing.

-e

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/66ebbb48-b319-4aa5-80c2-13b7d0af286en%40googlegroups.com.

[tw5] Re: Render a custom type as text/plain

[Eric Shulman]

You want to use the TWCore's "cascade" mechanism 
(see https://tiddlywiki.com/#Cascades)

* Create a tiddler (e.g., "$:/config/ViewTemplateBodyFilters/x-fountain"), 
containing:
   
[type[text/x-fountain]then[$:/core/ui/ViewTemplate/body/rendered-plain-text]]
* Tag it with `$:/tags/ViewTemplateBodyFilter`
* Add a field named `list-before` with no field value

Notes:
* Your "cascade" tiddler can have any name.  The name suggested above is 
consistent with the existing TWCore "ViewTemplateBodyFilters" shadow 
definitions.
* The tiddler content is evaluated by the TWCore cascade mechanism, and 
basically says: "If the tiddler's type field is equal to "text/x-fountain", 
then display the tiddlers body using the 
"$:/core/ui/ViewTemplate/body/rendered-plain-text" template
* The `$:/tags/ViewTemplateBodyFilter` tag adds your definition to the 
default ViewTemplateBodyFilters cascade
* The `list-before` field ensures that your custom cascade is evaluated 
first when the cascade is processed by the TWCore

enjoy,
-e

P.S. You might want to visit https://talk.tiddlywiki.org/, which is a 
"Discourse" server that is now the TiddlyWiki community's primary 
discussion/Q+A area.
On Saturday, April 1, 2023 at 8:41:13 AM UTC-7 gab...@tibas.media wrote:

> Hi, 
>
> I registered a new type on my TW,  `text/x-fountain`, as per 
> https://groups.google.com/g/tiddlywiki/c/l_uxgh_tsDU.  All good; it shows 
> up on the type selector.
>
> But I'd like it rendered as if it was a `text/plain` file, not as a TW 5 
> tiddler.
>
> Is there a simple way to achieve this? 
>
> Thanks,
> Gabriel
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/b8e1eef5-38e7-4b30-a78a-93148af6d596n%40googlegroups.com.

[tw5] Render a custom type as text/plain

[Gabriel Montagné Láscaris-Comneno]

Hi, 

I registered a new type on my TW,  `text/x-fountain`, as per 
https://groups.google.com/g/tiddlywiki/c/l_uxgh_tsDU.  All good; it shows 
up on the type selector.

But I'd like it rendered as if it was a `text/plain` file, not as a TW 5 
tiddler.

Is there a simple way to achieve this? 

Thanks,
Gabriel

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/88b97576-c6f3-423b-bf89-9056e6c78912n%40googlegroups.com.