Git Ignoring $__StoryList.tid

[Taylor Jensen]

I can't ignore $__StoryList.tid from my repository. I have *.tid ignored, and every single tiddler except $__StoryList.tid gets ignored. Is there some kind of weird interaction going on here with git and the file name?

Any thoughts on how to get this temporary file out of my repository?

[BJ]

HI there. What system are you using , windows, linux or what?

[TW Tones]

The story list is what keeps the list of tiddlers in view, you need it?

It will create it if its not there!

Tones

[Saq Imtiaz]

Hi Taylor,

If by any chance you've previously committed the file for the story list, you will need to use git rm --cached to remove it.

Otherwise I wonder if somehow the $ character at the beginning of the file name is throwing things off. Are other system tiddlers ignored, that is those with names starting with $ ?

[Taylor Jensen]

BJ,

I have encountered the same problem in the same repo on both Windows and Linux. I'm using Git Kraken as my client if it matters.

[Taylor Jensen]

TW Tones,

I don't need it saved between sessions. When a new contributor clones the repo they will open the default tiddlers and generate their own. So I don't need it saved into the repository.

[Taylor Jensen]

Saq,

That was it. I needed to commit a deletion of the file. Which doesn't seem to be my understanding of how git is supposed to work. If I ignore the file after committing it once, I shouldn't be able to commit modifications. Oh well very sill, next time I'll just be sure to fill out the entire gitignore before initializing TiddlyWiki.

Thanks!

-TCJ

[TW Tones]

Taylor,

I am not so sure about node but you can exclude tiddlers from the save process in single files.

You can see the filter in $:/core/save/all

[is[tiddler]] -[prefix[$:/state/popup/]] -[[$:/HistoryList]] -[[$:/boot/boot.css]] -[type[application/javascript]library[yes]] -[[$:/boot/boot.js]] -[[$:/boot/bootprefix.js]] +[sort[title]] $(publishFilter)$

and add -[[$:/storyList]]

Tones

[Taylor Jensen]

Oh that's clever, I suspect that would work in node as well. 

Thanks! 

--
You received this message because you are subscribed to a topic in the Google Groups "TiddlyWiki" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tiddlywiki/RMV4C3ZvxY8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tiddlywiki+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/8e763724-773f-4623-8d41-779fd4eba4e9o%40googlegroups.com.

[Eric Shulman]

On Tuesday, October 6, 2020 at 9:36:11 PM UTC-7, TW Tones wrote:

...you can exclude tiddlers from the save process in single files.

You can see the filter in $:/core/save/all

[is[tiddler]] -[prefix[$:/state/popup/]] -[[$:/HistoryList]] -[[$:/boot/boot.css]] -[type[application/javascript]library[yes]] -[[$:/boot/boot.js]] -[[$:/boot/bootprefix.js]] +[sort[title]] $(publishFilter)$

and add -[[$:/storyList]]

Take note of the $(publishFilter)$ syntax at the end of the list of filters.

This allows you to add custom filters to $:/core/save/all without modifying the shadow tiddler.

Just create any tiddler (e.g., "MyPublishFilter"), tagged with $:/tags/Macro, containing:

\define publishFilter() -[[$:/StoryList]]

-e

 

[TW Tones]

Eric,

Does the publish filter only exist if you define it?

I have always had trouble finding where it was defined :) 

Perhaps it would be better as {{$:/config/publishFilter}} and editable somewhere.

Tones

[Eric Shulman]

On Wednesday, October 7, 2020 at 12:17:32 AM UTC-7, TW Tones wrote:

Does the publish filter only exist if you define it?

yes.

 

I have always had trouble finding where it was defined :) 

Perhaps it would be better as {{$:/config/publishFilter}} and editable somewhere.

In $:/core/save/all, saveTiddlerFilter() is defined as a macro whose value is passed

along to a subsequent filter action as part of the TWCore saver handler and thus

needs to be a fully expanded sequence of filter runs.

Using $(publishFilter)$ does a "string replace" to assemble the full filter syntax.

However... it occurs to me that it might be possible to use [subfilter{$:/config/PublishFilter}]

which *should* produce the same effect without relying upon a global macro definition.

-e