Mat,
That is a good point, I will just add the alternative is to not use double
quotes in any tiddler title, only use single quotes then "value" "filter"
is sufficient.
Without going into the details now, we can use Unicode characters that look
like quotes as well, but do not delimit like
David,
Perhaps you did not realise that your macro may be introducing the line
feed you do not want?. Do share a simple example to discuss.
- Further this issue has being there since TW5 one long term solution in
progress using custom mark-up where you decide how paragraphs and line
Very helpful explanation, Charlie, thanks!
On Sat, Jul 10, 2021, 8:18 PM Charlie Veniot wrote:
> G'day David,
>
> I'm thinking what you're running into is the nature of HTML, and not so
> much the nature of TiddlyWiki.
>
> In HTML, to have the following appear as separate lines, you might have
works like a charm thank you very much :)
On Friday, July 9, 2021 at 4:25:55 AM UTC+2 cj.v...@gmail.com wrote:
> G'day,
>
> Give this a spin:
>
> <$edit-text tiddler={{{ [addsuffix[ Data]] }}}
> field="search_value"/>
>
> <$list variable="checkLength" filter="[addsuffix[
>
If you don't want the drop-down menu to move, you can use CSS to stick the
menu anywhere on screen. As an example, the following code with put the
menu on the right side of the screen, stretched from top to bottom with a
decent fixed width. BACKUP before trying it.
.tc-edit-tags
If you want some more room for the tags menu, and for it not to move, you
can use CSS to pin the menu on-screen. The following code will pin the menu
to the top, left, and bottom of the screen to let you see more entries at
once.
.tc-edit-tags .tc-block-dropdown.tc-block-tags-dropdown {
Here's an option for a longer tags menu that doesn't move: use CSS to pin
it to the sides of the screen...
.tc-edit-tags .tc-block-dropdown.tc-block-tags-dropdown {
position: fixed;
top: 0;
left: 0;
bottom: 0;
width: 20em;
overflow: scroll;
}
On Saturday, July 10, 2021 at
G'day David,
I'm thinking what you're running into is the nature of HTML, and not so
much the nature of TiddlyWiki.
In HTML, to have the following appear as separate lines, you might have
Line of text
Line of text
Line of text
or each line of text wrapped in HTML elements that force to
Okay, but the last problem remains.
How to make *popup **tag-picker *not move after clicking on the tag, only
in the vertical direction. It doesn't have to jump to a different place
every time!
This is how it works
http://tw5magick.tiddlyspot.com/
This is very convenient when you do not need
Here is an easy way, just a simple stylesheet.
https://giffmex.org/gifts/documenting.tw.html#Tag%20editor%20dropdown
On Friday, July 9, 2021 at 4:10:15 PM UTC-5 miket...@gmail.com wrote:
> Now the usual view is very inconvenient when you have a lot of tags and
> need to scroll and scroll down
So if I type
Line of text
Line of text
Line of text
It will show in view mode as
Line of textLine of textLine of text
Unless I separate each line with a second carriage return or a
But if I type
<>
<>
<>
it renders as
Text of macrocall
Text of macrocall2
Text of macrocall3
Unless
Thanks a lot Soren!
>>> I was not able to reproduce this with the *rememberq* macro, nor do I
see anything in that macro definition that would be able to cause a similar
issue, so if you're still seeing problems with that, please provide an
example of something that doesn't work.
My
Wow! Already three brackets have been used!
Thank you.
суббота, 10 июля 2021 г. в 18:22:55 UTC+3, Eric Shulman:
> On Saturday, July 10, 2021 at 7:30:22 AM UTC-7 miket...@gmail.com wrote:
>
>> I can create a field with *color*.
>> And *caption*
>> @@color:{{!!color}}; {{!!title}} @@
>> The name
And another useful custom CSS edit. More tags on the screen line by line in
the block!
.tc-block-tags-dropdown{
white-space: normal;
min-width: 620px !important;
}
.tc-block-tags-dropdown a {
display: inline-block !important;
padding: 4px 4px 4px 4px !important;
}
To remove unnecessary tags from *tag-picker* that already exist, find two
filters *nonSystemTagsFilter* & *systemTagsFilter *in
$:/core/macros/tag-picker and add this to them at the end:
*-[all[current]tags[]]*
суббота, 10 июля 2021 г. в 01:49:47 UTC+3, TW Tones:
> Miket,
>
> Good questions
Si,
It looks like I have a $list widget that is being used to choose which
macro call variant to use, and I forgot to set the *variable *parameter to
something other than currentTiddler. I'll include a fix for this in the
next version.
In the meantime, you can apply the fix yourself by
On Saturday, July 10, 2021 at 3:51:46 PM UTC+1 saq.i...@gmail.com wrote:
> Hi Gene,
>
> No attribution needed from my end, if you feel its necessary a link to
> Github would do: https://github.com/saqimtiaz
> Cheers,
> Saq
>
> On Saturday, July 10, 2021 at 4:20:39 PM UTC+2
Hey all,
The behavior of those Relink filter operators is undefined because I didn't
wish to lock their behavior down and have to remain backward compatible for
them (for instance, I did make changes to their behavior between V1 and
V2). They are highly specific toward Relink's internal needs,
Hi Soren, I am enjoying the Grok! One possible fix: the Miscellaneous
Widgets > $radio example doesn't seem to work.
On Saturday, July 10, 2021 at 4:28:07 AM UTC-5 TiddlyTweeter wrote:
> Ciao Soren
>
> This is an updated comment. Your Grok is *very good*. I learned a lot
> from it.
>
>
Hi Soren.
I've run into a bit of trouble trying to create a custom cloze-macro using
TiddlyRemember. I have tiddlers with the fields cloze and context, and am
trying to create a global macro that will generate cloze cards based on
those fields. Here is the code:
\define cloze-text()
Thank you very much Saq! (I assume you meant to put idListRegexp in curly
braces?)
I have kind of a follow up question:
What if instead of using search terms as identifiers, I instead used
filters. So for example I might have a tiddler with
identifier:[search[my-example]] or
Hi everyone. I've been away on an impromptu leave the last week, apologies
for the late reply.
I am very grateful to everyone that provided feedback or even just taken
the time to acknowledge that they use Streams. Thank you Keelan, Zhang,
Stan, Steph and everyone else.
*@keelan* It is very
On Saturday, July 10, 2021 at 7:30:22 AM UTC-7 miket...@gmail.com wrote:
> I can create a field with *color*.
> And *caption*
> @@color:{{!!color}}; {{!!title}} @@
> The name is transmitted correctly, but the color is ignored. How to do it
> right?
> In HTML*:*
> * New Tiddler
> 121231 *
>
1)
Assuming your identifiers are alphanumeric and do not contain characters
that might need to be escaped in regular expressions, something like this
should work:
<$vars idListRegexp="[tag[Flashcard]get[identifier]join[|]]">
<$list filter="[all[tiddlers]!regexp]">
<>
On Saturday, July 10, 2021
Hi Gene,
No attribution needed from my end, if you feel its necessary a link to
Github would do: https://github.com/saqimtiaz
Cheers,
Saq
On Saturday, July 10, 2021 at 4:20:39 PM UTC+2 he...@preciouschicken.com
wrote:
> Thank you, interesting, I hadn't seen this plugin previously. I've put a
Hi Jeremy,
Using HTTPS requests was indeed my first instinct. I held back on going
that route in this exploration due to two reasons:
i) I realized that the core already had everything in place that was needed
- including UI - so this was very low hanging fruit for something only
meant to
Best explained with an example:
I have a bunch of tiddlers tagged Flashcard, each with a field identifier
containing
some text.
I want to return all the tiddlers that do not feature the values of *any*
identifier fields within their text.
Initially I tried the following:
<$list
I can create a field with *color*.
And *caption*
@@color:{{!!color}}; {{!!title}} @@
The name is transmitted correctly, but the color is ignored. How to do it
right?
In HTML
*:*
* New Tiddler
121231 *
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki"
Thank you, interesting, I hadn't seen this plugin previously. I've put a
link to this thread in the addendum; but I will enlarge the section and put
an explicit link to the plugin and include your code snippet too.
Incidentally do you have a home page / social media profile so I can
Hi Saq,
I think an easy opt-in mechanism to detect plugin updates would be worth adding
to the core.
One thing that has changed fairly recently is that GitHub Pages is now CORS
enabled, so it would be possible to just use HTTP requests, instead of the
whole iframe shenanigans. It would be
I upgraded Mentat to 5.1.23 and found that edited tiddlers are not being
able to be saved. So I changed the $:/core/ui/EditTemplate to initial
version's. Now tiddlers can be saved, but whenever i try to close a window
in mentat, it shows internal javascript error.
I know that the creator of
I've been wanting to make it easier to inform end users of my plugins (well
really just Streams) that there are updates available via an opt-in
mechanism for those that would like such a feature. I realized that for
plugins installed via a plugin library, the core actually already does the
Ciao Soren
This is an updated comment. Your Grok is *very good*. I learned a lot from
it.
Basically I think it is a go-to resource/reference for learning TW-ese.
I have one REQUEST. *Could you include an SVG of this fish icon?* which is
currently only a bitmap ...
[image: Screenshot
33 matches
Mail list logo
