Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues with CamelCase in captions fields with the tab macro #1697

Closed
Spangenhelm opened this issue May 5, 2015 · 7 comments
Closed

Issues with CamelCase in captions fields with the tab macro #1697

Spangenhelm opened this issue May 5, 2015 · 7 comments

Comments

@Spangenhelm
Copy link
Contributor

Hi, we can not use CamelCase words in captions fields with the tab macro otherwise they get transformed in links..

Left side: a tiddler called "Test" with "TiddlyWiki" as caption field
Right side: a tiddler called "TestTest" without caption field

capture du 2015-05-05 02 02 25

I suppose that it is not normal. Thank you

@Jermolene
Copy link
Owner

One of the differences between using the ''title'' field and the ''caption'' field is wikified. The advantage is that it enables you to embed images and other formatting within a tab. The autolinking behaviour is a confusing side-effect but I don't see much of a way of avoiding it without losing the ability to embed images.

@Spangenhelm
Copy link
Contributor Author

I feel stupid i did not think about the tilde that we can use to prevent wikifying... 😊

@BramChen
Copy link
Contributor

BramChen commented May 5, 2015

@Jermolene How about if we set the tv-wikilinks variable to no?

<$set name="tv-wikilinks" value="no">
<$transclude tiddler=<<currentTab>> field="caption">
<$macrocall $name="currentTab" $type="text/plain" $output="text/plain"/>
</$transclude>
</$set>

@Jermolene
Copy link
Owner

@BramChen - that is ingenious, congratulations.

Jermolene pushed a commit that referenced this issue May 5, 2015
@Spangenhelm
Copy link
Contributor Author

👍 @BramChen

@BramChen
Copy link
Contributor

BramChen commented May 8, 2015

Thanks @Spangenhelm, but this does credit to @Jermolene (see 5b38c21).

@Spangenhelm
Copy link
Contributor Author

Fair enough ;-) Thanks for him !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants