David,

Thanks for helping us keep up with Saq's prolific work.

Saq,

I would see adding "*tabs*" into the editors and wikification process of 
tiddlywiki a great improvement. 
Of course the handling of tabs is almost identical to this bullet solution 
just they are invisible. 
Deciding on a standard tab size in view and edit or allow customisation? 
Using https://www.w3schools.com/cssref/css3_pr_tab-size.asp css may be 
sufficient.

The question now is how do we do this given tab is used for bullets in this 
solution?

Perhaps a smart tab, if # * etc proceeds it add/remove a # *
If no character or tab then add/remove an actual tab?

Regards
Tony

On Friday, August 14, 2020 at 7:14:23 AM UTC+10, Saq Imtiaz wrote:
>
> @bimlas @JD
>
> Assuming the following selection, would you expect the line that does not 
> start with a * or # to be indented as well?
>
> # It's a fez.
> # I wear a fez now. 
> # Fezzes <http://127.0.0.1:7777/#Demo> are cool. 
> Bow ties are cool.
>
> Similarly should the following be indented on tab, or not:
>
> It's a fez.
> I wear a fez now. 
>
> My feeling is that any line selected should be indented/unindented, 
> regardless of whether it is already part of a list. But what should the 
> default list type be, * for unordered list?
>
> On Thursday, August 13, 2020 at 8:07:55 PM UTC+2, bimlas wrote:
>>
>> Honestly, this solution is more handy for me now than Streams, because I 
>> can handle list items the same way in a single tiddler as I do in Streams.
>>
>> One feature is missing from me: indenting / deindenting the selected 
>> text. If multiple rows are selected at once, I like to change their 
>> indentation at the touch of a button. Is it possible or hard to implement?
>>
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/4159627d-aea3-4d27-b1c3-8da4c64a71d1o%40googlegroups.com.

Reply via email to