Streams fighting with autolist for use of the enter key

#1

hi all,
ive been trying to work the streams plugin into my workflow as it is very convenient for making and reordering lists quickly. however i am having trouble getting it to play nice with the autolist plugin, as it seems to take over use of the enter and tab keys (even when the streams editor is set to default).

is there a way to make autolist not apply in streams, so i can continue using it to continue bulleted lists in standard tiddler text fields?

some possible solutions could be to have autolist ignore any tiddler with a parent field, or the certain type of edit-text used by streams, but i am not sure what edits would be needed to either/both plugins to make that work. i would like to preserve the streams hotkeys (enter and tab / shift-tab) if possible. currently, i have a conveniently placed toggle to enable/disable autolist, but as it is a JS plugin i have to restart my wiki every time i use it so that is not ideal.

thanks!

#2

would probably use the stream-type field instead of the parent, because it’s potentially more stream-specific :wink: will reflect some on your question and post thoughts if nobody else offers. I don’t know much about autolist, but one potential would be remapping the keys for either and avoid setting up conditional factors at all.

1 Like
#3

Hello,

I use these two plugins routinely. I have re-configured the Streams streams-save-and-continue keyboard shortcut to shift+enter and that works well for me.
It is better in my workflow anyways, because I wish to enter more than a single “bullet” in my Streams nodes.

1 Like
#4

thanks to both of you for your input. i will try and get used to enter for autolist and shift-enter for streams. i’ll still have to figure out something that works well for intent/unindent, maybe i will go with ctrl-tab / ctrl-shift-tab for a while and see if i can get used to it.

i don’t think i will need this, so my ideal solution would sacrifice this to allow me to use enter, tab etc. for both depending on whether i’m in edit or view mode in a tiddler (as streams works from view mode).

if it’s not easily hackable, consider “ignore streams / view mode” an autolist feature request for @saqimtiaz ? :slight_smile:

#5

I’ve never used autolist or taken a look at its code, but I would imagine that it has more to do with how broad its effects are. I find that most keyboard shortcuts that I trigger in edit mode of a tiddler do not work within the context of streams. You could look into limiting the context of autolist a bit more, rather than either creating an ignore feature for autolist or using a different shortcut for streams.

#6

is it possible to limit the scope of a plugin externally/globally? it is a javascript plugin (a world which i have not yet explored) that seems to act in any block mode text field currently, and i am not sure how to limit its area of influence. i could write a filter, but how can i tell the plugin to only operate within it? could i link it to an element class somehow?

thanks for your help in exploring solutions!