Just pushed a new version:
https://groups.google.com/d/msg/tiddlywiki/pVqcVuNaTbA/ZB4w3T8lAQAJ
-m
--
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
On Friday, June 16, 2017 at 5:41:26 PM UTC+2, Stuart Amor wrote:
>
> When creating the links its a lot easier to point them to the
> shorter tiddler title, but it would be nice to allow the previewed text
> (which is read by the uninitiated) to see the current long form.
>
Hi Stuart,
I
Hi Folks,
I pushed out the "uni-link" plugin:
https://wikilabs.github.io/editions/uni-link/ discussed here in the thread.
It's a new parser for the the TW link / prettylink detection: eg: [[test]]
... it links to the tiddler named: test but it shows a different text.
Depending on the
I think having the option in the control panel to turn it off makes sense.
Turning it off would then allow you to error check the links as the true unique
title IDs would be displayed.
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To
On Tuesday, June 20, 2017 at 3:30:33 PM UTC+2, Mark S. wrote:
> I'm not sure what is being compared here.
>
If you open "ConrolPanel: Info: Advancec: Parsing" tab, you can disable
every single parsing rule.
The "prettylink" rule is one of them
> When you say 'prettylink', do you mean the
Hi Mario,
I'm not sure what is being compared here. When you say 'prettylink', do you
mean the native prettylink ability, the ability to force a title inline or
??
I think using your macro (renamed as unilink) with the prettlink.js script,
possibly configurable (though I don't know why
On Monday, June 19, 2017 at 10:47:31 PM UTC+2, Mark S. wrote:
>
> The problem with Tobias' macro in this context, in addition to probable
> performance issues (it uses both list and regex), is that it can be broken
> if a person, for instance, clones a tiddler and forgets to update the alias
>
On Monday, June 19, 2017 at 1:35:28 AM UTC+2, Mark S. wrote:
>
> I don't think "phony " is quite the right term. It's a bit pejorative.
>
q:-) ... ok
> Maybe "prettierlinks"?
>
imo to close to the original. ... What about "*uni-link*" in the sense of
"union" or "universal" or just "one" if
Oh snap -- I knew there must be some other way to make collapsing titles
besides the view widget. But the text widget doesn't work and I forgot
about the transclude widget.
I don't think "phony " is quite the right term. It's a bit pejorative.
Maybe "prettierlinks"?
Mark
On Sunday, June
On Sunday, June 18, 2017 at 6:34:41 PM UTC+2, Mark S. wrote:
>
> subtitle might work. I see that its been used exactly 6 times so far. But
> what I liked about 'caption' was that it automatically got used in the toc
> macros. Perhaps the toc macros could be written to select the titles with
>
subtitle might work. I see that its been used exactly 6 times so far. But
what I liked about 'caption' was that it automatically got used in the toc
macros. Perhaps the toc macros could be written to select the titles with
this priority:
caption -> subtitle -> title
Mark
On Sunday, June
Thank you for all your responses. I am not at all put off at all. I have
already had to make quite a few changes for this to work. There have been a few
discussions about captions and alternative (non-unique) titles before. In
fact this is not the first time I have been down this route, but
@Stuart,
Please don't be afraid by the "techy" conversation here. You scratched in
important issue, where we don't have a generic solution yet!!
On Sunday, June 18, 2017 at 3:20:18 PM UTC+2, Mark S. wrote:
>
> But if it only needs to be short for menus ... just use it for menus and
> let
But if it only needs to be short for menus ... just use it for menus and
let it be long for other things. A photo 'caption' is often long. If the
intention was that the content be short, there should have been a
'short-title' field.
The 'title' field is really, and unfortunately, an id field.
On Saturday, June 17, 2017 at 11:00:57 PM UTC+2, Mark S. wrote:
> The files include a macro that when invoked like <> returns a
> link to "My Tiddler Caption". This macro is used by the other bit of code,
> which overwrites the core prettylinks code to use the macro whenever you
> have a
On Friday, June 16, 2017 at 5:41:26 PM UTC+2, Stuart Amor wrote:
>
> Is there a way of making an internal link, such as [[Contents]] return the
> caption field of the Contents tiddler (if it was available) rather than
> title?
>
> To give you some background, I am writing a collaborative
Just had another thought. If you used 'caption' instead of alias, I believe
that the toc menus in the sidebar would automatically use the caption
field. In the long run, I think it's best if 'caption' be the field that's
used to display the user-readable title.
Mark
On Saturday, June 17, 2017
Hi Mat,
Very clever approach! I really need to bone up on CSS. I think in the 2016
TW meet-up Jeremy said something about CSS making fools of everybody.
Certainly works that way with me ;-)
I may be mistaken, but it appears that the links are only aliased when the
corresponding tiddlers are
Stuart Amor wrote:
>
> Is there a way of making an internal link, such as [[Contents]] return the
> caption field of the Contents tiddler (if it was available) rather than
> title?
>
Yes. I made this for that purpose:
http://aliases.tiddlyspot.com/
it is however not perfected but the main
The attached is very experimental. It changes one of the core files, so if
I messed up with the code you might get a red screen of embarrassment. So
*absolutely* *make a backup* not only at the start but from time to time as
you work with it.
Just drag and drop the attached file into your TW.
20 matches
Mail list logo
